Why use a service integration bus?

 To connect any kind of application to any other kind of application. This is the traditional
WebSphere MQ scenario, where different applications written in different languages are running
on different operating systems and you want them all to be able to communicate with each other.
 To connect J2EE applications running in WAS servers. What has changed in the last few years is
that many of our customers are converting everything to J2EE applications deployed in
WebSphere Application Server so they do not have to support every platform, only WebSphere
Application Server. WebSphere Application Server Version 5 enabled this with its Embedded
Messaging feature, however this is now better addressed with a service integration bus. For the
situation where many WebSphere Application Server applications are communicating, and you
also need to communicate with other non-WebSphere Application Server applications, you must
still use WebSphere MQ as the messaging system.

Architectures you can use for interoperating WebSphere Application Server and WebSphere MQ are
WebSphere MQ as an external JMS messaging provider, WebSphere MQ links, and WebSphere MQ
servers.

What are the benefits of service integration bus?

 Secure externalizing of existing applications: You can use the bus to expose existing applications
as Web services, for use by any Web service-enabled tool, regardless of the implementation
details. This enables applications or Web services deployed on a server deep inside an enterprise to
be made available as Web services on the Internet to customers, suppliers, and business partners.
Security options mean that this access can be tightly controlled.
 Return on investment: Business partners can reuse an existing process that you make available as a
Web service using the bus. This gives great scope for the reuse of existing assets.
 Protocol transformation: The bus provides support for exposing an existing service implemented
in one protocol (for example, SOAP/JMS), as something entirely different from clients (for
example, SOAP/HTTP). This function is invaluable for ensuring smooth interoperability between
businesses that may implement varying Web services protocols in their business applications.
 Messaging benefits: The fact that the bus is built on top of the Java Messaging Service (JMS)
delivered in WebSphere Application Server means that it is able to expose messaging artifacts,
such as queues and topics, as Web services. It also provides advanced options for asynchronous
communication, prioritized message delivery, and quality of service (message persistence).

For more information about what is provided by service integration within WebSphere Application Server,
see the following topics:

Message exchange through a WebSphere MQ link:-

The figure below shows a high level view of the function of a WebSphere MQ link: it allows messages to be
exchanged between a WebSphere Application Server and a WebSphere MQ network.
A WebSphere MQ link is a configurable object that describes the attributes required to connect
to, and send or receive messages to or from, a WebSphere MQ queue manager. It is an
administrative entity in WebSphere Application Server, not in WebSphere MQ. A WebSphere
MQ link connects to a specific foreign bus which represents a WebSphere MQ network. A
WebSphere MQ link is defined on a WebSphere Application Server messaging engine in a
service integration bus. The messaging engine that supports the WebSphere MQ link is known
as the WebSphere MQ link engine.

The WebSphere MQ link engine inside the WebSphere Application Server can exchange
messages with a WebSphere MQ queue manager. To the WebSphere MQ link engine, the
WebSphere MQ queue manager appears to be a foreign bus. To the queue manager, the
WebSphere MQ link engine appears to be another WebSphere MQ queue manager.

The figure below shows a bus on a WebSphere Application server and how a messaging engine
on the bus can have a WebSphere MQ link. WebSphere MQ appears as a foreign bus with a
gateway queue manager with a connection to the WebSphere MQ link.

Exchanging messages between a service integration bus, and a foreign bus in a WebSphere MQ
network
WebSphere MQ link can have definitions for a WebSphere MQ link sender or a WebSphere MQ
link receiver or both. The link sender and receiver emulate the behavior of WebSphere MQ
sender and receiver channels.

Note:-

WebSphere MQ link sender, over which messages are sent from a messaging engine in a
service integration bus(in WAS admin console) to a queue manager in a WebSphere MQ
network.

The WebSphere MQ link sender (MQLinkSender) converts messages to WebSphere MQ format

messages, and then sends them to a receiver channel on the WebSphere MQ gateway queue
manager. The WebSphere MQ link sender, part of the WebSphere MQ link, emulates the
behavior of the sender channel in WebSphere MQ.

Sender and receiver channels that enable the messaging engine with the WebSphere MQ link

 The WebSphere MQ link can have a publish/subscribe bridge, which allows the
publication of messages and establishment of subscription to topics between the
WebSphere Application Server and a broker in the WebSphere MQ network. The
bridge, consisting of one or more broker profiles and topic mappings can be configured
after you define the WebSphere MQ link .

 When sending messages to WebSphere MQ through the WebSphere MQ link, you can
include additional fields unique to WebSphere Application Server messaging
technology in the MQRFH2 header, inside a container called the sib folder. The
MQRFH2 header contains information about the structure of the message and its
intended consumers. A WebSphere MQ application can look at or manipulate the
contents of the sib folder if desired.

Exchanging messages between alias destinations, foreign destinations and remote queues.
Defining a WebSphere MQ link in WAS.

WebSphere MQ link on a messaging engine in a service integration bus.

Note :-Before starting this task you will need to configure Websphere MQ server:

 Know the name of the messaging engine on which you intend to put the WebSphere MQ link.
 Have created the foreign bus that represents the WebSphere MQ queue manager network. For
