Copyright © TIBCO Software Inc. All Rights Reserved

Services of Adapter for LDAP

The adapter provides the following services: publication service, subscription service, and request-response service.

Publication Service

The adapter gets a message from the LDAP server and sends the message to the TIBCO environment.

For example, a new employee joins Company A. The administrator updates the corporate LDAP server with the details of the new employee. The Publication Service of the adapter receives this information from the LDAP server, assigns a structure to it, and publishes it using TIBCO Rendezvous or JMS messaging for other applications to pick up. All other applications that need to be aware of this change are informed by the Publication Service via TIBCO Rendezvous or JMS messaging.

Figure 11 Typical publication service flow

Subscription Service

The adapter gets a message from the TIBCO environment and sends the message to the LDAP server.

For example, Company A adds 50 computers to its existing infrastructure, as part of its expansion program. This asset information needs to be reflected on the corporate LDAP server. This information is published by the application using TIBCO Rendezvous or JMS messaging, probably through an application adapter. When the Subscription Service of the adapter receives this information from TIBCO Rendezvous or JMS messaging, it uses the standard LDAP API to update the LDAP server by adding the required entries.

Figure 12 Typical subscription service flow

Request-response Service

The adapter gets a request from the TIBCO environment and sends the request to an LDAP server. When a response is returned to the adapter from the LDAP server, the adapter sends the response to the TIBCO environment. The adapter supports request-response scenarios with an RPC server.

For example, User A of an email client does not know the first name or email address of the contact to whom a mail must be sent. Therefore, the user searches for all names ending with Smith using the Find Contact option on the email client. The email client publishes this request using TIBCO Rendezvous or JMS messaging, probably through an application adapter. When the Request-Response Server Service of the adapter receives this query, it uses the standard LDAP API to contact the LDAP server, and uses the Search operation to find all names (or the specified number of names) ending with Smith. It then returns the search results in its response to TIBCO Rendezvous or JMS messaging.

Figure 13 Typical Request-response Service Flow

 

Copyright © TIBCO Software Inc. All Rights Reserved