No matter what role a queue manager performs, there is a basic amount of configuration required. This basic configuration results in what is here termed a Basic Queue Manager. Depending upon the type of role intended for the queue manager, this Basic Queue Manager is extended, resulting in a Client Queue Manager, a Server Queue Manager or a Gateway Queue Manager. The following diagram attempts to summarize these configurations:
Basic Queue Manager | + | Connection definition and remote queue definition | = | Client queue manager |
Basic Queue Manager | + | Listener | = | Server queue manager |
Basic Queue Manager | + | Bridge functionality | = | Gateway queue manager |
Basic Queue Manager | + | Security configuration, and so on |
The complete management life cycle for most managed resources can be controlled with administration messages. This means that the managed resource can be brought into existence, managed and then deleted with administration messages. This is not the case for queue managers. Before a queue manager can be managed it must be created and started.
The queue manager has very few characteristics itself, but it controls other MQe resources. When you inquire on a queue manager, you can obtain a list of connections to other queue managers and a list of queues that the queue manager can work with. Each list item is the name of either a connection or a queue. Once you know the name of a resource, you can use the appropriate message to manage the resource. For instance you use an MQeConnectionAdminMessage to manage connections.