Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Creating local databases

When you use a local DB2 server, use this task to automatically create the required databases as a remote database on the local system.

If you plan to transfer multiple instances of WebSphere Portal Express, 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.

• The WebSphere Portal Express database can be used to hold information for applications such as Personalization, 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=wpsdb
  • jcr.DbName=jcrdb
  • feedback.DbName=fdbkdb
  • likeminds.DbName=lkmddb
• If you are using a remote database, enter the values for the remote server.
• Use forward slash (/) instead of 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 Express 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 wp_profile_root/ConfigEngine/.
2. Create a backup copy of the configuration files before changing any values.

   • wp_profile_root/ConfigEngine/properties/wkplc.properties
   • wp_profile_root/ConfigEngine/properties/wkplc_comp.properties
   • wp_profile_root/ConfigEngine/properties/wkplc_dbtype.properties
3. Use a text editor to open 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 Express domain database and schema. Note: This value is also the database element in the dbdomain.DbUrl property.
   3. For dbdomain.DbSchema, type the schema name of the database domain. Note: Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems.
   4. For dbdomain.DataSourceName, type the name of the data source that WebSphere Portal Express uses to communicate with its databases.
   5. For dbdomain.DbUrl, type the database URL used to access the WebSphere Portal Express database with JDBC. The value must conform to the JDBC URL syntax specified by the database. Note: The database element of this value should match the value of DbName. Recommended value:

      • Type 2: { jdbc:db2:wpsdb }
      • Type 4: { jdbc:db2://YourDatabaseServer:port/wpsdb:returnAlias=0; }
   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.
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. Recommended value:

      • Type 2: COM.ibm.db2.jdbc.app.DB2Driver
      • Type 4: com.ibm.db2.jcc.DB2Driver
   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 Express uses to communicate with its databases.

      Recommended value: wpdbJDBC_db2

6. Save and close the file.
7. Update the following property in the file wkplc.properties.

   1. For WasPassword, type the password for the WebSphere Application Server security authentication used in your environment.
8. Save and close the file.
9. To create the WebSphere Portal Express, Member Manager, Java Content Repository, Feedback and LikeMinds databases, type the following commands:

   • ConfigEngine.bat create-database -DTransferDomainList=release,community,customization,jcr,feedback,likeminds
   • ConfigEngine.bat setup-database -DTransferDomainList=release,community,customization,jcr,feedback,likeminds
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. Use a text editor to open the file %SYSTEMROOT%\system32\drivers\etc\services.
    2. Add the text db2c_db2 50000/tcp, where db2 is the default instance.