Setting Up Aliases for Remote Integration Servers
You can set up aliases for remote servers. Communication through the alias is optimized, making transactions with the remote server faster.
Use a remote alias when:
Invoking services on other Integration Server s . After you establish aliases, you can use the
pub.remote:invokeand
pub.remote.gd:*services to invoke services on remote servers by identifying the remote servers by their aliases.
Presenting multiple client certificates. The
Integration Server can present a single client certificate to all servers or it can present different client certificates to different SSL servers. In addition, the
Integration Server can present certificates provided for this purpose by other organizations. Setting up remote aliases for these SSL servers makes it easier to present different certificates to them. See
Authenticating Clients for more information.
Performing package replication. For a subscriber to set up a subscription with a publisher or pull a package from the publisher, you must define the publishing server as a remote server to the subscriber. The alias tells the subscribing server how to connect to the publishing server to set up the subscription or pull the package. See
The Subscribing Server for more information.
The definition for an alias contains the connection information the server requires to connect to a remote server. It identifies the host name or IP address of the remote server and indicates whether the server should use an HTTP or HTTPS connection to connect to the remote server.
The alias also identifies a user name and password that the server supplies to the remote server. The remote server uses the user name and password to authenticate the client and to determine if the client is authorized to execute the requested service.
In effect, the alias grants access to a remote service by allowing the user to impersonate an authorized user on the remote server. Therefore, to prevent unauthorized users from accessing services on remote servers, the alias also contains access control information. You specify an ACL that protects the use of the alias. If a client that is authorized to use the alias makes a request, the server will request the service on the remote server. If a client that is not authorized to use the alias makes a request, the server rejects the request and does not invoke the service on the remote server.
Integration Server has a predefined remote server alias named “local” that connects to the local Integration Server. This alias is used when resubmitting transactions from Monitor. The “local” alias uses the Administrator user account to connect to the local Integration Server. If you plan to use Monitor to resubmit failed requests, or to use the “local” remote server alias for other purposes, you must edit the “local” alias and set the Administrator password.