Lesson13-Service Data Objects (SDO)

Please complete part1 of this example before continuing …

Lets build Order BPEL process to consumer ADF Business Components we created in previous example through an entity variable.

• Create an SOA project and name it “OrderSDOProcess”. Select Empty Composite from next screen and click Finish.

• Make a note of OrderSDO service WSDL we created in previous step. In my case,  it is http://192.168.0.5:7001/OrderBCServices/OrderSDOService?WSDL.
• Drag and drop a BPEL Process component on to components section of composite.xml. Name it “OrderSDOProcess”. Select “Base on a WSDL” as template.

Related posts

• BPEL Entity Services and SDO – Part1
• What is Fusion Middleware?
• Validations
• SOA Suite 11g Mediator Example Implementation Part 3
• SOA Suite 11g Mediator Example Design

We have seen in previous articles how DB Adapter can be used in SOA Suite to write information to Database. SOA Suite 11g provides another method to implement Entity Services: Service Data Object (SDO).

SDO provides a unified interface to access datasource, irrespective of its type, from SOA composite. This is achieved by creating Data Services with the help of ADF Business Components. At the outset, it may sound no different from previous methods. However, the difference is that the data can be accessed with the help of an entity variable within BPEL. Data is synchronized with external updates as well. Nested objects are also supported. In addition, we can enable RMI communication instead of SOAP to improve performance.

Related posts

• BPEL Entity Services and SDO – Part2
• What is Fusion Middleware?
• Validations
• SOA Suite 11g Mediator Example Implementation Part 3
• SOA Suite 11g Mediator Example Design