HLD for OSB Dynamic Routing.

Dynamic Routing

Sterling

Core BPEL Composite

Enterprise Business Service (EBS)

OSB PS

OSB BS

BODI

Step 1 Sterling calls the Core BPEL composite which is exposed as web service through a mediator. Step 2 Core BPEL service calls the EBS service which is another SCA component. EBS is a mediator exposed as web service to the core BPEL service. Step 3 The EBS call OSB proxy service using a direct binding or Web service Adapter. Step 4 The OSB proxy service makes use of the Dynamic routing feature to call the correct operation on the OSB business Service. Step 5 The business service calls the operation on the BODI web service. The response from BODI also flows back to the core BPEL service as all the calls at HTTP/SOAP calls.

HLD for SOA Suite. ABCS job1 Sterling Core BPEL Composite Enterprise Business Service (EBS) BODI ABCS job2 ABCS job...n Step 1 Sterling calls the Core BPEL composite which is exposed as web service through a mediator. Step 2 Core BPEL service calls the EBS service which is another SCA component. EBS is a mediator exposed as web service to the core BPEL composite. Step 3 The EBS calls the ABCS service. This is achieved by assigning the URL to endpointuri property. This URL of the ABCS is passed as an input parameter from the Sterling. Step 4 The ABCS is a mediator which is exposed as a web service. We have one ABCS for each job on the BODI service. ABCS transforms the request and calls the desired operation on the BODI .The response from BODI also flows back to the core BPEL service as all the calls are HTTP/SOAP calls.

OSB dynamic Routing Vs SOA Suite Dynamic Routing OSB Out of the Box feature. Simple to Implement. Development effort is less. Few Resources to deploy and maintain. There should not be more than 5 resources to be deployed. Maintenance is easier as resources are less. For deployment need to contact two teams. If BODI adds a new JOB we just have to update the DB or a constants file. No need for any coding to be done. SOA suite and Scheduler will have no dependency on each other. The coupling is loose. SOA Suite Implemented using AIA. Cumbersome to implement. Development effort is large. Large number of composites to be deployed. We will have one composite for each JOB. Maintenance takes a toll as we have a huge number of composites to be maintained. All deployments can be handled by a single team. A new composite has to be built and deployed.

Scheduler becomes more tightly coupled with SOA Suite as Scheduler needs to know the end point of each ABCS SCA