In production environment, it is indeed required to have multiple access servers as Primary/Secondary or to be used a Access Server cluster for all WebGates in the same deployment. This is specific to OAM 10g.
Let us assume that there are 3 access servers totally out of which 2 are designated as Primary and other as Secondary. Hence primarily the requests will be handled by Primary Servers unless one/all of the access servers goes down. I am going to explain how to attach multiple access servers to a webgate either while installing the webgate or during webgate reconfiguration.
At first, we would need to attach the Access Servers to WebGate in profile as shown below.
However, if you are installing WebGate 10g or reconfiguring webgate, there is no option to specify Primary/Secondary Access Servers or Access Server Cluster. So I thought it is worth to let you all the procedure.
While installing the WebGate, we can provide one of the Primary Access Server ID and Access Server hostname (of the same webgate) so that WebGate will check the Access Server ID in OAM Configuration Store and finds that Primary/Secondary servers are available and accordingly will update the ObAccessClient.xml (present in $WEBGATE_HOME/access/oblix/lib) as shown below.
Blocks marked in RED specify that there are 2 Primary Servers configured and respective access server details are marked in PINK blocks.
Secondary Access Server details are shown in below screenshot.
Comments are closed.