Note: | You can create a Universal Messaging connection alias for use with webMethods Universal Messaging 9.5 and higher. However, if you want to use Integration Server with an earlier, supported version of Universal Messaging, you must manually replace files in Software AG_directory \common\lib with the those available in the version of Universal Messaging that you want to use. For more information about replacing client libraries, see Adding Client Libraries for Earlier
Versions of Universal
Messaging
. |
For this parameter... | Specify... |
Connection Alias Name | A unique name for the messaging connection alias. |
Description | A description of the messaging connection alias. |
Client Prefix | A string that identifies the Integration Server to Universal Messaging. If your Integration Server belongs to a cluster, make sure all servers in the cluster use the same client prefix. |
Share Client Prefix | Whether Integration Server shares the client prefix with multiple Integration Servers. Leave the check box cleared if you do not want the client prefix to be shared. You must select Share Client Prefix if the Integration Server: Belongs to a cluster. Belongs to a non-clustered group of Integration Servers that operate in a load-balanced fashion. For more information about configuring Integration Servers to receive messages from Universal Messaging in a load-balanced fashion, see Load Balancing with a Non-Clustered
Group of Integration Servers. |
For this parameter... | Specify... | ||
Realm URL | The URL for the Universal Messaging server in the format protocol:// UM_host: UM_port where protocol is the protocol for the port., such as nsp, nsps, or nhps. For example, nsp://127.0.0.1:9000 or nsps://localhost:9000). If the protocol for connecting to Universal Messaging server is nsps or nhps, you must configure the connection alias to enable Integration Server to connect to an SSL-enabled port on Universal Messaging. You must set Client Authentication to SSL and provide truststore and possibly keystore information. If you are using a cluster of Universal Messaging servers, supply the list of URLs to each server in the cluster using a comma or a semicolon: Separate the URLs using a comma if Integration Server always attempts to connect to the first Universal Messaging server in the list, only trying the second Universal Messaging server in the list if the first server becomes unavailable. Separate the URLs using a semicolon if Integration Server connects to a randomly chosen URL from the list. This may result in better distribution of clients across the servers in the cluster.
| ||
Maximum Reconnection Attempts | Specify the maximum number of reconnection attempts that Integration Server makes if the connection to Universal Messaging fails. If the connection cannot be re-established, Integration Server writes messages to the error log and the connection created by this messaging connection alias will be stopped. The default is 5 attempts.
|
For this parameter... | Specify... | ||
Enable CSQ | Whether a client side queue is used with this Universal Messaging connection alias. Do one of the following: Select the Enable CSQ check box if you want to use a client side queue with this Universal Messaging connection alias. When a client side queue is in use, if the Universal Messaging server is not available when Integration Server publishes documents using this Universal Messaging connection alias Integration Server writes the documents to the client side queue. Clear the Enable CSQ check box if you do not want to use a client side queue with this Universal Messaging connection alias. When a client side queue is not in use, if the Universal Messaging server is not available when Integration Server publishes documents using this Universal Messaging connection alias, the publishing service ends with an ISRuntimeException. | ||
Maximum CSQ Size (messages) | The maximum number of documents (messages) that can exist in the client side queue for this Universal Messaging connection alias. If the client side queue is at capacity, publishing services that use this connection alias will end with an ISRuntimeException. Specify -1 if you want the client side queue to be able to contain an unlimited number of messages. | ||
Drain CSQ in Order | Whether Integration Server drains the client side queue for this alias by sending the messages to the Universal Messaging server in the same order in which Integration Server placed the messages in the client side queue. Select the check box if you want Integration Server to send messages from the client side queue in the same order in which Integration Server originally placed the messages in the client side queue. When the Drain CSQ in Order check box is selected, after the connection to the Universal Messaging server s re-established, Integration Server continues to write new messages to the client side queue until the client side queue is completely drained. If the Drain CSQ in Order check box is not selected, after the connection to the Universal Messaging server re-established, Integration Server sends new messages directly to the Universal Messaging server while it drains the client side queue. | ||
Publish Wait Time While Reconnecting | The number of milliseconds that a publishing service using this Universal Messaging connection alias will wait for a connection to the Universal Messaging server to be re-established after the connection fails. If Integration Server re-establishes the connection before the Publish Wait Time While Reconnecting elapses, the publishing service continues executing. If the specified time elapses before a connection is re-established, the publishing service ends with an ISRuntimeException. The default is 0 milliseconds, which means that publishing services will not wait for Integration Server to re-establish the connection.
|
For this parameter... | Specify... | |||
Client Authentication | The type of authentication an Integration Server client will use to connect to the Universal Messaging server. Choose one of the following options: None. Select this option if no authentication should be performed. This is the default. Username/Password. Select this option if the Universal Messaging server performs basic client authentication using user name/password combinations. If you select this option, specify the user name and password the client will use in the Username and Password fields. SSL. Select this option if Integration Server connects to a secure socket layer (SSL) port on Universal Messaging. If the Realm URL specifies nsps or nhps as the protocol, you must select SSL. | |||
Truststore Alias | The alias for the truststore that contains the certificate authority (CA) certificates for the Universal Messaging server. You must select a truststore alias if the Universal Messaging port is configured for either one-way authentication or two-way authentication. | |||
Keystore Alias | The alias for the keystore that contains the client certificates that you want Integration Server to use when connecting to the Universal Messaging port. You must select a keystore alias if the Universal Messaging port is configured for two-way authentication.
| |||
Key Alias | The alias to the key that contains the private key for connecting to the Universal Messaging port securely. The key alias must be in the keystore specified in Keystore Alias. You must specify a Key Alias if you specify a Keystore Alias. |
Note: | For more information about configuring a Universal Messaging to connect to an SSL-enabled port on Universal Messaging see Configuring Integration Server to Connect to an SSL-Enabled Port on Universal
Messaging
. |