+

Search Tips   |   Advanced Search

Staging to production list

The items in the production list can be included in the staging to production Portal Application Archive (PAA) file. However, if we are not using the staging to production PAA file, use this list to determine the tools that are required to move your artifacts from the staging server to the production server. We can also use this list to determine what tool to use for the items not included in the staging to production PAA file. Within the Staging to production documentation, the following directories are the root directories where you place your subdirectories:


Themes and skins

Static resource options:


Portal Server artifacts

These artifacts are included by default in your initial or differential release PAA. If we are building a custom PAA, use an XMLAccess.xml file for installation or uninstallation.


WebDAV files


Personalization rules and campaigns

These artifacts are included by default in your initial or differential release PAA. Use these tasks if we are building a custom PAA.


Web Content Manager data

To include Web Content Manager data in your initial release PAA, use the -DexportWcmData=true parameter. For a custom PAA, then use the following tasks.Attention: Run the export task if the data set is less than 10,000 content items and behind a firewall. Syndicate the content if the data set is less than 10,000 content items and not behind a firewall. If the data set is large, clone the database and run the sycn-vanityurl-data task to synchronize your vanity URL data. Either clone the database or run the export task. Do not do both.


Portlet WAR files

These artifacts are included by default in your initial or differential release PAA. If we are building a custom PAA, choose one or more of the following portlet options:


Shared libraries

To create shared libraries in production, use the sharedAppResourcesRootDir and sharedExtResourcesRootDir parameters when we create the initial or differential release PAA. If we are deploying shared libraries manually, be sure that they are included on the production server and that their contents are up to date. Or, if we are manually creating a PAA, put the JAR files into either the shared/app or shared/ext directories of your custom PAA.


EAR files

To include EAR files in your initial or differential release PAA, use the -DappsToExtract parameter.

For a custom PAA, place files in the WebSpherePortal.paa\WebSpherePortal\components\WebSpherePortal.shared\installableApps\ear directory. This directory contains any EAR files that must be deployed to the application server. It also contains WAR files that do not contain any portlets and must be installed directly to the application server.


More components to stage

The following list contains portal components that are not handled by the initial import and are configured on each system outside of xmlaccess and PAA files.