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, you must run a configuration task to create JMS
resources as described in this topic.
- Stop the WebSphere_Portal
server:
- stopServer WebSphere_Portal -username admin_userid -password admin_password
- Validate configuration properties using
the ConfigEngine.sh validate-database -DWasPassword=password command.
Tip: Add the -DTransferDomainList parameter
to the validating task to specify the domains you want to validate;
for example: -DTransferDomainList=jcr.
If you want to validate all domains, you do not need to specify this
parameter on the command line.
- Transfer the database:
Note: Important:
Do not execute the database-transfer task as a background process.
This might cause the task to stall.
- Enter the following command: ConfigEngine.sh
database-transfer -DWasPassword=password
Note: - To select specific database domains to transfer, modify the -DTransferDomainList
specified in the command to include only the domains that you want
to transfer. For example, to transfer only the JCR domain you can
enter the following command: ConfigEngine.sh database-transfer -DTransferDomainList=jcr
-DWasPassword=password
- 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=password))
- After running the task, a message is added to the following
log file for you to verify the task ran successfully: wp_profile_root/ConfigEngine/log/ConfigTrace.log If the configuration fails, verify the values in the wkplc.properties, wkplc_dbdomain.properties,
and wkplc_dbtype.properties files and then repeat
this step.
- Start
the WebSphere® Portal Express® server. See Starting and stopping servers, deployment managers,
and node agents for instructions.
If
you have additional nodes already configured, you need to compare
the following file on all nodes with the file from the primary node.
Ensure all instances of the file are identical:
wp_profile_root/PortalServer/jcr/lib/com/ibm/icm/icm.properties.
If the files are not identical, copy
icm.properties from
the primary node on which you ran the
database-transfer task
to the node.
- Stop the portal server on the secondary node.
- Copy wp_profile_root/PortalServer/jcr/lib/com/ibm/icm/icm.properties from
the primary node and replace icm.properties on
the secondary node.
- Start the portal server on the secondary node.