3/42

List of Figures

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