Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Transferring manually
This section provides information on how to manually transfer data to another database domain.
Before you begin
Before transferring IBM® WebSphere® Portal Express data to another domain, ensure that the following prerequisites are met:
- Supported database software is installed.
- Databases and users are correctly set up for use by WebSphere Portal Express.
- If you are using one of the following fix packs complete the steps below prior to database transfer. Failure to follow these steps will cause the database transfer to hang at the task action-process-constraints.
- DB2 8.1 Fix Pack 10
- DB2 8.1 Fix Pack 11
- DB2 8.1 Fix Pack 12
- DB2 8.1 Fix Pack 13
DB2 8.1
Fix Pack 14
- DB2 9.1
Fix Pack 1
- Locate the following file:
- Linux:
/home/db2inst1/sqllib/cfg/db2cli.ini
- Windows:
db2home/sqllib/db2cli.ini
- Linux:
- Edit the file by adding the following to the end of the file:
- For Fix Pack 10 or Fix Pack 11:
[COMMON] DYNAMIC=1
An empty line is required after the dynamic=1 at the end of the file.
- For all other Fix Packs listed above:
[COMMON] DYNAMIC=1 ReturnAliases=0
An empty line is required after the ReturnAliases=0 at the end of the file.
- For Fix Pack 10 or Fix Pack 11:
Notes:
- This fix should be applied to both the client side and server side of the DB2 installation.
If you are using DB2 type 4 JDBC driver at the client side, the fix should be applied to the server side only.
- If you are transferring from Oracle Enterprise Edition, the open_cursors setting should be set to 1500 by default. If you are using DB2® Content Manager Runtime Edition, this value may need to be increased based on the table count in the DB2 Content Manager Runtime Edition schema.
As with other properties, each password property must have the -D prefix and be set equal to (=) a value. If you have multiple properties in a single command, use a space character between each -Dproperty=value setting.
Steps for transferring data to a DB2 for i5/OS database
Follow these steps to transfer data between domains.
- Open a command prompt, and change to the Userdata directory portal_server_root_user/config.
- Enter one of the first two commands to validate the database connection, and then enter the last command to validate the database driver, where domain is replaced with the database domain you are transferring.
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 in a single domain:
SBMJOB CMD(STRQSH CMD(WPSconfig.sh -profileName profile_root validate-database-connection-wps -DDbDomainList=domain))
- For a single domain: WPSconfig.sh -profileName profile_root validate-database-connection-wps -DDbDomainList=domain
- For multiple domains: WPSconfig.sh -profileName profile_root validate-database-connection-wps -DDbDomainList=domain1,domain2,domain3
- WPSconfig.sh -profileName profile_root validate-database-driver
where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
- From the same command prompt as the previous steps, be sure you are in the Userdata directory portal_server_root_user/config.
- Stop both the WebSphere Application Server administrative server and the WebSphere Portal Express server before running the database-transfer task. See Starting and stopping WebSphere Application Server and WebSphere Portal Express for information about stopping servers.
- To transfer the database, perform this step:
- Enter the following commands to run the configuration task.
- To run the task on an individual domain, enter the following command from the UserData directory:
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(WPSconfig.sh -profileName profile_root database-transfer-domain -Ddomain.DbPassword=password))
WPSconfig.sh -profileName profile_root database-transfer-domain -Ddomain.DbPassword=password
where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile and where domain is one of the domain database names (community, customization, feedback, jcr, likeminds, release or wmm). - To run the task on multiple domains, enter the following command from the UserData directory:
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(WPSconfig.sh -profileName profile_root database-transfer -DTransferDomainList=domain1,domain2,domain3))
WPSconfig.sh -profileName profile_root database-transfer -DTransferDomainList=domain1,domain2,domain3
where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile and where domain is one of the domain database names (community, customization, feedback, jcr, likeminds, release or wmm). - To run the task on all domains, enter the following command from the UserData directory:
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(WPSconfig.sh -profileName profile_root database-transfer))
WPSconfig.sh -profileName profile_root database-transfer
where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile
- To run the task on an individual domain, enter the following command from the UserData directory:
- After running this task, a message indicating success should result. 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.
- Enter the following commands to run the configuration task.
- Change to the UserData directory app_server_root/bin.
- Start the WebSphere Portal Express server.
startServer WebSphere_Portal -profileName profile_root
where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal Express is installed; for example, wp_profile.
Next steps
You have completed this step. Continue to the next step: