Configure Duplicate Gateway Administrator Systems

To support high availability, you will configure and test an initial instance of Gateway Administrator, then create an identically-configured Gateway Administrator system and use a load-balancing proxy to distribute the load between these systems. Each Gateway Administrator system must:

Use a common database.
Use identical server certificates.
Use identical copies of the Gateway Administrator properties file (container.properties).
Use identical Job templates (if this optional feature is configured).

NOTE:Configuring more than two Gateway Administrator systems will not improve performance and may lead to slower response rates.

Before you begin

Run the Setup program on each system that will run Gateway Administrator. Use the Features tab to install the Reflection Gateway Administrator feature. Restart Windows on each system. This starts the service and creates initial default settings files.
Select one of the Gateway Administrator systems for initial configuration and testing. After you have this instance working, you will copy required files to duplicate the configuration on your second system.

Configure an initial Gateway Administrator system

Configure Gateway Administrator to use an external database. The database should be located on a different system from each of the systems that will run Gateway Administrator. (This database should be configured for failover, for example using a Microsoft cluster. This procedure is not included here.)
If you are using a CA-signed certificate for server HTTPS authentication, replace the default self-signed server certificate with the CA certificate and test connections using the new certificate. See Replace the Default Server Certificate. This certificate should be configured to authenticate the server name that will be used for connecting to you your load-balancing proxy.
If you are using Transfer Site email notifications, configure the URL that will be used to create links in email messages. This requires an edit to the container.properties file.
If you are using Job templates, configure and test a jobTemplate.xml file.
Log onto Gateway Administrator and test your configuration.

Copy required files to the duplicate Gateway Administrator system

Locate the Gateway Administrator folder on your initial system. The default location is:

C:\Program Files\Micro Focus\ReflectionGateway\GatewayAdministrator\

Copy the following files to the duplicate system.

Files	Details
container.properties	In the conf subfolder. Includes settings and password for connecting to the database. If configured, it includes the URL used in email notifications, and settings for using a CA-signed certificate.
server.cer server.jks	In the etc subfolder. A private key stored in server.jks is used to encrypt passwords for LDAP servers, SFTP servers, and SMTP servers. An identical private key must be present in each system to enable each server to encrypt or decrypt these passwords.
servletcontainer.cer servletcontainer.jks -OR- Your CA-signed certificate package (typically a .p12, .pfx, or .jks file)	These files contain the certificate and private key used to authenticate the server when users make HTTPS connections to Gateway Administrator. If you are using the default self-signed certificate, copy servletcontainer.cer and servletcontainer.jks located in the etc subfolder. If you are using a CA-signed certificate, find the certificate package file in the location specified in the container.properties file. For example: servletengine.ssl.keystore=../etc/fips-compliant-cert.p12 Copy this file to the same location on each of the other systems.
jobTemplate.xml	In the conf subfolder. This file is only needed if you have configured a Job template.