Create local databases on Windows

When you use a local DB2 server, complete this task if you want to change the configuration and transfer to another local DB2 database. Before you begin, you should have completed installing DB2.

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:

• WebSphere Portal 6.1.5 wkplc.properties file reference

• WebSphere Portal 6.1.5 wkplc_comp.properties file reference

• WebSphere Portal 6.1.5 wkplc_dbtype.properties file reference

If you plan to transfer multiple instances of WebSphere Portal, increase the default number of concurrently active databases.

For example, to change the default number to 30, enter the following command at the database prompt: UPDATE DATABASE MANAGER CONFIGURATION USING NUMDB 30. A message confirms successful completion of the update. Working with properties files:

• The WebSphere Portal database can be used to hold information for applications such as Feedback and LikeMinds. Use similar naming conventions for property values such as release.DbName, jcr.DbName, feedback.DbName, and likeminds.DbName.

  For example:

  • release.DbName=release

  • jcr.DbName=jcrdb

  • feedback.DbName=fdbkdb

  • likeminds.DbName=lmdb

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

• Use a forward slash (/) instead of a backslash (\).

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

• The recommended value listed for each property represents the specific information that is required to configure WebSphere Portal to your 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.DbType

  • dbdomain.DbName

  • dbdomain.DbUrl

  • dbdomain.DbSchema

  If you use the same values for all four properties across the release, customization, community, and JCR domains, the database-transfer task fails because of 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.

1. Open a command prompt, and change to the directory profile_root/ConfigEngine/properties.

2. Create a backup copy of the configuration files before changing any values.

   • profile_root/ConfigEngine/properties/wkplc.properties

   • profile_root/ConfigEngine/properties/wkplc_comp.properties

   • profile_root/ConfigEngine/properties/wkplc_dbtype.properties

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

   1. For dbdomain.DbType, type db2.

   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.

4. Save and close the file.

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

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

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

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

6. Save and close the file.

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

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

8. Save and close the file.

9. To create the WebSphere Portal, Java Content Repository, Feedback and LikeMinds databases, type the following commands:

   • ConfigEngine.bat create-database -DTransferDomainList=release,community,customization,jcr,feedback,likeminds -DWasPassword=password

   • ConfigEngine.bat setup-database -DTransferDomainList=release,community,customization,jcr,feedback,likeminds -DWasPassword=password

10. Check the services file on the DB2 server system.

    If it does not specify DB2 connection and interrupt service ports, specify the ports for your operating system.

    1. Edit the file %SYSTEMROOT%\system32\drivers\etc\services.

    2. Add the text db2c_db2 50000/tcp, where db2 is the default instance.

Parent topic:

Set up a local DB2

Related tasks

Set up databases

---