SOA Composite Templates
One of the best new feature in this SOA 12.1.3 release is this about the Template.The SOA template can really increase the productivity of the Developers team and Oracle is right saying this..
Here I just want to recap the different type of template and main features, across SOA and OSB, hope this might help.
SOA ‘Starter’ Templates
- ‘Starter’ Template is a re-usable part of a SOA project
- Fully editable
- Store in MDS
- Three types:
- SOA Project Template
- Component Template
- Custom Activity Template
- Project template accessible at the time of new project creation
- Automatically discover in the component palette
- Component Template
- Custom Activity Template
- Share and re-use from MDS
BPEL Sub-processes: standalone and inline
Very useful for groups of activities that are reused within one (inline) BPEL process or the whole Composite (standalone).
- Allows business logic to be modularized and reused
- Permits access of data in parent process
- Improves performance and manageability
- Compensation and fault handling inherited from calling process
- Faster rendering as only the entity in question is rendered
Service Bus Templates
Pipeline ‘Inherited’ Templates
- New artifact type.
- Two ways to create a Template
- Generate template from existing pipeline
- Create template from scratch.
- New pipelines are generated from the Template.
- Derived pipelines are considered concrete
- Concrete pipelines can be linked (default) or unlinked
- If linked, all changes in Template are reflected in derived concretes
- Templates actions can be ‘Locked’
- Placeholders in Pipeline template to define where modifications may be placed
Share artifacts within and across applications
SOA Design-Time MDS Repository
- Wizard to share design time artifacts such as WSDLs and Schemas
- Moves the artifacts and its dependencies to Design-Time MDS (viz. schema with WSDL)
- Updates all the references to the transferred artifacts with MDS URLs on transfer
