Solaris clustered server: Modify Oracle or Oracle RAC database properties

This section provides information on how to modify the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files to work with the database. Modify these property files before running tasks to create databases, create users, or transfer data.

Prerequisites

Solaris clustered server: Install Oracle or Oracle RAC

Work with properties files:

• Property files are read by ConfigEngine when tasks are executed. They are not read during Portal appserver startup.

• Multiple databases can be used to hold information for applications such as Feedback and LikeMinds.

  For example:

  • release.DbName=reldb
  • jcr.DbName=jcrdb
  • feedback.DbName=fdbkdb
  • likeminds.DbName=lmdb
  • community.DbName=commdb
  • customization.DbName=custdb

• If we are using a remote database, enter the values for the remote server.

• Regardless of the operating system, use a forward slash (/) instead of a backslash (\) in the property files for file system paths.

• There might be additional database properties other than those listed here. Only change the properties within this task and skip all other properties.

• Property files provide default values. These values are not correct for all databases. Enter values in accordance with the database management system that we are using.

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

• Depending on which database domain has to be configured, replace dbdomain with:
  • release
  • customization
  • community
  • jcr
  • feedback
  • likeminds

• The values for at least one of the following properties must be unique for the release, customization, community, and JCR domains:
  • dbdomain.DbName
  • dbdomain.DbUrl
  • dbdomain.DbSchema

  If we use the same values for all three properties across the release, customization, community, and JCR domains, the database-transfer task fails due to ambiguous database object names.

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

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. Make backup copies of the following files:

   • WP_PROFILE/ConfigEngine/properties/wkplc.properties

   • WP_PROFILE/ConfigEngine/properties/wkplc_dbdomain.properties

   • WP_PROFILE/ConfigEngine/properties/wkplc_dbtype.properties

   • If we 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. Set the appropriate values for each instance of each property. In wkplc_dbdomain.properties, most properties are repeated for each domain.

2. Set properties in wkplc_dbdomain.properties

   1. For dbdomain.DbType, type oracle.

   2. dbdomain.DbName=domain_db_name

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

   3. dbdomain.DbSchema=domain_schema_name

      Some database management systems have schema name restrictions.

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

   4. dbdomain.DataSourceName=data_source_name

      Do not use the following reserved words:

      • releaseDS
      • communityDS
      • customizationDS
      • jcrDS
      • lmdbDS
      • feedback

   5. dbdomain.DbUrl=JDBC_DB_URL

      The value must conform to the JDBC URL syntax specified by the database.

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

      • Oracle JDBC OCI Type 2 drivers:

        For example, the Oracle database URL should use the following format:

        jdbc:oracle:oci:@//YourDatabaseServer:1521/service_name

      • Oracle JDBC Type 4 drivers:

        For example, the Oracle database URL should use the following format:

        jdbc:oracle:thin:@YourDatabaseServer:1521:service_name.

      • Oracle RAC JDBC OCI Type 2 drivers only:

        For example, the Oracle RAC database URL should use the following format:

        jdbc:oracle:oci:@//NODE_HOSTNAME:1521/NODE_INSTANCENAME

      • Oracle RAC JDBC Type 4 drivers only: The WebSphere Portal server must explicitly connect to one RAC node during database transfer. Specify the information of one Oracle RAC node as if it is the only database server.

        For example, the Oracle RAC database URL should use the following format:

        jdbc:oracle:thin:@NODE_HOSTNAME:1521:NODE_INSTANCENAME

        Use this format since the database transfer script does not parse the full Oracle RAC URL due to multiple host names. When database transfer is completed, the WebSphere Portal server will be configured to use this single database server. After transferring your data, use the WAS admin console to access the datasource definition, and update the URL to use the format of a RAC URL.

      The value for service_name in the database URL is the same value used for the service name value in the tnsnames.ora file on the Oracle database.

   6. For dbdomain.DbUser, set the user ID for the database configuration user.

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

   7. For dbdomain.DbPassword, set the password for the database configuration user.

   8. For dbdomain.DbConfigRoleName, set the name of the 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, set 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, set 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.

       DB administrator user ID for privileged access operations during database creation and setup. Required.if you run the create-database and setup-database ConfigEngine tasks . The database administrator must have SYSDBA permissions. If you do not need this parameter, we can either accept the default value or leave blank.

   13. Optional: For dbdomain.DBA.DbPassword, set the database administrator password for privileged access operations during database creation. If you do not need this parameter, we can either accept the default value or leave blank.

   14. For dbdomain.DbHome, set 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, set the name of the Oracle JDBC driver class.

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

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

5. Save and close the file.

6. Update the WasPassword value in wkplc.properties. This value is the password for the WAS security authentication used in the environment.

7. Save and close the file.

Parent: Solaris clustered server: Set up a remote Oracle or Oracle RAC database
Previous: Solaris clustered server: Install Oracle or Oracle RAC
Next: Solaris clustered server: Create Oracle or Oracle RAC databases