Deploying WebCenter

WebCenter uses a three-tier installation framework to facilitate in-house development and configuration before deploying it in production form. The three tiers are the Installation version, the Development version, and the Production version.

Deployment Workflow

The intended workflow is to install WebCenter, deploy it to Development, modify the Development version, and then when you are satisfied, deploy the Development version to Production.

As time goes by, you can keep modifying the Development version as desired without affecting the Production version. When you are satisfied with the changes made to the Development version, you can deploy it to Production.

At the time of deployment, the custom directory is not overwritten if it already exists in a target instance, so customizationConfig.xml and any other customized files in the custom directory are not changed. But when a new instance is created by deployment, the custom directory is created with its default configuration.

The WebCenter Deployment Manager

The WebCenter Deployment Manager, located in Start > Programs > WebCenter , manages the deployment process. If there is more than one website on the Web Server, choose the website with which the WebCenter Deployment Manager will work and click OK.

To further develop the installed version, use the WebCenter Deployment Manager:


You can have multiple development and deployment versions of WebCenter by changing the names for each deployment, e.g. DEV1, DEV_Other, WebCenter_Prod1, and so forth.

Also, the deployment name is not case sensitive, so for example WebCenter_Dev and WebCenter_dev are considered to be the same deployment instances.

Need More Help?Esko Help CenterSoftware Support PortalProduct information on