| Oracle® Identity Manager Installation and Upgrade Guide for WebLogic Release 9.0 B28761-01 |
|
 Previous |
 Next |
| Oracle® Identity Manager Installation and Upgrade Guide for WebLogic Release 9.0 B28761-01 |
|
Previous |
Next |
Oracle Identity Manager has formerly been known as both Oracle Xellerate Identity Provisioning and also Thor Xellerate Identity Manager. The Oracle Identity Manager Audit and Compliance module, formerly known as Oracle Xellerate Audit and Compliance Manager, is a new, optional module that installs on top of Oracle Identity Manager and facilitates user profile auditing.
Both Oracle Identity Manager and the Oracle Identity Manager Audit and Compliance module run on the WebLogic application server version 8.1 with Service Pack 4. Upgrading from Oracle Xellerate Identity Provisioning version 8.5.2 or 8.5.3 (henceforth referred to collectively as version 8.5.x) to Oracle Identity Manager version 9.0.1, and upgrading from the Oracle Xellerate Audit and Compliance Manager 8.5.x to Oracle Identity Manager Audit and Compliance module 9.0.1 requires upgrading with the Oracle Identity Manager version 9.0.1 application.
The following is a list of the steps required in the upgrade process:
Upgrade the database you used for Oracle Xellerate Identity Provisioning 8.5.x—see "Upgrading Your Database" for more information.
Prepare for the upgrade to Oracle Identity Manager 9.0.1 by performing the pre-upgrade configuration tasks—see "Pre-Upgrade Configuration" for more information.
Migrating any version 8.5.x custom code to your new Oracle Identity Manager 9.0.1 deployment—see "Migrating Custom Code to 9.0.1" for more information.
Upgrade your legacy Oracle Xellerate Identity Provisioning 8.5.x deployment to Oracle Identity Manager 9.0.1—see "Performing the Upgrade to 9.0.1" for more information.
Perform the post-upgrade configuration tasks—see "Post-Upgrade Configuration" for more information.
Upgrade the database used by your Oracle Xellerate Identity Provisioning 8.5.x installation. You can choose among the following upgrade methods:
Perform an in-place upgrade of the existing database configured for Oracle Xellerate Identity Provisioning 8.5.x.
Create a new instance of the database, then import the data used by your Oracle Xellerate Identity Provisioning 8.5.x installation into that new database.
This approach upgrades your existing database instance by upgrading the database schema while your database remains in-place.
Extract the contents of the Oracle Identity Manager 9.0.1 upgrade package (upg_852_853_to_901.zip) to a temporary directory on the machine that you plan to install Oracle Identity Manager 9.0.1. Henceforth, this document refers to this temporary directory as <Patch>.
Backup your existing database. As appropriate to your particular database, use the export/backup utilities provided with the Oracle database or SQL Server to perform a complete backup of your production database. Production database backup includes, but is not limited to, complete export or backup of the Oracle Xellerate Identity Provisioning 8.5.x database instance to ensure that no data is lost during the upgrade process. If the upgrade fails, this backup can be used to restore the database to its original state.
Verify your database configuration. Make sure that your existing database is properly configured. As appropriate for your database, consult the following documentation:
Oracle
"Setting Up the Oracle Database"
SQL Server
If you plan to install the optional Oracle Identity Manager Audit and Compliance module, you should create a separate file group for your SQL Server or a separate tablespace for Oracle databases to facilitate the new user profile auditing feature in version 9.0.1 of the Oracle Identity Manager Audit and Compliance module. If your database is SQL Server, you must create a new file group. If your database is Oracle, the new separate tablespace is not mandatory, but it is highly recommended for performance reasons.
|
Note: Refer to "Creating a User Profile Audit File Group in SQL Server" for details on how to create a new file group in SQL Server. Refer to Oracle database documentation for details on setting up a tablespace for Oracle databases. |
Upgrade your database schema from Oracle Xellerate Identity Provisioning 8.5.x to Oracle Identity Manager 9.0.1 by using one of the following scripts appropriate for your database and operating system. Be sure to run the script on the machine where the database resides.
Oracle
|
Note: The xl_db_upg_852_853_to_901 script also upgrades the required stored procedures for Oracle. |
For Oracle on UNIX:
Enable execute permissions on the xl_db_upg_852_853_to_901.sh script:
chmod 755 xl_db_upg_852_853_to_901.sh
Run the following script on the drive where you want to upgrade your database schema:
<Patch>/Database/Oracle/Scripts/xl_db_upg_852_853_to_901.sh
Enter the appropriate information for the Oracle database when prompted by the xl_db_upg_852_853_to_901.sh script.
For Oracle on Windows:
Run the following batch script on the drive where you want to upgrade your database schema:
<Patch>\Database\Oracle\Scripts\xl_db_upg_852_853_to_901.bat
The following is the command line usage for the Oracle xl_db_upg_852_853_to_901.bat script:
xl_db_upg_852_853_to_901.bat <ORACLE_SID><ORACLE_HOME> <ORACLE_XELL_USER><ORACLE_XELL_USER_PWD> <PATCH>
SQL Server
Run the <Patch>\Database\SQLServer\Scripts\upg_852_853_to_901.bat batch file.
|
Note: Refer to "Executing the SQL Server Upgrade Script" for more information on executing these scripts on an SQL Server database. |
New stored procedures have been introduced in Oracle Identity Manager 9.0.1. Perform the following steps to create the requisite stored procedures for your database:
|
Note: If you are using an Oracle database, you can skip this step as running the xl_db_upg_852_853_to_901 script already created the required stored procedures for Oracle. |
SQL Server
Launch a plain-text editor, then open:
<Patch>\Database\SQLServer\StoredProcedures\compile_all_XL_SP.bat
For every stored procedure listed in the Sequential Lists section of compile_all_XL_SP.bat, replace the string @sysuser with the database user name. This is necessary because SQL Server requires functions invoked from a stored procedure to be qualified by the database user name (owner).
Run the script:
<Patch>\Database\SQLServer\StoredProcedures\compile_all_XL_SP.bat
|
Note: Refer to "Executing the SQL Server Upgrade Script" for more information on executing these scripts on an SQL Server database. |
To upgrade and enable the optional Oracle Identity Manager Audit and Compliance module, perform the following steps appropriate for your database:
|
Note: This step is necessary only if you are upgrading from Oracle Xellerate Identity Provisioning 8.5.x to the 9.0.1 version of the Oracle Identity Manager Auditing and Compliance module. |
Oracle
Log in to SQL *Plus with the credentials of the Oracle Xellerate Identity Provisioning 8.5.x database schema owner. run the batch file.
Run the following script:
<Patch>\Database\Oracle\Scripts\Oracle_Enable_XACM.sql
SQL Server
Run the following script:
<Patch>\Database\SQLServer\Scripts\SQLServer_Enable_XACM.bat
|
Note: Refer to "Executing the SQL Server Upgrade Script" for more information on executing these scripts on an SQL Server database. |
The user profile auditing feature and the reports feature require that certain metadata be loaded into the database. As appropriate for the operating system on the machine hosting your Oracle Identity Manager server, load Oracle Identity Manager metadata into your database by executing one of the following commands:
Windows
Run the <Patch>\Database\Utilities\LoadXML.bat batch file.
UNIX
Run the <Patch>/Database/Utilities/LoadXML.sh script.
This approach creates a new database instance, then upgrades it with the database schema for Oracle Identity Manager 9.0.1. This method ensures that your current working database remains available if a rollback is required. Use the following steps for creating a new, upgraded database instance:
Backup your existing database. As appropriate to your particular database, use the export/backup utilities provided with the Oracle database or SQL Server to perform a complete backup of your production database. Production database backup includes, but is not limited to, complete export or backup of the Oracle Xellerate Identity Provisioning 8.5.x database instance to ensure that no data is lost during the upgrade process. If the upgrade fails, this backup can be used to restore the database to its original state.
Export the existing database data using the export/backup utilities for your Oracle or SQL Server database.
Create a new database by following the steps outlined in either of the following:
|
Note: If you create a new Oracle database, make sure to specify the username and password used by your original database instance as the credentials for your new database. |
Using the import utility provided by your particular database, import the data you exported from your original database in Step 2 into your newly created database you made in Step 3. This creates an exact copy of your original database instance.
If you plan to install the optional Oracle Identity Manager Audit and Compliance module, you should create a separate file group for your SQL Server or a separate tablespace for Oracle databases to facilitate the new user profile auditing feature in version 9.0.1 of the Oracle Identity Manager Audit and Compliance module. If your database is SQL Server, you must create a new file group. If your database is Oracle, the new separate tablespace is not mandatory, but it is highly recommended for performance reasons.
|
Note: Refer to "Creating a User Profile Audit File Group in SQL Server" for details on how to create a new file group in SQL Server. Refer to Oracle database documentation for details on setting up a tablespace for Oracle databases. |
Upgrade your database schema from Oracle Xellerate Identity Provisioning 8.5.x to Oracle Identity Manager 9.0.1 by using one of the scripts appropriate for your database and operating system. Be sure to run the script on the machine where the database resides.
Oracle
|
Note: The xl_db_upg_852_853_to_901 script also upgrades the required stored procedures for Oracle. |
For Oracle on UNIX
Enable execute permissions on the xl_db_upg_852_853_to_901.sh script:
chmod 755 xl_db_upg_852_853_to_901.sh
Run the following script on the drive where you want to upgrade your database schema:
<Patch>/Database/Oracle/Scripts/xl_db_upg_852_853_to_901.sh
Enter the appropriate information for the Oracle database when prompted by the xl_db_upg_852_853_to_901.sh script.
For Oracle on Windows:
Run the following batch script on the drive where you want to upgrade your database schema:
<Patch>\Database\Oracle\Scripts\xl_db_upg_852_853_to_901.bat
The following is the command line usage for the Oracle xl_db_upg_852_853_to_901.bat script:
xl_db_upg_852_853_to_901.bat <ORACLE_SID><ORACLE_HOME> <ORACLE_XELL_USER><ORACLE_XELL_USER_PWD> <PATCH>
SQL Server
Run the <Patch>\Database\SQLServer\Scripts\upg_852_853_to_901.bat batch file.
|
Note: Refer to "Executing the SQL Server Upgrade Script" for more information on executing these scripts on an SQL Server database. |
New stored procedures have been introduced in Oracle Identity Manager 9.0.1. Perform the following steps to create the requisite stored procedures for your database:
|
Note: If you are using an Oracle database, you can skip this step as running the xl_db_upg_852_853_to_901 script already created the required stored procedures for Oracle. |
SQL Server
Launch a plain-text editor, then open:
<Patch>\Database\SQLServer\StoredProcedures\compile_all_XL_SP.bat
For every stored procedure listed in the Sequential Lists section of compile_all_XL_SP.bat, replace the string @sysuser with the database user name. This is necessary because SQL Server requires functions invoked from a stored procedure to be qualified by the database user name (owner). Be sure you replace the entire @sysuser string, including the @ character.
Run the script:
<Patch>\Database\SQLServer\StoredProcedures\compile_all_XL_SP.bat
|
Note: Refer to "Executing the SQL Server Upgrade Script" for more information on executing these scripts on an SQL Server database. |
To upgrade and enable the optional Oracle Identity Manager Audit and Compliance module, perform the following steps appropriate for your database:
|
Note: This step is necessary only if you are upgrading from Oracle Xellerate Identity Provisioning 8.5.x to the 9.0.1 version of the Oracle Identity Manager Auditing and Compliance module. |
Log in to SQL *Plus with the credentials of the Oracle Xellerate Identity Provisioning 8.5.x database schema owner.
Run the following script:
<Patch>\Database\Oracle\Scripts\Oracle_Enable_XACM.sql
Oracle
Run the following script:
<Patch>\Database\SQLServer\Scripts\SQLServer_Enable_XACM.bat
|
Note: Refer to "Executing the SQL Server Upgrade Script" for more information on executing these scripts on an SQL Server database. |
The user profile auditing and the reports feature require that certain metadata be loaded into the database. As appropriate for the operating system on the machine hosting your Oracle Identity Manager server, load Oracle Identity Manager metadata into your database by executing one of the following commands.
Windows
Run the <Patch>\Database\Utilities\LoadXML.bat batch file.
UNIX
Run the <Patch>/Database/Utilities/LoadXML.sh script.
Before you upgrade to the Oracle Identity Manager 9.0.1, you must prepare for the upgrade by performing pre-upgrade configuration tasks to the following components:
Oracle Identity Manager Server
Remote Manager
Design Console
Prepare the Oracle Identity Manager Server for upgrade to 9.0.1 by updating 8.5.x libraries, scripts, and configuration files using the following steps:
|
Note: If upgrading from a clustered WebLogic environment, perform the following steps on all cluster members, including the model node. |
Backup the following directories:
<XL_85x_HOME>\xellerate\config
<XL_85x_HOME>\xellerate\DDTemplates
<XL_85x_HOME>\xellerate\ext
<XL_85x_HOME>\xellerate\lib
<XL_85x_HOME>\xellerate\setup
<XL_85x_HOME>\xellerate\webapp
<XL_85x_HOME>\xellerate\bin
<XL_85x_HOME>\documentation
Copy the directories and files listed in the location of the From column in the following table to the location listed in the To column in the following table. Overwrite the existing files in the To location if necessary.
Table 13-1 Oracle Identity Manager Server Pre-Upgrade Files to Copy
| Copy From.... | To |
|---|---|
|
Patch\xellerate\DDTemplates |
<XL_HOME>\xellerate\DDTemplates |
|
Patch\xellerate\ext |
<XL_HOME>\xellerate\ext |
|
Patch\xellerate\lib |
<XL_HOME>\xellerate\lib |
|
Patch\xellerate\webapp |
<XL_HOME>\xellerate\webapp |
|
Patch\xellerate\bin |
<XL_HOME>\xellerate\bin |
|
Patch\xellerate\config |
<XL_HOME>\xellerate\config |
|
Patch\documentation |
<XL_HOME>\documentation |
|
Patch\xellerate\readme.htm |
<XL_HOME> |
Copy the following files from Patch\xellerate\setup to <XL_HOME>\xellerate\setup:
setup.xml
weblogic-setup.xml
patch_weblogic.cmd
patch_weblogic.sh
Remove the following libraries from the <XL_HOME>\xellerate\ext directory:
classes12.zip
csv-1.0.jar
oscache-2.0.2-22Jan04.jar
sax.jar
dom.jar
jaxp-api.jar
Upgrade the <XL_HOME>/xellerate/config/xlconfig.xml file. See "Upgrading the Server Configuration File" for more information.
Upgrade the <XL_HOME>/xellerate/config/FormMetaData.xml. See "Upgrading the Metadata File" for more information.
Edit the <XL_HOME>/xellerate/setup/patch_weblogic script. For Windows, the script is named patch_weblogic.cmd. For UNIX, the script is named patch_weblogic.sh. Replace the following in the patch_weblogic script:
replace @bea_home with the path to the WebLogic installation directory
replace @loc with the path to the Oracle Identity Manager server installation directory
Edit the <XL_HOME>\xellerate\Profiles\weblogic.profile file as follows:
Locate the Reporting data source property and modify it to be the following:
# Reporting data sourcedatasource.report=jdbc/xlXADS
Set the following parameter values:
weblogic.max-beans-in-free-pool = 100
weblogic.transaction.timeout = 1200
Use a text editor to edit the PurgeCache script in the <XL_HOME>\xellerate\bin\ directory. For Windows, edit the PurgeCache.bat file. For UNIX, edit the PurgeCache.sh file.
Replace oscache-2.0.2-22Jan04.jar with oscache.jar in the definition of the CLASSPATH environment variable.
As of version 9.0.1, and for all future releases, the log.properties file replaces the log.conf file as the Oracle Identity Manager server configuration log file. Complete the following steps to migrate all the version 8.5.x logging settings:
Copy any version 8.5.x custom logging-related settings that exist in the log.conf file, which resides in the backup directory <XL_85x_HOME>/xellerate/config/, to the log.properties file, which resides in the directory <XL_HOME>/xellerate/config/.
|
Note: Copy only the custom logging-related settings in the log.conf file, not the syntax of the 8.5.x log.conf file. |
You must convert the formatting of the log-level settings in log.conf to new formatting in the log.properties file. For example, a logging-related entry in log.conf might look similar to the following:
Logger.module.ADAPTERS=WARN
The corresponding entry in log.properties might look like the following:
# log4j.logger.XELLERATE.ADAPTERS=WARN
You need to uncomment the line, then set the parameter to the value already set in the log.conf entry, so that the log.properties entry looks something like the following:
log4j.logger.XELLERATE.ADAPTERS=WARN
Repeat this for all logging-related entries, then save and close the file.
Copy the ojdbc14.jar file from Patch\xellerate\ext to <WEBLOGIC_HOME>\weblogic81\server\lib\. For clustered environments, copy the ojdbc14.jar file to <WEBLOGIC_HOME>\weblogic81\server\lib\ on each of the XLMANAGED_SERVER_HOST nodes in the cluster.
Prepare the Oracle Identity Manager Design Console for upgrade to 9.0.1 by updating 8.5.x libraries, scripts, and configuration files using the following steps:
Backup the following files and directories:
<XL_85x_DC_HOME>\xlclient\XLDesktopClient.ear
<XL_85x_DC_HOME>\xlclient\CustomClient.zip
<XL_85x_DC_HOME>\xlclient\lib
<XL_85x_DC_HOME>\xlclient\ext
<XL_85x_DC_HOME>\documentation
Copy the following files from Patch\xlclient\ to the <XL_DC_HOME>\xlclient directory, overwriting existing files if necessary:
Patch\xlclient\fvc.properties
Patch\xlclient\fvcutil.cmd
Patch\xlclient\XLDesktopClient.ear
Patch\xlclient\CustomClient.zip
Patch\xlclient\xlFvcUtil.ear
Open the <XL_DC_HOME>\xlclient\fvcutil.cmd file. Set the following environment variable values:
Set @java_loc to the path of the java directory
Set @auth_config to the path of the authwl.conf file
Copy the contents of the Patch\documentation directory to <XL_DC_HOME>\documentation, overwriting files if necessary.
Copy Patch\xellerate\readme.htm to <XL_DC_HOME>\xlclient\, overwriting the existing file if necessary.
Copy the contents of the Patch\xlclient\lib directory to <XL_DC_HOME>\xlclient\lib, overwriting files if necessary.
Copy the contents of the Patch\xlclient\ext directory to <XL_DC_HOME>\xlclient\ext, overwriting files if necessary.
Remove the following from the <XL_DC_HOME>\xlclient\ext\ directory:
classes12.zip
csv-1.0.jar
oscache-2.0.2-22Jan04.jar
Prepare the Oracle Identity Manager Remote Manager for upgrade to 9.0.1 by updating 8.5.x libraries, scripts, and configuration files using the following steps:
Backup the content of the following directories:
<XL_85x_RM_HOME>\xlremote\lib
<XL_85x_RM_HOME>\xlremote\config
Copy the contents of the Patch\xlremote\lib directory to the <XL_RM_HOME>\xlremote\lib directory, overwriting files if necessary.
As of version 9.0.1, and for all future releases, the log.properties file replaces the log.conf file as the Remote Manager configuration log file. Complete the following steps to migrate all the Remote Manager logging settings:
Copy the <XL_HOME>/xellerate/config/log.properties file from the version 9.0.1 server installation directory to the version 9.0.1 Remote Manager <XL_RM_HOME>/xlremote/config/ installation directory.
Copy any version 8.5.x custom logging-related settings that may exist in the file log.conf, which resides in the directory <XL_85x_RM_HOME>/xlremote/config/, to the file log.properties, which resides in the directory <XL_RM_HOME>/xlremote/config/.
|
Note: Copy only the custom logging-related settings in the log.conf file, not the syntax of the 8.5.x log.conf file. |
You must convert the formatting of the log-level settings in log.conf to new formatting in the log.properties file. For example, a logging-related entry in log.conf might look similar to the following:
Logger.module.RemoteManager=WARN
The corresponding entry in log.properties might look like the following:
# log4j.logger.XELLERATE.RemoteManager=DEBUG
You need to uncomment the line, then set the parameter to the value already set in the log.conf entry, so that the log.properties entry looks something like the following:
log4j.logger.XELLERATE.RemoteManager=WARN
Repeat this for all logging-related entries, then save and close the file.
Upgrade the <XL_RM_HOME>/xlremote/config/xlconfig.xml file. See "Upgrading the Remote Manager Configuration File" for more information.
In a version 9.0.1 environment, you can recycle custom code (including custom clients, scheduled tasks, event handlers and libraries bound to adapters) originally used in your version 8.5.x environment.
|
Note: Before migrating custom code from the 8.5.x environment, you must first rebuild it using the Oracle Identity Manager 9.0.1 libraries. |
Custom code written for Oracle Xellerate Identity Provisioning 8.5.x needs to be rebuilt using the Oracle Identity Manager 9.0.1 libraries, which are located in <XL_HOME>/xellerate/lib.
Using the integrated development environment (that is, Eclipse, JDeveloper, WASD or command line javac) that originally compiled the version 8.5.x custom code, recompile all custom java code using Oracle Identity Manager 9.0.1 libraries instead of Oracle Xellerate Identity Provisioning 8.5.x libraries.
Custom java libraries bound to functional Oracle Xellerate Identity Provisioning 8.5.x adapters can be reused in a Oracle Identity Manager 9.0.1 environment after they have been recompiled using Oracle Identity Manager 9.0.1 libraries.
The recompiled custom java libraries that were originally in the directory <XL_85x_HOME>/xellerate/JavaTasks must be copied to the directory <XL_HOME>/xellerate/JavaTasks.
The recompiled custom java libraries that were originally in the directory <XL_85x_RM_HOME>/xlremote/JavaTasks must be copied to the directory <XL_RM_HOME>/xlremote/JavaTasks.
|
Note: In a clustered environment you must repeat this step on all cluster members. |
|
Note: You do not need to recompile the adapters themselves. |
Custom scheduled tasks that were functional in Oracle Xellerate Identity Provisioning 8.5.x can be reused in your Oracle Identity Manager 9.0.1 environment after you have recompiled them using Oracle Identity Manager 9.0.1 libraries.
The recompiled custom scheduled tasks in <XL_85x_HOME>/xellerate/ScheduleTask need to be copied to <XL_HOME>/xellerate/ScheduleTask.
|
Note: In a clustered environment you must repeat this step on all cluster members. |
You must reapply within the 9.0.1 environment any customizations (for instance, JSP customizations) made to the web application shipped with Oracle Xellerate Identity Provisioning 8.5.x.
Migrate any customizations previously applied to your version 8.5.x web application to the out-of-box version 9.0.1 web application xlWebApp.war, which resides in the directory <XL_HOME>/xellerate/webapp.
Any custom clients that were built using Oracle Xellerate Identity Provisioning 8.5.x APIs must be updated and recompiled to make them compatible with the Oracle Identity Manager 9.0.1 APIs. For example, certain APIs might have been deprecated or replaced by new APIs. Refer to the Oracle Identity Manager Release Notes for a comprehensive list of API calls that have changed between Oracle Xellerate Identity Provisioning 8.5.x and Oracle Identity Manager 9.0.1.
Upgrading from an existing Oracle Xellerate Identity Provisioning 8.5.x deployment to Oracle Identity Manager 9.0.1 involves assembling a new enterprise application archive (EAR) file from the latest libraries, then redeploying the EAR. Perform the following steps after completing all the pre-upgrade tasks to upgrade an existing Oracle Xellerate Identity Provisioning 8.5.x deployment to Oracle Identity Manager 9.0.1 in a WebLogic environment:
Make sure the WebLogic application server is running. If it is not running, start it.
Run the patch_weblogic script:
Windows
Run <XL_HOME>\xellerate\setup\patch_weblogic.cmd
UNIX
Run <XL_HOME>/xellerate/setup/patch_weblogic.sh
The following post-upgrade configurations are required to complete the upgrade.
The following post-upgrade configuration procedures might be necessary if you have installed the Oracle Identity Manager Audit and Compliance module (previously named Oracle Xellerate Auditing and Compliance Manager in 8.5.x). The following is an overview of the process:
Set the user profile audit level
Generate user snapshots
Execute the Generate Snapshot script
Define a secondary data source for reporting, if necessary. Refer to the Oracle Identity Manager Audit Report Developer's Guide for more information on defining a secondary data source.
Start the application server hosting your Oracle Identity Manager server.
Set the audit level. The permissible values, in descending order are:
Process Task
Resource Form
Resource
Membership
Core
None
Specify an audit level by completing the following sub-steps:
Log into the Design Console as an administrator
Navigate to the System Configuration page
Locate XL.UserProfileAuditDataCollection and set its value to Resource Form or the appropriate audit level
To collect user profile audit data in the secondary reporting data store, complete the following sub-steps:
Log into the Design Console as an administrator
Navigate to the System Configuration page
Locate XL.UserProfileAuditInSecondaryDS and set its value to TRUE.
If you installed the Oracle Identity Manager Audit and Compliance module (previously named Oracle Xellerate Auditing and Compliance Manager in 8.5.x), you must generate new snapshots for all existing users in the system when either of the following two situations occur:
You upgrade from version 8.5.x to version 9.0.1 with the Oracle Xellerate Auditing and Compliance Manager module
You elevate the audit level for Audit and Compliance module
To generate new snapshots, complete the following steps:
Launch a plain-text editor and open the file GenerateSnapshot script located in the <XL_HOME>/xellerate/bin/ directory. If you are running on Windows, open GenerateSnapshot.bat. If you are running on UNIX, open GenerateSnapshot.sh.
Edit the following variables in the GenerateSnapshot script:
Modify the set XEL_HOME= variable to point to the directory where you installed Oracle Identity Manager.
Modify the set APP_SERVER=@appserver variable to be:
set APP_SERVER=weblogic
Modify the set APP_SERVER_HOME=@app_server_home variable to point to the directory where you installed WebLogic.
Modify the set JAVA_HOME=@jdk_loc variable to point to the directory containing the JDK.
If you are running on Windows and using SQL Server as your database, set the SQL_SERVER_DRIVER_DIR variable in GenerateSnapshot.bat to point to the directory containing the SQL Server JDBC drivers and remove the comment for the line. For example, change:
REM set SQL_SERVER_DRIVER_DIR=C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib
to the following:
set SQL_SERVER_DRIVER_DIR=<Set appropriate value here>
Execute one of the following GenerateSnapshot scripts as appropriate for the operating system on the machine hosting the Design Console:
Windows
Run the batch file GenerateSnapshot.bat, which resides in the directory <XL_HOME>/xellerate/bin/.
UNIX
Run the batch file GenerateSnapshot.sh, which resides in the directory <XL_HOME>/xellerate/bin/.
To upgrade your existing 8.5.x Diagnostic Dashboard to version 9.0.1, you must install a new instance of the Diagnostic Dashboard. Use the following steps to upgrade to the 9.0.1 Diagnostic Dashboard:
Remove the existing XIMDD application
Install a new instance of the XIMDD application using the new, version 9.0.1 XIMDD.war file in the Patch\DiagnosticDashboard directory
See "Using the Diagnostic Dashboard" for more information.
