This section provides specific information for upgrading individual components of Identity Manager. For example, you might want to upgrade Designer to the latest version without also upgrading iManager. This section also provides steps that you might need to take after performing an upgrade.
To complete the upgrade, see the following sections:
Log on as an administrator to the server where Designer is installed.
To create a backup copy of your projects, export your projects.
For more information about exporting, see Exporting a Project
in the Designer 4.0.2 for Identity Manager 4.0.2 Administration Guide.
Launch the Designer installation program from Identity Manager media:
Linux: IDM4.0.2_Lin/products/Designer/install
To execute the binary file, enter ./install.
Windows: IDM4.0.2_Win:\products\Designer\install.exe
Select the language to install Designer in, then read and accept the license agreement.
Specify the directory where Designer is installed, then click Yes in the message stating you already have Designer installed.
Select whether the shortcuts should be placed on your desktop and in your desktop menu.
Review the summary, then click Install.
Review the Readme, then click Next.
Select to launch Designer, then click Done.
Specify a location for your Designer workspace, then click OK.
Click OK in the warning message stating that your project needs to be closed and converted.
In the Project view, expand the project, then double-click Project needs conversion.
Review the steps that the Project Converter Wizard performs, then click Next.
Specify a name for the backup of your project, then click Next.
Review the summary of what happens during the conversion, then click Convert.
Review the summary after the conversion finishes, then click Open.
After upgrading to the current version of Designer, you must import all Designer projects from the older version. When you initiate the import process, Designer runs the Project Converter Wizard, which converts the older projects to the current version. In the wizard, select Copy project into the workspace. For more information about the Project Converter, see the Designer 4.0.2 for Identity Manager 4.0.2 Administration Guide.
In general, the upgrade process for iManager uses the existing configuration values in the configiman.properties file, such as port values and authorized users. Before upgradubg, NetIQ recommends that you back up the server.xml and context.xml configuration files if you modified them.
The upgrade process includes the following activities:
NOTE:When updating or re-installing iManager, the installation program does not update existing plug-ins. To update plug-ins manually, launch iManager and navigate to Configure > Plug-in Installation > Available Novell Plug-in Modules. For more information, see Section 16.1, Understanding Installation for iManager Plug-ins.
If the setup program for iManager Server detects a previously installed version of iManager, it might give you the option to stop the installation process or remove the existing iManager, JRE, and Tomcat installations.
Before upgrading iManager, ensure that the computer meets the prerequisites and system requirements. For more information, see the following sources:
The Release Notes accompanying the update.
iManager: Section 6.5.2, Considerations for Installing iManager on a Linux Platform.
iManager Workstation: Section 6.5.4, Considerations for Installing iManager Workstation on Linux Clients.
NOTE:The upgrade process uses the the HTTP port and SSL port values that were configured in the previous version of iManager.
To upgrade iManager Server on Linux:
Log on as root or root-equivalent to the computer where you want to run the installation program.
(Conditional) If you modified the server.xml and context.xml configuration files, save a backup copy of the files in a different location before performing the upgrade.
The upgrade process replaces the configuration files.
At the Novell Downloads Web site, search for iManager products, select the iManager version that you want, then download the .tgz file to a directory on your server. For example, iMan_277_linux.tgz.
To extract the iManager folder, enter the following command:
tar -zxvf iMan_version_linux.tgz
In a shell, change to the /extracted_directory/iManager/installs/linux directory.
This path is relative to the directory where you copied or extracted the iManager files.
(Conditional) To run a command-line (text) installation, enter the following command:
./iManagerInstallLinux.bin
(Conditional) To run the wizard for the installation program, enter the following command:
./iManagerInstallLinux.bin -i gui
At the splash screen, specify a language, and then click OK.
At the Upgrade prompt, select Upgrade.
Read the Introduction, and then click Next.
Accept the License Agreement, and then click Next.
(Optional) To use IPv6 addresses with iManager, click Yes in the Enable IPv6 window.
You can enable IPv6 addresses after you upgrade iManager. For more information, see Section 17.2, Configuring iManager for IPv6 Addresses after Installation.
Click Next.
Read the Pre-Upgrade Summary page, and then click Next.
The upgrade process can take several minutes. The process might add new files for iManager components or change the iManager configuration. For more information, see the Release Notes for the upgrade.
When the upgrade process completes, click Done.
When the initialization of iManager finishes, click the first link in the Getting Started page, and then log on. For more information, see “Accessing iManager” in the NetIQ iManager 2.7.7 Administration Guide.
(Conditional) If you made backup copies of the server.xml and context.xml configuration files before starting the upgrade process, replace the new configuration files with the backup copies.
If the setup program for iManager Server detects a previously installed version of iManager, it might prompt you to upgrade the installed version. If you choose to upgrade, the program replaces the existing JRE and Tomcat versions with the latest versions. This will also upgrade the iManager to the latest version.
Before upgrading iManager, ensure that the computer meets the prerequisites and system requirements. For more information, see the following sources:
The Release Notes accompanying the update.
iManager: Section 6.5.2, Considerations for Installing iManager on a Linux Platform.
iManager Workstation: Section 6.5.4, Considerations for Installing iManager Workstation on Linux Clients.
NOTE:The upgrade process uses the the HTTP port and SSL port values that were configured in the previous version of iManager.
To install iManager Server on Windows:
Log on as a user with administrator privileges on the computer where you want to upgrade iManager.
(Conditional) If you modified the server.xml and context.xml configuration files, save a backup copy of the files in a different location before performing the upgrade.
The upgrade process replaces the configuration files.
At the Novell Downloads Web site, select the iManager version that you want, then download the win.zip file to a directory on your server. For example, iMan_277_win.zip.
Extract the win.zip file to the iManager folder.
Run iManagerInstall.exe, located by default in the extracted_directory\iManager\installs\win folder.
In the iManager welcome window, select a language, and then click OK.
In the Introduction window, and then click Next.
Accept the License Agreement, and then click Next.
(Optional) To use IPv6 addresses with iManager, click Yes in the Enable IPv6 window.
You can enable IPv6 addresses after you upgrade iManager. For more information, see Section 17.2, Configuring iManager for IPv6 Addresses after Installation.
Click Next.
At the Upgrade prompt, select Upgrade.
(Conditional) Review the Detection Summary window.
The Detection Summary window lists the latest version of Servlet container and JVM software that iManager will use once it is upgraded.
Click Next.
Read the Pre-installation summary page, and then click Install.
The upgrade process can take several minutes. The process might add new files for iManager components or change the iManager configuration. For more information, see the Release Notes for the upgrade.
(Conditional) If the Install Complete window displays the following error message, complete the following steps:
The installation of iManager version is complete, but some errors occurred during the install. Please see the installation log Log file path for details. Press "Done" to quit the installer.
Note the path to the log file that the error message displays.
In the Install Complete window, click Done.
Open the log file.
(Conditional) If you find the following error in the log file, you can ignore the error message. The installation was successful, and iManager functions properly.
Custom Action: com.novell.application.iManager.install.InstallDLLs Status: ERROR Additional Notes: ERROR - class com.novell.application.iManager.install.InstallDLLs NonfatalInstallException C:\WINDOWS\system32\msvcr71.dll (The process cannot access the file because it is being used by another process)
(Conditional) If the log file does not contain the error listed in Step 20.d, NetIQ recommends that you retry the installation.
Click Done.
When the initialization of iManager finishes, click the first link in the Getting Started page, and then log on. For more information, see “Accessing iManager” in the NetIQ iManager 2.7.7 Administration Guide.
(Conditional) If you made backup copies of the server.xml and context.xml configuration files before starting the upgrade process, replace the new configuration files with the backup copies.
A silent (non-interactive) upgrade does not display a user interface or ask the user any questions. Instead, InstallAnywhere uses information from a properties file.
To perform a standard silent install on a Linux or Windows server, use the default installation values.
At the Novell Downloads Web site, select the iManager version that you want. For example:
Linux: iMan_version_linux.tgz
Windows: iMan_version_win.zip
Download the upgrade file to a directory on your server.
(Conditional) On Windows computers, extract the win.zip file to the iManager folder.
In a console window, go to the directory containing the upgrade file that you downloaded.
On the command line, enter one of the following commands:
Linux: ./iManagerInstallplatform.bin -i silent
Windows: iManagerInstall.exe -i silent
The first time that you use iManager to log on to an eDirectory tree that already contains a Role-Based Services (RBS) collection, you might not see all of the roles information. This behavior is normal because you must update some of the plug-ins to function with the latest version of iManager. NetIQ recommends that you update your RBS modules to the latest version so that you can see and use all of the available functionality in iManager. The RBS Configuration table lists which RBS modules need to be updated.
Be aware that you might have multiple roles with the same name. Starting with iManager 2.5, some plug-in developers changed task IDs or module names but retained the same display names. This issue causes the roles to appear to be duplicated when, in fact, one instance is from one version and the other is from a newer version.
NOTE:
When updating or re-installing iManager, the installation program does not update existing plug-ins. To update plug-ins manually, launch iManager and navigate to Configure > Plug-in Installation > Available Novell Plug-in Modules. For more information, see Section 16.1, Understanding Installation for iManager Plug-ins.
Different installations of iManager might have a different number of plug-ins locally installed. As a result, you might see discrepancies in the module report for any given collection from the Role Based Services > RBS Configuration page. For the numbers to match between iManager installations, ensure that you install the same subset of plug-ins on each iManager instance in the tree.
To check for and update outdated RBS objects:
Log on to iManager.
In the Configure view, select Role Based Services > RBS Configuration.
Review the table in the 2.x Collections tabbed page for any out-of-date modules.
(Optional) To update a module, complete the following steps:
For the Collection that you want to update, select the number in the Out-Of-Date column.
iManager displays the list of outdated modules.
Select the module you that want to update.
Click Update at the top of the table.
You can migrate or replicate Plug-in Studio plug-ins to another iManager instance, as well as to a new or updated version of iManager.
Log on to iManager.
In the iManager Configure view, select Role Based Services > Plug-in Studio.
The Content frame displays the Installed Custom Plug-ins list, including the location of the RBS collection to which the plug-ins belong.
Select the plug-in that you want to re-install or migrate, then click Edit.
NOTE:You can edit only one plug-in at a time.
Click Install.
Repeat these steps for every plug-in that you need to re-install or migrate.
If you are running the Remote Loader, you need to upgrade the Remote Loader files.
Create a backup of the Remote Loader configuration files. The default location of the files is as follows:
Windows: C:\Novell\RemoteLoader\remoteloadername-config.txt
Linux: Create your own configuration file in the path of rdxml.
Verify that the drivers are stopped. For instructions, see Section 46.3.1, Stopping the Drivers.
Stop the Remote Loader service or daemon for each driver.
Windows: In the Remote Loader Console, select the Remote Loader instance, then click Stop.
Linux: rdxml -config path_to_configfile -u
Java Remote Loader: dirxml_jremote -config path_to_configfile -u
On Linux, stop the lcache process.
If the Metadirectory server and Remote Loader are on the same server, manually stop the lcache process.
If the Metadirectory server and Remote Loader are not on the same server, the lcache process is automatically stopped by the ndsd process during upgrade.
On Windows and Solaris, kill the lcache process before starting the upgrade.
Run the installation program for the Remote Loader.
The installation process updates the files and binaries to the current version. For more information, see Installing the Remote Loader
in the Identity Manager 4.0.2 Framework Installation Guide.
After the installation finishes, verify that your configuration files contain your environment’s information.
(Conditional) If there is a problem with the configuration file, copy the backup file you created in Step 1. Otherwise, continue with Step 8.
Start the Remote Loader service or daemon for each driver.
Java Remote Loader: dirxml_jremote -config path_to_config_file
Linux: rdxml -config path_to_config_file
Windows: In the Remote Loader Console, select the Remote Loader instance, then click Start.
NOTE:After upgrading the Remote Loader from 32-bit to 64-bit, the GroupWise driver and the native custom drivers do not work.
The Identity Information Warehouse includes the Identity Reporting module, Event Auditing System, and two drivers. Perform the upgrade in the following order:
Upgrade the driver package for the Data Collection Services.
Upgrade the driver package for the Managed System Gateway Service.
Upgrade the Event Auditing Service
Upgrade the Identity Reporting Module.
For more information, see the following sections:
Before upgrading EAS, review the following considerations:
To upgrade EAS from version 4.0.x on a server running SLES 11 Service Pack 1 64-bit, include the following steps
Before upgrading, login as novleas and then copy the following files from the /etc/opt/novell/sentinel_eas/config/ directory to a non-installation location:
xdas_out.map
xdas_tax.map
After upgrading, copy the files to the /etc/opt/novell/sentinel_eas/config/ directory in the new or upgraded location.
If you are upgrading EAS from Novell Audit, verify that the logevent.conf file points to EAS and uses the correct ports. This ensures that events are routed to EAS rather than to the Novell Auditing server.
To upgrade EAS, simply install the new version on top of the older version. For more information about installing EAS, see Section 32.0, Installing the Event Auditing System.
Before upgrading the Identity Reporting module, you must upgrade the User Application and the Event Auditing Service.
To upgrade Identity Reporting Module 4.0.1. to 4.0.2, simply install the new version on top of the older version. For more information about installation, see Installing the Reporting Module.
To upgrade Analyzer, NetIQ provides patch files in .zip format. Before upgrading Analyzer, ensure that the computer meets the prerequisites and system requirements. For more information, see the Release Notes accompanying the update.
Download the patch file, such as analyzer_402_patch1_20121128.zip, from the NetIQ download Web site.
Extract the .zip file to the directory that contains the Analyzer installation files, such as the plug-ins, uninstallation script, and other Analyzer files.
Restart Analyzer.
To verify that you successfully applied the new patch, complete the following steps:
Launch Analyzer.
Click Help > About Analyzer.
Check whether the program displays the new version, such as 4.0.2 Update 1 and Build ID 20121128.