Configure JMS objects using the administration tool

We can use the IBM MQ JMS administration tool to define the properties of eight types of IBM MQ classes for JMS object and to store them within a JNDI namespace. Applications can then use JNDI to retrieve these administered objects from the namespace.


The following table shows the eight types of administered objects that we can create, configure and manipulate using verbs. The Keyword column shows the strings that we can substitute for TYPE in the commands shown in Table 1.

Object Type Keyword Description
MQConnectionFactory CF The IBM MQ implementation of the JMS ConnectionFactory interface. This represents a factory object for creating connections in both the point-to-point and publish/subscribe domains.
MQQueueConnectionFactory QCF The IBM MQ implementation of the JMS QueueConnectionFactory interface. This represents a factory object for creating connections in the point-to-point domain.
MQTopicConnectionFactory TCF The IBM MQ implementation of the JMS TopicConnectionFactory interface. This represents a factory object for creating connections in the publish/subscribe domain.
MQQueue Q The IBM MQ implementation of the JMS Queue interface. This represents a destination for messages in the point-to-point domain.
MQTopic T The IBM MQ implementation of the JMS Topic interface. This represents a destination for messages in the publish/subscribe domain.
MQXAConnectionFactory 1 XACF The IBM MQ implementation of the JMS XAConnectionFactory interface. This represents a factory object for creating connections in both the point-to-point and publish/subscribe domains, and where the connections use the XA versions of JMS classes.
MQXAQueueConnectionFactory 1 XAQCF The IBM MQ implementation of the JMS XAQueueConnectionFactory interface. This represents a factory object for creating connections in the point-to-point domain that use the XA versions of JMS classes.
MQXATopicConnectionFactory 1 XATCF The IBM MQ implementation of the JMS XATopicConnectionFactory interface. This represents a factory object for creating connections in the publish/subscribe domain that use the XA versions of JMS classes.
Note:
  1. These classes are provided for use by vendors of application servers. They are unlikely to be directly useful to application programmers.

For more information about how to configure these objects, see Configure JMS objects.

The property types and values that we need to use this tool are listed in Properties of IBM MQ classes for JMS objects.

We can also use the tool to manipulate directory namespace subcontexts within the JNDI as described in Configure subcontexts.

We can also create and configure JMS administered objects with IBM MQ Explorer.

  • Configure the JMS administration tool
    The IBM MQ JMS administration tool uses a configuration file to set the values of certain properties. A sample configuration file is supplied, which we can edit to suit the system.
  • Starting the administration tool
    The administration tool has a command-line interface that we can use either interactively, or to start a batch process.
  • Use administration commands
    The administration tool accepts commands consisting of an administration verb and its appropriate parameters.
  • Configure subcontexts
    We can use the verbs CHANGE, DEFINE, DISPLAY and DELETE to configure directory namespace subcontexts.
  • Create 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, we 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.
  • Configure JMS objects
    We can use the verbs ALTER, DEFINE, DISPLAY, DELETE, COPY, and MOVE to manipulate administered objects in the directory namespace.

Parent topic: Configure JMS resources


Related information