After you migrated to Version
8.0 and successfully tested
it, update your Version
8.0 web
content with the latest version data from your source environment.
Before you begin
WebDAV changes before update: If
you modified any resources in WebDAV, such as theme resources, you
must back up these resources before running the
wcm-post-migration-data-update task,
and then restore the resources after the task is complete.
- Connect your WebDAV client to http://host_name:port_number/wps/mycontenthandler/dav.
- Copy all folders to a temporary location.
About this task
Important: When you perform a post migration
data update you will lose any changes you have made to the data you
initially migrated. You must avoid updating content that you initially
migrated on your Version
8.0 server
and use it only to initially set up and test your new target environment.
If you need to continue adding content to your site, continue to do
so on your existing source environment and then perform a post-migration
data update to your Version
8.0 data.
Procedure
- Stop the portal server on both the source and target environments.
- Make a new copy of the source Portal JCR domain for the
most up-to-date content. For more information, see Using copies
of source database domains to minimize downtime.
- If the copy was not restored over the existing Version
8.0 database, connect to
the copy.
Update the
jcr.* database
properties in the
wp_profile_root/ConfigEngine/properties/wkplc_dbdomain.properties,
and run the
connect-database task from the
wp_profile_root/ConfigEngine directory.
- Windows: ConfigEngine.bat
connect-database -DPortalAdminPwd=password -DWasPassword=password -DTransferDomainList=jcr
- AIX® Linux Solaris: ./ConfigEngine.sh
connect-database -DPortalAdminPwd=password -DWasPassword=password -DTransferDomainList=jcr
- IBM® i: ConfigEngine.sh
connect-database -DPortalAdminPwd=password -DWasPassword=password -DTransferDomainList=jcr
- z/OS®: ConfigEngine.sh
connect-database -DPortalAdminPwd=password -DWasPassword=password -DTransferDomainList=jcr
- Run the wcm-post-migration-data-update task
from the wp_profile_root/ConfigEngine directory
of the 8.0 system.
- Windows: ConfigEngine.bat
wcm-post-migration-data-update -DPortalAdminPwd=password -DWasPassword=password -DPreviousPortalVersion=previous_portal_version
- AIX Linux Solaris: ./ConfigEngine.sh
wcm-post-migration-data-update -DPortalAdminPwd=password -DWasPassword=password -DPreviousPortalVersion=previous_portal_version
- IBM i: ConfigEngine.sh
wcm-post-migration-data-update -DPortalAdminPwd=password -DWasPassword=password -DPreviousPortalVersion=previous_portal_version
- z/OS: ConfigEngine.sh
wcm-post-migration-data-update -DPortalAdminPwd=password -DWasPassword=password -DPreviousPortalVersion=previous_portal_version
- previous_portal_version
- The version of the previous portal (for example, 6.1.0.6 or 7.0.0.2).
This value can be found in the previous Portal PortalServer_root/wps.properties.
- If managed pages was enabled before performing the data
update, you must re-enable it. Complete the steps as described
in Enabling managed pages.
- Cluster only: Compare the icm.properties file
on all secondary nodes with the version of the file on the primary
node, and ensure that all instances of the file are identical to the
one on the primary node.
- Once you completed these steps, review the following optional
post migration steps and update your system as required:
- If users have been updated on your source environment since the
original migration, run the member fixer tool on the target environment
after migrating your updated data. For more information, see Using
the web content member fixer task.
- Syndicate the updated data from your Version
8.0 primary server to the
other servers in your system.
- Update database statistics on all tables
found in the JCR domain. If you are using DB2®, you need to run reorgchk and runstats.
We recommend that the statistics gathering be done on all column,
for all tables and indexes and with at least a minimum level of sampling
and distribution.
What to do next
WebDAV changes after update: If
you backed up WebDAV folders before performing the web content update,
connect to the WebDAV client again, and restore the copied folders.