List of Figures

1-1 Illustration of the Integration Flow
2-1 Functional Decomposition of a Project into Actual Implemented Services
2-2 Add Project Button
2-3 Add Project Page
2-4 Update Project Page
2-5 Project Tab
2-6 Inactive Update Project Button
2-7 Copy Project Button
2-8 Copy Project Page
2-9 Add Service Solution Component Button
2-10 Sample Project Containing Three Business Tasks
2-11 Nine Composites in the BOM Generated from the Project
2-12 Copy the Project
2-13 Rename the Copied Project
2-14 Select to Update the Copied Project
2-15 Update Business Task Names
2-16 Generate Bill Of Material Link Available for the Edited Project
2-17 Click Generate
2-18 Composites in the Copied and Edited Project
2-19 Project Unique ID Displayed in the Project Lifecycle Workbench
2-20 Add Service Solution Component Button on the Service Solution Component Tab
2-21 Add Service Solution Component Button on the Business Tasks Tab on the Project Tab
2-22 Add Service Solution Component Page
2-23 Link to OER Button
2-24 Update Service Solution Component Button
2-25 Update Service Solution Component Page
2-26 Service Solution Component Page
2-27 Add Service Solution Component Button
2-28 Update Service Solution Component Button
4-1 Export BOM Button
4-2 Project Root Node Actions on the Bill Of Materials Page
4-3 Business Task Branch Node Actions on the Bill Of Materials Page
4-4 Composite Leaf Node Actions on the Bill Of Materials Page
5-1 Sample Usage Flow for Import and Export of Project Lifecycle Workbench Seed Data
6-1 Extending and Deploying Native Artifacts
6-2 Extending and Deploying Non-native Artifacts
7-1 Generate Deployment Plans for ODI
8-1 Edit Artifact Store Dialog Box
8-2 AIA Reference Doc Link
9-1 Example of Annotations
9-2 Example Of Annotation Elements
9-3 Reference Annotation Element Example
9-4 Example of the TransportDetails Element
10-1 Identifying the Interaction Pattern for EBS Operations
10-2 Creating an Assign
10-3 Fire-and-Forget Pattern with Compensation Operation
10-4 Request-Delayed Response Pattern
10-5 Structure of the WSAddress Type Element
11-1 ABCS in Oracle AIA Architecture
11-2 Decision Flow for Defining the ABCS Contract
11-3 GetAccountBalanceSummary Integration Scenario
11-4 Example of One-Way Invocation
12-1 Example of a Requester ABCS Composite
12-2 Example of a Provider ABCS Composite
12-3 Example of a Requester ABCS Composite
12-4 Structure of the WSAddressType
12-5 Structure of the CreateSalesOrderEBMType
12-6 Structure of the SWSAddressType
12-7 Example of Requester ABCS Process
12-8 Programming Model 1: Using a Separate Service for Error Handling
12-9 Programming Model 2: Using JMS Queue as a Milestone Between Requester ABCS and the EBS
12-10 Programming Model 3: Using a Parallel Routing Rule in the EBS
12-11 Structure of CreateSalesOrderResponseEBMType Element
12-12 Async Provider ABCS Composite with a Second Reference to ResponseEBS
12-13 Example of Query with Nested Query Expressions
13-1 Extending the Request-Response Interaction Style
13-2 Requester-Specific ABCS Using Fire-and-Forget Interaction Style
13-3 Provider-Specific ABCS Using Request-Response Interaction Style
13-4 Provider-Specific ABCS Using Fire-and-Forget Interaction Style
13-5 Example of Composite with Two Distinct External References
13-6 Example of Composite with One External Reference
13-7 Setting up the Extension Point Pre-ProcessABM
13-8 Setting up the Extension Point Pre-process EBM
13-9 Introducing a Version Adapter
13-10 System and CAVS-related System Entries on the System-Application Registry Page
13-11 Transaction Boundary
13-12 Transaction Boundary in Asynchronous MEP
15-1 Example of EBF Orchestrating a Flow from Source to Target
15-2 Example of Sales Order Flow
16-1 Schematic Overview of the B2B Architecture of AIA
16-2 Outbound B2B Document Flow
16-3 Inbound B2B Document Flow
16-4 Foundation Pack B2B Infrastructure Components
17-1 High-Level Steps to Develop and Implement a Simple Outbound B2B Flow
17-2 Step 1: Identifying B2B Document and Analyzing Service Requirements
17-3 OAGIS Directory Created to Store OAG Business Object Definitions
17-4 Corresponding XML Schema Files Stored in the OAGIS Directory
17-5 UpdateMetaDataDeploymentPlan.xml Edited to Update the B2BObjectLibrary in Oracle Metadata Services
17-6 Step 2: Developing a New Provider B2B Connector Service
17-7 Processing Flow for a Fire-and-Forget Provider B2BCS
17-8 AIA Metadata in MDS
17-9 AIA B2B Interface Support for Custom Internal Delivery Channels and Legacy B2B Connectivity
17-10 AIAB2BInterface/composite.xml in the Composite Editor
17-11 Addition of New Web Service Call to Interface with Third-Party B2B Software
17-12 AIAB2BInterface/ProcessB2BDocument.mplan in the Composite Editor
17-13 Addition of Custom Routing Rules to AIAB2BInterface/ProcessB2BDocument.mplan
17-14 Transformation Step to Provide Input to B2B Software
17-15 Example Snippet of an Annotated B2BCS Called X12ProcessSalesOrderReqB2BCSImpl composite.xml
17-16 AIA B2B Interface Utility Service Annotation Elements in composite.xml snippet
17-17 Business Component Mapped in the XSLT, including an invocation from the Shipped B2BCS to a Custom XSLT template
17-18 Custom XSLT Templates Defined in a Custom XSLT File
17-19 Trading Partner ID Passed as an Input to the Custom XSLT Template Call
17-20 Copies of Shipped XSLT Files Edited to Include Partner-Specific Mapping Logic and Saved Using a Partner Prefix in the Filename
17-21 DVM File Used to Map Trading Partners to XSLT Files
17-22 Provider B2BCS Implementation BPEL Process Requiring Trading Partner-Specific XSLT
17-23 DVM Lookup to Obtain XSLT Filename
17-24 Retrieval of XSLT Filename
17-25 DVM Used to Store Trading Partner B2B Document Type and Document Revision Information
17-26 B2BCS Composite Defined to Invoke AIAAsyncErrorHandlingBPELProcess
17-27 Invocation of the AIAAsyncEHService
17-28 B2B-Specific Elements in the corecom:Fault
17-29 Step 3: Developing or Extending an Existing Enterprise Business Service
17-30 B2B Implementation in which Trading Partners Need the Same EBM Data Sent Using Different B2B Document Protocols
17-31 Filter Expression in the EBS Routing Rule to Each B2BCS Used to Route the EBM Based on the Trading Partner
17-32 DVM Used to Store Trading Partner B2B Preferences
17-33 EBS Implementation Lookup to Determine the Target Provider B2BCS to be Invoked
17-34 Step 4: Developing or Extending an Existing Requester ABCS
17-35 Step 5: Configuring Oracle B2B and Defining Trading Partner Agreements
17-36 Step 6: Deploying and Configuring AIA Services
17-37 Step 7: Testing and Verifying
17-38 B2B Integration Flow Test Using CAVS
17-39 B2B Integration Flow Test Using Dummy Trading Partner Endpoints
17-40 B2B Integration Flow Test Using the Product code Value Set to "Test"
17-41 B2B Integration Flow Test Using Dummy Business Data
17-42 Step 8: Going Live and Monitoring
18-1 High-Level Steps to Develop and Implement a Simple Inbound B2B Flow
18-2 Step 1: Identifying B2B Document and Analyzing Service Requirements
18-3 Step 2: Adding Inbound Routing Rules to an AIA B2B Interface
18-4 Oracle B2B Routing New B2B Documents to Requester B2B Services
18-5 composite.xml in Oracle JDeveloper
18-6 New Service Reference Added to the Requester B2BCS that Processes the New Inbound B2B Document Type
18-7 Wiring Added to the Newly Added Service from the Receive B2BM Mediator Component in the Composite
18-8 ProcessInbound.mplan
18-9 New Routing Rule to Invoke the Requester B2BCS
18-10 Routing Filter Ensuring that EDI X12 Process Sales Order Documents are Routed to ProcessSalesOrder B2BCS Implementation
18-11 Step 3: Developing a New Requester B2B Connector Service
18-12 Process Flow of a Simple Fire-and-Forget Message Exchange Pattern-Based Provider B2BCS
18-13 AIA Metadata in the MDS
18-14 Example Snippet of an Annotated B2BCS Called X12ProcessSalesOrderReqB2BCSImpl composite.xml
18-15 Reference to the AIA EBS Invoked by the B2BCS Annotated in the composite.xml
18-16 B2BCS Composite Defined to Invoke AIAAsyncErrorHandlingBPELProcess
18-17 Invocation of the AIAAsyncEHService
18-18 B2B-Specific Elements in corecom:Fault
18-19 Step 4: Developing or Extending an Existing Enterprise Business Service
18-20 Step 5: Developing or Extending an Existing Provider ABCS
18-21 Step 6: Configuring Oracle B2B and Defining Trading Partner Agreements
18-22 Step 7: Deploying and Configuring AIA Services
18-23 Step 8: Testing and Verifying
18-24 Step 9: Going Live and Monitoring
19-1 Overview of the Service Construction Phase of the AIA Project Lifecycle
19-2 Flow for Creating a New AIA Service Component
19-3 Typical Opening View of a Generic Application in Oracle JDeveloper
19-4 All Technologies Tab
19-5 Welcome to the AIA Service Constructor
19-6 Import the Service Description
19-7 AIA Resource Browser
19-8 Connection
19-9 Service Solution Component Requests
19-10 Service Description Populated from Project Lifecycle Workbench Service Solution Component Request
19-11 Service Details
19-12 Service Object Definition for a Requester ABCS
19-13 Service Object Definition for a Provider ABCS
19-14 Select Service Operation
19-15 SOA Resource Browser
19-16 SOA Resource Browser - WSDL Selection
19-17 Select Service Operation - Operation Selected
19-18 Service Object Definition for a Provider ABCS - WSDL Information Populated
19-19 CallBack Button
19-20 Call Back Details
19-21 Service Object Fault Details
19-22 Target Service Details
19-23 Target Service Options
19-24 Target Service Fault Details
19-25 Service Options
19-26 Create Additional Target
19-27 Example of the ABCS Composite
20-1 AIA Project Lifecycle Flow: Phases and Actors
20-2 Example of a Requester Application Interacting Directly with a Provider Application
20-3 Example of Integration Flow with Native Application Services
20-4 Example of Integration Flow Leveraging Provider Services
20-5 Example Showing Canonical Model-based Virtualization
20-6 Systems page (1 of 2)
20-7 Systems page (2 of 2)
20-8 Flow of System Registration Data
21-1 Example of Inbound Connectivity
21-2 Example of Outbound Connectivity
21-3 Illustration of Using Web Services with SOAP/ HTTP
21-4 Example of Multiple Milestones in a Business Process (1 of 2)
21-5 Example of Multiple Milestones in a Business Process (2 of 2)
22-1 Initial Data Loads
22-2 Intermittent High-Volume Transactions
22-3 High-Volume Transactions
22-4 Using the XREF Knowledge Module
22-5 Variable: GetSourceColumnName Page
22-6 Interface Diagram Page
22-7 Package to Run the Interfaces
22-8 Filter for XREF_VW with a WHERE Clause to Filter Data from Your Table Name Only
22-9 Mapping Data Store and XREF_VW Joined with Columns that Store the Common ID
22-10 XREF_TABLE_NAME, XREF_COLUMN_NAME and VALUE Marked as Keys
22-11 Package Created to Run the Interface
22-12 XML Used in the JDBC Description for the Data Server
22-13 DVM XML Results in Six Tables Following Reverse-Engineering
22-14 Join of IM_FINANCIALS_STAGE with the CELL Table
22-15 Join of the CELL Table with the COLUMN Table
22-16 Filter Added to the COLUMN Table
22-17 Join of CELL1 with the COLUMN1 Table
22-18 Filter Added on the COLUMN1 Table
22-19 Self-Join of the CELL Table with Another CELL (CELL1) Table
22-20 Second CELL Data in the Target Interface Mapping
22-21 Sample Interface that Invokes AIAAsyncErrorHandlingBPELProcess When it Ends in Error
22-22 Topology Configuration
22-23 Services - Data Services Page
23-1 Canonical Pattern Implemented in AIA
23-2 Layout of the XSLT Mapper
23-3 Structure of the Identification Type Element
23-4 Structure of the Business Component ID
23-5 EBM Header Components
23-6 Structure of the Sender Element
23-7 Structure of the ESBHeaderExtension Element
23-8 Structure of the ESBHeaderExtension Element
23-9 Structure of the ObjectCrossReference Element
23-10 Structure of the Target Element
23-11 Structure of the BusinessScope Element
23-12 Use Case: Request-Response
23-13 Use Case: Asynchronous Process
23-14 Synchronous Process with Spawning Child Processes
23-15 ProcessOrder flow
23-16 Structure of the EBMTracking element
24-1 Assignment of the Faults in the Mediator
24-2 Integration Flow in Which the Receiver Target Milestone is the Target Participating Application
24-3 Integration Flow in Which the Receiver Target Milestone is Within the Global Transaction Space
24-4 Transaction Rollback Flow
24-5 Fault Element and Its Child Elements (1 of 2)
24-6 Fault Element and Its Child Elements (2 of 2)
24-7 EBMReference Element and Its Child Elements
24-8 B2BMReference Element and Its Child Elements
24-9 FaultNotification Element and Its Child Elements
24-10 IntermediateMessageHop Elements
24-11 ApplicationFaultData Element Highlighted in Meta.xsd
24-12 Example Error Extension Handler Property and Value in AIAConfigurationProperties.xml
24-13 Sample Extended Error Handling Flow Alongside a Default Error Handling Flow
25-1 Invoking an EBS Synchronously by the Requester Application
25-2 Fire-and-Forget Pattern Using Queuing Technology
25-3 Ensuring Guaranteed Delivery Using Milestones
25-4 Using Milestones to Ensure Guaranteed Delivery in a Complex Use Case
25-5 Content-Based Service Instance Routing
25-6 Setting Up Multiple Consumers or Listeners Connected to the Source Queue
25-7 Example of the Asynchronous Delayed Response Pattern
25-8 Example of Interaction Divided into Two Transactions: Error Handling and Requester ABCS
25-9 Error Scenario when Using JMS Queue as a Milestone
25-10 Error Scenario Using Parallel Routing Rule and Web Service Call
25-11 Extending AIA Services
26-1 High-level Security Architecture
26-2 Security Functional Flow
26-3 Requester Application Flow
26-4 Provider Application Flow
26-5 Structure of XACML Request
26-6 Structure of XACML Subject
26-7 Structure of XACML Resource
26-8 Structure of XACML Action
26-9 Structure of XACML Environment
27-1 References Between SOA Composites
27-2 Example of Adapters Interfaced with ABCS in a Different Composite
27-3 Example of ABCS and Transport Adapter Service in the Same Composite
A-1 Systems Page Entry and aia:getEBMHeaderSenderSystemNode()
A-2 Systems Page Entry and aia:getSystemType()