Migrating Custom Plug-ins created in iManager 2.0.2 to a new iManager 2.5 server

(Last modified: 12Jul2005)

This document (10098253) is provided subject to the disclaimer at the end of this document.

goal

Transfer or move Custom Plug-ins created with Plug-in Studio in iManager 2.0.2 to a new iManager 2.5 server

fact

Novell eDirectory 8.7.3 for All Platforms

Novell iManager 2.0.2

Novell iManager 2.5

fix

Prerequistes:

iManager 2.5 requires eDirectory 8.7.3, and if on a NetWare Server, must be at least NetWare 6.5 Sp2, but Sp3 is highly recommended

Procedure:

1) Install iManager 2.5 on target server. This server must either already be installed in the same eDirectory tree as the iManager 2.0.2 server you wish to transfer the custom plug-ins from, or be a Mobile iManager installation.

2) For the first time login to the new iManager 2.5 server, you MUST log in as one of the objects listed as Collection Owner of the RBS Collection in the original iManager 2.0.2 server. This will bring a reference to the existing collection to the new iManager 2.5 server. The owners are listed at Configure|Collection Configuration|Modify Collection Owners. If needed, have the user object to do the installation of iManager 2.5 added to the owners list of the 2.0.2 collection prior to the first login.

3) From the Configure page, go to Role Based Services, select the RBS Configuration task. It will bring up the RBS Collection name on the 2.x Collections tab. At the top of the screen will likely be a message stating: "Notice: The RBS schema definitions have not been installed or they are out of date. Extend schema now". Click the Extend Schema link to go ahead and extend the schema for iManager 2.5 now. This will only take a moment and after you click OK on the completion screen, it will return you to the main RBS Collections screen, and the message about extending schema will be gone.

4) There will be 4 columns of numbers listed. If there is a value greater than zero in the third column (Out-of-Date), then you should upgrade those modules.

a. Click the number (a hyperlink) in that column.

b. This will bring up a list of modules that need upgrading. Click the box at the top next to the TYPE column header to select all the modules, then click the "Update" function. It will then upgrade all the plug-ins for 2.5 to operate properly. If you still want to use the 2.0.2 iManager on the original server, it should still function fine too.

c. Repeat for the "Not Installed" modules in the fourth column if you want them also.

Now we are ready to transfer the custom plug-ins:

5) From the Configure page, expand Role Based Services, and select the Plug-in Studio task.

6) All your custom plug-ins should appear in the list of available plug-ins. They are not actually installed on the server yet, this list was just populated from the Collection object.

7) For each plug-in that you want installed and available:

a. Click the check box next to the Plug-in ID name, and select the Edit function. This will bring up the plug-in studio editor for your plug-in.

b. If you want to, you can make changes to your plug-in, but all you need to do is then select the Install function at the top of the screen, and the plug-in will be installed. If you had a custom role, it will be created also, and then will appear in your available roles list from the "Roles and Tasks" page.

8) You should be ready to go. If you want additional users to access the role(s), you may need to assign them the rights to it like you did for the iManager 2.0.2 server

note

If you want to copy a custom plug-in to a completely different tree, you can do the following steps:

1. First use the steps above with Mobile iManager to transfer the plugin to a temporary location that is running iManager 2.5.

2. After installing the plug-in, export it to a file using the export function from the action menu in Plug-in Studio. Copy the exported npm file to a location accessible by the new iManager 2.5 where you want to import the custom plugin.

3. Go to the new server and launch iManager 2.5. If any of the custom Tasks you have are stored in custom Roles, then the Roles must be manually created first. To create the role:

a. Go to the RBS Configuration page, and click on the collection name. The first screen that comes up is the Roles tab. Click "New", and select iManager role. This launches the Role Creation Wizard.

b. Fill in the Role name in the first page. Be sure and use exactly the same name as the custom role from the original version.

c. Just click Next on the following two screens.

d. On the fourth screen, you need to fill in the name and scope of where you want this role to be available. This should be similar to how you defined it in the original tree. Be sure and click the add button and decide if you want to keep the default rights assigned there, then click Next again.

e. This is the summary screen. Just click Finish, and your custom role is created.

4. Go to the Plug-In Studio, and click Import under the actions heading. Fill in your collection, and browse to the file you exported in Step 2 above. Click the Import button. This will copy the plug-in to your system, but it is not yet installed.

5. Your custom plug-in should now show up in the list of custom plug-ins. Check the box next to your custom plugin, and click Edit.

6. You can make changes now if you desire, but all you need to do is click Install. This will install the custom plugin into your collection, in the custom role, if you created one, and it is ready and available to be used.

document

Document Title:	Migrating Custom Plug-ins created in iManager 2.0.2 to a new iManager 2.5 server
Document ID:	10098253
Solution ID:	NOVL102701
Creation Date:	11Jul2005
Modified Date:	12Jul2005
Novell Product Class:	Novell Directory Services

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.