Enabling a Messaging Connection Alias
When a messaging connection alias is enabled, Integration Server can use it to send and receive messages from the messaging provider on behalf of publishing services and webMethods messaging triggers, respectively. Keep the following information about messaging connection aliases in mind:
When you enable a
Universal Messaging connection alias, the change takes effect immediately. Publishing services and triggers begin using the alias to send and receive messages from the messaging provider.
When you enable a
Broker connection alias, you must restart
Integration Server before the change takes effect. Publishing services and
webMethods messaging triggers do not begin using the alias to send and receive documents until after
Integration Server restarts.
The IS_LOCAL_CONNECTION messaging connection alias cannot be enabled or disabled. The alias is always available to
Integration Server for local publishing.
To enable a messaging connection alias
1. Open the Integration Server Administrator.
2. Go to Messaging > webMethods settings.
3. In the webMethods Connection Alias Definitions list, locate the messaging connection alias that you want to enable.
4. Click No in the Enabled column to enable the messaging connection alias.
For a
Universal Messaging connection alias,
Integration Server Administrator replaces
No with
Yes.
For a
Broker connection alias,
Integration Server Administrator replaces
No with
Yes [Pending Restart].
5. If this is a Broker connection alias, restart Integration Server for your changes to take effect.