WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Transferring Oracle RAC manually

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

 

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

 

Password Considerations

For security reasons, you should not store passwords in the wpconfig.properties, wpconfig_dbdomain.properties, and wpconfig_dbtype.properties files. IBM recommends that you edit each of the properties files prior to running a configuration task, inserting the passwords needed for that task. After the task has run, you should delete all passwords from each file. For more information, see Deleting passwords from configuration scripts.

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

As with other properties, 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. Tips:

 

Steps for transferring data to another supported database

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

Notes:

  1. Locate the following files and create a backup copy of each before changing any values:

  2. Use a text editor to open the properties files and enter the values that are appropriate for your environment. Tip:

    • IBM recommends to print out the properties tables in this step for reference while modifying the properties files.

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

    Notes:

    • The WebSphere Portal Express 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 your 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 Express to your 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

    • The values for at least one of the following properties must be unique for the release, customization, community, and jcr domains:

      If you use the same values for all four properties across the release, customization, community, and JCR domains, the database-transfer task will fail. If DbUser, DbUrl, and DbPassword are not the same across domains, the value for DataSourceName must differ from the DataSourceName of the other domains. In other words, this value must be unique for the database domain.

    • Do not modify the values for the sync and designer database domains. These domains are not used by WebSphere Portal Express and the values should remain pointing to the default database.

    • 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 Express 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 Express.

    Type: Alphanumeric text string

    Recommended:

    • Oracle: oracle

    dbdomain.DbName The name of the WebSphere Portal Express domain database and schema.

    Notes:

    • This value is also the database element in the dbdomain.DbUrl property.

    • For Oracle, this value should match your 'ORACLE_SID'.

    Type: Alphanumeric text string

    • If you change the name of the WebSphere Portal Express 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.

     

    Recommended value for all domains:

    • Release: release

    • Community: comm

    • Customization: cust

    • JCR: jcrdb

    • WMM: wmmdb

    • Feedback: fdbkdb

    • LikeMinds: lmdb

    dbdomain.DbSchema The schema name of the database domain.

    Notes:

    • For i5/OS: dbdomain.DbSchema must match the postfix of dbdomain.DbName after /. For example, if release.DbName=*LOCAL/REL60, then release.DbSchema=REL60.

    • Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems, for example on i5/OS.

    Notes:

    • This property is not used on Member Manager, which only uses the dbdomain.DbUser name as the schema.

    • Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems.

    • 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 only: For non-feedback domains, DbSchema and DbUser MUST be the same. For Feeback domains, the default schema name is FEEDBACK. If the value is set to something besides FEEDBACK, you also have to set the schemaName property in <wps_home>/shared/app/config/services/FeedbackService.properties to the new schema.

    Type: Alphanumeric text string

    dbdomain.DbUrl The database URL used to access the WebSphere Portal Express 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.

    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, 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.

    • For Oracle only: For non-feedback domains, DbSchema and DbUser MUST be the same. For Feeback domains, the default schema name is FEEDBACK. If the value is set to something besides FEEDBACK, you also have to set the schemaName property in <wps_home>/shared/app/config/services/FeedbackService.properties to the new schema.

    Type: Alphanumeric text string

    Default for all domains: wpdb2ins ReplacewithyourDBAdminUser

    Recommended:

    • Release: releaseusr

    • Community: communityusr

    • Customization: customizationusr

    • JCR: icmadmin

    • WMM: wmmdbusr

    • Feedback: feedback

    • LikeMinds: lmdbusr

    dbdomain.DbPassword

    The password for the database administrator.

    A value must be set for this property; it cannot be empty.

    Type: Alphanumeric text string

    Default for all domains: ReplaceWithYourDbAdminPwd

    dbdomain.DbNode

    The value for the node database.

    Required for non-Windows platforms when using DB2 only.

    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 Express 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. In other words, this value must be unique for the database domain.

    • The value for dbdomain.DataSourceName should not be set to the same value as dbdomain.DbName.

    • i5/OS: The value for dbdomain.DataSourceName must match the postfix of dbdomain.DbSchema name. For example, if release.DbSchema=REL60, then release.DataSourcename=REL60. This name must be unique for each database schema.

    • Follow the documentation of the target database management system in order to define a valid schema name, as restrictions apply for some database management systems.

    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

    oracle.DbDriver The name of class that SqlProcessor will use to import SQL files.

    Recommended: oracle.jdbc.driver.OracleDriver

    oracle.JdbcProviderName The name of the JDBC provider that WebSphere Portal Express uses to communicate with its databases.

    Recommended: wpdbJDBC_oracle

    oracle.DbLibrary The directory and name of the .zip or .jar file that contains the JDBC driver class.

    Recommended: oracleJDBC/lib/jar

    In Linux environments, use a colon (:) instead of a semi-colon (;) to separate multiple paths.

    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.

    Type: Alphanumeric text string

    Recommended: Set this value according to a environment.

    Default: ReplaceWithYourWASUserPwd

    Update the following properties in the file wpconfig_sourceDb.properties

    Property Description
    source.dbdomain.DbPassword The password for the source database.

    Type: Alphanumeric text string

    Recommended: Set this value according to a environment.

    This value is the same as the administrator password if the default user was used during install.

  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.

  6. Stop both server1 and the WebSphere Portal Express server.

    • Enter the following command:

      • Linux:

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

      • Windows:

        stopServer.bat server1 -user admin_userid -password admin_password

      • i5/OS:

        stopServer.sh server1 -profileName profile_root -user admin_userid -password admin_password

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

      server1 is the name of your WebSphere Application Server administrative server.

    • Enter the following command:

      • Linux:

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

      • Windows:

        stopServer.bat WebSphere_Portal -user admin_userid -password admin_password

      • i5/OS:

        stopServer.sh 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 Express 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.

      • Linux:

        ./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.properties, wpconfig_dbdomain.properties, wpconfig_sourceDb.properties, and wpconfig_dbtype.properties files, 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 your 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 your 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:

    • Linux: 

      ./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 Express application server:

    If your 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:

    • Linux: 

      ./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.

 

Parent topic:

Transferring all domains