This preview shows page 479 - 482 out of 672 pages.
You can join publish/subscribe domains across the service integration bus and WebSphere MQ. You must configure a service integration bus and messaging engines. You cannot connect to queue managers in bindings mode. Optimum load balancing is more complicated to achieve because messages must be "pushed" from either end of the link. You cannot use mediations for modifying messages, routing, or logging.
454WebSphere Application Server V8.5 Concepts, Planning, and Design GuideFigure 13-15 shows a JMS application in WebSphere Application Server sending messages to WebSphere MQ by using WebSphere MQ network as a foreign bus.Figure 13-15 WebSphere MQ network as a foreign bus WebSphere MQ server as a bus memberA WebSphere MQ server provides a direct client connection between a service integration bus and queues on a WebSphere MQ queue manager or queue-sharing group (z/OS). A WebSphere MQ server represents queues for point-to-point messaging only, and ensures that messages are converted between the formats that are used by WebSphere Application Server and WebSphere MQ. Table 13-3 lists the advantages and considerations of using a WebSphere MQ server as a bus member.Table 13-3 Advantages and considerations of WebSphere MQ server as a bus memberService integrationWMQqueuesDefault messagingproviderJMS applicationWebSphere MQ(a foreign bus)WMQtopicsService IntegrationBusMQ link(server to serverchannel connection)AdvantagesConsiderationsWebSphere Application Server and WebSphere MQ can exist on separate hosts. Each end of the connection is displayed in natural form to the other. WebSphere MQ queue manager is displayed to service integration as a foreign bus. Service integration is displayed to WebSphere MQ as a client. Close integration of applications is possible. Service integration applications can consume messages directly from the WebSphere MQ network. You can connect to queue managers in client mode or bindings mode. You can use mediations for modifying messages, routing, or logging. Good security support is provided. For example, you can control which users are allowed to put messages onto queues. You can get messages from WebSphere MQ queues. Interaction between WebSphere Application Server and WebSphere MQ is seamless. Queues on the WebSphere MQ network are automatically discovered. You must configure a service integration bus and messaging engines. The queue managers and queue-sharing groups must be accessible from all the messaging engines on the bus. A topic for publish/subscribe messaging cannot be represented as a WebSphere MQ server. WebSphere MQ for z/OS Version 6 or later, or WebSphere MQ (distributed platforms) Version 7 or later, is a prerequisite. If you are using different nodes with WebSphere MQ for z/OS, you might require the Client Attachment feature (CAF) on z/OS. The need for CAF is dependent on the number of nodes and your version of WebSphere MQ for z/OS,You must explicitly define all destinations.