Last updated on JUNE 06, 2017
Applies to:Oracle Access Manager - Version 22.214.171.124.1 and later
Information in this document applies to any platform.
The customer has configured their F5 BigIP load balancer to reference the new heartbeat component to check server health in OAM 11gR2 PS2 using the Administrator's Guide
If the App Server is stopped, then this heartbeat check works as expected, However, if the LDAP servers that act as the user id repository are stopped, the heartbeat check continues to return a successful code of 200, which is clearly not correct.
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