Transfer Oracle RAC manually

 

+
Search Tips   |   Advanced Search

 

Before you begin

This section provides information on how to manually transfer data to the Oracle RAC database you have installed and set up.

Before configuring databases, ensure that the following prerequisites are met:

• Supported database software is installed.

• Databases and users are correctly setup for use by IBM WebSphere Portal.

 

Password Considerations

For security reasons, do not store passwords in...

• wpconfig.properties
• wpconfig_dbdomain.properties
• wpconfig_dbtype.properties

Edit each of the properties files prior to running a configuration task, inserting the passwords needed for that task. After the task has run, delete all passwords from each file.

Alternatively, we can specify the password on the command line using the following syntax:

./WPSconfig.sh task_name -Dpassword_property_key=password_value

Each password property must have the -D prefix and be set equal to (=) a value. If you have multiple properties in a single command, use a space character between each -Dproperty=value setting.

 

Transfer Notes

The steps for transferring data to another supported database section provides instructions for manually transferring data. Instead of performing the following steps, we can use the configuration wizard, a graphical user interface, to transfer data to another supported database.

A configuration template might exist to support these instructions. Refer to the directory...

portal_server_root/config/helpers

...for available configuration templates. Use the configuration template to update the properties files...

• wpconfig.properties
• wpconfig_dbdomain.properties
• wpconfig_dbtype.properties

If you do not want to use a configuration template, follow theses instructions as written.

 

Steps for transferring data to another supported database

Follow these steps to transfer WebSphere Portal and Member Manager databases to Oracle Enterprise Edition RAC.

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.

To use Oracle RAC, we need to manually specify an RAC datasource URL in the WebSphere Application Server 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 to Oracle, there can be only one user for each domain (release, community, customization, JCR, Feedback, LikeMinds, and WMM), 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.

1. Locate the following files and create a backup copy of each before changing any values:
   • portal_server_root/config/wpconfig.properties
   • portal_server_root/config/wpconfig_dbdomain.properties
   • portal_server_root/config/wpconfig_dbtype.properties

