Deploying the Upgrade in a Test Environment

Deploying an upgrade in a test environment includes the following tasks:

• Upgrading the database

• Upgrading the environment

• Restoring customizations after the upgrade

To Upgrade the Oracle Identity Analytics Schema on the Database Server on a Windows Platform

Before You Begin - You should have created a backup of the Oracle Identity Analytics database.

Go to the section that contains instructions for your database server.

Microsoft SQL Server

If SQL Server is installed locally, you can upgrade the Oracle Identity Analytics schema using either the command prompt or the SQL Server Query Analyzer tool or the Management Studio tool. If SQL Server is not installed locally, use the SQL Server Query Analyzer tool or the Management Studio tool to upgrade the schema.

• To upgrade the schema from a command prompt, follow these steps:

  1. Navigate to the directory containing the upgrade scripts (C:\RM_Upgrade\db) by typing:

     C:\> cd C:\RM_Upgrade\db

  2. Run the following command(s) to execute the upgrade script(s):

     C:\> sqlcmd -S localhost -i rbacx-previous_version_To_current_version_mssql.sql -U rbacxservice -P rbacxservice -d rbacx

• To create the schema using Query Analyzer or Management Studio, follow these steps:

  1. Log in to the database server as rbacxservice.

  2. Click the Open Query File menu and locate the rbacx-previous_version_To_current_version_mssql.sql file.

  3. Execute the SQL file.

     This will upgrade the rbacx database on the server.

Oracle

You can upgrade the Oracle Identity Analytics schema using either the command prompt or the Oracle iSQL Plus Web Console (available in Oracle 10g Database Server). If the Oracle Database Server is not installed locally, use the iSQL Plus Web Console to upgrade the schema.

• To upgrade the schema from a command prompt, follow these steps:

  1. Navigate to the directory containing the upgrade scripts (C:\RM_Upgrade\db) by typing:

     C:\> cd C:\RM_Upgrade\db

  2. Run the following command(s) to execute the upgrade script(s):

     C:\> sqlplus rbacxservice/rbacxservice @rbacx-previous_version_To_current_version_oracle.sql

• To create the schema using the iSQL Plus Web Console, follow these steps:

  1. Open the following URL in a web browser.

     The default port for the iSQL Plus Web Console is 5560.

     http://hostname:5560/isqlplus

  2. Select Load Script and browse to C:\RM_Upgrade\db.

  3. Locate the file rbacx-previous_version_To_current_version_oracle.sql and click Load.

     The Oracle Identity Analytics upgrade schema creation script is loaded into the workspace window.

  4. Click Execute.

     The script is executed and the Oracle Identity Analytics schema is upgraded on the system.

DB2

The following steps assume that the DB2 database server is installed locally. One of the following authorizations is required to upgrade the database:

sysadm

sysctrl

To upgrade the schema from a command prompt, follow these steps:

1. Navigate to the directory containing the upgrade scripts (C:\RM_Upgrade\db) by typing:

   C:\> cd C:\RM_Upgrade\db

2. Run the following command(s) to execute the upgrade script(s):

   C:\> db2cmd

   db2 connect to rbacx user rbacxservice using rbacxservice

   db2 -tvf rbacx-previous_version_To_current_version_db2.sql

MySQL

The following assumes that the MySQL database server is installed locally.

To upgrade the schema from a command prompt, run the following command(s) to execute the upgrade script(s):

C:\> mysql --user=rbacxservice --password=rbacxservice < rbacx-previous_version_to_current_version_mysql.sql rbacx

To Upgrade the Oracle Identity Analytics Schema on the Database Server on a UNIX Platform

Before You Begin - You should have created a backup of the Oracle Identity Analytics database.

Oracle

You can upgrade the Oracle Identity Analytics schema using either the command prompt or the Oracle iSQL Plus Web Console (available in Oracle 10g Database Server). If the Oracle Database Server is not installed locally under the /opt directory, use the iSQL Plus Web Console to upgrade the schema.

