WebSphere WebSphere Application Server Version 6.1.x Feature Pack for Web Services Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Service integration technologies

Service integration is a set of technologies that provides asynchronous messaging services. Use this topic to work with the core technologies on which WebSphere Application Server service integration applications are developed and implemented.

About this task
Why use service integration?
  • Service integration can connect one kind of application to a different kind of application, including situations 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.
  • Service integration can enable J2EE applications running in application servers. Service integration is a complete JMS Version 1.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 works with a JDBC compliant database such as DB2.
  • Service integration can interoperate with your WebSphere MQ messaging system, through use of WebSphere MQ links, and WebSphere MQ servers.
What are the benefits of service integration?
  • 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:


Task topic

Terms of use | Feedback


Timestamp icon Last updated: 27 November 2008
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.wsfep.multiplatform.doc/tasks/tji0000_.html

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