WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Service integration

This set of topics provide information about the service integration technologies.

Why and when to perform this task

Service integration is implemented as a group of messaging engines running in application servers (usually one engine to one server) in a cell.

Service integration is a complete JMS v1.1 provider implementation (not just an API but a working messaging system. The JMS provider is a pure Java implementation that runs within the application server's JVM process. For persistent messaging, WebSphere Application Server also requires a JDBC compliant database such as DB2.

As a result, JMS messaging is built into WebSphere Application Server and is easily available to any J2EE application deployed in WebSphere Application Server.

Why use a service integration bus?

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?

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


Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tji0000_.html

© Copyright IBM Corporation 2004, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)