2. Edit the properties files and enter the values that are appropriate for the environment.

   Make sure to enter the appropriate values for each instance of each property. In wpconfig_dbdomain.properties, most properties are repeated for each domain.

   The WebSphere Portal database can be used to hold information for applications such as Document Manager, Personalization, Feedback and Likeminds. In this case, the user should use similar naming conventions for property values such as release.DbName, jcr.DbName, feedback.DbName, and likeminds.DbName. For example:

   • releaseDbName=wpsdb
   • jcr.DbName=jcrdb
   • feedback.DbName=fdbkdb
   • likeminds.DbName=lkmddb

   Do not change any settings other than those that are specified in these steps. For instructions on working with these files, see Configuration properties reference for a complete properties reference, including default values.

   If you are using a remote database, be sure to enter the values for the remote server.

   Use / instead of \ for all platforms.

   Some values, shown here in italics, might need to be modified to the specific environment.

   There might be additional database properties other than those listed here. Only change the properties within this table; skip all other properties.

   The value listed for each property in the following tables represents the specific information that is required to configure WebSphere Portal to the target database.

   Depending on which database domain has to be configured, dbdomain may need to be replaced by:

   • release
   • customization
   • community
   • jcr
   • feedback
   • likeminds
   • wmm

   If you are following the recommended architecture in Planning for Oracle RAC, the Value listed for each property in the following table represents the Oracle -specific information that is required to configure WebSphere Portal to Oracle RAC.

   Update the following properties in the file wpconfig_dbdomain.properties.

   Database domain properties
   Property	Value
   dbdomain.DbType	The type of database used to store information for WebSphere Portal. Value type: Alphanumeric text string Recommended: Oracle: oracle
   dbdomain.DbName	The name of the WebSphere Portal domain database and schema. Notes: This value is also the database element in the dbdomain.DbUrl property. Non-Windows platforms when using DB2 only. This value is the TCPIP Alias for the database. For Oracle, this value should match the 'ORACLE_SID'. Value type: Alphanumeric text string Notes: For DB2 and DB2 for z/OS, this value cannot exceed 8 characters and can only contain letters and numbers. Refer to the database documentation for more information. For DB2, this value must be different from the value of dbdomain.XDbName. If you change the name of the WebSphere Portal data source due to a database migration, manually update this property in the portal_server_root/config/wpconfig_dbdomain.properties file to maintain the proper resource reference mapping. Default value for all domains: wpsdb
   dbdomain.DbUrl	The database URL used to access the WebSphere Portal database with JDBC. The value must conform to standard JDBC URL syntax. For Oracle, Oracle RAC, and SQL Server, hostname is the name of the remote server and port is the port where the appropriate database instance is listening. The database element of this value should match the value of dbdomain.DbName. Value type: Alphanumeric text string, conforming to standard JDBC URL syntax Recommended value for all domains: Oracle: jdbc:oracle:thin:@YourDatabaseServer:1521:wpsdb
   dbdomain.DbUser	The user ID for the database administrator. Notes: For SQL Server and non-wmm databases only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same. For Oracle and SQL Server servers, this value must be set to FEEDBACK, which corresponds to the user FEEDBACK in the database. If the user you are using is an administrative user that has authority over the FEEDBACK schema, the administrative user should be entered for the dbdomain.DbUser property. Value type: Alphanumeric text string Default value for all domains: db2admin Recommended value: wpsdbusr (for databases other than DB2 )
   dbdomain.DbPassword	The password for the database administrator. A value must be set for this property; it cannot be empty. Value type: Alphanumeric text string Default value for all domains: ReplaceWithYourDbAdminPwd
   dbdomain.DbNode	The value for the node database. Required for non-Windows platforms when using DB2 only. Value type: Alphanumeric text string Default values: Release: wpsNode Community: wpsNode Customization: wpsNode JCR: wpsNode WMM: wpsNode Feedback value: pznNode LikeMinds value: pznNode
   dbdomain.DataSourceName	The name of the data store that WebSphere Portal uses to communicate with its databases. Notes: If the DbUser, DbUrl, and DbPassword are not the same across domains, this value must differ from the DataSourceName of the other domains. The value for dbdomain.DataSourceName should not be set to the same value as dbdomain.DbName. Value type: Alphanumeric text string Default values: Release: wpsdbDS Community: wpsdbDS Customization: wpsdbDS JCR: JCRDS WMM: wpsdbDS Feedback: feedback5 LikeMinds: lmdbDS

   Update the following properties in the file wpconfig_dbtype.properties.

   Database type properties
   Property	Value
   DbSafeMode	This only applies to database-specific tasks. If this property is set to true, database-specific tasks, such as create/modify/drop database, will not be performed. The property should be used if a pre-configured database (from a previous installation) already exists. If the property is set to false, the database will be updated and the pre-existing database configuration will be overwritten. Recommended: false Default: false
   oracle.DbDriver	The name of class that SqlProcessor will use to import SQL files. Recommended: oracle.jdbc.driver.OracleDriver Windows and UNIX Default value: oracle.jdbc.driver.OracleDriver (Cloudscape )
   oracle.JdbcProviderName	The name of the JDBC provider that WebSphere Portal uses to communicate with its databases. Recommended: wpdbJDBC_oracle Default: wpdbJDBC_cloudscape
   oracle.DbLibrary	The directory and name of the.zip or.jar file that contains the JDBC driver class. Recommended: oracleJDBC/lib/jar In UNIX environments, use a colon (:) instead of a semi-colon (;) to separate multiple paths. Windows and UNIX Default value: D:/oracleJDBC/ojdbc14.jar

   Update the following properties in the file wpconfig.properties.

   WebSphere Application Server properties
   Property	Description
   WasPassword	The password for WebSphere Application Server security authentication. If a value is specified for WasPassword, a value must also be specified for WasUserid. If WasPassword is left blank, WasUserid must also be left blank. Value type: Alphanumeric text string Recommended: Set this value according to your own environment. Default: ReplaceWithYourWASUserPwd

