In the jdeveloper 11g tp3 you can configure a soa project where you can use sdo webservice as a reference adapter. Too bad this is not working (at runtime) in TP3 but this blog will show you how you can use sdo web services in a bpel process and it gives an overview how soa suite 11g works.
First what is SDO ? This is a technology which is developed by IBM, SAP, BEA, Oracle etc. SDO or Service Data Objects is designed to simplify and unify the way in which applications handle data. Oracle made it very easy with adf bc (bc4j) to make sdo webservices. You only have to edit the application module, Go the service definitions link and enable support for service definitions. Select the viewobjects and the operations you want to use. Deploy this to the embedded oc4j and we have our sdo webservice.
In this example I used the customer table of the oe sample schema. In the viewobject of this customer table I had the remove the following attributes cust_address, phone_numbers, cust_geo_location because these types are not supported by sdo.
We are ready to make a soa 11g project. Create a new soa project and open the composite.xml Now drag the bpel process from the component windows to the components area of the composite.xml. Make sure you check create composite service.
Now we can add the sdo webservice. Drag the sdo webservice to the reference area of the composite.xml. Now fill in the wdsl entry of our customer sdo web service and select the operation. Now drag a line from the bpel proces to the sdo web service, so we can use it in the bpel process
This is a bit different as in 10.1.3. In the composite.xml we define our adapters and which adapters the bpel can use ( the line between the components) . Now we complete the bpel process by clicking on the bpel process in the composite.xml. Here we add an invoke service to call our sdo webservice and in this we select the right operation getCustomerView.
We add some assign activities to fill the input variable of the sdo web service and one to assign the output of the ws to the output of the bpel.
Run the composite.xml and go the following url http://localhost:8988/soa-infra/ to test our bpel web service. This goes wrong because in TP3 the runtime support of sdo is not supported in this release but let's look at the soa suite console why it goes wrong.
Now we can look at the details
In the TP4 release I will retest it and update this blog