This documentation supports the 9.0 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.

Note

BMC recommends configuring 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

Comments

  1. Mpumelelo Tsabedze

    The last sentence on paragraph "A persistent session allows login content to be maintained. Session migration between JSP engine instances is not supported."

     

    Is this still relevant with the mid-tier clustering option ?

     

    Mpumi

    Dec 04, 2015 09:50
    1. Prachi Kalyani

      Hello,

      I will verify this with the concerned SME and get back to you soon.

      Thanks,

      Prachi

      Dec 14, 2015 11:22
    1. Prachi Kalyani

      Hello,

      The sentence "A persistent session allows login content to be maintained. Session migration between JSP engine instances is not supported." holds true for mid tier cluster.

      Thanks,

      Prachi

      Dec 16, 2015 04:40
      1. Mpumelelo Tsabedze

        Hi,

        May you please explain the function of mid-tier clustering perhaps I'm not understanding it correctly - I thought this was the Tomcat's session replication that I configured as cluster..

        What would a user see if mid-tier they were working on would fail and they were routed to another mid-tier ?

         

        Thanks

        Mpumi

        Dec 16, 2015 08:16
        1. Srikanth Pss

          Hi Mpumi,

          You are correct in your understanding that if one of the Midtiers were to fail, the user's requests would be routed to another Midtier in the cluster.

          However, for a user's session information to be available across all the nodes in a cluster, may take a bit of time. It is an asynchronous process to the actual user login.

          As a consequence, it is still a good idea to maintain session persistence between the user and the Midtier (similar to how it was in previous versions of Midtier).

          Hope this helps.

           

          Thanks,
          Srikanth 

          Dec 28, 2015 05:27