Creating JMS objects
To create JMS connection factory and destination objects and store them in a JNDI namespace, use the DEFINE
verb. To store your objects in an LDAP environment, you must give them names that comply with certain conventions. The administration tool can help you obey LDAP naming conventions by adding a default prefix to object names.
About this task
The DEFINE verb creates an administered object with the type, name and properties that you specify. The new object is stored in the current context.
The names of JMS objects that are stored in an LDAP environment must comply with LDAP naming conventions. One of these conventions is that object and context names must include a prefix, such as cn=
(common name), or ou=
(organizational unit). The administration tool simplifies the use of LDAP service providers by allowing you to refer to object and context names without a prefix. If you do not supply a prefix, the tool automatically adds a default prefix to the name you supply. For LDAP, this is cn=
. If required, you can change the default prefix by setting the NAME_PREFIX property in the configuration file. For more information, see Configuring the JMS administration tool.
Procedure
Example
DEFINE
verb. Since this object is being stored in an LDAP environment, although the object name testQueue
is not entered with a prefix, the tool automatically adds one to ensure compliance with the LDAP naming convention. Submitting the command DISPLAY Q(testQueue)
also causes this prefix to be added.
InitCtx> DEFINE Q(testQueue)
InitCtx> DISPLAY CTX
Contents of InitCtx
a cn=testQueue com.ibm.mq.jms.MQQueue
1 Object(s)
0 Context(s)
1 Binding(s), 1 Administered