Operations parameters

Table 1. Remote queue manager operation parameters
Parameter name Parameter type Parameter description
adapter java.lang.String Class name for the adapter to use with the message store - optional
address java.lang.String IP address for a connection
alias java.lang.String Name of the queue manager alias
aliases [Ljava.lang.String; Names of the queue manager aliases
bridgeName java.lang.String Name of an MQ bridge
clientConnectionName java.lang.String Name of MQ client connection associated with an MQ bridge queue
connectionName java.lang.String Name of a connection
destinationQMgrName java.lang.String Name of the queue manager that owns a given proxy (remote) queue or a bridge queue
forwardToQMgrName java.lang.String Name of the queue manager that messages are forwarded to from a Forward queue
getFromQMgrName java.lang.String Name of the queue manager that owns a given home server queue
listenerAdapter java.lang.String Listener adapter class
listenerName java.lang.String Name of a listener
listenerPort java.lang.String Port for a listener to listen on
messageStore java.lang.String Class name for the message store optional
path java.lang.String Path for the queue store - optional
port java.lang.String IP Port for a connection
proxyName java.lang.String Name of MQ queue manager proxy associated with an MQ bridge queue
queueName java.lang.String Name of the queue
viaQMName java.lang.String Name of a queue manager to connect via (for an indirect connection)
Note:
  1. The refresh() operation requires particular comment. When resources are added to or removed from a JMX-enabled queue manager, whether via the JMX interface or from another application, these updates are automatically reflected in the MBeans (that is to say, corresponding MBeans are registered or deregistered). However, when the MBeans corresponding to a queue manager which is remote to the JMX-enabled queue manager (known to it through a direct connection) are updated from another application, these changes are not reflected automatically. In this case, the refresh() operation has to be invoked to update the MBeans in accordance with the current remote queue manager resources.
  2. When a direct connection to another Queue Manager is created, a RemoteQueueManager MBean is created in addition to the MBean for the connection definition itself. If the MQeAdminJmx attribute InquireOnConnect is set to true, MBeans for the remote queue manager child resources will be created and registered with the MBeanServer instance at this point. However, if InquireOnConnect is set to false, the child MBeans will not be created. The refresh operation on this MBean will need to be invoked at a later time in order to create the remote queue manager alias MBeans and the MBeans for the child resources when/if required. Note that MBeans for the remote Queue Manager child resources are only created for queue managers connected to the JMX local queue manager by direct connections no child MBeans are created for queue managers known only through MQ, alias or indirect connections.

Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.