Browse Prior Art Database

Heartbeat for LDAP servers being managed by eNetwork Dispatcher

IP.com Disclosure Number: IPCOM000013338D
Original Publication Date: 2000-Apr-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 1 page(s) / 54K

Publishing Venue

IBM

Abstract

Disclosed is a program which can be used by IBM eNetwork Dispatch (eND a Load

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 97% of the total text.

Page 1 of 1

Heartbeat for LDAP servers being managed by eNetwork Dispatcher

Disclosed is a program which can be used by IBM eNetwork Dispatch (eND - a Load

Balancing server) to determine if an LDAP server the Dispatcher is managing is

available to take requests. The program runs on each LDAP server being managed and

is regularly polled by an AdvisorAgent (a Java object which returns a number

indicating load. Please see the eND documentation) on the eND machine. The

response given by the program is used by eND to decide if that LDAP server should

have new requests dispatched to it.

The Heartbeat Server runs on an LDAP server that is being managed by an eND

machine. The program listens on a TCP/IP port (specified when it is started) for a

client to connect. Should a client connect and send data, the program attempts to

connect to an LDAP server on "localhost" and request a search. If the search succeeds,

the Heartbeat Server returns "HTTP/1.0 200 OK" to the client that connected to it.

Should the search, or any activity leading up to the search fail, the client connection

is immediately dropped.

Accompanying the Heartbeat Server is an eND AdvisorAgent which exists on the

eND server. This agent is what attempts to connect to the LDAP server. This agent

sends an HTTP HEAD request and expects an OK response. Should the OK response

not come, the agent indicates that the server is unreachable and the eND software will

not dispatch any more requests to that server, until such that a...