7.5 Installing Plug-ins to an Existing iManager

You can install an NPM into an existing iManager environment. However, the NPM you plan on installing must be compatible with the version of iManager currently installed. You can determine the currently installed version of iManager by calling eMFrameUtils.getVersion(TaskContext context).

Alternatively, you can retrieve the current version of iManager from version.properties, as shown in the following example:

 public static Version getVersion(TaskContext context)
 
 {   String versionStr =      eMFrameUtils.getLocalizedString("com.novell.emframe.version", "version", context);   return new Version(versionStr);}

You can install plug-in programmatically or manually. If you install plug-in manually, the process varies depending on whether or not you have RBS configured. For more information about RBS, see Role-Based Services.

To install a plug-in programmatically, see Installing a Plug-In Programmatically. To install a plug-in manually, see Installing a Plug-In Manually.

7.5.1 Installing a Plug-In Programmatically

  1. To programmatically install a plug-in into iManager, use one of the following calls:

    • ModuleManager.externalInstall(File sWebAppContextPath, File npmFile, File fJspPath)

    • ModuleManager.externalInstall(File sWebAppContextPath, File npmFile, File fJspPath, boolean silentInstall)

    • ModuleManager.externalInstall(File sWebAppContextPath, File npmFile, File fJspPath, String LOGIN_DN, String HOST, String PASSWORD)

    • ModuleManager.externalInstall(File sWebAppContextPath,File npmFile,File fJspPath,boolean silentInstall,String LOGIN_DN,String HOST,String PASSWORD)

  2. Make sure that all the plug-ins are in the local directory because the command line installation checks only the local directory for plug-ins. This completely resolves the dependencies.

    Dependencies are identified through Depends-on element of the MANIFEST file from the npm.

    If there are any unavailable dependent plug-ins, you are prompted.

  3. After getting the set of dependent plug-ins, you are prompted to continue the installation of main plug-in by installing all dependent plug-ins, install only the main plug-in, or terminate the installation process. Select the desired option.

NOTE:To programmatically uninstall a plug-in from iManager, use the following call:

ModuleManager.externalUninstall(File sWebAppContextPath, String npmFileName)

7.5.2 Installing a Plug-In Manually

  1. Log in to iManager.

  2. Click Configure > Plug-in Installation > > Available Novell Plug-in Modules.

    The Available Novell Plug-in Modules page is displayed.

  3. Under Novell Plug-in Modules, click Add, browse for the appropriate NPM file, then click OK.

  4. In the Available Novell Plug-in Modules page, select the NPM and click Install.

  5. Restart Tomcat.

    Platform

    Restart Command

    NetWare® 6.5 or later

    Enter tomcat5 stop. Wait at least one minute, then enter tomcat5 start to start the service again.

    Windows*

    Stop and start the Tomcat service.

    Linux

    Enter /etc/init.d/novell-tomcat5 restart.

    Tomcat takes some time to fully initialize. Wait a couple minutes before trying to log in to iManager.

  6. (Conditional) If RBS is configured, do the following:

    1. Log in to iManager, then click the Configure button.

    2. Select Role-Based Services > RBS Configuration.

    3. To update an RBS module, select the number in the Out-of-Date column for the Collection you want to update.

      The list of outdated plug-ins is displayed.

    4. Select the plug-in you want to update and then click Update at the top of the table.

    5. Repeat steps 8c and 8d for the Not-Installed column of the RBS Configuration page.

  7. Verify that the new Role appears in the Roles and Tasks page.

    To add members to the new Role, select Role Based Services > Edit Member Association in the navigation frame.