How To Setup A Health Check On A BIG-IP Loadbalancer To Monitor E-Business Suite JVM's
Last updated on MAY 23, 2017
Applies to:Oracle E-Business Suite Technology Stack - Version 12.1.2 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
You have set up your BIG-IP F5 load balancer in front of multiple E-Business Suite application tiers according to one of the following notes:
R12: <Note.380489.1> Using Load-Balancers with Oracle E-Business Suite Release 12
R11i: <Note.217368.1> Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i
You may have set up a basic HTTP health check which determines whether the Apache web server is functioning and able to serve static HTTP requests.
It is possible to have a situation where Apache can successfully serve HTTP requests however the Java Virtual Machine (JVM) is hung, spinning, down, or experiencing severe performance issues. In these cases your health check may continue to allow requests from the load balancer to be sent to a application tier which is effectively not able to serve java related requests. Considering all of the E-Business Suite web based applications are coded in java this can be a concern.
This brief article explains how to set up a health check to monitor the 'oacore' JVM so that in the events described above, requests will not be sent to that node.
Important: In the situation when multiple JVM's are enabled on an individual application tier the monitor can only check the status of the JVM which served the monitor request.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms