About Disabling a Message Connection Alias
You can disable any messaging connection alias on Integration Server. A disabled messaging connection alias cannot be used to send messages to or receive messages from the messaging provider specified in the alias. Specifically, when a messaging connection alias is disabled:
Publishing services that use the disabled alias end with an ISRuntimeException.
webMethods messaging triggers that use the alias are suspended.
When you disable a Universal Messaging connection alias, you do not need to restart Integration Server for the change to take effect.
Publishing services that use the alias receive an ISRuntimeException as soon as the messaging connection alias is disabled.
Before suspending
webMethods messaging triggers that use the alias
Integration Server waits a short time for triggers to finish processing messages the triggers already received.
Integration Server considers message processing to be complete if the trigger service executes to completion (success or failure) and the trigger acknowledges the message to the message provider. If the trigger service is long running and cannot complete in the allotted time,
Integration Server disables the trigger and considers message processing to be incomplete.
Note: Suspending a trigger does not stop the trigger service. Consequently, even after Integration Server suspends the webMethods messaging trigger, the trigger service will execute to completion. After the trigger service completes, Integration Server attempts to acknowledge the message to the messaging provider. However, the acknowledgment attempt fails because the messaging connection alias is disabled. If the message is guaranteed, the messaging provider redelivers the message when the messaging connection alias is enabled and the trigger resumes. Redelivery of messages can result in duplicate processing.
When you disable a Broker connection alias, you must restart Integration Server for the change to the alias to take effect. The Broker connection alias is not actually disabled until Integration Server restarts. This means that publishing services and webMethods messaging triggers that use the alias continue to send and receive messages until restart occurs. Upon restart, Integration Server suspends any webMethods messaging trigger that use the messaging connection alias. Additionally, after restart, any publishing services that use the messaging connection alias will end with an ISRuntimeException.
Note: The IS_LOCAL_CONNECTION messaging connection alias cannot be enabled or disabled. The alias is always available to Integration Server for local publishing.