• To upgrade the schema from a command prompt, follow these steps:

  1. Navigate to directory containing the upgrade scripts (/opt/RM_Upgrade/db) by typing:

     $ su - oracle

     $ export ORACLE_HOME=/opt/oracle/product/10.2.0

     $ cd /opt/RM_Upgrade/db

  2. Run the following command(s) to execute the upgrade script(s):

     $ ./sqlplus rbacxservice/rbacxservice @rbacx-previous_version_To_current_version_oracle.sql

     The Oracle Identity Analytics database schema is upgraded on Oracle Database server.

• To create the schema using the iSQL Plus Web Console, follow these steps:

  1. Open the following URL in a web browser.

     The default port for the iSQL Plus Web Console is 5560.

     http://hostname:5560/isqlplus

  2. Select Load Script and browse to /opt/RM_Upgrade/db.

  3. Locate the file rbacx-previous_version_To_current_version_oracle.sql and click Load.

     The Oracle Identity Analytics schema upgrade script is loaded into the workspace window.

  4. Click Execute.

     The script is executed and the Oracle Identity Analytics schema is upgraded on the system.

DB2

The following steps assume that the DB2 database server is installed locally. One of the following authorizations is required to upgrade the database:

sysadm

sysctrl

To upgrade the schema using a terminal session, follow these steps:

1. Navigate to the directory containing the upgrade scripts (/opt/RM_Upgrade/db) by typing:

   # cd /opt/RM_Upgrade/db

2. Run the following command(s) to execute the upgrade script(s):

   db2 connect to rbacx user rbacxservice using rbacxservice

   db2 -tvf rbacx-previous_version_To_current_version_db2.sql

MySQL

The following assumes that the MySQL database server is installed locally.

To upgrade the schema from a command prompt, run the following command(s) to execute the upgrade script(s):

$ mysql -user=rbacxservice -password=rbacxservice< rbacx-previous_version_To_current_version_mysql.sql rbacx

To Upgrade the Environment on a Windows Platform for a Standalone Deployment

Use the following steps to upgrade Oracle Identity Analytics manually on a supported Windows platform.

1. Stop the application server.

2. Update the Oracle Identity Analytics database.

3. Type the following commands in the test environment:

   set INSPATH=Path to the upgrade software  (For example, set INSPATH=C:\RM_Upgrade)

   set RBACXWAR=Path to the Oracle Identity Analytics deployment directory  (For example, set RBACXWAR=Tomcat install directory\webapps)

   set RM_LIB=Path to the downloaded third-party library files  (For example, set RM_LIB=C:\RM_Lib)

   set TEMP=Path to the temporary directory

4. Run the pre-process commands:

   mkdir %TEMP%

   cd %TEMP%

   jar -xvf %INSPATH%\rbacx.war

5. Copy the downloaded third-party library files to the Oracle Identity Analytics library directory.

   copy %RM_LIB%

   * %TEMP%\WEB-INF\lib

6. Remove report-related files from the Oracle Identity Analytics Installation Directory\reports directory

   rmdir /s /q %RBACX_HOME%\reports

7. Copy the target Oracle Identity Analytics version-specific reports based on the database server to the Oracle Identity Analytics Installation Directory\reports folder.

   The following sample steps assume that the target database server is MySQL.

   xcopy %INSPATH%\reports %RBACX_HOME%\reports /I/E

   xcopy %RBACX_HOME%\reports\mysql

   * %RBACX_HOME%\reports

8. Remove search-related files from the Oracle Identity Analytics Installation Directory\.indexes directory

   rmdir /s /q %RBACX_HOME%\.indexes

9. Copy the files related to advanced search from the upgrade folder to the Oracle Identity Analytics Installation Directory\.indexes folder.

   xcopy %INSPATH%\.indexes %RBACX_HOME%\.indexes /I/E

