LDAP as a Naming Service in Enterprise Application Integration

Integrating JMS Adapter of IBM Sterling B2B Integrator and IBM WebSphere MQ with OpenLDAP as a Naming Service

From the developerWorks archives

Kanagarajan Ramakrishnan Maheshwari

Date archived: May 15, 2019 | First published: January 20, 2014

In enterprise integrations, applications across different systems are integrated by various means and techniques. In such large-scale integration, there is a need to identify the key integration components or elements and maintain them in a secure centralized location that provides easy and dynamic access. Here, Lightweight Directory Access Protocol (LDAP) is used as a naming service to discover most of the common integration elements. LDAP satisfies the needs and challenges that are faced in a typical integration scenario. The article explains how the LDAP-based naming service is used for application integration. The scenario explains how the JMS queue adapter of IBM® Sterling B2B Integrator® is integrated with another downstream system, IBM® WebSphere® MQ. The JMS adapter application looks up the OpenLDAP registry for key integration elements, such as queue connection details. Using these integration parameters, the JMS adapter connects to the appropriate queue in WebSphere MQ and delivers the message.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.

Zone=Commerce, WebSphere
ArticleTitle=LDAP as a Naming Service in Enterprise Application Integration