DevOps Edition for Continuous Integration 10.5 | Integration Server Administrator's Guide | Quiescing the Server for Maintenance | Overview | What Happens when Integration Server Enters Quiesce Mode?
 
What Happens when Integration Server Enters Quiesce Mode?
When Integration Server enters quiesce mode, the server disables or suspends the following assets and activities:
*Ports. Integration Server disables all ports except the diagnostic port and the port used to enter and exit quiesce mode.
For details about specifying a port to use for quiescing the server, see Specifying the Quiesce Port.
*JMS messaging. Integration Server disables all JMS connection aliases and suspends all JMS triggers including SOAP-JMS triggers and web service endpoint triggers. This prevents the retrieval and processing of new messages. Any trigger services that are running attempt to execute to completion. For more information about how Integration Server suspends JMS triggers, see Configuring Integration Server to Enable JMS Triggers Automatically after a Consumer Error.
*MQTT Messaging. Integration Server disables all MQTT connection aliases and suspends all MQTT triggers. This prevents the retrieval and processing of new messages. Any trigger services that are running attempt to execute to completion. For more information about how Integration Server suspends MQTT triggers, see Changing the State of an MQTT Trigger.
*webMethods messaging. Integration Server disables all webMethods messaging connection aliases that specify Universal Messaging as the messaging provider. Integration Server also suspends document retrieval and document processing for webMethods messaging triggers, which includes webMethods messaging triggers that receive documents from Universal Messaging, Broker, or locally published documents from the Integration Server. Any trigger services that are running attempt to execute to completion. For more information about how Integration Server suspends document retrieval for webMethods messaging triggers, see Suspending and Resuming Document Retrieval. For more information about how Integration Server suspends document processing for webMethods messaging triggers, see Suspending and Resuming Document Processing.
*Packages. Integration Server disables all packages except WmRoot and WmPublic. The server unloads the packages and their resources, completes the package’s shutdown services, and disables the packages in memory.
When you switch a server from active mode to quiesce mode, you can specify the number of minutes the server should wait before disabling packages. If services are running, this wait time gives the services a chance to complete before the server disables the package in which they reside, or the packages in which their dependent services reside. If you do not specify a wait time, Integration Server disables packages immediately.
*Scheduled user tasks. Integration Server pauses the scheduler, permits the completion of any scheduled user tasks that are already running, and suspends any scheduled user tasks that have not yet started. If a running user task does not complete before its dependent services are disabled, the task will end in error because of the unresolved dependencies.
*Guaranteed delivery. Integration Server shuts down the inbound and outbound guaranteed delivery Job Managers and stops both inbound and outbound guaranteed delivery of documents. For outbound delivery, the server sets the watt property watt.tx.disabled to True to disable the use of guaranteed delivery for outbound requests.
Note: Because the server forcefully shuts down the inbound and outbound Job Managers when entering quiesce mode, in-process transactions may fail. Avoid submitting any transactions for processing as the server enters quiesce mode.
If you want to receive inbound guaranteed delivery requests while the server is in quiesce mode, you must first make sure the watt property watt.server.tx.heuristicFailRetry is set to True. Then, start the inbound Job Manager using the service pub.tx:init. The server will re-execute the services for transactions in the job store that are in PENDING status.
If you want to submit outbound transactions while the server is in quiesce mode, you must first set the watt property watt.tx.disabled to False. Then, start the outbound Job Manager using the service pub.tx:resetOutbound.
*Clustering. Integration Server shuts down all cache managers in the Integration Server_directory \instances\instance_name\config\Caching directory and exits the cluster.
The following activities continue when the server is in quiesce mode:
*Active tasks. Integration Server completes user tasks that were started before Integration Server entered quiesce mode. Integration Server continues to process scheduled system tasks while in quiesce mode.
*Audit logging. The server continues to write audit logging records to the database while in quiesce mode.
*Enterprise Gateway. If the Integration Server acting as the Internal Server is quiesced, the server disconnects any existing connections to the Enterprise Gateway Server and completes user tasks that were started before the server entered quiesce mode. If the Integration Server acting as the Enterprise Gateway Server is quiesced, the server’s external and registration ports are disabled, any existing connections to the Internal Server are disconnected, and any requests made by the Internal Server to the Enterprise Gateway Server will time out.
In an Enterprise Gateway scenario, you can avoid unnecessary connection attempts between the two servers by doing one of the following:
*Quiesce the Enterprise Gateway Server and the Internal Server at the same time.
*Disable the Enterprise Gateway registration port on the server that is not being put into quiesce mode.
For more information about webMethods Enterprise Gateway, see Configuring webMethods Enterprise Gateway .
Copyright © 2017-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.