Introducting the SCA HTTP Binding
From DeveloperWorks, Configuring SCA HTTP binding to enable real-life scenarios
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.
The HTTP binding is new in WebSphere Process Server v6.1. It appears to support REST and includes an example of mashing-up Atom feeds. Enjoy.
Related Posts
- Integrating Oracle BPEL with an HTTP (REST) Service
- Enabling SCA-MQ integration via MQ bindings
- JMS Function Selectors & Method Bindings
- Web services with SOAP/JMS in IBM WebSphere Process Server
- Asynchronous SCA One-Way Operations And How To Recover
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

May 26th, 2008 at 1:52 pm
Hey, Mr. technical architect. Fancy title
So I see you read our HTTP article. Was it helpful?
By the way, have you tried to set up an HTTP binding with SSL and basic auth? I am trying to build a prototype to figure out how to integrate Monitor and WID app. And I am puzzled as it does not seem to work.
Hope you remember me.
Eugene.
May 26th, 2008 at 1:59 pm
Hi Eugene,
“Do I remember you?” I pay professionals money to try to forget!
Alas, my current client is only on v6.0.2 of the software so I haven’t had a chance to play with the HTTP binding on my own. As with any good WebSphere error when things don’t work, what the exception?