2 Upgrading to Release 9.0.3 from Release 9.0.2 on JBoss Application Servers

This chapter explains how to upgrade to Release 9.0.3 from Release 9.0.2 on JBoss application servers—do not attempt to upgrade to Release 9.0.3 from any other previous Oracle Identity Manager release.

Extract the contents of the Release 9.0.3 upgrade package to a temporary directory on your existing Release 9.0.2 system.

Note:

This document refers to this temporary directory as <PATCH>.

The following is a list of the steps in this section that explain how to upgrade from Release 9.0.2 to Release 9.0.3 on JBoss:

Backing Up Your Existing Release 9.0.2 Deployment
Upgrading the Database for Oracle Identity Manager
Install JBoss 4.0.3 with Service Pack 1(SP1)
Install Release 9.0.3 Using the Oracle Identity Manager Installer Program
Migrating Release 9.0.2 Custom Code

Backing Up Your Existing Release 9.0.2 Deployment

The first step for upgrading to Release 9.0.3 is to back up your existing Release 9.0.2 deployment to ensure that no data is lost during the upgrade process. If the upgrade fails, you can use this backup to restore the Release 9.0.2 deployment to its original state. Back up the following:

Oracle Identity Manager server
Oracle Identity Manager Design Console
Oracle Identity Manager Administrative and User Console
Oracle Identity Manager Remote Manager
Database used for Release 9.0.2

Upgrading the Database for Oracle Identity Manager

Perform the following steps to upgrade your existing Release 9.0.2 database instance to Release 9.0.3:

Extract the contents of the Oracle Identity Manager Release 9.0.3 upgrade package to a temporary directory on the database machine—this document refers to this temporary directory as <PATCH>.
Enable execute permissions on the scripts in the <PATCH> directory.
Verify your database is properly configured by referring to the database vendor's documentation and the Oracle Identity Manager Installation and Upgrade Guide specific to your application server.
Upgrade your database schema from Oracle Identity Manager Release 9.0.2 to Release 9.0.3 by using the 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.

Note:
The oim_db_upg_902_to_903 script also upgrades the required stored procedures for Oracle.

Oracle on Linux:
1. Run the following script on the system where the database for Oracle Identity Manager Release 9.0.2 is installed to upgrade the database schema:
```
<PATCH>/db/oracle/Scripts/oim_db_upg_902_to_903.sh
```
2. Enter the appropriate information for the Oracle database when prompted by the oim_db_upg_902_to_903.sh script.
Oracle on Windows:

Run the following batch script on the system where the Release 9.0.2 database is installed to upgrade the database schema:
```
<PATCH>\db\oracle\Scripts\oim_db_upg_902_to_903.bat
```
The following is the command line usage for the Oracle oim_db_upg_902_to_903.bat script:
```
oim_db_upg_902_to_903.bat <ORACLE_SID> <ORACLE_HOME> <ORACLE_XELL_USER> <ORACLE_XELL_USER_PWD> <PATCH> 
```
SQL Server:

Run the <PATCH>\db\SQLServer\Scripts\upg_902_to_903.bat batch file. Refer to Appendix A, "Executing the SQL Server Upgrade Scripts" for more information on executing this script.
Perform the following steps to recompile the stored procedures for your database:

Note:
If you are using an Oracle database, you can skip this step as running the oim_db_upg_902_to_903 script already created the required stored procedures for Oracle.

SQL Server:
1. Launch a plain-text editor, then open:
```
<PATCH>\db\SQLServer\StoredProcedures\compile_all_XL_SP.bat
```
1. 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
1. Run the following script:
```
<PATCH>\db\SQLServer\StoredProcedures\compile_all_XL_SP.bat
```
  Refer to Appendix A, "Executing the SQL Server Upgrade Scripts" for more information on executing this script.
Perform the following steps appropriate for your database to upgrade the Oracle Identity Manager Audit and Compliance module:

Oracle:
1. Log in to SQL *Plus with the credentials of the Oracle Identity Manager Release 9.0.2 database schema owner.
1. Run the following script:
```
<PATCH>/db/oracle/Scripts/Oracle_Enable_XACM.sql
```
SQL Server:

Run the following script:
```
<PATCH>\db\SQLServer\Scripts\SQLServer_Enable_XACM.bat
```
Refer to Appendix A, "Executing the SQL Server Upgrade Scripts" for more information on executing this script.
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 following .bat file:
```
<PATCH>\db\Utilities\LoadXML.bat
```
Linux:

Run the following script:
```
<PATCH>/db/Utilities/LoadXML.sh
```
Refer to Appendix B, "Loading Metadata into the Database" for more information on executing this script.

