Administered objects
Using administered objects, you can administer the connection settings used by client applications to be administered from a central repository. An application retrieves object definitions from the central repository and uses them to create ConnectionFactory and Destination objects. Using administered objects, you can de-couple applications from the resources that they use at run time.
For example, XMS applications can be written and tested with administered objects that reference a set of connections and destinations in a test environment. When the applications are deployed, the administered objects can be changed to configure the applications to refer to connections and destinations in the production environment.
- A ConnectionFactory object, which is used by applications to make the initial connection to the server.
- A Destination object, which is used by applications to specify the destination for messages that are being sent, and the source of messages that are being received. A destination is either a topic or a queue on the server to which an application connects.
The administration tool JMSAdmin is supplied with IBM® MQ. It is used to create and manage administered objects in a central repository of administered objects.
The administered objects in the repository can be used by IBM MQ classes for JMS and XMS applications. XMS applications can use the ConnectionFactory and Destination objects to connect to an IBM MQ queue manager. An administrator can change the object definitions held in the repository without affecting application code.
The following diagram shows how an XMS application typically uses administered objects. The left-hand side of the diagram shows a repository containing ConnectionFactory and Destination object definitions that are administered using an administration console. The right-hand side of the diagram shows an XMS application that looks up object definitions in the repository, and then uses these object definitions when connecting to a messaging server.
