Posted Oct 30 by Edmund Clayton.
Updated Oct 31.

Learn how to improve resilience and reliability of the OpenText AppWorks Gateway by deploying the Gateway in a cluster.

Last activity Oct 31 by Edmund Clayton.
248 views. 0 comments.

Chapter 8 – Deploying the OpenText AppWorks Gateway in a Cluster

You can deploy and configure additional AppWorks Gateway servers to use an existing AppWorks Gateway database. Any application, service, or component that is installed on one node in the cluster is automatically installed on all of the other nodes. All settings changes are also propagated to all of the nodes. You do not need to perform any manual steps on any other node or restart the Apache Tomcat service. However, you must restart the Apache Tomcat service if you change any of the following settings in the AppWorks Gateway:

  • On the Notifications page, changes to the Back-channel Stale Connection Cleanup Period (s) will only take effect when the current period elapses or when the Apache Tomcat servers are restarted.

  • On the General Settings page, changes to the Session Token Cleanup Interval (s) and the Session Token Timeout (s) will only take effect once the current interval elapses or when the Apache Tomcat servers are restarted.

  • On the Temp File Settings page, changes to the Temporary Directory Path should be done when the servers are off-line, because some services may lose temporary data. Changing the Temporary Directory Path may leave old temporary files in the former location. The Temporary Directory Path location must exist on disk before changing the path in the AppWorks Gateway. The location on disk must be the same on all nodes in the cluster. The default location is C:\Program Files\Apache Software Foundation\Tomcat 8.0\tmp.

    Note: The location of the Temporary Directory Path must be exclusive to each node in the cluster. It must not be physically accessible or shared by any other node in the cluster.

  • On the Temp File Settings page, changes to the Temporary File Cleanup Interval (s) will only take effect when the current interval elapses or when the Apache Tomcat servers are restarted.

    Note: In most cases, you should not change these settings.

Clients that are connected to one node can also switch to another node and continue functioning.

To deploy AppWorks Gateway on additional nodes:

  1. Install Apache Tomcat on the new node. For details, see Chapter 1 - Installing the OpenText AppWorks Gateway.

  2. Stop the Apache Tomcat service on each node.

  3. Extract the contents of the otag-gateway-16.7.zip file to the root of the Apache Tomcat folder, for example, C:\Program Files\Apache Software Foundation\Tomcat 9.0.

  4. Start the Apache Tomcat service.

    Tip: Navigate to the <Tomcat_Home>\logs folder and open the catalina.<yyyy-mm-dd> file. When you see a line containing INFO: Server startup in <55278> ms, you can start to configure the AppWorks Gateway.

  5. Complete the database configuration steps to connect to the database you are using for all nodes in the cluster

  6. Configure a load-balancer in front of the OpenText AppWorks Gateway nodes. When complete, sign in to the OpenText AppWorks Gateway, click Settings, and edit the AppWorks Gateway Server URL to point to the load-balancer's address.

    Note: Repeat this procedure at any time to add nodes to the cluster. They must also be added to the load-balancer.

Top of page



Table of Contents

Your comment

To leave a comment, please sign in.