Editing a Messaging Connection Alias

You can edit the properties of any messaging connection alias that you create or some of the default messaging connection aliases created by Integration Server. Keep the following points in mind before editing a messaging connection alias:

You can edit any properties of an existing messaging connection alias with the exception of the connection alias name.

You must disable a messaging connection alias before you can edit it. If the alias is not disabled, the Edit messagingConnectionAlias name link will not be hyper-linked.

If you change the client prefix for an existing Universal Messaging connection alias, Integration Server creates new durable objects on Universal Messaging for triggers that use the alias. The durable objects that use the old client prefix are not automatically removed from Universal Messaging. Old durable objects might contain messages and continue to receive messages.

For the IS_DES_CONNECTION alias, you can edit the description and client prefix only. If the Integration Server is part of a cluster (stateless or stateful), the client prefix for the IS_DES_CONNECTION connection alias needs to be the same on each Integration Server.

You cannot edit the IS_LOCAL_CONNECTION alias.

5. Do one of the following depending on whether you are editing a Broker connection alias, Universal Messaging, or Digital Event Services connection alias:

Note:
If the Edit messagingConnectionAliasType link appears but is not available, that is, it is not hyper-linked, the messaging connection alias might not be disabled. You can only edit a disabled messaging connection alias.

8. Enable the messaging connection alias. For more information about enabling a messaging connection alias, see Enabling a Messaging Connection Alias.

10. If this is a Universal Messaging connection alias used for writing or reading logging entries to a Universal Messaging queue, you must restart Integration Server for changes to take effect.

If you changed a Broker connection alias to connect to Broker in another territory, you might need to synchronize your publishable document types with the new Broker. For information about synchronizing publishable document types, see webMethods Service Development Help.

If you change the client prefix of a Universal Messaging connection alias for which the Enable Request/Reply Channel and Listener check box is selected, Universal Messaging creates a new request/reply channel with the new client prefix. However, Universal Messaging does not delete the previous request/reply channel for the Universal Messaging connection alias. Use Universal Messaging Enterprise Manager to delete the old channel.

If you edit a Universal Messaging connection alias by clearing the Enable Request/Reply Channel and Listener check box is selected, the request/reply channel for Universal Messaging connection alias remains on the Universal Messaging server. If you want to delete the channel, use Universal Messaging Enterprise Manager to delete the channel.

For a Universal Messaging connection alias used by loggers to write log entries to or read log entries from a Universal Messaging queue, the state of the Client Prefix Is Shared check box determines whether or not the client prefix of the alias is included in the Universal Messaging queue name. If you edit a Universal Messaging connection alias by selecting or clearing the Client Prefix Is Shared check box and the alias is used by loggers, you must restart Integration Server for changes to the queue name to take effect. Additionally, you must make the same changes to other Integration Servers in the cluster or non-clustered group of Integration Servers that use the alias.