+

Search Tips   |   Advanced Search


Prepare for creation of databases

View the mandatory preparation tasks prior to creating databases that are required by WebSphere Portal.

The wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties 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:

  1. Preparing database domain property values prior to creating database names and schemas. Before you manually configure your database schemas, first edit your database domain properties files.

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

      • profile_root/ConfigEngine/properties/wkplc.properties

      • profile_root/ConfigEngine/properties/wkplc_comp.properties

      • profile_root/ConfigEngine/properties/wkplc_dbtype.properties

    2. The WebSphere Portal database can be used to hold information for applications such as Personalization (Feedback) and LikeMinds. To prepare the database to hold such application information, use similar naming conventions for property values such as release.DbName. Here are some examples:

      • release.DbName=hostname/WP61REL

      • community.DbName=hostname/WP61COM

      • customization.DbName=hostname/WP61CUS

      • jcr.DbName=hostname/WP61JCR

      • feedback.DbName=hostname/WP61FBK

      • likeminds.DbName=hostname/WP61LKM

      When you create a schema, use the following schema naming conventions on the i5/OS system:

      The default schema names may be used with the product.

      • Length cannot exceed 10 characters

      • All alphanumerical characters are allowed ( "A" through "Z" and "1" through "0")

      • The following characters are invalid:

        • spaces

        • null values

        • asterisk (*)

        • quotation marks (")

        • colon (:)

        • greater than symbol (>)

        • less than symbol (<)

        • vertical bar (|)

        • plus sign (+)

        • semicolon (;)

        • single quotation mark (')

        • question mark (?)

        Notes:

        • Make sure you know what valid schema names are and do not use a schema name which already exists on the local or remote system. Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply. Note that the Create WebSphere Portal wizard will automatically check schema names for you.

        • For more information on database and schema naming conventions, refer to DB2 Universal Database for System i5 topic in the System i5 information center.

      • Do not change any settings other than those that are specified in these substeps.

      • For a remote database, be sure to enter the values for the remote server.

      • Use / instead of \ for i5/OS.

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

      • Password considerations: For security reasons, you should not store passwords in the wkplc.properties, wkplc_comp.properties, and wkplc_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. Then, after the task has run, you should delete all passwords from each file.

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

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

        • release

        • customization

        • community

        • jcr

        • feedback

        • likeminds

    3. Edit the properties files and enter the values that are appropriate for your environment. You can also modify each properties file locally on your System i5 system by typing the following on an OS/400 command line in a 5250 session: 

      EDTF 'profile_root/ConfigEngine/properties/property filename.properties'

      where property filename is wkplc_comp, wkplc, or wkplc_dbtype.

      You must have a user profile on the System i5 server and must have at least *USE special authority to edit the properties file. Tip: The steps for transferring data to another supported database section provide instructions for manually transferring data. Instead of performing the following steps, you can use the configuration wizard, which is a graphical user interface, to transfer data to another supported database.

      The following properties must be changed before creating a database name and schema on a local or remote System i5 server.

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

    1. For dbdomain.DbType, type db2_iseries.

    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.

    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.

    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.

  3. Save and close the file.

  4. Update the following properties in the file wkplc_dbtype.properties.

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

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

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

    4. For db2_iseries.DbDriverType, type the number representing the driver type for the database.

  5. Save and close the file.

  6. Update the following property in the file wkplc.properties.

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

  7. Save and close the file.


Parent topic:

Prepare DB2 for i5/OS for a stand-alone production server


Next topic:

Create user profiles