10. Make changes to the following files located under %INSPATH%\conf directory to reflect customizations as documented in Documenting Custom Components.

    • iam.properties - In a text editor, replace any occurrences of $RBACX_HOME with the Oracle Identity Analytics installation directory path.

    • jdbc.properties - In a text editor, edit the following lines, substituting $SERVER_NAME and $PORT_NUMBER with the host name and connectivity port of the target database. Refer to UNIX: To Create the Oracle Identity Analytics Schema on the Database Server for instructions.

    • ldap.properties - Refer to Authenticating With LDAP for instructions on LDAP customizations.

    • rm_idm_init.xml - This file is required by Oracle Identity Analytics to exchange and manage information with Identity Manager.

11. Remove the configuration related directory from Oracle Identity Analytics Installation Directory directory

    rmdir /s /q %RBACX_HOME%\conf

12. Copy configuration directory and files from the upgrade directory to the Oracle Identity Analytics Installation Directory directory.

    xcopy %INSPATH%\conf %RBACX_HOME%\conf /I/E

13. Apply any customizations necessary for the environment to the extracted .war file in the %TEMP% directory.

14. Make the following changes if there are multiple instances of Oracle Identity Analytics, standalone or clustered, on the same subnet.

    1. Navigate to %TEMP%\WEB-INF directory.

    2. In a text editor, open application-context.xml, find bean id commManager, and examine the constructor-arg value.

    3. Set the constructor-arg value with a unique instance name, for example value="SRM-Instance-1".

    4. In a text editor, open search-context.xml, find bean id searchConfiguration, and examine the constructor-arg value.

       • The deployment is a standalone, constructor-arg defaults to a value of 0, which is specified as value="0".

    5. Navigate to %TEMP%\WEB-INF\classes directory and do the following:

       1. In a text editor, open oscache.properties (located in the %TEMP%\WEB-INF\classes), and find the cache.cluster.multicast.ip property.

       2. Uncomment cache.cluster.multicast.ip by removing # at the start of the line. Each Oracle Identity Analytics instance requires a unique cache.cluster.multicast.ip value.

15. To migrate Role Provisioning and Identity Audit rules, open scheduling-context.xml using a text editor and find bean id quartzSchedulerFactoryBean.

    1. Examine the jobDetails list. Uncomment rmeRuleMigrationJob and identityAuditDataMigrationJob.

    2. Examine the triggers list. Uncomment rmeRuleMigrationJobTrigger and identityAuditDataMigrationTrigger

16. Repackage the .war file in the %TEMP% directory if changes are made. Type the following commands in the test environment:

    cd %TEMP%

    jar -cvfM %RBACXWAR%\rbacx.war .

17. Uninstall Oracle Identity Analytics from the application server.

18. Deploy the rebuild Oracle Identity Analytics .war file on the target application server. Refer to Chapter 4, Deploying Oracle Identity Analytics for instructions on Oracle Identity Analytics deployment.

19. Start the application server.

20. Go to the following address in a browser: https://Hostname:Port-Number/rbacx/welcome.action

    When the Welcome screen appears, enter your rbacxadmin user name and password and verify that the installation is successful.

21. Open the rbacx.log file and check for errors.

    The installation is successful if the following message appears in the rbacx.log file:

    Oracle Identity Analytics (build: 11.1.1.3.0.20100727_21_7842) Started

22. Role Provisioning and Identity Audit rules are automatically migrated by Oracle Identity Analytics when started for the first time. The migration jobs should be disabled for any subsequent restarts. To disable the jobs, navigate to the rbacx.war directory exploded by the application server and locate scheduling-context.xml under rbacx\WEB-INF. Open it using a text editor and find bean ID quartzSchedulerFactoryBean.

    1. Examine the jobDetails list. Comment rmeRuleMigrationJob and identityAuditDataMigrationJob.

    2. Examine the triggers list. Comment rmeRuleMigrationJobTrigger and identityAuditDataMigrationTrigger.

To Upgrade the Environment on a UNIX Platform for a Standalone Deployment

Use the following steps to upgrade Oracle Identity Analytics manually on a supported UNIX platform.

