Ana içeriğe atla

porting datamodel from SOA Suite to OSB - part 2

in addition to part 1 , we have some other duties to do.

supposing that you have created some interfaces that clients connect to SOA Suite, these interface wsdls' do not have binding part in abstract form, but in runtime, SOA Suite generate it for clients.

if you have an intent to port these abstract wsdls while unbeknownst to the caller parties about the porting from SOA Suite to OSB, perhaps you want to use these abstract wsdls as a proxy service, which clients want to connect with OSB.

to make this, you must generate binding parts as SOA Suite does. below is a simple snipped part of abstact wsdl (wsdl that generated by jdev for composite to soap interface ) that shows the portType which has not got the binding part. when you deploy a composite which has an soap interface depending on this wsdl to SOA Suite, this portType has a binding part as shown below. as you can quickly realize that, is has an easy pattern for this part. you can see it blow abow example shows an asynchronous interface that served from SOA.

depending on synchronous or asynchronous interface defined, you have 1 or 2 portType. synchronous interface one portType and most probably two operations input and output and maybe in addition to this a fault can be, asynchronous interface two portTypes and one operation for per portType.

then you have to careful about this point when generating binding part from abstract wsdl that generated by jdev to port it and use it as exactly same way like SOA in OSB. in a conclusion, below is the full ant script to do all the necessary things and prepare your datamodel for OSB.

Yorumlar