Linux clustered server: Modify Oracle or Oracle RAC database properties

You must modify the approriate properties files before transferring data from the default database to the Oracle database.


Prerequisites


Linux clustered server: Install Oracle or Oracle RAC

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.

  1. Create backups:

    • WP_PROFILE/ConfigEngine/properties/wkplc.properties
    • WP_PROFILE/ConfigEngine/properties/wkplc_dbdomain.properties
    • WP_PROFILE/ConfigEngine/properties/wkplc_dbtype.properties

    • If you are transferring from a database other than Derby: WP_PROFILE/ConfigEngine/properties/wkplc_sourceDb.properties

      Default values are listed in these files. Unless otherwise noted, all values are of type alphanumeric text string. Print out the steps below for reference before modifying the properties files. Make sure to enter the appropriate values for each instance of each property. In wkplc_dbdomain.properties, most properties are repeated for each domain.

  2. Edit wkplc_dbdomain.properties

    1. For dbdomain.DbType, type oracle.

    2. dbdomain.DbName=domain_db_name

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

    3. dbdomain.DbSchema=domain_schema_name

        Restriction: The value for dbdomain.DbSchema must equal the value for dbdomain.DbUser unless you are using a single user to manage all of the database schemas.

    4. For dbdomain.DataSourceName, type the name of the data source that WebSphere Portal uses to communicate with its databases.

        Do not use the following reserved words:

          releaseDS
          communityDS
          customizationDS
          jcrDS
          lmdbDS

          feedback

    5. dbdomain.DbUrl=jdbc_db_url

        • The database element of this value should match the value of DbName.

        • For Oracle RAC only, 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.

    6. dbdomain.DbUser = database configuration user.

      The value for dbdomain.DbUser must equal the value for dbdomain.DbSchema unless you are using a single user to manage all of the database schemas.

    7. dbdomain.DbPassword = password for database configuration user.

    8. dbdomain.DbConfigRoleName = group for database configuration users

      Database rights are granted to this group instead of individuals. The user specified for dbdomain.DbUser must be assigned to this group.

    9. Optional. For dbdomain.DbRuntimeUser, type the user ID of the database user that should be used by WebSphere Portal to connect to the database at runtime. If no value is specified for this setting, the database configuration user will be used to connect to the databases at runtime.

    10. If dbdomain.DbRuntimeUser is specified, set dbdomain.DbRuntimePassword to be the password of the runtime database user.

    11. For dbdomain.DbRuntimeRoleName, type the name of the group for database runtime users

      Database rights are granted to this group instead of individuals. The user specified for dbdomain.DbRuntimeUser must be assigned to this group.

    12. Optional. For dbdomain.DBA.DbUser, type the database administrator user ID for privileged access operations during database creation. If not required, you can accept the default value or leave blank.

    13. Optional. For dbdomain.DBA.DbPassword, database administrator password for privileged access operations during database creation. If not required, you can accept the default value or leave blank.

    14. For dbdomain.DbHome, type the root location for the database.

        This value is used to specify the location to create the tablespaces.

  3. Save and close the file.

  4. Update the following properties in wkplc_dbtype.properties.

    1. For oracle.DbDriver, type the name of the Oracle JDBC driver class.

    2. For oracle.DbLibrary, type the directory and name of the .jar file that contains the JDBC driver class.

    3. For oracle.JdbcProviderName, type the name of the JDBC provider that WebSphere Portal uses to communicate with its databases.

  5. Save and close the file.

  6. Update the WasPassword value in wkplc.properties. Password for the WAS security authentication used in environment.

  7. Save and close the file.


Parent

Linux clustered server: Set up a remote Oracle or Oracle RAC database


Previous

Linux clustered server: Install Oracle or Oracle RAC


Next topic

Linux clustered server: Create Oracle or Oracle RAC databases

  Apr 5, 2011 11:13:27 AM Removed the following step from 2c: "The dbdomain.DbName should be the...


+

Search Tips   |   Advanced Search