How many times have you developed a new composite, or migrated an older composite, that simply turned into an overly complex process? Modifying and debugging the new process can become more difficult and take longer to implement.
A good java implementation breaks the problem into manageable classes that can be easily understood and managed over the life of the implementation. Since this works well with java, why not apply the basic principle to a composite. In comes SOA 12C and the implementation of subprocesses, which can be utilized for breaking down a composite into manageable components.
Breaking down a complex composite provides several benefits:
Now I will show a simplistic example of a composite that performs database syncing. The composite will attempt to sync table 1 and if any number of records are sync’d, then we want to sync table 2. I will not go into the details of how to create a subprocess since there are many tutorials already available.
My general approach is to simplify the main process so the flow is easier to follow. This concept can be extended to the subprocess layer in a similar fashion as the BPEL layer, if the subprocess layer becomes too complex. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.