Install JBoss 4.0.3 with Service Pack 1(SP1)

Release 9.0.3 is certified on the JBoss 4.0.3 with SP1 application server. You must install JBoss 4.0.3 with SP1 to upgrade to Release 9.0.3. Refer to the JBoss application server documentation for details on installing JBoss 4.0.3 with SP1.

Install Release 9.0.3 Using the Oracle Identity Manager Installer Program

Install Release 9.0.3 using the Oracle Identity Manager Release 9.0.3 installer program and refer to the Oracle Identity Manager Installation Guide for JBoss for complete information about installing Release 9.0.3 on JBoss.

Important:

When installing Release 9.0.3, be sure you point to the existing database you upgraded to Release 9.0.3 on the Database Server Selection screen in the installer program. Enter the information for existing database you upgraded to Release 9.0.3 in the following fields on the Database Server Selection screen:

Host
Port
Database SID
User Name
Password

When Oracle Identity Manager is installed against an existing database, the .xldatabasekey file from the existing Oracle Identity Manager installation must be copied to the new <XL_HOME>\xellerate\config directory. You should create the \config directory in the new <XL_HOME>\xellerate\ path if it does not already exist.

Migrating Release 9.0.2 Custom Code

You can migrate custom code used in your Release 9.0.2 environment into your new Release 9.0.3 environment. Before you migrate custom code from the Release 9.0.2 environment, you must first recompile the custom code using the Release 9.0.3 libraries located in the <XL_HOME>/xellerate/lib directory.

Using the integrated development environment that originally compiled the Release 9.0.2 custom code (that is, Eclipse, JDeveloper, WASD or command line javac), recompile all custom java code using the Release 9.0.3 libraries.

The following is a list of the custom items you can migrate from Release 9.0.2 and reuse in Release 9.0.3 after recompiling using the Release 9.0.3 libraries.

Note:

For clustered environments, after recompiling the following items using the Release 9.0.3 libraries, copy them to each participant node in the cluster.

Custom java libraries bound to functional Oracle Identity Manager Release 9.0.2 adapters recompiled using Release 9.0.3 libraries. You do not need to recompile the adapters. You must copy the recompiled custom java libraries in the Release 9.0.2 <XL_HOME>/xellerate/JavaTasks directory to the Release 9.0.3 <XL_HOME>/xellerate/JavaTasks directory. You must copy the recompiled custom java libraries in the Release 9.0.2 <XL_RM_HOME>/xellerate/JavaTasks directory to the Release 9.0.3 <XL_RM_HOME>/xellerate/JavaTasks directory.
Custom scheduled tasks recompiled using Release 9.0.3 libraries. You must copy the recompiled custom scheduled tasks to the Release 9.0.3 <XL_HOME>/xellerate/ScheduleTask directory.
Custom event handlers recompiled using Release 9.0.3 libraries. You must copy the recompiled custom scheduled tasks to the Release 9.0.3 <XL_HOME>/xellerate/EventHandlers directory.
Connector Resource bundles by copying the Release 9.0.2 <XL_HOME>/xellerate/connectorResources directory to the Release 9.0.3 <XL_HOME>/xellerate/connectorResources directory.
Custom Resources by copying the Release 9.0.2 <XL_HOME>/xellerate/customResources directory to the Release 9.0.3 <XL_HOME>/xellerate/customResources directory.
Custom Administrative and User Console deployments. Several Administrative and User Console files were modified in Release 9.0.3. If you customized your Release 9.0.2 Administrative and User Console, that is, you made changes to the default, stock Administrative and User Console that shipped with Release 9.0.2, you must add your customizations into the new Release 9.0.3 Administrative and User Console files using the following steps:
1. Refer to Appendix C, "Upgrading Customized Administrative and User Consoles" to identify the Administrative and User Console files modified in Release 9.0.3 and to add your Release 9.0.2 customizations into the Release 9.0.3 files.
2. Stop the JBoss application server gracefully by running one of the following commands, as appropriate for the operating system on the machine hosting the Oracle Identity Manager server:
  
  Windows
```
<JBOSS_HOME>\bin\shutdown.bat -S
```
  UNIX and Linux
```
<JBOSS_HOME>/bin/shutdown.sh -S
```
3. Patch your updated Release 9.0.3 Administrative and User Console by running the following command:
  
  Windows
```
<XL_HOME>\xellerate\setup\patch_jboss.cmd
```
  UNIX and Linux
```
<XL_HOME>/xellerate/setup/patch_jboss.sh
```