Operations parameters

Table 1. Queue manager operation parameters
Parameter nameParameter typeParameter description
adapterjava.lang.StringClass name for the adapter to use with the message store - optional
addressjava.lang.StringIP address for a connection
aliasjava.lang.StringName of the queue manager alias
aliases[Ljava.lang.String;Names of the queue manager aliases
bridgeNamejava.lang.StringName of an MQ bridge
clientConnectionNamejava.lang.StringName of MQ client connection associated with an MQ bridge queue
connectionNamejava.lang.StringName of a connection
destinationQMgrNamejava.lang.StringName of the queue manager that owns a given proxy (remote) queue or a bridge queue
forwardToQMgrNamejava.lang.StringName of the queue manager that messages are forwarded to from a Forward queue
getFromQMgrNamejava.lang.StringName of the queue manager that owns a given home server queue
listenerAdapterjava.lang.StringListener adapter class
listenerNamejava.lang.StringName of a listener
listenerPortjava.lang.StringPort for a listener to listen on
messageStorejava.lang.StringClass name for the message store optional
pathjava.lang.StringPath for the queue store optional
portjava.lang.StringIP Port for a connection
proxyName java.lang.StringName of MQ queue manager proxy associated with an MQ bridge queue
queueName java.lang.StringName of the queue
viaQMNamejava.lang.StringName 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 WMQe 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 WMQe programmatic interface. In particular the methods createStoreQueue(), and createForwardQueue() do not correspond to WMQe standard APIs. The rationale behind these resources is explained in the relevant sections below on Store Queues, Forward Queues and Connections.

Parent topic: Queue manager