3. Save the file.

4. Open a command prompt, and change to the directory portal_server_root/config.

5. Enter the following commands to validate configuration properties.
   • UNIX:
     • ./WPSconfig.sh validate-database-connection-wps -DDbPassword=password

     • ./WPSconfig.sh validate-database-connection-jcr -DJcrDbPassword=password

     • ./WPSconfig.sh validate-database-connection-feedback -DFeedbackDbPassword=password

     • ./WPSconfig.sh validate-database-connection-likeminds -DLikemindsDbPassword=password

     • ./WPSconfig.sh validate-database-connection-wmm -DWmmDbPassword=password

     • ./WPSconfig.sh validate-database-driver

   • Windows :
     • WPSconfig.bat validate-database-connection-wps -DDbPassword=password

     • WPSconfig.bat validate-database-connection-jcr -DJcrDbPassword=password

     • WPSconfig.bat validate-database-connection-feedback -DFeedbackDbPassword=password

     • WPSconfig.bat validate-database-connection-likeminds -DLikemindsDbPassword=password

     • WPSconfig.bat validate-database-connection-wmm -DWmmDbPassword=password

     • WPSconfig.bat validate-database-driver

6. Stop both server1 and the WebSphere Portal server.
   • Enter the following command:
     • UNIX:

       ./stopServer.sh server1 -user admin_userid -password admin_password

     • Windows:

       stopServer.bat server1 -user admin_userid -password admin_password

     • i5/OS:

       stopServer -profileName profile_root -user admin_userid -password admin_password

       ...where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

     ...where server1 is the name of the WebSphere Application Server administrative server, and profile_root is the name given to the WebSphere Application Server profile in use.

   • Enter the following command:

     • UNIX:

       ./stopServer.sh WebSphere_Portal -user admin_userid -password admin_password

     • Windows:

       stopServer.bat WebSphere_Portal -user admin_userid -password admin_password

     • i5/OS:

       stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password

       ...where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

7. To transfer the database, perform this step:
   1. Change to the directory portal_server_root/config.

   2. Enter the following commands to run the configuration task.
      • UNIX:

        ./WPSconfig.sh database-transfer -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dwmm.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password

      • Windows:

        WPSconfig.bat database-transfer -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dwmm.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password

   3. After running this task, a message indicating success should result. Check the log files to verify that this task was successful. If the configuration fails, verify the values in the wpconfig_dbdomain.properties file, and then repeat this step.

8. Specify the JDBC URL to connect to the cluster:
   1. Login to the WebSphere Application Server 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 the changes

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

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

10. Change to the directory was_profile_root/bin.

11. Enter the following command to start the server1 application server: startServer WebSphere_Portal.

    If our application server (server1) does not have security enabled, exclude the user identification (-user was_admin_userid) and password (-password was_adminpassword) from the stop server command line. For example:

    • UNIX:

          ./stopServer.sh server1 -user was_admin_userid -password was_admin_password     ./startServer.sh server1
      

    • Windows:

          stopServer.bat server1 -user was_admin_userid -password was_admin_password     startServer.bat server1
      

12. Enter the following command to restart the WebSphere Portal application server:

    If the server does not have security enabled, exclude the user identification ((-user was_admin_userid)) and password (-password was_adminpassword) from the stop server command line. For example:

    • UNIX:

         ./stopServer.sh WebSphere_Portal -user was_admin_userid -password was_admin_password    ./startServer.sh WebSphere_Portal 
      

    • Windows:

          stopServer.bat WebSphere_Portal -user was_admin_userid -password was_admin_password 
          startServer.bat WebSphere_Portal 
      

 

Next steps

You have completed this step. Continue to the next step.

• Verify database connections

 

Parent Topic

Transfer all domains

 

---