IBM Content Manager, Version 8.5.0.3 Operating systems: Windows

LDAP server configuration for storing Java objects

Before you set up the JMS queue, you might need to configure your LDAP server for storing Java™ objects to support the RFC 2713 schema.

WebSphere® MQ and the Java Message Service (JMS) require the LDAP provider to store the JMS context information as Java objects. Some LDAP providers, such as Microsoft Active Directory, might require additional configuration to support RFC 2713: Schema for Representing Java Objects in an LDAP Directory. This schema defines elements to represent a Java serialized object, a Java marshalled object, and a Java Naming and Directory Interface (JNDI) reference. A Java remote object is stored as either a Java marshalled object or a JNDI reference.

Sun Microsystems provides a Java tool, CreateJavaSchema, to configure the schema for storing Java objects for JMS. You can download a complete compressed file from the Sun Microsystems JNDI LDAP service provider Web site. You can also find additional information in the WebSphere MQ documentation.

If the directory's administration tool supports the disabling of schema checking, turn off schema checking before running the CreateJavaSchema tool as recommended in the CreateJavaSchema tool's instructions.

Example

Follow this Microsoft Windows Server Active Directory 2003 example to run the CreateJavaSchema tool. Enter the following command, where ldap://www.myhost.com is the LDAP server URL, cmuser is the distinguished name for authentication, and password is the password for authentication:

java -Djava.naming.provider.url=ldap://www.myhost.com 
CreateJavaSchema -sad -ncmuser -ppassword

The tool displays output that is similar to the following example:

[updating Active Directory schema ...]
  [locating the schema]
  [inserting new attribute definitions ...]
    [javaClassName]
    [javaCodeBase]
    [javaSerializedData]
    [javaFactory]
    [javaReferenceAddress]
    [javaDoc]
    [javaClassNames]
  [inserting new object class definitions ...]
    [javaContainer]
    [javaObject]
    [javaSerializedObject]
    [javaNamingReference]
    [javaMarshalledObject]
[update completed]
Use your directory server's administration tool to verify
that the schema is correct:

Tip:

If you use Microsoft Windows Server Active Directory 2003, use the -sad option for the CreateJavaSchema command as shown in this example to work around schema bugs in the server. Also, to enable any schema modifications, you must create the Schema Update Allowed registry property of type DWORD and set the value to 1. Open the registry editor and create this registry property in the following location: HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > NTDS > Parameters > Schema Update Allowed.