Bypassing the load balancer to work on a specific server
To change object definitions and workflow on the administrative server in a load-balanced environment, you must bypass the load balancer to connect to the administrative server with BMC Remedy Developer Studio. The same consideration applies when you must make configuration changes on a specific server in the group in a browser.
To do this, you can connect to the server by using the unique server name rather than the load balancer name (which is the same as the common server name alias for the group).
To ensure that the server recognizes references to itself as the current server while designing workflow and applications, add the IP Name setting to the configuration file. This setting indicates to the server that any of a given set of server names is recognized as the current server. You might need to designate a short name and a long name for each server as shown in the following example:
IP-Name: serverA IP-Name: serverA.remedy.com
If BMC Remedy Developer Studio used either of these server names to log in, that server is recognized as the current server in workflow.