Configure WebSphere Portal to use Oracle RAC

View information on manually transferring data to the Oracle RAC database you have installed and set up. Follow these steps to transfer WebSphere Portal, and Java Content Repository databases to Oracle. As an alternative to the manual database transfer procedure described here, you can use the configuration wizard to complete the database transfer task.

Before you begin:

Ensure that the following prerequisites are met:

• Supported database software is installed.

• Databases and users are set up.

• Property files are modified.

Prerequisites

Installing Oracle RAC

Create users

Creating databases

Modifying database properties

Set up databases

Tips:

• If you are transferring from Oracle, the open_cursors setting should be set to 1500 by default.

  For Java Content Repository, this value might need to be increased based on the table count in the Java Content Repository schema.

• The WebSphere Portal server must explicitly connect to one RAC node during database transfer. You need to specify the information of one Oracle RAC node as if it is the only database server.

  For example, the Oracle database URL should look like the following: jdbc:oracle:thin:@PRIMARY_NODE_HOSTNAME:1521:PRIMARY_NODE_INSTANCENAME. When database transfer is completed, the WebSphere Portal server will be configured to use this single database server.

• Manually specify an RAC datasource URL in the WAS console.

  The URL should look like the following: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PRIMARY_NODE_HOSTNAME)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=SECONDARY_NODE_HOSTNAME)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=DATABASE_SERVICENAME))).

• When doing a single database, single user, and multi schema database transfer, there can be only one user for each domain (release, community, customization, JCR, Feedback, and LikeMinds), and the schema for each database must be different.

  The user must be a superuser or DBA and must have authority over all other schemas for the transfer to work.

Steps for transferring data to another supported database

1. Open a command prompt and change to the directory profile_root/ConfigEngine.

2. Enter the following commands to validate configuration properties.

   ConfigEngine.bat validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DWasPassword=password
   

   ConfigEngine.bat validate-database-connection -DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DWasPassword=password
   

3. From the same command prompt as the previous steps, change to the directory profile_root\bin.

4. Stop both WAS and the WebSphere Portal server:

   Option	Description
   WAS	stopServer.bat server1-username admin_userid -password admin_password
   WebSphere Portal	stopServer.bat WebSphere_Portal-username admin_userid -password admin_password

5. Transfer the database:

   1. cd profile_root/ConfigEngine.

   2. Enter the following command:

      ConfigEngine.bat database-transfer -DTransferDomainList=release,customization,community,jcr, feedback,likeminds 
      

   3. After running this task, a message is added to the log files to verify that this task was successful. Check the log files. If the configuration fails, verify the values in the wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties files and then repeat this step.

6. After transferring the database tables, run the dbms_stats.gather_schema_stats command to avoid slow database response. Example:

   SQL> execute dbms_stats.gather_schema_stats(ownname=> 'jcr', cascade=> TRUE);
   

7. Specify the JDBC URL to connect to the cluster:

   1. Login to the WAS Administrator Console

   2. Navigate to Resources > JDBC Providers

   3. If there is a value in the Node field, remove it and click Apply.

   4. For each Oracle JDBC provider, repeat the following steps:

      1. Click the provider name.

      2. Select Data Sources.

      3. Click the name of the data source.

      4. Under the Oracle data source properties, modify the URL attribute according to Oracle RAC configuration: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PRIMARY_NODE_HOSTNAME)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=SECONDARY_NODE_HOSTNAME)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=DATABASE_SERVICENAME)))

      5. Save changes

8. Change to the directory profile_root\bin.

9. Enter the following command to start the WebSphere Portal server: startServer.bat WebSphere_Portal

If you have performed database transfer in a clustered environment, explicitly copy the profile_root\PortalServer\jcr\lib\com\ibm\icm\icm.properties file from the primary node on which the database-transfer task was processed to all secondary nodes. This ensures that the secondary nodes have the new JCR database values specified in the icm.properties file.

1. Stop the portal server on the secondary node.

2. Copy the profile_root\PortalServer\jcr\lib\com\ibm\icm\icm.properties file from the primary node and replace the icm.properties file on the secondary node with the new file from the primary node.

3. Start the portal server on the secondary node.

Parent topic:

Configure WebSphere Portal to use Oracle RAC

Previous topic:

Assigning custom table spaces

---