Configuring Redundancy during eG Manager Configuration
When running the setup_manager script to set up an eG manager on Unix, the setup_cluster script in the /opt/egurkha/bin directory is automatically invoked. This script is used to configure redundancy, and when executed, requests for the following inputs:
First, the script requests a confirmation to enable the redundant manager capability of eG Enterprise.
Would you like to enable eG Manager redundancy y/n [n]? y
If n is specified, the setup_cluster script will automatically terminate.
If y is specified at step 1, you will then be required to indicate whether SSL has been enabled for the manager being configured.
Please indicate if your eG Manager uses SSL y/n :[n] n
Press y to indicate that the manager has been SSL-enabled, or n to deny it.
Next, indicate whether Network Address Translation (NAT) is being used for the manager being configured.
Please specify if you use Network Address Translation(NAT) y/n :[n] y
NAT facilitates multiple managers executing in different domains to communicate with one another. Specify y if any of the other managers in the redundant cluster have to use the NAT address of the current manager to communicate with it. If not, enter n.
If NAT is used (i.e., if y is specified at step 3), provide the NAT IP (or hostname), using which the managers interact with each other.
Please enter the NAT IP/hostname of this eG Manager:
Similarly, also indicate whether Port Address Translation (PAT) is used. PAT again comes into play only when the managers span multiple domains. In such a case, enter y. If not, press n.
Please specify if you use Port Address Translation (PAT) y/n :[n]y
If y is specified against PAT usage, then specify the PAT port number.
Please enter the PAT port: 8088
Then, specify y if the current eG manager uses a proxy server for communication with other eG managers in the cluster.
Please indicate if you would use proxy server for communications y/n :[n] y
If a proxy server is used, you will then have to provide the IP address (or hostname) and port number of the proxy server.
Please enter the hostname of the proxy: 192.168.10.60
Please enter the port of the proxy: 80
Indicate whether authentication is required for the proxy server, and if so, proceed to provide the user name and password to be used for the proxy.
Do you need authentication for the proxy? y/n [n]: y
Please enter the username to be used for the proxy: user
Please enter the password for user :
Please re-enter the password for user :
Next, state whether the manager being configured is to be set as the primary manager.
Is this a primary eG Manager y/n [n]? n
If the current eG manager is not a primary manager (i.e., if n is specified at step 10), then it is a secondary manager. Therefore, proceed to provide the IP address and port number of the primary manager with which this secondary manager communicates.
Please enter the hostname of the primary eG Manager: 192.168.10.59
Please enter the port of the primary eG Manager: 7077
- A target environment can have only one primary manager, and one secondary manager.
- Users with Admin privileges can login to the primary and the secondary managers, but he/she can access the eG administrative interface only when he/she logs into the primary manager.
- Monitor users can login to any of the eG managers in a redundant cluster.
- When running setup_cluster on a secondary manager, make sure that you specify the IP/hostname of the primary manager depending upon how you have configured the primary manager. In other words, if when installing and configuring the primary manager, you have provided the IP address of that manager, then make sure that you provide the IP address only when setup_cluster prompts you for the details of the primary manager on the secondary manager.
Finally, indicate whether the primary manager uses SSL or not by specifying y or n.
Please indicate if your primary eG Manager uses SSL y/n [n]: n
Once this is specified, the setup_cluster script will exit, and the setup_manager script will resume.
While configuring the two managers in the cluster, ensure that each of the managers uses a separate database. The databases used can be of different types - i.e., Manager A in the cluster can use an Oracle database, and Manager B can use an MS SQL server.