Staging artifacts that are not transferred by syndication

For an example that uses xmlaccess.sh to export all portal artifacts except pages and wires, see...

PORTAL_HOME/doc/xml-samples/ExportManagedPagesRelease.xml

Use this file when staging to production with managed pages.

Stage artifacts that are not part of the syndication, such as portlet definitions, themes, and personalization rules with the release builder Portal staging tool. It ensures the artifacts have the same object IDs across the staging systems because they are referenced by this object ID.

1. To export these artifacts...

   ./xmlaccess.sh -in /opt/IBM/WebSphere/PortalServer/doc/xml-samples/ExportManagedPagesRelease.xml -out /path/to/staging-version1.xml -url "http://stagingserver.example.com:port/wps/config" -user wpsadmin_user_ID -password wpsadmin_pwd

   The exported configuration is stored in the staging-version1.xml file.

2. Use the exported file to import these artifacts.
   ./xmlaccess.sh -in /path/to/staging-version1.xml -out /path/to/staging-version1-Output.xml -url "http://productionserver.example.com:port/wps/config" -user wpsadmin_user_ID -password wpsadmin_pwd

Parent Updates with syndication