Transfer DB2 for iSeries manually

 

+
Search Tips   |   Advanced Search

 

This section details configuring IBM WebSphere Portal to use IBM DB2 Universal Database for iSeries™, and transferring data from other databases to DB2 for iSeries. If you choose to transfer from Cloudscape to DB2 for iSeries, there is no option to transfer back to Cloudscape.

You are here

  1. Plan for DB2 for iSeries
  2. Create schemas and users for DB2 for iSeries
  3. Transferring DB2 for iSeries manually (Current task) or Transfer between databases manually
  4. Verify database connections for iSeries

To transfer WebSphere Portal, Member Manager, and DB2Content Manager Runtime Edition databases to DB2 for iSeries.

  1. Locate the following files and create a backup copy of each using the backup-main-cfg-file task before changing any values:

  2. Edit the properties files and enter the values that are appropriate for the environment.

    Notes:

    • The WebSphere Portal database can be used to hold information for applications such as Document Manager, Personalization (Feedback), and LikeMinds. To prepare the database to hold such application information, you should use similar naming conventions for property values such as release.DbName. For example:

      • release.DbName=*LOCAL/REL60
      • community.DbName=*LOCAL/COMM60
      • customization.DbName=*LOCAL/CUST60
      • jcr.DbName=*LOCAL/JCR60
      • feedback.DbName=*LOCAL/FDB60
      • likeminds.DbName=*LOCAL/LKM60

    • Do not change any settings other than those that are specified in these steps. For instructions on working with these files, see the complete Configuration properties reference that includes default values.

    • If you are using 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 the specific environment.

    • Password considerations: For security reasons, you should not store passwords in the wpconfig.properties, wpconfig_dbdomain.properties, and wpconfig_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. For more information, see Delete passwords from configuration scripts.

    • 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, dbdomain may need to be replaced by:

      • release
      • customization
      • community
      • jcr
      • wmm
      • feedback
      • likeminds

    Database type properties in wpconfig_dbtype.properties
    Property Value
    DbSafeMode

    This property only applies to database-specific tasks. If this property is set to true, database-specific tasks such as create/modify/drop database will not be performed. The property should be used if a pre-configured database, such as from a previous installation, already exists. If the property is set to false, the database will be updated and the pre-existing database configuration will be overwritten.

    Value type: true, false

    Default: false

    Recommended: false

    db2_iseries.DbDriver

    The Java class name for the JDBC provider that WebSphere Portal uses to communicate with its databases.

    DB2 for i5/OS Recommended:

    • For local databases: com.ibm.db2.jdbc.app.DB2Driver

    • For remote databases: com.ibm.as400.access.AS400JDBCDriver

    Default: com.ibm.db2.jdbc.app.DB2Driver

    db2_iseries.DbLibrary

    The directory and name of the.zip or.jar file that contains the JDBC driver class.

    Value type: Directory path with elements delimited by forward slashes (/).

    i5/OS Recommended value: DB2 for i5/OS:

    • Local: /QIBM /ProdData/Java400/ext/db2_classes.jar

    • Remote: For the UserData path of the installed edition of WebSphere Application Server :portal_server_root/IBM Trans/lib/jt400.jar

    i5/OS Default value: /QIBM /ProdData/Java400/ext/db2_classes.jar

    For remote DB2 configuration, for the UserData path of the installed edition of WebSphere Application Server this value should be: portal_server_root/IBM Trans/lib/jt400.jar

    db2_iseries.DbDriverType

    The database driver type for local and remote

    Value type: Numeric text string; 2 for local, 4 for remote

    i5/OS Default value: 2

    Database properties in wpconfig_dbdomain.properties
    Property Value
    dbdomain.DbType

    The type of database used to store information for WebSphere Portal.

    Value type: Alphanumeric text string

    Recommended value for all domains:

    • Cloudscape : cloudscape

    • DB2 for i5/OS: db2_iseries

    dbdomain.DbName

    The name of the WebSphere Portal domain database and schema.

    Notes:

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

    • Non-Windows platforms when using DB2 only. This value is the TCPIP Alias for the database.

    • For Oracle, this value should match the 'ORACLE_SID'.

    Recommended value for local DB2 for i5/OS:

    • For non-Member Manager databases:

      • Release: *LOCAL/REL60
      • Customization: *LOCAL/CUST60
      • Community: *LOCAL/COMM60
      • Jcr: *LOCAL/JCR60
      • Feedback: *LOCAL/FDB60
      • LikeMinds: *LOCAL/LKM60

    • For Member Manager databases: *LOCAL/wmmDbUser, where *LOCAL is the database and wmmDbUser is the Member Manager database administrator user ID (the schema you will use to connect to the database).

    Recommended value for remote DB2 for i5/OS:

    • For non-Member Manager databases:

      • Release: hostName/REL60

      • Customization: hostName/CUST60

      • Community:hostNameCOMM60

      • JCR: hostName/JCR60

      • Feedback: hostName/FDB60

      • LikeMinds: hostName/LKM60

    • For Member Manager databases: hostName/wmmDbUser, where wmmDbUser is the Member Manager database administrator user ID (the schema you will use to connect to the database).

    dbdomain.DbSchema

    Description: The schema name of the database domain.

    Notes:

    • For i5/OS: dbdomain.DbSchema must match the postfix of dbdomain.DbName after /. For example, if release.DbName=*LOCAL/REL60, it must also have release.DbSchema=REL60.

    • 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, for example on i5/OS.

    Notes:

    • This property is not used on Member Manager, which only uses the dbdomain.DbUser name as the schema.

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

    • For SQL Server only, unless you are the system administrator, the values for dbdomain.DbUser and dbdomain.DbSchema must be the same.

    • For Oracle and SQL Server servers, the value must be set to FEEDBACK.

    Value type: Alphanumeric text string

    Default: dbdomain

    dbdomain.DbUrl

    The database URL used to access the WebSphere Portal database with JDBC. The value must conform to standard JDBC URL syntax.

    Recommended:

    • DB2 for i5/OS (local):

      • For non-Member Manager databases: jdbc:db2:*LOCAL/dbdomain.DbName

      • For Member Manager databases: jdbc:db2:*LOCAL/wmmDbUser, where *LOCAL is the database and wmmDbUser is the Member Manager database administrator user ID (the schema you will use to connect to the database).

    • DB2 for i5/OS (remote):

      • For non-Member Manager databases: jdbc:as400:hostName/dbdomain.DbName

      • For Member Manager databases: jdbc:as400:hostname/wmmDbUser, where wmmDbUser is the Member Manager database administrator user ID (the schema you will use to connect to the database).

    dbdomain.DbUser

    The user ID for the database administrator.

    Value type: Alphanumeric text string

    Recommended: Set this value according to your own environment.

    Default:

    • Release: db2admin
    • Community: db2admin
    • Customization: db2admin
    • JCR: db2admin
    • WMM: db2admin
    • Feedback: db2admin
    • LikeMinds: db2admin

    dbdomain.DbPassword

    The password for the database administrator.

    A value must be set for this property; it cannot be empty.

    Value type: Alphanumeric text string

    Recommended: Set this value according to your own environment.

    Default value for all domains: ReplaceWithYourDbAdminPwd

    dbdomain.XDbName

    The database loop back alias that needs to be set if you plan to use the create-local-database-db2 task.

    Notes:

    Value type: Alphanumeric text string

    Default:

    • Release: wps6TCP

    • Community: wps6TCP

    • Customization: wps6TCP

    • WMM: wps6TCP

    • JCR: wps6TCP

    • Feedback: fdbk6TCP

    • LikeMinds: lmdb6TCP

    dbdomain.DbNode

    The value for the node database.

    Required for non-Windows platforms when using DB2 only.

    Value type: Alphanumeric text string

    Default values:

    • Release: wpsNode

    • Community: wpsNode

    • Customization: wpsNode

    • JCR: wpsNode

    • WMM: wpsNode

    • Feedback value: pznNode

    • LikeMinds value: pznNode

  3. If you have come to this step while creating databases and users, please return to that section of the InfoCenter now. Otherwise, continue with the next step.

  4. Save the file.

  5. Open a command prompt, and change to the UserData directory portal_server_root/config.

  6. Enter the following commands to validate configuration properties.

    where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

  7. From the same command prompt as the previous steps, be sure you are in the UserData directory portal_server_root/config.

  8. Stop both the WebSphere Application Server administrative server and the WebSphere Portal server before running the database-transfer task. See Starting and stopping WAS and WebSphere Portal for information about stopping servers.

  9. To transfer the database, type the following command to run the configuration task: 

    WPSconfig.sh -profileName profile_root database-transfer -Drelease.DbPassword=password 
-Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password  -Dwmm.DbPassword=password -Dfeedback.DbPassword=password 
-Dlikeminds.DbPassword=password
    After running this task, a message indicating success should appear. Check the log files to verify that this task was successful. If the configuration fails, verify the values in the wpconfig.properties, wpconfig_dbdomain.properties, and wpconfig_dbtype.properties files, and then repeat this step.

  10. Change to the directory app_server_root/bin.

  11. Enter the following command: 

    startServer WebSphere_Portal -profileName profile_root
    where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

You have completed configuring and transferring database information. Continue to the next step, Verifying database connections for iSeries.

 

Parent Topic

Transferring all domains