Home

 

How the name service works

 

If a queue definition specifies the Scope attribute as queue manager, that is, SCOPE(QMGR) in MQSC, the queue definition (along with all the queue attributes) is stored in the queue manager’s directory only. This cannot be replaced by an installable service.

If a queue definition specifies the Scope attribute as cell, that is, SCOPE(CELL) in MQSC, the queue definition is again stored in the queue manager’s directory, along with all the queue attributes. However, the queue and queue-manager name are also stored in a name service. If no service is available that can store this information, a queue with the Scope cell cannot be defined.

The directory in which the information is stored can be managed by the service, or the service can use an underlying service, for example, an LDAP directory, for this purpose. In either case, definitions stored in the directory must persist, even after the component and queue manager have terminated, until they are explicitly deleted.

1. To send a message to a remote host’s local queue definition (with a scope of CELL) on a different queue manager within a naming directory cell, you need to define a channel.

2. We cannot get messages directly from the remote queue, even when it has a scope of CELL.

3. No remote queue definition is required when sending to a queue with a scope of CELL.

4. The naming service centrally defines the destination queue, although you still need a transmission queue to the destination queue manager and a pair of channel definitions. In addition, the transmission queue on the local system must have the same name as the queue manager owning the target queue, with the scope of cell, on the remote system.

   For example, if the remote queue manager has the name QM01, the transmission queue on the local system must also have the name QM01. See WebSphere MQ Intercommunications for further information.

• Name service interface
  

 

Parent topic:

Name service

fa16520_

 

Home