Deploying Quiesce Mode Configuration
When you specify a quiesce port, Integration Server maintains the port alias in the quiesce configuration file (quiesce.cnf). This file resides in the Integration Server_directory \instances\instance_name\config directory. The quiesce.cnf file is a deployable asset.
When you use webMethods Deployer to deploy the quiesce.cnf file to another Integration Server, keep the following points in mind:
The quiesce port you want to deploy must reside in either the WmRoot or the WmPublic package. Because all other packages are disabled when a server enters quiesce mode, the target server will not be able to enter quiesce mode if the quiesce port resides in a package other than WmRoot or WmPublic.
Packages that are installed with
Integration Server, such as WmRoot and WmPublic, are not deployable assets.
Deployer identifies these packages as unresolved dependencies when you include the quiesce.cnf file as part of the deployment set. Click
Ignore to bypass dependency checking for this situation.
If no quiesce port is specified on the target server, the target server uses the port specified in quiesce.cnf. Either ensure that this port exists on the target server or add the port to the list of deployable assets. The port should be of type HTTP or HTTPS.
You can substitute the quiesce port alias value during the mapping step in
Deployer.
For details about deploying assets using Deployer, see webMethods Deployer User’s Guide.