To check whether the LDAP server is already configured to accept Java objects, run the WebSphere MQ JMS Administration Tool JMSAdmin against your LDAP server (see Invoking the Administration tool).
Attempt to create and display a test object using the following commands:
DEFINE QCF(ldapTest) DISPLAY QCF(ldapTest)
If no errors occur, your server is properly configured to store Java objects and you can proceed to store JMS objects. However, if your LDAP server contains older schema definitions (for example, from an earlier draft of RFC 2713 such as the now-obsolete "draft-ryan-java-schema-00" and "draft-ryan-java-schema-01" specifications), you should update them with those presented here.
If a SchemaViolationException occurs, or if the message "Unable to bind to object" is returned, your server is not properly configured. Either your server is not configured to store Java objects, or permissions on the objects are not correct, or the provided suffix or context has not been set up. The following information should help you with the schema configuration part of your server setup.