Staging to production list

Use this list to determine the tools that are required to move your artifacts from a staging server to your production server.

Within the Staging to production documentation, the following directories are the root directories where you place your subdirectories:
  • For the base portal: SampleBase
  • For the Virtual Portals: Sampele1

Themes and skins

Choose one of the following static resource options:

Static resources in the WebDAV file store
Follow the staging to production documentation to export and import your themes and skins. See Developing themes for a production portal.
Directory structure
Compress the files that contain static theme content and place them in the content/webdav directory. This placement allows the themes to be automatically uploaded to the dav:fs-type1/themes/ directory in the WebDAV file store.
Static resources in an .ear file
Follow the staging to production documentation to export and import your themes and skins. See Developing themes for a production portal.
Directory structure
Place the theme .ear files in the InstallableApps/ear directory.

Portal Server artifacts

The following is a list of portal server artifacts:
  • action
  • client
  • component
  • content-node (pages)
  • credential-segment
  • device-class
  • global-settings
  • language
  • markup
  • resource-type
  • skin (definition)
  • task
  • theme (definition)
  • services-settings
  • servlet (definition)
  • portal
  • portlet-app
  • portlet
  • portletinstance
  • transformation
  • transformation-app
  • transformationinstance
  • url-mapping-context
  • virtual-resource
  • web-app
  • wsrp-producer
  • cross-page-wire
  • wire
XMLAccess .xml files (for installation)
Place these files in the following directory: content/xmlaccess/install.
Note: These files might contain the statements to install portlets and transformations out of the war directory and to create pages.
XMLAccess .xml files (for uninstallation)
Place these files in the following directory: content/xmlaccess/uninstall.
Note: These files might contain the statements to remove portlets, transformations, and pages.
References
For information about the portal XML configuration interface and how to work with it see Working with the XML configuration interface and XML configuration reference.

WebDAV files

Directory
Place these files in the webdav directory. This directory and its subtree structure contain artifacts that must be uploaded to the WebDAV file store. There are the following possible subdirectories:
  • themes
  • skins
  • layout-templates
  • common-resources
References
See Exporting content from the filestore.

Personalization rules and campaigns

Task
Use the pznload task to export and import the rules and campaigns.
Directory
Place the files in the content/pzn directory. Personalization related artifacts, such as JAR files that contain business rules and personalization .nodes files, are in this directory.
References
See Staging Personalization rules to production.

Web Content Manager data

Attention: Run the export task if the data set is small and behind a firewall. Syndicate the content if the data set is small and not behind a firewall. If the data set is large, you should consider cloning your database. See Cloning preparation to determine if your environment can clone the database.
Export task
Use the export-wcm-data task to export Web Content Manager data.
Import task
Use the import-wcm-data task to import Web Content Manager data.
Directory
Place the files in the content/wcm directory. Each subdirectory represents a separate web content library. These libraries are a specialized form of JCR artifact. Web content libraries are separated into their own directory.
References
See Exporting and importing web content libraries.

Portlet WAR files

Choose one or more of the following portlet options:

JSR 168 and JSR 286 Portlets (without an XMLAccess script to deploy)
Place these portlets in the following directory: InstallableApps/portlets.
JSR 168 and JSR 286 Portlets (with an XMLAccess script to deploy)
Place these portlets in the following directory: InstallableApps/war.
IBM API Portlets
Place these portlets in the following directory: InstallableApps/war.
Note: IBM legacy portlets are not handled automatically. These portlets are copied to the archive and must be installed by an accompanied XMLAccess script.
Transformation .war files
Place these portlets in the following directory: InstallableApps/war.
Note: These .war files are not handled automatically. These files are copied to the archive and must be installed by an accompanied XMLAccess script.

Shared libraries

For globally available JAR files, place the JAR files into either the shared/app or shared/ext directories. These files are not copied to the equivalent directories.

EAR files

Places files in the 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 all portal components that are not handled by the initial import. Use the information in the following list to install the component on each system that is involved in the staging to production process.
Portal Server Performance Tuning parameters
Follow the performance tuning guide: Performance
Active Site Analytics Statistics
There are no applicable tools for exporting or importing Active Site Analytics Statistics. Statistics from staging server are not typically exported or imported. See Analyzing portal usage data.
WebSphere® Application Server Resource Environment Providers (Portal service settings are stored as Resource Environment Providers)
Run the wsadmin task to export. Run the following ConfigEngine task to import: update-properties.
See the following documentation:
External Security Manager
Follow the staging to production documentation. See Staging and external security managers.
Custom components
The following items are custom components:
  • Custom login commands
  • Custom credential vault adapters
  • Custom credentials
  • Custom component property files

Custom components are not part of IBM WebSphere Portal. Custom components that are developed by the customer must be manually re-created on each system that is involved in the staging to production process.