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. This allows applications to be de-coupled from the resources that they use at runtime.
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 point the applications to a production environment.
The WebSphere MQ JMS administration tool (JMSAdmin) available with WebSphere MQ can be used to create and manage administered objects for WebSphere MQ, WebSphere Message Broker, or WebSphere Event Broker in a central repository of administered objects.
The administered objects in the repository can be used by WebSphere MQ JMS applications, and also by XMS applications for ConnectionFactories and Destinations for WebSphere MQ queue manager, or for a realtime connection to a broker. 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.