In this section, we are going to take a BPEL component in a stand alone SOA Composite application, and turn it into a Component Template that we publish to be reused across different projects. Note that unlike a Service Bus pipeline template, there is no lasting relationship between the template and components derived from the template. Using a SOA component template is more like a complex copy and paste operation than an inheritance definition.
Next, we will create a new BPEL component in the FlightScheduleService composite, based on this template. The new component is wired to the existing FlightScheduleProcessor component and invoked from the last remaining empty scope CheckAirlineWithFinancialDepartment. This in turn completes the ProcessingAndRoutingScope.
The starting point for this section is application FlightScheduleService_step5. The end result is in FlightScheduleService_step6.