Sample program for Connection Endpoint Lookup (CEPL)

IBM MQ Connection Endpoint Lookup sample provides a simple yet powerful exit module that offers IBM MQ users a way to retrieve connection definitions from an LDAP repository such as Tivoli Directory Server.

Tivoli Directory Server v6.3 Client must be installed in order to use CEPL.

A working knowledge of IBM MQ administration on the supported platforms is required to use this sample.

• Introduction
  Configure a global repository, for example, an LDAP (Lightweight Directory Access Protocol) directory, to store client connection definitions to aid maintenance and administration.
• Supported environments
  Verify that we have a supported operating system and the relevant software before running the Connection Endpoint Lookup sample.
• Installation and configuration
  Installing and configuring the exit module and connection endpoint schema.
• Overview of the exit and schema
  Syntax, and parameters used to establish a connection to a queue manager.
• MQ LDAP Context Information
  The exit uses the following data structure for context information.
• Sample code for building the connection endpoint lookup exit
  We can use the sample code snippets for compiling the source on AIX, or Linux, or Windows.
• Invocation of the PreConnect exit module
  The PreConnect exit module can be invoked with three different reason codes: the MQXR_INIT reason code for initializing and establishing a connection to an LDAP server, the MQXR_PRECONNECT reason code for retrieving channel definitions from an LDAP server, or the MQXR_TERM reason code when the exit is to be cleaned.
• LDAP schemas
  Client connection data is stored in a global repository called the LDAP (Lightweight Directory Access Protocol) directory. An IBM MQ client uses an LDAP directory to obtain the connection definitions. The structure of the IBM MQ client connection definitions within the LDAP directory is known as the LDAP schema. An LDAP schema is the collection of attribute type definitions, object class definitions, and other information which a server uses to determine whether a filter or attribute value assertion matches against the attributes of an entry, and whether to permit, add, and modify operations.
• LDAP attributes
  LDAP attributes defined are specific to IBM MQ and maps directly to the client connection properties.

Parent topic: Use the sample programs on Multiplatforms