Alternative_Server_0, Alternative_Server_1,... Alternative_Server_<n>
Strings which specify server access profiles within the Web Gateway’s routing behavior for the application access profile, and whether those InterSystems IRIS application servers are enabled or disabled within the application access profile. When failoverOpens in a new tab is enabled, the Web Gateway attempts to route requests for the application to the application server identified by the Alternative_Server_0 parameter, then the Alternative_Server_1 parameter, then Alternative_Server_2, and so on. The Web Gateway can continue this failover behavior for an arbitrary number (<n>) of alternative servers—in other words, up to the Alternative_Server_<n> parameter.
Each Alternative_Server_<n> parameter begins with a bit specifying the status of the application server within the application access profile (1 for enabled, 0 for disabled) and ends with the name of the server access profile for the desired InterSystems IRIS application server. When the Web Gateway updates the value of this parameter, it separates the status and the server access profile name using an arbitrary number of ~ characters, for legibility.
For example, if you want to specify that the third active InterSystems IRIS application server in your application’s failover sequence should be the server which corresponds to a server access profile named irisserv1, then you would add the following line to the application access profile block:
Alternative_Server_2=1~~~~~~irisserv1