You can use IBM® MQ to create flexible connection topologies from the different connectivity options.
If you already have a WebSphere® MQ solution, you do not need to change your existing WebSphere MQ topology to work with IBM App Connect Enterprise; the products integrate automatically.
Your WebSphere MQ applications exchange messages and other data by communicating with message flows that are running in the integration server. You can connect your applications to the integration server by using one of the supported communication methods. If your applications are written to use WebSphere MQ, the requirement for the channels or client connections are determined by the types of nodes that you include in your message flows. These resources are application-specific, and you must create these resources yourself.
For more information about creating resources, see Intercommunication in the
WebSphere MQ Version 7.5 product
documentation online.
A local connection is a connection to a local queue manager that uses server bindings. A client connection connects to remote queue managers. You can use local connections, client connections, or a combination of local and client connections to your queue managers. On z/OS®, only local connections are supported.
When you configure a connection from an MQ node to a WebSphere MQ queue manager, you can optionally configure the connection to use a security identity for authentication, SSL for confidentiality, or both. The security identity, which passes user name and password security credentials to the queue manager, can be used on connections to local or remote queue managers. For connections to remote queue managers, you can choose whether to use the SSL protocol to provide confidentiality on the client connection. IBM App Connect Enterprise supports a subset of the SSL functionality that is supported by WebSphere MQ. For more information, see Connecting to a secured WebSphere MQ queue manager.
If a connection is lost between an integration server and queue manager, the integration server automatically attempts to reconnect to the queue manager. All resources and transports that do not require access to that connection continue to run. In a non-transactional message flow, MQInput, MQOutput, MQGet, and MQReply nodes automatically attempt to reconnect once. If the node still cannot connect, then normal exception processing occurs.
Connection details for MQ nodes can be managed by MQEndpoint policies (see MQEndpoint policy).