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 Broker. The Broker Manager displays this prefix for each client it creates for the server. (The Broker creates multiple clients for each server that connects to it.) |
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: ![]() ![]() For more information about configuring Integration Servers to receive messages from the Broker in a load-balanced fashion, see Load Balancing with a Non-Clustered
Group of Integration Servers. |
For this parameter... | Specify... | ||
Broker Host | Name (DNSname: port or ipaddress: port) of the machine on which the Broker Server resides. | ||
Broker Name | Name of the Broker as defined on the Broker Server. The default name is Broker #1. | ||
Client Group | Broker client group to which this Integration Server belongs. A client group defines a single set of properties and access permissions assigned to one or more clients (here, Integration Servers) on a single Broker. If the specified client group does not exist, the Integration Server creates it on the named Broker upon establishing its initial connection.
|
For this parameter... | Specify... | |
Client Authentication | The type of authentication an Integration Server client will use to connect to the Broker. Choose one of the following options: ![]() ![]() ![]() | |
Parameter... | Specify... | |
Keystore | The full path to the keystore file for this Integration Server. A keystore file contains the credentials (private key/signed certificate) that an entity needs for SSL authentication. If the Broker Server requires an SSL connection, then the information in this file is used to authenticate the Integration Server client to that Broker Server. The keystore file for an Integration Server is stored on the machine on which the Integration Server resides. | |
Keystore Type | The file type of the keystore file for Integration Server. The file type can be either PKCS12 or JKS. | |
Keystore Password | Password required to access the SSL certificate in the keystore file for Integration Server. |
For this parameter... | Specify... | |||
Encryption | Specify whether or not to encrypt the connection between the Integration Server and the Broker.
If you select Yes for the Encryption parameter, configure the following truststore parameters. | |||
Parameter... | Specify... | |||
Truststore | The full path to the truststore file for the Integration Server client. A truststore file contains trusted root certificates for the authorities responsible for signing SSL certificates. For an SSL connection to be made, a valid trusted root for the SSL certificate stored in the keystore must be accessible in a truststore file. The truststore file for Integration Server is stored on the machine on which the Integration Server resides. | |||
Truststore Type | The file type of the truststore file for Integration Server. The file type is JKS. |
Note: | You can configure the outbound document store, also known as the client side queue, to contain documents published when the Broker used by this connection alias is not available. For more information, see About the Outbound Document Store |