Use the following checklist for a successful upgrade of the Identity Manager system.
Table 4-2 Identity Manager Component Upgrade Checklist
Identity Manager Component |
Need Upgrade (Yes/No) |
---|---|
Metadirectory Server |
Yes |
Remote Loader |
No change |
eDirectory |
No change |
Designer |
No change |
User Application |
Yes |
Role Mapping Administrator |
Not available with the Identity Manager 4.0.2 Standard Edition. You must separately install it in order to use it. |
Identity Reporting Module |
Yes |
Analyzer |
Not available with the Identity Manager 4.0.2 Standard Edition. You must separately install it in order to use it. |
iManager |
No change |
Upgrading Identity Manager 4.0.2 Standard Edition to Identity Manager 4.0.2 Advanced Edition involves configuration changes for Identity Manager components. You don't need to run the Identity Manager installer to upgrade to Identity Manager Advanced Edition from the Standard Edition. The Role Mapping Administrator is not available with the Standard Edition. You need to separately install it in order to use it. For installing the Role Mapping Administrator, refer to the Identity Manager Role Mapping Administrator 4.0.2 Installation and Configuration Guide.
Perform the following steps to upgrade Identity Manager Standard Edition to the Advanced Edition.
In iManager, make sure that you apply the Identity Manager 4.0.2 Advanced Edition activation. The Metadirectory Server upgrade does not proceed if you don't apply the Identity Manager 4.0.2 Advanced Edition activation.
Stop the JBoss server.
Linux: Run the /etc/init.d/jboss_init stop command.
Windows: Run the <RBPM Installation Location>/UserApplication/stop-jboss.bat command.
Run the <RBPM installation directory>/configupdate.sh from the Identity Manager Standard Edition installation subdirectory.
For example, on Windows, run the following command: C:\Novell\IdentityManager\rbpm\UserApplication\configupdate.bat.
By default, the installer runs in console mode. For GUI mode, replace the -use_console true Java command argument with -use_console false in the configupdate.bat file.
Edit the admin fields by changing the value of -edit_admin setting to true.
The admin fields are disabled by default.
Fill the following fields in the default view of the Roles Based Provisioning Module Configuration panel:
Press the Tab key, which displays a prompt. When you click
, additional admin fields are displayed in the Identity Vault DNs section of the Roles Based Provisioning Module Configuration page.Update all the admin fields with the appropriate users if you want the admin to be anything other than the User Application admin.
Verify if the advanced options are displayed. Click
to display the advanced options.In the Miscellaneous section, select the
check box, then click .Start the JBoss server.
Linux: Run the /etc/init.d/jboss_init start command.
Windows: Run the <RBPM Installation Location>/UserApplication/start-jboss.bat command.
This redeploys the WAR file. If you are running in a JBoss cluster, the WAR file needs to be updated in each JBoss server in the cluster.
Configure the Managed System Gateway Driver (MSGW) driver by using Designer.
Refer to the Configuring the Managed System Gateway Driver
section in the Identity Reporting Module Guide.
Update the configuration information of the Identity Manager Driver for Data Collection Service (DCS). Launch Designer, then go to
.In the Managed System Gateway Registration section, change the settings as below:
to .
Change the
. For example, .Change the User DN. For example, cn=admin,ou=sa,o=system.
Specify the password for the User DN.
For more information on configuring the driver, refer to the Configuring the Identity Manager Driver for Data Collection Service
section in the Identity Reporting Module Guide.
Save the settings, then deploy the DCS driver.
Restart the DCS driver.
Download the Identity Manager 4.0.2 Advanced Edition Report Templates from the Identity Reporting download page.
Upgrading the Identity Reporting Module might not immediately show the Advanced Version. The version change occurs after the next batch of events is processed.