Support Policies for RHEL High Availability Clusters - Management of a tomcat Server in a Cluster

Updated -

Contents

Overview

Applicable Environments

  • Red Hat Enterprise Linux (RHEL) with the High Availability Add-On

Useful References and Guides

Introduction

This guide offers Red Hat's policies and requirements around the management of a tomcat server by a RHEL High Availability cluster. Users of RHEL High Availability clusters should adhere to these policies in order to be eligible for support from Red Hat with the appropriate product support subscriptions.

Policies

tomcat releases and Red Hat resource-agents: Red Hat's tomcat resource-agents are developed with a target of managing the releases of tomcat that are shipped in the same release of RHEL. Red Hat supports the tomcat agent when used in conjunction with tomcat releases shipped in that same release of RHEL as the cluster software that is being used.


Using non-RHEL tomcat releases: While Red Hat's agents may work with other non-RHEL tomcat releases, Red Hat cannot guarantee the behavior will be as expected, and does not test these combinations. It is up to the organization deploying any such combination to thoroughly test the operation of the agent being used and determine if it is adequate for that deployment's needs. In cases where Red Hat's tomcat-targeted resource agent is being used with a release of tomcat other than what is shipped in that release of RHEL, Red Hat Support may be unable to assist with concerns relating to the agent's management of that release of tomcat.


Using 3rd party or custom agents or scripts: In situations where Red Hat's agent is not adequate for managing the tomcat server(s) deployed on a cluster, customer organizations may wish to develop their own scripts or agents, or some 3rd party may offer a script or agent for this purpose. Red Hat's typical policy on 3rd-party or custom agents or scripts applies here.

Comments