This documentation supports the 19.02 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Using the Mid Tier Configuration Tool with a load balancer

If you are using the Mid Tier Configuration Tool with a load balancer, you must use the web server's real IP address, not a virtual IP address, to open the Mid Tier Configuration Tool. Explicitly configure each mid tier instance directly, not through the load balancer's virtual IP. The Mid Tier Configuration Tool will not function as expected if you use a virtual server to open it.

Each web server must have its own mid tier. You must configure each mid tier individually, and you must configure each mid tier identically.

Best Practice

When you have a load balancer between Mid Tier and AR Server group, we recommend that you configure the load balancer without using a "sticky bit" (session affinity) to allow sessions from any BMC Remedy Mid Tier server to be distributed to any BMC Remedy AR System server on the fly. For more information, see Configuring the Connection Settings page.
A persistent session allows login content to be maintained. Session migration between JSP engine instances is not supported.

Was this page helpful? Yes No Submitting... Thank you