This section explains how to uninstall iManager on the following platforms:
WARNING:Before uninstalling iManager, make sure to back up any custom content or other special iManager files that you would like to preserve. Custom content is usually stored in the webapps\nps\packages directory and is called custom.npm.
There is no specific sequence in which iManager or the associated third-party components must be uninstalled.
There are, of course, ramifications to uninstalling any of these components. For example, if you uninstall either the Web server or the servlet container, you will not be able to run iManager. Also, on all platforms except NetWare, the uninstall removes only files that it installed in the first place. If there are files that were created by the application (for example, the log files and auto-generated configuration files that are created while Tomcat runs), these will not be deleted by the uninstall because it did not install them.
Likewise, if you have created new files or modified existing files within the directory structure that was originally laid down during the install, these files are not removed by the uninstall. This is a safeguard so that data is not unintentionally deleted when a product is uninstalled.
Uninstalling iManager does not affect any of the RBS configurations that you have set in your tree.
Root access is required for uninstalling.
Open a shell and execute the following command:
/opt/hpws/tomcat/webapps/nps/UninstallerData/UninstalliManager
Root access is required for uninstalling.
Open a shell and go to the iManager_linux directory created when you extracted the installation files from the iMan_25_linux.tgz file.
Execute the installation script:
./uninstall.sh
When the script pauses to display the products to uninstall, enter a to uninstall all.
NOTE:The uninstall procedure does not remove configuration, log files, and custom content.
In the NetWare GUI, click > .
From the installed products list, select and then click .
Root access is required for uninstalling.
Open a shell and execute the following command:
/var/opt/novell/tomcat4/nps/UninstallerData/UninstalliManager
Click .
iManager can be uninstalled from Windows using the applet in the Control Panel. If the iManager installation installed Apache, Tomcat, or NICI, they are listed separately in . If you are no longer using them, you can uninstall each program separately, in any order, using the applet.
IMPORTANT:If eDirectory is installed on the same server as iManager, NICI might be required to continue to run eDirectory.
When you remove iManager 2.5, only a portion of the files in the file system are removed. You are asked if you want to remove all iManager files. If you select , all iManager files are removed, including all custom content. However, the 2.5 RBS objects are not removed from the eDirectory tree, and the schema remains in the same state.
To uninstall Mobile iManager, delete the directory where you extracted the files. NMAS and NICI files remain on the server.
Do not use the iManager 2.5 uninstall script to uninstall iManager 2.5 if it was installed with Open Enterprise Server (OES). Rather, use existing OES mechanisms to uninstall the iManager component for the relevant OES platform.
NetWare: Use the OES product removal process to uninstall iManager.
Linux: Use YAST to uninstall iManager. When uninstalling iManager with YaST, you will receive a dependency conflict that states that the package is required by the following:
Unless you really want to remove these products, ignore these dependencies and continue.
Subsequently, you will receive a second dependency conflict that states that is required by some or all of the following:
These are iManager plug-ins and should be removed with iManager. Choose to remove these packages when uninstalling iManager from OES Linux.