Name that you want to use for the alias. You can give the remote server any alias name but it cannot include the following illegal characters: #-&@^!%*:$./\\`;,~+=)(|}{][><" .

Host name or IP address of the remote server for which you are creating an alias (e.g., workstation5.webmethods.com).

Port number on which the remote server listens for incoming requests from your server (e.g., 5555).

User name for a user account on the remote server. When you invoke a service using this alias, the remote server uses this user account for authentication and access control. Specify a user name that has access to the services you want to invoke on the remote server.

Password identified in the user account for User Name.

ACL that governs which user groups on your server can use this alias for the remote server. Select an ACL from the drop down list. By default, only members of groups governed by the Internal ACL can use this alias.

Sets the default number of client keep alive connections to retain for a given target endpoint. If not specified, five keep alive connections are retained. This field specifies the maximum number of client connections that should be retained for any given remote host. In other words, this is not a maximum number of connections that can be established, but a limit on the number of inactive client connections to retain for reuse.

Specifies the length of time (in minutes) that your server maintains an idle connection to a remote server. This value will cause the connection to be retained for possible reuse until it times out. If the specified keep alive timeout value expires, the connection will close and the HTTP Listener will attempt to create a new one.

Whether you want your server to connect to the remote server using Secure Sockets Layer (SSL). If you want to use SSL, select yes; otherwise, select no.

A user-specified, text identifier for an Integration Server keystore.

The alias points to a repository of keys and their associated SSL certificates.

The alias for the Integration Server private key and associated certificate, which must be stored in the keystore specified by the above keystore alias.

You must create a key alias with a third-party certificate utility, such as Java keytool. You cannot create a key alias with Integration Server Administrator.

Host name or IP address (for example, workstation6.webmethods.com) of a remote server you want your local Integration Server to connect to if the primary remote server is unavailable. The retry server you specify will use the same port as the primary remote server. If the remote server is part of a cluster, the local Integration Server will, by default, try to connect to other Integration Servers in the cluster before trying to connect to the retry server. If clients are using the pub.remote:invoke service to run services on a remote server, it is possible to change this default behavior by using the $retryCluster input parameter with the service. If you set this parameter to false, the service will not try to use other Integration Servers in the cluster. Instead, the service will immediately try using the retry server specified on this page.