We are trying to use business processes defined in Websphere Integration Developer to coordinate coarse grained services. It seems like currently websphere process server and integration developer use "Classic SCA" and WAS SCA feature pack uses Open SCA.
While there is some interoperability between these two flavours of SCA there are limitations like not support for SCA async binding.
Are there any plans to migrate WID and WPS to open SCA?
This topic has been locked.
2 replies Latest Post - 2010-05-13T21:31:30Z by Rohit_R
Pinned topic Websphere Integration Developer 7.0 and Open SCA
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2010-05-13T21:31:30Z at 2010-05-13T21:31:30Z by Rohit_R
SteveKinder 110000HUHT14 PostsACCEPTED ANSWER
Re: Websphere Integration Developer 7.0 and Open SCA2010-05-12T13:31:58Z in response to Rohit_RRohit,
IBM has been on a journey to standardize Service Component Architecture for a number of years. As you're probably aware, the precursor to the Open Specification support we have delivered in WebSphere Application Server was pioneered by the WESB, WPS and BPM Suite starting with their V6 release. The precursor version we call Classic SCA to distinguish it from the Open spelling. IBM seeded the open consortium with Classic SCA, and as usually happens when you collaborate, other vendor's perspectives shaped the specifications such that while the concepts and principles are identical, there are syntactical and semantic differences based on concessions made to move the specifications forward.
In V7 we started the journey towards embracing the Open SCA world in our WESB, WPS, etc. products with the SCA binding as you suggest in your post; and the stated long term direction is to embrace Open SCA in the portfolio. You can also see evidence of this support in CICS which has initial support for Open SCA assemblies.
As we roll out support in the various products and tools IBM needs to also protect the large number of successful deployments of applications which leverage the Classic SCA programming model; so you'll see us move forward towards adopting Open SCA but protecting our customers business and technical investment.
SOA Architect for WebSphere
Rohit_R 270000VB9P24 PostsACCEPTED ANSWER
Re: Websphere Integration Developer 7.0 and Open SCA2010-05-13T21:31:30Z in response to SteveKinderSteve, thanks for the reply.
I ran into another issue which is related to invoking Open SCA service using a business process but I have opened another thread regarding that.