We have reviewed the entire set of integration flows for the Oracle Application Integration Architecture Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release 11.3 and as a result of the reviews, working with customers, and understanding the most common use cases and deployment scenarios, we have made a number of changes. The most significant of these changes is to optimize for the most common deployment scenarios. Oracle believes that these changes result in:
Reduction in the number of artifacts required to complete the end-to-end integration flows.
Reduction in the number of “hops” between the various participating applications and middleware components – simplifying operational management.
Preserving the ability for more complex deployments when and where warranted.
Because of these optimization changes, for release 11.3, this guide has been updated in several ways, including the removal of enterprise business services (EBSs) from integration flows and also the way in which the Composite Application Validation System (CAVS) is enabled. (Previously you used the CAVS UI -- now you are asked to modify the AIA configuration properties file).
EBSs were introduced to simply help route to multiple provider connectors. However, the majority of our customers are using just one source and one target system for most of the integration flows. With this configuration, dynamically identifying a provider system during runtime (content-based routing) is never required and EBSs are therefore, unnecessary. The removal of EBSs, reduces one hop in each flow, reduces the number of artifacts, and in addition, maintenance and debugging becomes simpler. If required, EBSs can be reintroduced.
The extension points and EBS removal in BPEL's are kept inside customizable scopes. These scopes can be customized by following the "Customizing SOA Composite Applications" section in "Developers Guide for Oracle SOA Suite 11.1.1.x where x>=7."
The following table lists the chapters and sections that have been added or changed.
| Sections | Changes Made |
|---|---|
|
New chapter added for error handling procedures. |
|
|
|
|
|
|
Section 4.2.3, "Defining Transaction Boundaries and Recovery Details" |
New section added to define transaction boundaries and recovery details based on removal of EBSs. |
|
Section 5.2.3, "Defining Transaction Boundaries and Recovery Details" |
New section added to define transaction boundaries and recovery details based on removal of EBSs. |
|
|
|
Section 7.2.8, "Defining Transaction Boundaries and Recovery Details" |
New section added to define transaction boundaries and recovery details based on removal of EBSs. |
|
|
|
Section revised to describe new sequence of events for this flow based on removal of EBSs. The flow diagram has also been updated. New section added to define transaction boundaries and recovery details based on removal of EBSs. |
|
|
Section 10.6, "Defining Transaction Boundaries and Recovery Details" |
New section added to define transaction boundaries and recovery details based on removal of EBSs. |
|
Table B-3, "Queue Operators and Operations"Figure B-3, "Change Priorities" |
Table revised to describe new button - "Ok". The Change Priorities page has also been updated. |
|
Table E-1, "Agile PLM Version Upgrade"Table E-2, "Agile PLM Version Downgrade" |
Table revised to describe Agile PLM versions. |