Use Release and JCR domain copies
To keep the source portal environment in production and reduce downtime when migrating a clustered environment, it is recommended that you copy the earlier portal server Release and JCR domains and then update the target portal server's primary and secondary nodes to use the domain copies.
- Use database tools to copy the source portal JCR domain and Release domain.
If you are using IBM DB2 Universal Database™ for z/OS®, review the following considerations:
- If you plan to use the DB2 Administration Tool to copy the database domains, additional steps are required to ensure that the migration process completes successfully. Refer to Technote 1441277 for instructions on using the tool during the migration process.
- Make sure you verify that the databases are not in a COPY PENDING state before you connect to the database copies as described below.
- On the target portal primary node, in WP_PROFILE/ConfigEngine/properties, locate wkplc_dbdomain.properties and then update the jcr.* and release.* database properties to point to the JCR and Release domain copies that you created in the previous step.
If the source portal uses the default Apache Derby database, the migration tools automatically copy the database for you. However, if you have modified or customized the default Derby database, copy the entire Derby directory to a new directory, and then update all database properties to point to the copy of the Derby database. Ensure that derby.DBLibrary is set to use the WAS v7.derby.jar as the JDBC driver class and includes the directory location of the file. For example: derby.DBLibrary=WAS7_root/derby/lib/derby.jar
- On the target portal primary node, change to the WP_PROFILE/ConfigEngine and then connect to the copies of the Release domain and JCR domain:
- Windows™:
ConfigEngine.bat validate-database-connection -DTransferDomainList=release,jcr
ConfigEngine.bat connect-database -DTransferDomainList=release,jcr
- UNIX™:
./ConfigEngine.sh validate-database-connection -DTransferDomainList=release,jcr
/ConfigEngine.sh connect-database -DTransferDomainList=release,jcr
- i:
ConfigEngine.sh validate-database-connection -DTransferDomainList=release,jcr
ConfigEngine.sh connect-database -DTransferDomainList=release,jcr
- Repeat steps 2 and 3 on each secondary node.
Parent
Migrate a V6.1.x clustered portal
Previous
Upgrading the ConfigEngine tool on the primary and secondary nodes
Next topic
Retaining custom table spaces in a clustered portal