Environment
Novell NetWare 6.5
Novell NetWare 6
Novell iManager 2.5
Novell NetWare 6
Novell iManager 2.5
Novell iManager 2.6
Situation
A Custom plugin is created through the Plug-in
Studio on one iManager server but is not replicated to other
iManager servers
By default, custom plug-ins are not replicated to other
iManager servers.
How to replicate custom plugins on iManager servers?
Resolution
When a custom plug-in is created by the Plug-in Studio from
within iManager 2.5 or iManager 2.6, only that server will be able
to use that custom task. A custom plugin needs to be
installed on each individual iManager server that will be used to
perform the custom task.
Follow these steps to export a custom plug-in with iManager:
Follow these steps to export a custom plug-in with iManager:
- Launch the Plug-in Studio:
- Log into iManager where the custom plug-in is installed.
- Select the Configure button
- Expand the "Role Based Services" role
- Select the "Plug-in Studio" task.
Note: A list of custom plug-ins and their RBS collection location should be displayed. - Place a check-mark next to the desired custom plug-in
- Select Actions in the menu
- Click Export
Note: A download will be triggered for the browser.
Follow these steps to import a custom plug-in on a new
iManager server:
- Launch the Plug-in Studio:
- Log into iManager where you want to install the custom plug-in.
- Select the Configure button
- Expand the "Role Based Services" role
- Select the "Plug-in Studio" task.
Note: A list of custom plug-ins and their RBS collection location should be displayed. - Select Actions, click Import.
- Assign to a Collection and Choose the exported NPM file that was exported from above.
- Select Import.
You should now be able to use the custom plugin task on the
new iManager server.
NOTE: In order to see the custom plug-in from the new iManager instance, you must be logged into the same tree and have access to the same collection where the custom plug-in resides.
NOTE: In order to see the custom plug-in from the new iManager instance, you must be logged into the same tree and have access to the same collection where the custom plug-in resides.
Additional Information
Formerly known as TID# 10094201