Tools for staging to production

Export and import artifacts independently

Each type of artifact can be exported, moved to the target, and imported independently. For example, to install ear files and import portal artifacts ...

cd $PROFILE_HOME/bin
./App_Install.sh

./xmlaccess.sh -user wpsadmin@myco.com \
               -password wpsadmin \
               -url host1:10040/wps/config/usa \
               -in deregister-usa-myco-content.xml \
               -out /tmp/deregister-usa-myco-content.out

./xmlaccess.sh -user wpsadmin@myco.com \
               -password wpsadmin \
               -url host1:10040/wps/config \
               -in install-myco-content.xml \
               -out /tmp/install-myco-content.out

./xmlaccess.sh -user wpsadmin@myco.com \
               -password wpsadmin \
               -url host1:10040/wps/config \
               -in register-themes-and-skins.xml \
               -out /tmp/register-themes-and-skins.out

./xmlaccess.sh -user wpsadmin@myco.com \
               -password wpsadmin \
               -url host1:10040/wps/config/usa \
               -in register-usa-myco-content.xml \
               -out /tmp/register-usa-myco-content.out




Package artifacts into an archive file

1. Place all artifacts into the PAA archive file
2. Copy the PAA file to the target
3. Use the Solution Installer to deploy the PAA file




Stage WCM content using network

We can synchronize WCM libraries from authoring environments to target isystems using network connections between.

Because portal pages refer to portlets with the Object_ID of the portlets, an initial staging needs to take place before syndication can be used.


Parent Overview of staging to production