Deploy the initial release

After creating the initial staging and production servers, deploy staging contents to production. For clusters, deploy to the primary node.

1. Install, then deploy, the PAA file on the production server:

   cd WP_PROFILE/ConfigEngine 
   ./ConfigEngine.sh install-paa \
       -DPAALocation=/WebSpherePortal.paa \
       -DWasPassword=foo \
       -DPortalAdminPwd=foo \
       -Dwp.si.offlineMode=true
   ./ConfigEngine.sh deploy-paa \
       -DappName=WebSpherePortal \
       -DforceDeploy=true \
       -DWasPassword=foo \
       -DPortalAdminPwd=foo
   

2. Install, then deploy, the virtual portal PAA file on the production server.

    ./ConfigEngine.sh install-paa \
        -DPAALocation=/path/to/object_id.paa \
        -DWasPassword=foo 
        -DPortalAdminPwd=foo 
        -Dwp.si.offlineMode=true
   ./ConfigEngine.sh deploy-paa  \
       -DappName=object_id  \
       -DforceDeploy=true  \
       -DWasPassword=foo  \
       -DPortalAdminPwd=foo  \
       -DVirtualPortalParameter=value
   

   Where VirtualPortalParameter is one of the following options:

   -DVirtualPortalHostName=myvirtualportal.myco.com

   Host name of the virtual portal.

   -DVirtualPortalContext=VirtualPortal1

   Context root of the virtual portal.

   For deployment to multiple virtual portals, run list-all-virtual-portals on the source environment, to associate the VirtualPortalParameter value with the correct virtual portal.

   Anything included in the PAA file is included when you run this command, including WCM and EAR files. If created the PAA using the exportWcmData flag, then the WCM libraries are imported during the deploy step.

3. If we cloned your JCR database, attach the clone JCR database after doing the deployment for the base and virtual portals.

   The JCR database has objectids for the virtual portal that must match the source environment. The deploy-paa for the virtual portal does that task, but the deploy-paa for the virtual portals must be done before attaching to the cloned database.

   On the target server, synchronize the vanity URL data. The release database and JCR databases share some vanity URLs. If we clone the JCR database, the sharing is broken. This task fixes those errors.

   ./ConfigEngine.sh sync-vanityurl-data -DWasPassword=foo -DPortalAdminPwd=foo

4. Review the checklist. Export or manually re-create any items that cannot be packaged with the PAA file such as Resource Environment Providers and custom content.

5. If we use WSRP, review the configuration of the WSRP web services.

   • If we use the portal as a WSRP producer, manually re-create the web service security configuration of the WSRP service providers. See the WSRP services section.

   • If we use the portal as a consumer, verify the web service security configuration and manually re-create the web service security configuration if needed.

     1. If we configured producer ports using the Web Services admin portlet or xmlaccess, review the web service security configuration.

     2. If we configured WSRP web service clients, for example, by configuring WSRP service clients through policy sets in the WebSphere Administrative Console or by adding service references, manually re-create the configuration of the WSRP web service clients.

     3. If we configured web service security using an LTPA version 1 token, we can enable those tokens.

     4. If we configured HTTP-cookie-based single sign-on, for example, by configuring corresponding client cookie forwarding rules, review and re-create the resource environment properties for the cookie forwarding rules.

6. Optional: For alternative context root URLs, click...
   Administration menu | Search Administration | Manage Search

   Update the search collection URL links on the staging server to point to the alternative root. For example...

   http://yourdomain.com:port/your_root/seedlist/myserver?SeedlistId=&Source=com.ibm.workplace.wcm.plugins.seedlist.retriever.WCMRetrieverFactory&Action=GetDocuments

7. If we installed any additional PAAs on the staging server, they are not included in the initial release PAA. Each additional PAA that was installed and deployed on the staging server must be manually installed and deployed on the production server after the initial release PAA is installed.

8. Restart the server.

Parent Staging to production

Related concepts:

WSRP services