Implementing a L4 switch with the Middle Tier server

From MicroFocusInternationalWiki
Revision as of 23:45, 15 March 2006 by Equill (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Implementing a L4 switch with the Middle Tier server

Configure Sticky Sessions

  • Setup for the HTTP (80) port.
  • Setup for the SSL (443) port if Zen agents access the Middle Tier server over the SSL port.
  • Configure Sticky session timeouts to the same session timeout as the web server (IIS or Apache).

Configuring the L4 switch to detect if the Middle Tier server is down

  • URL comes back with “HEAD /â€? status. The “HEAD /â€? is the start of a HTML

page so if the web server is down, then “HEAD /� will not be returned. When this happens, the L4 should set the server to a failed stated and redirect all traffic to another Middle Tier server.

Supported HTTP Protocol Error Codes by the Middle Tier

  • 204 – No Content
  • 400 – Bad Request
  • 404 – Not Found
  • 500 – Server Error
  • 503 – Out of Resources

There are other errors codes that can be implemented to help the L4 switch in detecting a server failure which depends on the needs of the customer. Certain error codes can cause more traffic or the L4 can also put the middle tier server into a bad state and forcing all traffic to a single server if implemented incorrectly. The error codes should be implemented with care.