Staging to production of theme artifacts
When you promote code from staging to production, you need to make sure to move all theme artifacts.
Theme artifacts fall into two categories:
When you promote code from staging to production, verify you move both categories of resources. You can move J2EE resources from staging to production by deploying or updating the EAR or WAR file. You can move static resources by one of the following ways:
- J2EE resources deployed in EAR or WAR files
- Static resources deployed to the WebDAV filestore
For more details about the specific locations of all theme related artifacts refer to the topic about the Location of Theme Resources.
- By using a manual copy operation. You can use a WebDAV client to copy the folder from the source portal server or cluster to the target portal server or cluster.
- By using the portal ConfigEngine configuration task webdav-deploy-zip-file .
Proceed as follows:
- Create a copy of the theme or the skin directory from development server by using WebDAV client. Make sure that all the files in this directory are checked into a source control library system such as Rational ClearCase.
- Create a deployable unit by creating a compressed file and adding that file to deployment package.
- Deploy this package to a portal server or cluster in another environment.
Follow the instructions given in the topic about the Task webdav-deploy-zip-file.
Develop custom themes
Location of theme resources
Task webdav-deploy-zip-file
Minor change Added description of two ways to deploy WebDAV artifacts