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

Transferring DB2 for i5/OS manually

This section provides information on how to manually transfer data to the IBM^® DB2™ for i5/OS™ database you have set up.

Before you begin:
Ensure that the following prerequisites are met:

• Supported database software is installed.
• Databases and users are correctly set up.

• The steps for transferring data to another supported database section provides 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.
• A configuration template might exist to support these instructions. Refer to the wp_profile_root/ConfigEngine/helpers directory for available configuration templates. Use the configuration template to update the wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties files, as described in the topic Configuration program, according to the property descriptions and recommended values provided. If you do not want to use a configuration template, follow the steps in this task.

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

Steps for transferring data to another supported database

1. Locate the following files and create a backup copy of each 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

   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 wkplc_comp.properties, most properties are repeated for each domain.

2. 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_iseries.
   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 driver: 2 (local only, non-clustered only): { jdbc:db2:*LOCAL/QWPS61 }
      • Type 4 driver: 4 (local or remote or clustered): { jdbc:as400:hostname/QWPS61 }
   6. For dbdomain.DbUser, type the user ID for the database administrator.
   7. For dbdomain.DbPassword, type the password for the database administrator.
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. Recommended value:

      • Type 2 driver: com.ibm.db2.jdbc.app.DB2Driver
      • Type 4 driver: com.ibm.as400.access.AS400JDBCDriver
   2. For db2_iseries.DbLibrary, type the directory and name of the .zip or .jar file that contains the JDBC driver class. Recommended value:

      • Type 2 driver: /QIBM/ProdData/Java400/ext/db2_classes.jar
      • Type 4 driver: /QIBM/ProdData/HTTP/Public/jt400/lib/jt400.jar
   3. For db2_iseries.JdbcProviderName, type the name of the JDBC provider that WebSphere Portal Express uses to communicate with its databases.

      Recommended value: wpdbJDBC_db2_iseries

5. Save and close the file.
6. 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.
7. Save and close the file.
8. Stop both WebSphere Application Server and the WebSphere Portal Express server:

   Option	Description
   WebSphere Application Server	stopServer server1 -profileName profile_root -user admin_userid -password admin_password
   WebSphere Portal Express	stopServer WebSphere_Portal -profileName profile_root -user admin_userid -password admin_password

9. Create the database schemas using the following commands:

   1. Change to the directory WAS_User_Profile_Root/ConfigEngine
   2. Create schemas for the Community, Customization, Release, JCR, Feedback, and LikeMinds domains: ConfigEngine.sh -profileName wp_profile create-database
10. Validate configuration properties using the following commands:

    • ConfigEngine.sh -profileName wp_profile validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds
    • ConfigEngine.sh -profileName wp_profile validate-database-connection -DTransferDomainList=release,customization,community,jcr,feedback,likeminds
11. Transfer the database:

    1. Enter the following command: ConfigEngine.sh -profileName wp_profile database-transfer
    2. After running this task, a message is added to the log files to verify that this task was successful. Check the log files. If the configuration fails, verify the values in the wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties files and then repeat this step.
12. Enter the following command to start the WebSphere Portal Express server: startServer WebSphere_Portal -profileName profile_root