AIX stand-alone: Configure the portal to use IBM DB2 for i

View the steps to manually transfer data to the IBM DB2 Universal Databaseā„¢ for i database you have set up. As an alternative to the manual database transfer procedure described here, you can use the configuration wizard to complete the database transfer task. However, you cannot specify all settings through the configuration wizard. For example, regardless of the method used to transfer data, run a configuration task to create JMS resources as described in this topic.

Before you begin:

Ensure that the following prerequisites are met:


Prerequisites


Modify properties for IBM DB2 for i
Create user profiles for IBM DB2 for i
AIX stand-alone server: Set up IBM DB2 for i databases automatically

  1. Stop both the server1 and WebSphere_Portal servers:

    • stopServer server1 -username admin_userid -password foo

    • stopServer WebSphere_Portal -username admin_userid -password foo

  2. Validate configuration properties using...

      ConfigEngine.sh validate-database -DWasPassword=foo

      Add -DTransferDomainList to specify the domains to validate; for example: -DTransferDomainList=jcr.

  3. Transfer the database:

      Do not execute the database-transfer task as a background process. This might cause the task to stall.

      1. Enter the following command:

          ConfigEngine.sh database-transfer -DWasPassword=foo


          • To select specific database domains to transfer, set -DTransferDomainList to include only the domains that you want to transfer. For example, to transfer only the JCR domain:

              ./ConfigEngine.sh database-transfer -DTransferDomainList=jcr -DWasPassword=foo

          • This note only applies when transferring databases from IBM DB2 for i to another server with IBM DB2 for i. If you are transferring databases from a database other than IBM DB2 for i, you can skip this note. Use SBMJOB to submit the Qshell script as a batch job to run in *BASE pool when *INTERACT pool does not have 1GB or more of allocated memory. For example: SBMJOB CMD(STRQSH CMD(ConfigEngine.sh database-transfer -DWasPassword=foo))

      2. After running the task, a message is added to the following log file for you to verify the task ran successfully:

          WP_PROFILE/ConfigEngine/log/ConfigTrace.log

          If the configuration fails, verify the values in wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties and then repeat this step.

  4. To create JMS resources in the new database...

      ConfigEngine.sh create-jcr-jms-resources-post-dbxfer -DWasPassword=foo

      Regardless of the method used to transfer data (configuration wizard or the steps in this topic), run this task to create JMS resources.

  5. Start the WebSphere Portal server.

      See Start and stopping servers, dmgrs, and node agents for instructions.

If you have additional nodes already configured, compare the following file on all nodes with the file from the primary node. Ensure all instances of the file are identical:

If the files are not identical, copy icm.properties from the primary node on which you ran the database-transfer task to the node.

  1. Stop the portal server on the secondary node.

  2. Copy

      WP_PROFILE/PortalServer/jcr/lib/com/ibm/icm/icm.properties

    from the primary node and replace icm.properties on the secondary node.

  3. Start the portal server on the secondary node.


Parent

Prepare IBM DB2 for i


Previous

AIX stand-alone server: Set up IBM DB2 for i databases automatically


Next topic

Verify the IBM DB2 for i configuration

 


+

Search Tips   |   Advanced Search