1. Stop the application server.

2. Update the Oracle Identity Analytics database.

3. Type the following commands in the test environment:

   export INSPATH=Path to the upgrade software  (For example, export INSPATH=/opt/RM_Upgrade)

   export RBACXWAR=Path to the Oracle Identity Analytics deployment directory  (For example, export RBACXWAR=Tomcat install directory/webapps)

   export RM_LIB=Path to the downloaded third-party library files  (For example, export RM_LIB=/opt/RM_Lib)

   export TEMP=Path to the temporary directory

4. Run the pre-process commands:

   mkdir $TEMP

   cd $TEMP

   jar -xvf $INSPATH/rbacx.war

5. Copy the downloaded third-party library files to the Oracle Identity Analytics library directory.

   cp $RM_LIB/* $TEMP/WEB-INF/lib

6. Remove report-related files from the Oracle Identity Analytics Installation Directory/reports directory.

   /usr/bin/rm -f $RBACX_HOME/reports

7. Copy the target Oracle Identity Analytics version-specific reports based on the database server to the Oracle Identity Analytics Installation Directory/reports folder.

   The following sample steps assume that the target database server is MySQL.

   cp -R $INSPATH/reports $RBACX_HOME/.

   cp -R $RBACX_HOME/reports/mysql/* $RBACX_HOME/reports/.

8. Remove search-related files from the Oracle Identity Analytics Installation Directory/.indexes directory.

   /usr/bin/rm -f $RBACX_HOME/.indexes

9. Copy the files related to advanced search from the upgrade folder to Oracle Identity Analytics Installation Directory/.indexes

   cp -R $INSPATH/.indexes $RBACX_HOME/.

10. Make changes to the following files located under $INSPATH/conf directory to reflect customizations as documented in Documenting Custom Components.

    • iam.properties - In a text editor, replace any occurrences of $RBACX_HOME with the Oracle Identity Analytics installation directory path.

    • jdbc.properties - In a text editor, edit the following lines, substituting $SERVER_NAME and $PORT_NUMBER with the host name and connectivity port of the target database. Refer to UNIX: To Create the Oracle Identity Analytics Schema on the Database Server for instructions.

    • ldap.properties - Refer to Authenticating With LDAP for instructions on LDAP customizations.

    • rm_idm_init.xml - This file is required by Oracle Identity Analytics to exchange and manage information with Identity Manager.

11. Remove the configuration related directory from Oracle Identity Analytics Installation Directory directory

    /usr/bin/rm -f $RBACX_HOME/conf

12. Copy configuration directory and files from the upgrade directory to the Oracle Identity Analytics Installation Directory directory.

    cp -R $INSPATH/conf $RBACX_HOME/.

13. Apply any customizations necessary for the environment to the extracted .war file in the $TEMP directory.

14. Make the following changes if there are multiple instances of Oracle Identity Analytics, standalone or clustered, on the same subnet.

    1. Navigate to $TEMP/WEB-INF directory.

    2. In a text editor, open application-context.xml, find bean id commManager, and examine the constructor-arg value.

    3. Set the constructor-arg value with a unique instance name, for example value="SRM-Instance-1".

    4. In a text editor, open search-context.xml, find bean id searchConfiguration, and examine the constructor-arg value.

       • The deployment is a standalone, constructor-arg defaults to a value of 0, which is specified as value="0".

    5. Navigate to $TEMP/WEB-INF/classes directory and do the following:

       1. In a text editor, open oscache.properties (located in the $TEMP/WEB-INF/classes), and find the cache.cluster.multicast.ip property.

       2. Uncomment cache.cluster.multicast.ip by removing # at the start of the line. Each Oracle Identity Analytics instance requires a unique cache.cluster.multicast.ip value.

15. To migrate Role Provisioning and Identity Audit rules, open scheduling-context.xml using a text editor and find bean id quartzSchedulerFactoryBean.

    1. Examine the jobDetails list. Uncomment rmeRuleMigrationJob and identityAuditDataMigrationJob.

    2. Examine the triggers list. Uncomment rmeRuleMigrationJobTrigger and identityAuditDataMigrationTrigger

16. Repackage the .war file in the $TEMP directory if changes are made. Type the following commands in the test environment:

    cd $TEMP

    jar -cvfM $RBACXWAR/rbacx.war .

17. Uninstall Oracle Identity Analytics from the application server.

18. Deploy the rebuild Oracle Identity Analytics .war file on target application server.

    Refer to Chapter 4, Deploying Oracle Identity Analytics for instructions on Oracle Identity Analytics deployment.

19. Start the application server.

20. Go to the following address in a browser: https://Hostname:Port-Number/rbacx/welcome.action

    When the Welcome screen appears, enter your rbacxadmin user name and password and verify that the installation is successful.

21. Open the rbacx.log file and check for errors.

    The installation is successful if the following message appears in the rbacx.log file:

    Oracle Identity Analytics (build: 11.1.1.3.0.20100727_21_7842) Started

22. Role Provisioning and Identity Audit rules are automatically migrated by Oracle Identity Analytics when started for the first time. The migration jobs should be disabled for any subsequent restarts. To disable the jobs, navigate to the rbacx.war directory exploded by the application server and locate scheduling-context.xml under rbacx/WEB-INF. Open it using a text editor and find bean ID quartzSchedulerFactoryBean.

    1. Examine the jobDetails list. Comment rmeRuleMigrationJob and identityAuditDataMigrationJob.

    2. Examine the triggers list. Comment rmeRuleMigrationJobTrigger and identityAuditDataMigrationTrigger.

To Upgrade the Environment on a Windows Platform for a Clustered Deployment

Use the following steps to upgrade Oracle Identity Analytics manually on a supported Windows platform.

1. Stop the application server.

2. Update the Oracle Identity Analytics database.

3. Type the following commands in the test environment:

   set INSPATH=Path to the upgrade software  (For example, set INSPATH=C:\RM_Upgrade)

   set RBACXWAR=Path to the Oracle Identity Analytics deployment directory  (For example, set RBACXWAR=Tomcat install directory\webapps)

   set RM_LIB=Path to the downloaded third-party library files  (For example, set RM_LIB=C:\RM_Lib)

   set TEMP=Path to the temporary directory

4. Run the pre-process commands:

   mkdir %TEMP%

   cd %TEMP%

   jar -xvf %INSPATH%\rbacx.war

5. Copy the downloaded third-party library files to the Oracle Identity Analytics library directory.

   copy %RM_LIB%* %TEMP%\WEB-INF\lib

6. Remove report-related files from the Oracle Identity Analytics Installation Directory\reports directory

   rmdir /s /q %RBACX_HOME%\reports

7. Copy the target Oracle Identity Analytics version-specific reports based on the database server to the Oracle Identity Analytics Installation Directory\reports folder.

   The following sample steps assume that the target database server is MySQL.

   xcopy %INSPATH%\reports %RBACX_HOME%\reports /I/E

   xcopy %RBACX_HOME%\reports\mysql * %RBACX_HOME%\reports

8. Remove search-related files from the Oracle Identity Analytics Installation Directory\.indexes directory

   rmdir /s /q %RBACX_HOME%\.indexes

9. Copy the files related to advanced search from the upgrade folder to the Oracle Identity Analytics Installation Directory\.indexes folder.

   xcopy %INSPATH%\.indexes %RBACX_HOME%\.indexes /I/E

10. Make changes to the following files located under %INSPATH%\conf directory to reflect customizations as documented in Documenting Custom Components.

    • iam.properties - In a text editor, replace any occurrences of $RBACX_HOME with the Oracle Identity Analytics installation directory path.

      Note: When the application server is clustered, the nodes can maintain localized import/export directories, or utilize import/export directories on a NFS share. If the nodes use a shared NFS location for import/export, substitute $RBACX_HOME with the path to the NFS share.

    • jdbc.properties

      • In a text editor, edit the following lines, substituting $SERVER_NAME and $PORT_NUMBER with the host name and connectivity port of the target database. Refer to UNIX: To Create the Oracle Identity Analytics Schema on the Database Server for instructions.

      • Make the following change to jdbc.properties for clustered Quartz support, and save the file:

        jdbc.quartz.isClustered=true

    • ldap.properties - Refer to Authenticating With LDAP for instructions on LDAP customizations.

    • rm_idm_init.xml - This file is required by Oracle Identity Analytics to exchange and manage information with Identity Manager.

11. Remove the configuration related directory from Oracle Identity Analytics Installation Directory directory

    rmdir /s /q %RBACX_HOME%\conf

12. Copy configuration directory and files from the upgrade directory to the Oracle Identity Analytics Installation Directory directory.

    xcopy %INSPATH%\conf %RBACX_HOME%\conf /I/E

13. Apply any customizations necessary for the environment to the extracted .war file in the %TEMP% directory.

14. Make the following changes to enable Oracle Identity Analytics support for clustered application server deployments.

    1. Navigate to %TEMP%\WEB-INF directory.

    2. In a text editor, open application-context.xml, find bean ID commManager, and examine the constructor-arg value.

    3. Set the constructor-arg value as the cluster name-for example, value="Prod-1-Cluster".

       • If Oracle Identity Analytics is deployed on multiple clusters within the same subnet, you should define unique constructor-arg values for each deployment. For example, if both clusters Prod-Cluster and QA-Cluster have Oracle Identity Analytics deployed, the constructor-arg values of each should be set to Prod-Cluster and QA-Cluster respectively.

       • Members of the same cluster should have the same constructor-arg value.

    4. In a text editor, open search-context.xml, find bean id searchConfiguration, and examine the constructor-arg value.

       • For a clustered deployment, constructor-arg defaults to a value of 1 or 2 depending on the location of the .indexes directory.

         1. To set the constructor-arg value, do the following:

            • If each clustered node will be accessing local individual .indexes directories, set constructor-arg to 1. For example, value="1"

            • If clustered nodes will be accessing a shared

              .indexes

              directory, set constructor-arg to 2. For example, value="2". The .indexes directory needs to be located on an NFS share location where each clustered node has read-write permission. Edit indexLocation such that the NFS share location replaces $RBACX_HOME in the value field.

    5. If multiple instances of Oracle Identity Analytics, standalone or clustered, exist on the same subnet, navigate to the %TEMP%\WEB-INF\classes directory and do the following:

       1. In a text editor, open oscache.properties (located in the %TEMP%\WEB-INF\classes directory), and find the cache.cluster.multicast.ip property.

       2. Uncomment cache.cluster.multicast.ip by removing # at the start of the line. Each non-member instance requires a unique cache.cluster.multicast.ip value.

15. To migrate Role Provisioning and Identity Audit rules, open scheduling-context.xml using a text editor and find bean id quartzSchedulerFactoryBean.

    1. Examine the jobDetails list. Uncomment rmeRuleMigrationJob and identityAuditDataMigrationJob.

    2. Examine the triggers list. Uncomment rmeRuleMigrationJobTrigger and identityAuditDataMigrationTrigger

16. Repackage the .war file in the %TEMP% directory if changes are made. Type the following commands in the test environment:

    cd %TEMP%

    jar -cvfM %RBACXWAR%\rbacx.war .

17. Uninstall Oracle Identity Analytics from the application server.

18. Deploy the rebuild Oracle Identity Analytics .war file on the target application server. Refer to Chapter 4, Deploying Oracle Identity Analytics for instructions about Oracle Identity Analytics deployment.

19. Start the application server.

20. Go to the following address in a browser: https://Hostname:Port-Number/rbacx/welcome.action

    When the Welcome screen appears, enter your rbacxadmin user name and password and verify that the installation is successful.

21. Open the rbacx.log file and check for errors.

    The installation is successful if the following message appears in the rbacx.log file:

    Oracle Identity Analytics (build: 11.1.1.3.0.20100727_21_7842) Started

22. Role Provisioning and Identity Audit rules are automatically migrated by Oracle Identity Analytics when started for the first time. The migration jobs should be disabled for any subsequent restarts. To disable the jobs, navigate to the rbacx.war directory exploded by the application server and locate scheduling-context.xml under rbacx\WEB-INF. Open it using a text editor and find bean id quartzSchedulerFactoryBean.

    1. Examine the jobDetails list. Comment rmeRuleMigrationJob and identityAuditDataMigrationJob.

    2. Examine the triggers list. Comment rmeRuleMigrationJobTrigger and identityAuditDataMigrationTrigger.

To Upgrade the Environment on a UNIX Platform for a Clustered Deployment

Use the following steps to upgrade Oracle Identity Analytics manually on a supported UNIX platform.

1. Stop the application server.

2. Update the Oracle Identity Analytics database.

3. Type the following commands in the test environment:

   export INSPATH=Path to the upgrade software  (For example, export INSPATH=/opt/RM_Upgrade)

   export RBACXWAR=Path to the Oracle Identity Analytics deployment directory  (For example, export RBACXWAR=Tomcat install directory/webapps)

   export RM_LIB=Path to the downloaded third-party library files.  (For example, export RM_LIB=/opt/RM_Lib)

   export TEMP=Path to the temporary directory

4. Run the pre-process commands:

   mkdir $TEMP

   cd $TEMP

   jar -xvf $INSPATH/rbacx.war

5. Copy the downloaded third-party library files to the Oracle Identity Analytics library directory.

   cp $RM_LIB/* $TEMP/WEB-INF/lib

6. Remove report-related files from the Oracle Identity Analytics Installation Directory/reports directory.

   /usr/bin/rm -f $RBACX_HOME/reports

7. Copy the target Oracle Identity Analytics version-specific reports based on the database server to the Oracle Identity Analytics Installation Directory/reports folder.

   The following sample steps assume that the target database server is MySQL.

   cp -R $INSPATH/reports $RBACX_HOME/.

   cp -R $RBACX_HOME/reports/mysql/* $RBACX_HOME/reports/.

8. Remove search-related files from the Oracle Identity Analytics Installation Directory/.indexes directory.

   /usr/bin/rm -f $RBACX_HOME/.indexes

9. Copy the files related to advanced search from the upgrade folder to Oracle Identity Analytics Installation Directory/.indexes

   cp -R $INSPATH/.indexes $RBACX_HOME/.

10. Make changes to the following files located under $INSPATH/conf directory to reflect customizations as documented in Documenting Custom Components.

    • iam.properties - In a text editor, replace any occurrences of $RBACX_HOME with the Oracle Identity Analytics installation directory path.

      Note: When the application server is clustered, the nodes can maintain localized import/export directories, or utilize import/export directories on a NFS share. If the nodes use a shared NFS location for import/export, substitute $RBACX_HOME with the path to the NFS share.

    • jdbc.properties

      • In a text editor, edit the following lines, substituting $SERVER_NAME and $PORT_NUMBER with the host name and connectivity port of the target database. Refer to UNIX: To Create the Oracle Identity Analytics Schema on the Database Server for instructions.

      • Make the following change to jdbc.properties for clustered Quartz support, and save the file:

        jdbc.quartz.isClustered=true

    • ldap.properties - Refer to Authenticating With LDAP for instructions on LDAP customizations.

    • rm_idm_init.xml - This file is required by Oracle Identity Analytics to exchange and manage information with Identity Manager.

11. Remove the configuration related directory from Oracle Identity Analytics Installation Directory directory

    /usr/bin/rm -f $RBACX_HOME/conf

12. Copy configuration directory and files from the upgrade directory to the Oracle Identity Analytics Installation Directory directory.

    cp -R $INSPATH/conf $RBACX_HOME/.

13. Apply any customizations necessary for the environment to the extracted .war file in the $TEMP directory.

14. Make the following changes to enable Oracle Identity Analytics support for clustered application server deployments.

    1. Navigate to $TEMP/WEB-INF directory.

    2. In a text editor, open application-context.xml, find bean id commManager, and examine the constructor-arg value.

    3. Set the constructor-arg value as the cluster name-for example, value="Prod-1-Cluster".

       • If Oracle Identity Analytics is deployed on multiple clusters within the same subnet, you should define unique constructor-arg values for each deployment. For example, if both clusters Prod-Cluster and QA-Cluster have Oracle Identity Analytics deployed, the constructor-arg values of each should be set to Prod-Cluster and QA-Cluster respectively.

       • Members of the same cluster should have the same constructor-arg value.

    4. In a text editor, open search-context.xml, find bean id searchConfiguration, and examine the constructor-arg value.

       • For a clustered deployment, constructor-arg defaults to a value of 1 or 2 depending on the location of the .indexes directory.

         1. To set the constructor-arg value, do the following:

            • If each clustered node will be accessing local individual .indexes directories, set constructor-arg to 1. For example, value="1"

            • If clustered nodes will be accessing a shared

              .indexes

              directory, set constructor-arg to 2. For example, value="2". The .indexes directory needs to be located on an NFS share location where each clustered node has read-write permission. Edit indexLocation such that the NFS share location replaces $RBACX_HOME in the value field.

    5. If multiple instances of Oracle Identity Analytics, standalone or clustered, exist on the same subnet, navigate to the $TEMP/WEB-INF/classes directory and do the following:

       1. In a text editor, open oscache.properties (located in the $TEMP/WEB-INF/classes directory), and find the cache.cluster.multicast.ip property.

       2. Uncomment cache.cluster.multicast.ip by removing # at the start of the line. Each non-member instance requires a unique cache.cluster.multicast.ip value.

15. To migrate Role Provisioning and Identity Audit rules, open scheduling-context.xml using a text editor and find bean id quartzSchedulerFactoryBean.

    1. Examine the jobDetails list. Uncomment rmeRuleMigrationJob and identityAuditDataMigrationJob.

    2. Examine the triggers list. Uncomment rmeRuleMigrationJobTrigger and identityAuditDataMigrationTrigger

16. Repackage the .war file in the $TEMP directory if changes are made. Type the following commands in the test environment:

    cd $TEMP

    jar -cvfM $RBACXWAR/rbacx.war .

17. Uninstall Oracle Identity Analytics from the application server.

18. Deploy the rebuild Oracle Identity Analytics .war file on target application server.

    Refer to Chapter 4, Deploying Oracle Identity Analytics for instructions on Oracle Identity Analytics deployment.

19. Start the application server.

20. Go to the following address in a browser: https://Hostname:Port-Number/rbacx/welcome.action

    When the Welcome screen appears, enter your rbacxadmin user name and password and verify that the installation is successful.

21. Open the rbacx.log file and check for errors.

    The installation is successful if the following message appears in the rbacx.log file:

    Oracle Identity Analytics (build: 11.1.1.3.0.20100727_21_7842) Started

22. Role Provisioning and Identity Audit rules are automatically migrated by Oracle Identity Analytics when started for the first time. The migration jobs should be disabled for any subsequent restarts. To disable the jobs, navigate to the rbacx.war directory exploded by the application server and locate scheduling-context.xml under rbacx/WEB-INF. Open it using a text editor and find bean id quartzSchedulerFactoryBean.

    1. Examine the jobDetails list. Comment rmeRuleMigrationJob and identityAuditDataMigrationJob.

    2. Examine the triggers list. Comment rmeRuleMigrationJobTrigger and identityAuditDataMigrationTrigger.

To Restore Customization after the Upgrade

1. Once the upgrade process is complete, set up the customized repository objects to restore application customizations.