Most of the configuration tasks are same for a single Access Gateway and a cluster of Access Gateways.
This section describes the tasks that are specific to managing the servers in a cluster:
Use the Cluster Details page to perform general maintenance actions on the selected cluster and to display server information about the selected cluster.
In the Administration Console, click> > .
View the following fields:
Name: Specifies the name of the cluster.
Description: Specifies the purpose of the cluster. This is optional, but useful if your network has multiple Access Gateway clusters. If the field is empty, clickto add a description.
Primary Server: Indicates which server in the cluster has been assigned to be the primary server.
To modify the information, click Editing Cluster Details.. For more information, see
To select a different Access Gateway to be the primary cluster member, click.
To modify details about a cluster member, click the server name in thelist.
Use the Cluster Detail Edit to change the name of the cluster and assign a different server to be the primary cluster member.
In the Administration Console, click> > > .
Modify the following fields:
Name: Specify a name for the cluster.
Description: Specify the purpose of the cluster. This is optional, but useful if your network has multiple Access Gateway clusters.
Primary Server: Indicates which server in the cluster has been assigned to be the primary server. To change this assignment, select the server from the drop-down list.
When you are configuring services of the Access Gateway, thebutton saves the change to browser cache except on the Configuration page. The Configuration page ( > > ) provides a summary of the changes you have made. The column allows you to cancel changes to individual services. When you click , the changes are saved to the configuration datastore, and you no longer have the option to cancel changes to individual services.
If you don’t save the changes to the configuration datastore and your session times out or you log out, any configuration changes that are saved to browser cache are flushed. These changes cannot be applied to other members of the cluster because they are no longer available. To prevent this from happening, save the changes to the configuration datastore.
It is especially important to save the changes to the configuration datastore when you select to update individual members one at a time rather than update all members of the cluster at the same time. Updating members one at a time has the following benefits:
When you update all servers at the same time, the site goes down until one server has finished updating its configuration. If you update the cluster members one at a time, only the member that is updating its configuration becomes unavailable.
If you update the servers one at time, you can verify that the changes are behaving as expected. After testing the configuration on one server, you can then apply the saved changes to the other servers in the cluster. If you decide that the configuration changes are not behaving as expected, you can revert to the previously applied configuration. See Reverting to a Previous Configuration.
Some configuration changes cannot be applied to individual cluster members. For a list of these changes, see Modifications Requiring an Update All.
If you have updated only one server in the cluster, you can use the following procedure to revert back to the previous configuration.
Remove the server that you have applied the configuration changes from the cluster.
Access the Configuration page for the cluster, then click.
The servers in the cluster revert to the last applied configuration.
Add the removed server to the cluster.
The server is configured to use the same configuration as the other cluster members.
When you make the following configuration changes, theoption is the only option available and your site is unavailable while the update occurs:
If you change the Identity Server configuration that is used for authentication (> > then select a different value for the option).
If you select a different reverse proxy to use for authentication (> > , then select a different value for the option).
If you modify the protocol or port of the authenticating reverse proxy (> > > , then change the SSL options or the port options).
If you modify the published DNS name of the authentication proxy service (> > > > , then modify the option).