Conclusion
In this tutorial we have used WebSphere Integration Developer and WebSphere ESB to develop and test:
- An MQ client that can send MQ messages containing a custom data type
- A Java Service implemented using a Java component
- A custom data binding allowing the format of the message to be translated into the format required by the service
This tutorial has shown how to invoke a Web service using WebSphere MQ. However, the same custom data binding could be used to expose an MQ application as a Web service. By connecting an Export, with a Web service Binding, to an MQ Import, using our custom data binding, MQ applications could be invoked with a Web service call. Hopefully this article has given you a basic understanding of how to use these two products, to integrate WebSphere MQ and WebSphere MQ applications with Web services.
6 of 9 |
Previous |
Next
Comments
Back to top
Help: Update or add to My dW interests
What's this?
This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.
And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.
View your My developerWorks profile
Return from help
static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=SOA and Web services, WebSphere
ArticleID=188387
TutorialTitle=Invoke Web services with WebSphere MQ and WebSphere Enterprise Service Bus
publish-date=01162007
author1-email=nortonp@uk.ibm.com
author1-email-cc=