A bus has a number of bus members. Each bus member is a server or a cluster. A server will have one messaging engine on the bus, while a cluster will have one or more messaging engine on a bus. Buses and bus members are held in a separate document to messaging engines - buses and bus members are held in a file called sib-bus.xml at bus scope while messaging engines are held in files called sib-engine.xml at server and/or cluster scope as appropriate. To avoid cross-document links, a bus member simply indicates the scope (server or cluster) at wich the bus member's engines can be found. A bus has a number of bus members. Each bus member is a server or a cluster. A server will have one messaging engine on the bus, while a cluster will have one or more messaging engine on a bus. Buses and bus members are held in a separate document to messaging engines - buses and bus members are held in a file called sib-bus.xml at bus scope while messaging engines are held in files called sib-engine.xml at server and/or cluster scope as appropriate. To avoid cross-document links, a bus member simply indicates the scope (server or cluster) at wich the bus member's engines can be found. The name of the WebSphere MQ server. This is for administrative purposes. The name of the WebSphere MQ Queue Manager, or Queue Sharing Group. This is the WebSphere MQ name by which the queue manager or queue sharing group is identified. Determines the type of the server. When this is set to "Queue Manager" resource discovery will retrieve queue names specific to the queue manager. When this is set to "Queue Sharing Group" resource discovery will retrieve queue names that belong to the group. The description of the WebSphere MQ sever. This is for administrative purposes. When the application server and queue manager are co-located, one can use a fast path connection mechanism. When this option is selected, bindings transport mode connections will be used in preference to network connections, where available. Note that it is only possible to connect to a single queue manager in bindings mode even if more than one is co-located. The hostname of the machine hosting the WebSphere MQ Queue Manager that this WebSphere MQ server represents. This may be a symbolic hostname, a numeric IPv4 or a numeric IPv6 address. The port number that the WebSphere MQ Queue Manager, that this WebSphere MQ server represents, is listening on. The channel framework outbound transport chain used for establishing a connection to WebSphere MQ. The WebSphere MQ Client Channel name to use when connecting to the WebSphere MQ Queue Manager that this WebSphere MQ server represents. The authentication alias to use when establishing a messaging connection to the WebSphere MQ Queue Manager. Determines whether user identifiers received as part of WebSphere MQ message data should be used in the Platform Messaging bus. Determines if automatic discovery of WebSphere MQ Queue names should be performed. This feature is intended to assist the administrator. The authentication alias to use when establishing a resource discovery connection to the WebSphere MQ Queue Manager. The reply-to queue used for resource discovery. Indicates whether or not the connection values defined here (host, port, transportChainName, channel, messagingAuthAlias and trustMessageUserIdentifiers) override the values defined in the WebSphere MQ server.. Value to override the host specified in the WebSphere MQ server. Value to override the port specified in the WebSphere MQ server. Value to override the transportChainName specified in the WebSphere MQ server. Value to override the channel specified in the WebSphere MQ server. Value to override the messagingAuthAlias specified in the WebSphere MQ server. Value to override the trustMessageUserIdentifiers specified in the WebSphere MQ server.