Operations parameters

Table 1. 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 return type in each case is of type java.lang.Void. Hence, return types have not been included in the table.
  2. There may seem to be a discrepancy between the input parameters listed for the operations and the input parameters required for the corresponding MQe operations. This is because the interface design allows the user to input only mandatory parameters at this point. The reason for this is that where the adapter used provides a graphical interface, the inclusion of all optional parameters for each operation would result in a very cluttered interface. Thus, all optional parameters have been omitted in these create operations. Once the resource has been created, they can be specified as updates using setAttribute() or setAttributes().
  3. Some of these methods may seem unfamiliar to someone who uses the MQe programmatic interface. In particular the methods createStoreQueue(), and createForwardQueue() do not correspond to MQe standard APIs. The rationale behind these resources is explained in the relevant sections below on Store Queues, Forward Queues and Connections.

Terms of use | WebSphere software

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