What Happens when Integration Server Exits Quiesce Mode?
When Integration Server exits quiesce mode, the server:
Retains state changes made to any assets during the quiesce session. For example, if you enabled a package that was disabled before the server entered quiesce mode, the package remains enabled when the server exits quiesce mode. If you created a package and then disabled it, the package remains disabled when the server exits quiesce mode.
Restores the state of any unchanged assets to their state before the server entered quiesce mode. For example, if a scheduled user task was suspended before the server was quiesced, the task remains suspended when the server exits quiesce mode.
Resumes the task scheduler.
Resumes clustering activities.
If Integration Server encounters any errors that prevent it from joining the cluster when exiting quiesce mode, Integration Server does not re-enter quiesce mode. Instead, Integration Server runs as an unclustered, stand-alone server. Integration Server logs any errors that occurred while attempting to join the cluster in the report that appears in Integration Server Administrator after exiting quiesce mode. Use the report and error logs to help correct the underlying configuration errors. Then, to rejoin the cluster, either restart Integration Server or enter and then exit quiesce mode.
Starts the guaranteed delivery inbound and outbound Job Managers, if you did not start them while the server was in quiesce mode. The server also sets the watt property watt.tx.disabled to False and resumes inbound and outbound guaranteed delivery of documents.