Installing and Configuring

Installing and configuring the exit module and connection endpoint schema.

Installing exit module

During installation of WebSphere MQ, the exit module is installed under tools/samples/c/preconnexit/bin. For 32 bit platforms, the exit module must be copied to exit/<install name>/ before it can be used. For 64 bit platforms, the exit module must be copied to exit64/<installation name>/ before it can be used.

Installing Connection Endpoint schema

The exit uses the Connection Endpoint schema, ibm-amq.schema . The schema file must be imported into any LDAP server before the exit can be used. After importing the schema, values for the attributes must be added.

Here is an example for importing Connection Endpoint schema. The example assumes IBM Tivoli Directory Server (ITDS) is being used.
  • Ensure that IBM Tivoli Directory Server is running, then copy or FTP the ibm-amq.schema file to the ITDS server.
  • On the ITDS server, enter the following command to install the schema into ITDS store, where LDAP ID and LDAP password are the root DN and password for the LDAP server:

    ldapadd -D "LDAP ID" -w "LDAP password" -f ibm-amq.schema

  • In a command window, enter the following command or use a third party tool to browse the schema for verification:

    ldapsearch objectclass=ibm-amqClientConnection

Refer to your LDAP Server documentation for further details on importing the schema file.

Configuration

A new section called PreConnect must be added to the client configuration file say mqclient.ini file. The PreConnect section contains the following keywords:

Module : The name of the module containing the API exit code. If this field contains the full path of the module, it is used as is else exit or exit64 folder in WebSphere MQ installation is searched.

Function : Name of the functional entry point into the library that contains the PreConnect exit code. The function definition adheres to the MQ_PRECONNECT_EXIT prototype.

Data : URI of the LDAP repository containing channel definitions.

The following snippet is an example of the changes required to mqclient.ini file.

PreConnect:
  Module=amqlcelp
  Function=PreConnectExit
  Data=ldap://myLDAPServer.com:389/cn=wmq,ou=ibm,ou=com
  Sequence=1