information about creating a foreign bus, see Configuring foreign bus definitions.

 Know the name of the WebSphere MQ queue manager that you will define as the gateway through
which messages will be exchanged with the WebSphere MQ link.
 Have created sender and receiver channels in the WebSphere MQ network. The WebSphere MQ
link receiver channel must have the same name as its partner sender channel in the WebSphere
MQ network. The WebSphere MQ link sender channel must have the same name as its partner
receiver channel in the WebSphere MQ network. For examples on creating channels
1. In the navigation pane, click Service integration > Buses > [Content Pane] bus_name > [Topology]
Messaging engines > engine_name > [Additional Properties] WebSphere MQ links

2. In the content pane, click New.

3. Type the name of the new WebSphere MQ link.

4. Enter a description for the WebSphere MQ link.

5. In the foreign bus name, click the name of the foreign bus that represents the WebSphere MQ network.

6. Type the virtual, messaging-engine queue-manager name, that is, the queue name that WebSphere MQ
will use to address this service integration bus. This is the service integration bus name. Maximum
48 characters.

7. Review the default values in the remaining fields on the panel, using the field help in the Help pane to
find out more information about each field. Modify any values as necessary.

8. Click Next.

9. Define the WebSphere MQ link sender channel.

1. Type the name of the sender channel associated with this WebSphere MQ link. Maximum 20
characters. This name must be the same as the name of the partner receiver channel in the
WebSphere MQ network.

2. Type the host name or address of the target queue manager in the WebSphere MQ network.

3. Enter the port number on which the gateway queue manager is listening for the inbound
communication requests.

4. Type the transport chain, that is the communication protocol for the foreign bus. Possible choices
include "OutboundBasicMQLink" and "OutboundSecureMQLink". For more information
seeOutbound transport options and Securing connections to a WebSphere MQ network.

5. Review the default values in the remaining fields on the panel, using the field help in the Help pane
to find out more information about each field. Modify any values as necessary.

10. Click Next.

11. Define the WebSphere MQ link receiver channel.

1. Type the name of the receiver channel associated with this WebSphere MQ link. Maximum 20
characters. This name must be the same as the name of the partner sender channel in the WebSphere
MQ network.

2. Review the default values in the remaining fields on the panel, using the field help in the Help pane
to find out more information about each field. Modify any values as necessary.

12. Click Next

13. Check the summary of WebSphere MQ link properties, and when you are satisfied click Finish.

14. Save your changes to the master configuration.

 15. Restart the application server if you have completed configuring the WebSphere MQ link, that is, you
are not going to define broker profiles. The WebSphere MQ link is ready to send, receive, or
exchange messages with the WebSphere MQ network, provided the queue manager (the gateway
queue manager) has been created on the WebSphere MQ network, and the required resources
defined.

Securing connections to a WebSphere MQ network:-

onnections between a WebSphere Application Server and a WebSphere MQ network may utilize the Secure
Sockets Layer (SSL) protocol to increase the confidentiality and integrity of messages transferred between
a messaging engine on a service integration bus and WebSphere MQ.

By default, new application servers are configured to accept inbound WebSphere MQ connections through
two inbound transport chains. To read about inbound transport chains, see Inbound transport options. One
of these chains is configured to accept SSL-based connections, making it possible to configure a sender
channel in the WebSphere MQ network to connect through this channel chain and establish an SSL-based
connection (information about securing WebSphere MQ sender channels can be found in the book
WebSphere MQ Security, SC34-6079). Because all WebSphere MQ interoperation resources hosted by an
application server can be contacted by all inbound MQ transports defined to that server, take care to restrict
the inbound transports that are enabled. This is important because the default application server
configuration has definitions for inbound WebSphere MQ transports that are not secured using SSL. To
read about secure transport considerations see Secure transport considerations).

When connecting a WebSphere Application Server to a WebSphere MQ queue manager through a

WebSphere MQ link sender channel definition, you may choose to secure the link through SSL. This is
achieved by specifying a suitable transport chain for the "Transport chain" property of the WebSphere MQ
link sender channel definition. The name of the default SSL-based outbound transport chain suitable for
securing a WebSphere MQ link sender channel is "OutboundSecureMQLink". To read about outbound
transport chains, see Outbound transport options

Link for Reference:-

WebSphere MQ link sender

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0002_.html

Configure WAS for MQ.

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0001_.html

Configuring foreign bus definitions:-

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0001_.html

Multiple bus topology:-

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0001_.html
Point to point messaging across multiple buses:-
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0001_.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0001_.html

Viewing the status of a WebSphere MQ link and its components

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0001_.html

Service integration bus:-

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0001_.html

Securing connections to a WebSphere MQ network:-

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0001_.html

The service integration environment backup:-

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsptopic=/com.ibm.websphere.pmc.express.do
c/concepts/cjc0001_.html

Restoring a data store and recovering its messaging engine:-

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?
topic=/com.ibm.websphere.pmc.express.doc/concepts/cjc0001_.html