Modify database properties

This section provides information on how to modify the,, and files to work with your database. Modify these property files before running tasks to create datbases, create users, or transfer data.


Installing Oracle RAC

Create users

Creating databases

The,, and are published in the WebSphere Portal wiki.

The wiki articles include examples, valid values, and descriptions to help you determine what value to provide for a given property.

The documentation team and other IBM teams will update the properties to provide more examples and clarity as needed.

For the most up-to-date information about properties, such as examples, valid values, and more, see the following wiki articles:

Working with properties files:

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. Locate the following files and create a backup copy of each before changing any values:

    • profile_root/ConfigEngine/properties/

    • profile_root/ConfigEngine/properties/

    • profile_root/ConfigEngine/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, most properties are repeated for each domain.

  2. Edit the properties file and modify the values to correspond to your environment.

    1. For dbdomain.DbType, type oracle.

    2. For dbdomain.DbName, type the name of the WebSphere Portal domain database.

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

    3. For dbdomain.DbSchema, type the schema name of the database domain.

      Review your target database management system documentation to define a valid schema name. Some database management systems have schema name restrictions that understand. The dbdomain.DbName should be the same value used for the dbdomain.DbSchema

      Restriction: The value for dbdomain.DbSchema must equal the value for dbdomain.DbUser.

    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. For dbdomain.DbUrl, type the database URL used to access the WebSphere Portal database with JDBC.

      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.

    6. For dbdomain.DbUser, type the user ID for the database administrator. Restriction: The value for dbdomain.DbUser must equal the value for dbdomain.DbSchema.

    7. For dbdomain.DbPassword, type the password for the database administrator.

    8. For dbdomain.DBA.DbUser, type the database administrator user ID for privileged access operations during creation of the database.

    9. For dbdomain.DBA.DbPassword, type the database administrator password for privileged access operations during creation of the database.

    10. 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 the file

    1. For oracle.DbDriver, type the name of the class that SqlProcessor uses to import SQL files.

    2. For oracle.DbLibrary, type the directory and name of the .zip or .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 following property in the file

    1. For WasPassword, type the password for the WAS security authentication used in your environment.

  7. Save and close the file.

Parent topic:

Set up a remote Oracle RAC database on AIX, HP-UX, Linux, and Solaris for a stand-alone production server

Previous topic:

Creating databases

Next topic:

Set up databases