Configuring SCA HTTP binding to enable real-life scenarios

From the developerWorks archives

Eugene Kharlamov and Mihnea Galeteanu

Date archived: June 29, 2017 | First published: March 26, 2008

You can use HTTP bindings supported by IBM WebSphere Integration Developer Version 6.1 in many common real-life integration scenarios involving Service Component Architecture (SCA) applications. For example, by properly configuring the HTTP bindings you can expose SCA applications as a simple HTTP URL using HTTP export binding; enable SCA applications to consume third party XML Web services using HTTP import binding; and use HTTP bindings to integrate multiple SCA applications.

Using a downloadable, hands-on, sophisticated example SCA application, you see how to configure the key HTTP binding attributes to enable these scenarios. It is intended for WebSphere business integration consultants and developers who want to integrate SCA applications using HTTP infrastructure.

You should have a good understanding of an SCA application's structure, common SCA components (Java™ Component, BPEL component, Mediation Flow, XSL transformation map), SCA bindings and their common configuration attributes (Function selector, Data binding), SCA mediation, the WebSphere Integration Developer 6.1 tooling environment, and HTTP infrastructure. Understanding the sample Web client code requires some knowledge of JavaScript and basic HTML. For help in learning more about these topcis see Resources.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.

ArticleTitle=Configuring SCA HTTP binding to enable real-life scenarios