Aliases
Aliases provide a consistent way to address dynamically configured hosts. To avoid the loss of proxy configuration data when names are changed, aliases are recommended.
Aliases provide flexibility so you can have multiple aliases pointing to the same real remote server, or you can have one alias pointing to another alias. You can also use aliases to prevent confusion for your users. You can instruct them to use the alias (a name that is easy to remember and unlikely to change) with an unspecified or 0 port number.
The following example illustrates a typical set up for the use of aliases. The configuration properties shown are contained in the is.properties file. Corresponding user connection preferences are also detailed in the sample.
#Federated Server Architecture settings
#
mksis.proxyList=intranet:7001,Europe,NorthAmerica
#
mksis.Europe.targetServerID=si-europe:9001
mksis.Europe.9001.targetServerID=si-europe:9001
mksis.NorthAmerica.targetServerID=si-na:9001
mksis.NA.targetServerID=NorthAmerica
In this configuration, the host Integrity Lifecycle Manager server proxies for three remote servers: intranet:7001, si-europe:9001, and si-na:9001.