How to minimize down time with the WCBD tool during the deployment process

Technote (FAQ)


The WebSphere Commerce Build and Deploy tool (WCBD) helps automate the WebSphere Commerce application deployment process.

To minimize downtime in a production clustered environment, what configurations should be considered?


The following factors should be considered to minimize downtime in a production clustered environment:

1. Set rollout.update to true.
Navigate to your file.

For Example:
/opt/IBM/WebSphere/CommerceServer70/wcbd/deploy/server/ (This is a sample path. Use your deployed properties file.)

Find the following snippet:


# rollout.update
# "true" if roll-out update should be executed; "false" otherwise. This option
# only works for clustered environments w/ DMGR.

Change 'rollout.update=false' to 'rollout.update=true'

This enables roll-out updates to occur against all cluster members, keeping the system up for high availability.

2. Disable automatic synchronization on the nodes during the roll-out update event.
Follow the steps in the following document: File synchronization service settings.

3. WebSphere Application Server has the following timeout properties that can be set on the Deployment Manager (DMGR) to either stop or start the AppServer JVMs.

More information on these properties is provided in WebSphere Application Server Information Center: Java™ virtual machine custom properties.

Example settings are: serverStopWaitTimeout = 1800 and appExpansionTimeout=900, as an initial starting point.

Document information

More support for:

WebSphere Commerce Enterprise

Software version:


Operating system(s):

AIX, IBM i, Linux, Solaris, Windows

Software edition:


Reference #:


Modified date:


Translate my page

Content navigation