Contents

Expand All · Collapse All

Title and Copyright Information

Preface

• Audience
• Oracle AIA Guides
• Related Guides
• Documentation Accessibility
• Conventions

1 Using SOA Core Extensions for AIA Development

• 1.1 AIA Development Using SOA Core Extension
• 1.2 Understanding AIA
  • 1.2.1 AIA Foundation Pack
  • 1.2.2 AIA Pre-built Integrations and Process Integration Packs (PIPs)
• 1.3 AIA Integration Types
• 1.4 AIA Integration Flows
• 1.5 How to Use this Developer's Guide

2 Building AIA Integration Flows

• 2.1 Setting up Development and Test Environments
  • 2.1.1 Getting a Quick Start on your AIA Development
  • 2.1.2 How to Set Up AIA Workstation
• 2.2 AIA Artifacts in Various Integration Styles
  • 2.2.1 Integration Through Native Application Interfaces Using the Oracle Applications Technology Infrastructure
  • 2.2.2 Understanding Integration Styles with Integration Framework
  • 2.2.3 Bulk Data Processing
  • 2.2.4 Integration Style Choice Matrix
• 2.3 Development Tasks for AIA Artifacts
  • 2.3.1 Identifying the EBO
  • 2.3.2 Designing an Oracle AIA Integration Flow
  • 2.3.3 Identifying and Creating the EBS
  • 2.3.4 Constructing the ABCSs
  • 2.3.5 Enabling and Registering Participating Applications
  • 2.3.6 Identifying and Creating the EBF
• 2.4 Testing an Oracle AIA Integration Flow

3 Implementing Direct Integrations

• 3.1 Understanding Direct Integrations
• 3.2 Using the Application Business Flow Design Pattern for Direct Integrations
• 3.3 Finding the Correct Granularity
• 3.4 Handling Transactions
  • 3.4.1 Building an ABF as a Transactional Composite
  • 3.4.2 Achieving Transactionality in the ABF
• 3.5 Enabling Outbound Interaction with Applications
  • 3.5.1 Using JCA Adapters
  • 3.5.2 Using Standard Web Service Interfaces (SOAP/HTTP, XML/HTTP)
  • 3.5.3 Using JMS Queues
  • 3.5.4 Using Adapters in a Composite or as a Separate Composite
• 3.6 Invoking an ABF
• 3.7 Handling Errors
  • 3.7.1 Using Direct Integration Services
  • 3.7.2 Using the Fault Management Framework
• 3.8 Securing the Service
  • 3.8.1 Security Recommendations for OWSM Policies for Authentication
  • 3.8.2 Attaching OWSM Policies to the Composites
• 3.9 Using Cross References
• 3.10 Naming Conventions and Standards
  • 3.10.1 Additional Guidelines for Naming Services
• 3.11 Annotating Composites
  • 3.11.1 Annotating WSDLs
• 3.12 Service Configuration
• 3.13 Extending Direct Integrations
  • 3.13.1 Extending XSLs
  • 3.13.2 Extending Services
  • 3.13.3 Guidelines for Enabling Customizations

4 Developing and Deploying Custom XPath Functions

• 4.1 Implementing a Function in Java as a Java XPath Class
  • 4.1.1 Naming Standards for Custom XPath Functions
  • 4.1.2 Supported Data Types
• 4.2 Deploying the XPath/XSL Function in JDeveloper
• 4.3 Deploying the XPath/XSL Function in the Application Server

5 Designing and Developing Enterprise Business Services

• 5.1 Introduction to Enterprise Business Services
  • 5.1.1 Understanding EBS Types
  • 5.1.2 Working with the Enterprise Business Service Library
• 5.2 Designing the EBS
  • 5.2.1 Understanding Design Guidelines
  • 5.2.2 Understanding Design Considerations
  • 5.2.3 Establishing the MEP of a New Process EBS
  • 5.2.4 How to Establish the MEP for a New Process EBS
  • 5.2.5 How to Handle Errors
  • 5.2.6 How to Secure the EBS
  • 5.2.7 How to Configure Transactions
  • 5.2.8 How to Guarantee Delivery
  • 5.2.9 How to Define the EBS Service Contract
• 5.3 Constructing the WSDL for the Process EBS
  • 5.3.1 Introduction to WSDL Construction for the Activity Service EBS
  • 5.3.2 How to Complete the <definitions> Section
  • 5.3.3 How to Define Message Structures
  • 5.3.4 How to Check for WS-I Basic Profile Conformance
• 5.4 Working with Message Routing
  • 5.4.1 Creating Routing Rules
  • 5.4.2 Routing at the EBS
  • 5.4.3 Guidelines for EBS Routing Rules
  • 5.4.4 How to Identify the Target System at EBS
• 5.5 Building EBS Using Oracle Mediator
  • 5.5.1 How to Develop the Oracle Mediator Service
• 5.6 Implementing the Fire-and-Forget Message Exchange Pattern
  • 5.6.1 How to Implement Fire-and-Forget Pattern with EBS One-Way Calls
  • 5.6.2 Creating EBS WSDLs
  • 5.6.3 Creating Mediator Routing Services for Asynchronous Fire-and-Forget Patterns with a One-Way Call EBS
  • 5.6.4 Asynchronous Fire-and-Forget MEP Error Handling Using Compensatory Operations
  • 5.6.5 How to Invoke the Compensate Operation of EBS
  • 5.6.6 How to Enable Routing Rules in Compensate Operation Routing Service
• 5.7 Implementing the Synchronous Request-Response Message Exchange Pattern
  • 5.7.1 How to Implement Synchronous Request-Reply Message Exchange Patterns in EBS
  • 5.7.2 How to Create Mediator Projects for the Synchronous Request-Response MEP
  • 5.7.3 How to Create Routing Services for the Synchronous Request-Response MEP
  • 5.7.4 How to Implement Error Handling for the Synchronous Request-Response MEP
• 5.8 Implementing the Asynchronous Request-Delayed Response Message Exchange Pattern
  • 5.8.1 How to Implement the Request-Delayed Response Pattern with the Two One-Way Calls of the EBS
  • 5.8.2 Creating Mediator Routing Services for Asynchronous Request-Delayed Response Patterns with Two One-Way Call EBS
  • 5.8.3 Asynchronous Request-Delayed Response MEP Error Handling

6 Designing Application Business Connector Services

• 6.1 Introduction to ABCS
  • 6.1.1 ABCS Types
  • 6.1.2 Designing ABCS - Key Tasks
• 6.2 Defining the ABCS Contract
  • 6.2.1 Defining the Role of the ABCS
  • 6.2.2 Constructing ABM Schemas
  • 6.2.3 Analyzing the Participating Application Integration Capabilities
• 6.3 Identifying the MEP
  • 6.3.1 Introduction to MEPs
  • 6.3.2 Choosing the Appropriate MEP
• 6.4 Technology Options
  • 6.4.1 Outbound Interaction with the Application
  • 6.4.2 Using BPEL for Building ABCS

7 Constructing the ABCS

• 7.1 Constructing an ABCS
  • 7.1.1 Prerequisites
  • 7.1.2 ABCS as a Composite Application
  • 7.1.3 How Many Components Must Be Built
• 7.2 Constructing an ABCS Composite Using JDeveloper
  • 7.2.1 How to Construct the ABCS Composite Using JDeveloper
  • 7.2.2 Developing the BPEL Process
  • 7.2.3 How to Create References, Services, and Components
  • 7.2.4 Moving Abstract Service WSDLs in MDS
• 7.3 Implementing the Fire-and-Forget MEP
  • 7.3.1 When to Use Compensating Services
  • 7.3.2 How to Invoke the Compensating Service
  • 7.3.3 Additional Tasks Required in Provider ABCS to Implement This MEP
  • 7.3.4 How to Ensure Transactions
  • 7.3.5 How to Handle Errors
• 7.4 Implementing the Asynchronous Request Delayed Response MEP
  • 7.4.1 How to Populate the EBM Header for Asynchronous-Delayed Response
  • 7.4.2 Setting Correlation for the Asynchronous Request-Delayed Response MEP
  • 7.4.3 Programming Models for Handling Error Response in the Asynchronous Request-Delayed Response MEP
  • 7.4.4 What Tasks Are Required in Provider ABCS to Implement This MEP
• 7.5 Implementing Provider ABCS in an Asynchronous Message Exchange Scenario
  • 7.5.1 How to Implement the Asynchronous MEP
  • 7.5.2 Using the Programming Models for the Request-Delayed Response Pattern
  • 7.5.3 How to Ensure Transactions in Services
  • 7.5.4 How to Handle Errors in the Asynchronous Request-Delayed Response MEP
• 7.6 Implementing Synchronous Request-Response Message Exchange Scenario
  • 7.6.1 How to Ensure Transactions in Services
  • 7.6.2 How to Handle Errors in the Synchronous Request-Response MEP
  • 7.6.3 How to Optimize the Services to Improve Response Time
• 7.7 Invoking Enterprise Business Services
  • 7.7.1 Create
  • 7.7.2 Update
  • 7.7.3 Delete
  • 7.7.4 Sync
  • 7.7.5 Validate
  • 7.7.6 Process
  • 7.7.7 Query
• 7.8 Invoking the ABCS
  • 7.8.1 How to Invoke an ABCS Directly from an Application
  • 7.8.2 How to Invoke an ABCS Using Transport Adapters
  • 7.8.3 When Does an Enterprise Business Service Invoke an ABCS

8 Completing ABCS Development

• 8.1 Developing Extensible ABCS
  • 8.1.1 Introduction to Enabling Requester ABCS for Extension
  • 8.1.2 Introduction to Enabling Provider ABCS for Extension
  • 8.1.3 How to Design Extensions-Aware ABCS
  • 8.1.4 Designing an ABCS Composite with Extension
  • 8.1.5 Defining Service at Extension Points
  • 8.1.6 Defining a Service Using an Abstract WSDL
  • 8.1.7 How to Specify a Concrete WSDL at Deployment Time
  • 8.1.8 Designing Extension Points in the ABCS BPEL Process
  • 8.1.9 How to Set Up the Extension Point Pre-ProcessABM
  • 8.1.10 How to Set Up the Extension Point Pre-ProcessEBM
  • 8.1.11 How to Test the Extensibility with Servlet as Sample Extension Service
• 8.2 Handling Errors and Faults
  • 8.2.1 How to Handle Errors and Faults
• 8.3 Working with Adapters
  • 8.3.1 Interfacing with Transport Adapters
  • 8.3.2 How to Develop Transport Adapters
  • 8.3.3 How to Develop Portal DB Adapter
  • 8.3.4 When to Put Adapters in a Single Composite
  • 8.3.5 Planning Version Adapters
  • 8.3.6 How to Configure a Version Adapter
• 8.4 Developing ABCS for CAVS Enablement
  • 8.4.1 How to CAVS Enable Provider ABCS
  • 8.4.2 How to CAVS Enable the Requester ABCS
  • 8.4.3 Introduction to the CAVSEndpointURL Value Designation
  • 8.4.4 Purging CAVS-Related Cross-Reference Entries to Enable Rerunning of Test Scenarios
• 8.5 Securing the ABCS
  • 8.5.1 How to Secure the ABCS
• 8.6 Enabling Transactions
  • 8.6.1 How to Ensure Transactions in AIA Services
  • 8.6.2 Transactions in Oracle Mediator
  • 8.6.3 Transactions in BPEL
  • 8.6.4 Developing ABCS to Participate in a Global Transaction
  • 8.6.5 How to Transaction-Enable AIA Services
• 8.7 Guaranteed Message Delivery
• 8.8 Versioning ABCS
  • 8.8.1 Guidelines for Versioning
• 8.9 Resequencing in Oracle Mediator
  • 8.9.1 Configuring the Oracle Mediator Service to Use its Resequencer Feature
  • 8.9.2 How to Configure the Resequencing Strategy
  • 8.9.3 Processing Multiple Groups Parallelly
  • 8.9.4 Describing Oracle Mediator Resequencer Error Management
  • 8.9.5 Tuning the Resequencer
• 8.10 Developing Layered Customizations
  • 8.10.1 Deploying services after customizations
  • 8.10.2 Customizing the Customer Version
  • 8.10.3 Applying patches after customization

9 Designing and Constructing Enterprise Business Flows

• 9.1 Introduction to Enterprise Business Flows
• 9.2 How to Define the Contract for an EBF
  • 9.2.1 How to Identify the Need for an EBF
  • 9.2.2 How to Identify the Message Pattern for an EBF
  • 9.2.3 How to Identify the Message Structure
• 9.3 How to Create the Contract for an EBF
  • 9.3.1 Constructing the WSDL for the EBF
• 9.4 How to Implement the EBF as a BPEL Service

10 Introduction to B2B Integration Using AIA

• 10.1 Overview of B2B Integration Using AIA
• 10.2 Understanding B2B Document Flows
  • 10.2.1 Describing Outbound B2B Document Flows Built Using AIA
  • 10.2.2 Describing Inbound B2B Document Flows Built Using AIA
• 10.3 Understanding the Oracle B2B Component of Oracle Fusion Middleware
  • 10.3.1 How AIA Complements Oracle Fusion Middleware Oracle B2B
• 10.4 Understanding the SOA Core Extension Infrastructure for B2B
  • 10.4.1 B2B Support in AIA Error Handling Framework
  • 10.4.2 AIA B2B Interface

11 Developing and Implementing Outbound B2B Integration Flows

• 11.1 Introduction to Developing and Implementing Outbound B2B Integration Flows
• 11.2 Step 1: Identifying the B2B Document and Analyzing Requirements
  • 11.2.1 How to Identify the B2B Document Protocol
  • 11.2.2 How to Identify the B2B Document Type and Definition
  • 11.2.3 How to Define the Document in Oracle B2B
  • 11.2.4 How to Define the Document in AIA
  • 11.2.5 How to Identify the EBO, EBS, and EBM to Be Used
  • 11.2.6 How to Design Mappings for the B2B Document
  • 11.2.7 How to Publish Mapping to Trading Partners
• 11.3 Step 2: Developing a New Provider B2B Connector Service
  • 11.3.1 Introduction to a Provider B2B Connector Service
  • 11.3.2 How to Identify the Message Exchange Pattern
  • 11.3.3 How to Develop a B2BCS Service Contract
  • 11.3.4 How to Store a WSDL in the Oracle Metadata Repository
  • 11.3.5 How to Develop a B2B Connector Service
  • 11.3.6 How to Customize the AIA B2B Interface
  • 11.3.7 How to Annotate B2B Connector Services
  • 11.3.8 How to Support Trading Partner-Specific Variants
  • 11.3.9 How to Enable Error Handling
• 11.4 Step 3: Developing or Extending an Existing Enterprise Business Service
  • 11.4.1 How to Route Based on Trading Partner B2B Preferences
• 11.5 Step 4: Developing or Extending an Existing Requester ABCS
  • 11.5.1 What You Must Know About Message Exchange Patterns
  • 11.5.2 What You Must Know About Transformations
• 11.6 Step 5: Configuring Oracle B2B and Defining Trading Partner Agreements
• 11.7 Step 6: Deploying and Configuring AIA Services
• 11.8 Step 7: Testing and Verifying
  • 11.8.1 How to Test Using CAVS
  • 11.8.2 How to Test Using Dummy Trading Partner Endpoints
• 11.9 Step 8: Going Live and Monitoring
  • 11.9.1 Monitoring Using Oracle B2B Reports
  • 11.9.2 Monitoring Using Oracle Enterprise Manager Console
  • 11.9.3 Monitoring Using Error Notifications

12 Developing and Implementing Inbound B2B Integration Flows

• 12.1 Introduction to Developing and Implementing Inbound B2B Integration Flows
• 12.2 Step 1: Identifying the B2B Document and Analyzing Requirements
• 12.3 Step 2: Adding Inbound Routing Rules to an AIA B2B Interface
  • 12.3.1 How to Add a New Routing Rule to the AIA B2B Interface
• 12.4 Step 3: Developing a New Requester B2B Connector Service
  • 12.4.1 Introduction to Requester B2B Connector Services
  • 12.4.2 How to Identify the Message Exchange Pattern
  • 12.4.3 How to Develop a B2BCS Service Contract
  • 12.4.4 How to Store a WSDL in Oracle Metadata Services Repository
  • 12.4.5 How to Develop a B2B Connector Service
  • 12.4.6 How to Annotate B2B Connector Services
  • 12.4.7 How to Support Trading Partner-Specific Variants
  • 12.4.8 How to Enable Error Handling
• 12.5 Step 4: Developing or Extending an Existing Enterprise Business Service
• 12.6 Step 5: Developing or Extending an Existing Provider ABCS
  • 12.6.1 What You Must Know About Transformations
• 12.7 Step 6: Configuring Oracle B2B and Defining Trading Partner Agreements
• 12.8 Step 7: Deploying and Configuring AIA Services
• 12.9 Step 8: Testing and Verifying
• 12.10 Step 9: Going Live and Monitoring

13 Describing the Event Aggregation Programming Model

• 13.1 Overview
  • 13.1.1 Event Producer
  • 13.1.2 Event Aggregator Service
  • 13.1.3 Consumer Service
• 13.2 Implementing the Event Aggregation Programming Model
  • 13.2.1 Creating the Event Aggregation Service
  • 13.2.2 Creating Consumer Service
  • 13.2.3 Implementing Error Handling for the Event Aggregation Programming Model

14 Establishing Resource Connectivity

• 14.1 Introduction to Resource Connectivity
  • 14.1.1 Inbound Connectivity
  • 14.1.2 Outbound Connectivity
• 14.2 Modes of Connectivity
  • 14.2.1 Web Services with SOAP/HTTP
  • 14.2.2 When to Use Web Services with SOAP/HTTP
  • 14.2.3 Session Management for Web Services with SOAP/HTTP
  • 14.2.4 Error Handling for Web Services with SOAP/HTTP
  • 14.2.5 Security for Web Services with SOAP/HTTP
  • 14.2.6 Message Propagation Using Queues or Topics
  • 14.2.7 Ensuring Guaranteed Message Delivery
  • 14.2.8 When to Use JCA Adapters
• 14.3 Siebel Application-Specific Connectivity Guidelines
  • 14.3.1 Inbound: Siebel Application Interaction with AIA Services
  • 14.3.2 Web Services with SOAP/HTTP
  • 14.3.3 Developer Tasks in the Service Design and Construction Phase
  • 14.3.4 Creating JMS Consumers to Consume Siebel Messages from JMS Queues/Topics
  • 14.3.5 Developer Tasks in Service Design and Outline Construction Phase
  • 14.3.6 Outbound - Siebel Application Interaction with AIA Services
  • 14.3.7 Web Services with SOAP/HTTP
• 14.4 Oracle E-Business Suite Application-Specific Connectivity Guidelines
  • 14.4.1 Inbound: E-Business Suite Application Interaction with AIA Services
  • 14.4.2 Concurrent Program Executable
  • 14.4.3 Best Practices and Design Asynchronous Patterns
  • 14.4.4 Business Event Subscription (JCA Connectivity Using OAPPS Adapter)
  • 14.4.5 Outbound: Oracle E-Business Suite Application Interaction with AIA Services
• 14.5 Design Guidelines

15 Using Oracle Data Integrator for Bulk Processing

• 15.1 Introduction to Design Patterns for AIA-Oracle Data Integrator Architecture
  • 15.1.1 Initial Data Loads
  • 15.1.2 How to Perform the Oracle Data Integrator Data Load
  • 15.1.3 High Volume Transactions with Xref Table
  • 15.1.4 Intermittent High Volume Transactions
• 15.2 High-Volume Transactions with Xref Table
• 15.3 Building Oracle Data Integrator Projects
  • 15.3.1 How to Build Oracle Data Integrator Projects
• 15.4 Using the XREF Knowledge Module
  • 15.4.1 What You Must Know About Cross-Referencing
• 15.5 Working with Oracle Data Integrator
  • 15.5.1 How to Define Variables (Source and Target Column Names)
  • 15.5.2 How to Create the First Interface (Source to Target)
  • 15.5.3 How to Create a Package for the First Interface
  • 15.5.4 How to Define the XREF View in SOA
  • 15.5.5 How to Create the Second Interface (Update Target Identifier in XREF)
• 15.6 Working with Domain Value Maps
• 15.7 Using Error Handling
• 15.8 Oracle Data Integrator Ref Functions
• 15.9 How to Publish the Package and Data Model as Web Service

16 Working with Message Transformations

• 16.1 Introduction to Transformation Maps
  • 16.1.1 Connecting Applications to Implement Business Processes
  • 16.1.2 Using Tools and Technologies to Perform Message Transformations
• 16.2 Creating Transformation Maps
  • 16.2.1 Considerations for Creating Transformation Maps
  • 16.2.2 Handling Missing or Empty Elements
  • 16.2.3 How to Map an Optional Source Node to an Optional Target Node
  • 16.2.4 How to Load System IDs Dynamically
  • 16.2.5 Using XSLT Transformations on Large Payloads
  • 16.2.6 When to Populate the LanguageCode Attribute
  • 16.2.7 How to Name Transformations
• 16.3 Making Transformation Maps Extension Aware
  • 16.3.1 How to Make Transformation Maps Extension Aware
  • 16.3.2 How to Make the Transformation Template Industry Extensible
• 16.4 Working with DVMs and Cross-References
  • 16.4.1 Introduction to DVMs
  • 16.4.2 When to Use DVMs
  • 16.4.3 Using Cross-Referencing
  • 16.4.4 How to Set Up Cross References
• 16.5 Mapping and Populating the Identification Type
  • 16.5.1 How to Populate Values for corecom:Identification
• 16.6 Introducing EBM Header Concepts
  • 16.6.1 Standard Elements
  • 16.6.2 Sender
  • 16.6.3 Target
  • 16.6.4 BusinessScope
  • 16.6.5 Use Case: Request-Response
  • 16.6.6 Use Case: Asynchronous Process
  • 16.6.7 Use Case: Synchronous Process with Spawning Child Processes
  • 16.6.8 EBMTracking
  • 16.6.9 Custom

17 Configuring Oracle AIA Processes for Error Handling and Trace Logging

• 17.1 Overview of Oracle BPEL and Mediator Process Error Handling
  • 17.1.1 Understanding Oracle BPEL Error Handling
  • 17.1.2 Understanding Oracle Mediator Error Handling
• 17.2 Overview of AIA Error Handler Framework
• 17.3 Enabling AIA Processes for Fault Handling
  • 17.3.1 What You Must Know About Fault Policy Files
  • 17.3.2 How to Implement Fault Handling in BPEL Processes
• 17.4 Implementing Error Handling for the Synchronous Message Exchange Pattern
  • 17.4.1 Guidelines for Defining Fault Policies
  • 17.4.2 Guidelines for BPEL Catch and Catch-All Blocks in Synchronous Request-Response
  • 17.4.3 Guidelines for Configuring Mediator for Handling Business Faults
• 17.5 Implementing Error Handling and Recovery for the Asynchronous Message Exchange Pattern to Ensure Guaranteed Message Delivery
  • 17.5.1 Overview
  • 17.5.2 Configuring Milestones
  • 17.5.3 Configuring Services Between Milestones
  • 17.5.4 Guidelines for BPEL Catch and Catch-All Blocks
  • 17.5.5 Guidelines for Defining Fault Policies
  • 17.5.6 Configuring Fault Policies to Not Issue Rollback Messages
  • 17.5.7 Using the Message Resubmission Utility API
• 17.6 How to Configure AIA Services for Notification
  • 17.6.1 Defining Corrective Action Codes
  • 17.6.2 Defining Error Message Codes
• 17.7 Describing the Oracle AIA Fault Message Schema
  • 17.7.1 Describing the EBMReference Element
  • 17.7.2 Describing the B2BMReference Element
  • 17.7.3 Describing the FaultNotification Element
• 17.8 Extending Fault Messages
  • 17.8.1 Introduction to Extending Fault Messages
  • 17.8.2 Extending a Fault Message
• 17.9 Extending Error Handling
  • 17.9.1 Introduction to Extending Error Handling
  • 17.9.2 Implementing an Error Handling Extension
• 17.10 Configuring Oracle AIA Processes for Trace Logging
  • 17.10.1 Describing Details of the isTraceLoggingEnabled Custom XPath Function
  • 17.10.2 Describing Details of the logTraceMessage Custom XPath Function
  • 17.10.3 Describing the Trace Logging Java API

18 Working with AIA Design Patterns

• 18.1 AIA Message Processing Patterns
  • 18.1.1 Synchronous Request-Reply Pattern: How to get Synchronous Response in AIA
  • 18.1.2 Asynchronous Fire-and-Forget Pattern
  • 18.1.3 Guaranteed Delivery Pattern: How to Ensure Guaranteed Delivery in AIA
  • 18.1.4 Service Routing Pattern: How to Route the Messages to Appropriate Service Provider in AIA
  • 18.1.5 Competing Consumers Pattern: How are Multiple Consumers used to Improve Parallelism and Efficiency?
  • 18.1.6 Asynchronous Delayed-Response Pattern: How does the Service Provider Communicate with the Requester when Synchronous Communication is not Feasible?
  • 18.1.7 Asynchronous Request Response Pattern: How does the Service Provider Notify the Requester Regarding the Errors?
• 18.2 AIA Assets Centralization Patterns
  • 18.2.1 How to Avoid Redundant Data Model Representation in AIA
  • 18.2.2 How to Avoid Redundant Service Contracts Representation in AIA
• 18.3 AIA Assets Extensibility Patterns
  • 18.3.1 Extending Existing Schemas in AIA
  • 18.3.2 Extending AIA Services
  • 18.3.3 Extending Existing Transformations in AIA
  • 18.3.4 Extending the Business Processes in AIA

19 Working with Security

• 19.1 Introduction to Oracle AIA Remote Security
  • 19.1.1 Securing Service to Service Interaction
  • 19.1.2 Oracle AIA Recommendations for Securing Services
  • 19.1.3 Introduction to Web Service Security Using Oracle Web Services Manager
• 19.2 Implementing Security
  • 19.2.1 Enabling Security for AIA Services
  • 19.2.2 Invoking Secured Application Services
  • 19.2.3 Overriding Policies Using a Deployment Plan
  • 19.2.4 Testing Secured Services using CAVS
• 19.3 Security for Applications
  • 19.3.1 Enabling Security in Application Services
  • 19.3.2 Invoking Secured AIA Services
• 19.4 Deploying Security Policies
  • 19.4.1 Oracle AIA Recommendations for Policies
• 19.5 Policy Naming Conventions
  • 19.5.1 Naming Conventions for Global Policy Sets
  • 19.5.2 Naming Conventions for Overriding Config Params
• 19.6 How Does SOA Core Extension Help in Securing AIA Services?
  • 19.6.1 What Default Policies are Attached to a Service?
  • 19.6.2 How Can the Global Policy be Overridden for an Individual Service?
  • 19.6.3 AIA Security Configuration Properties
• 19.7 Application Security Context
  • 19.7.1 Introduction to Application Security
  • 19.7.2 How To Exchange Security Context Between Participating Applications and ABCS
  • 19.7.3 Mapping Application Security Context in ABCS To and From Standard Security Context
  • 19.7.4 Using the AppContext Mapping Service
  • 19.7.5 Understanding the Structure for Security Context
  • 19.7.6 Using Attribute Names
  • 19.7.7 Propagating Standard Security Context through EBS and EBF
  • 19.7.8 Implementing Application Security Context

20 Best Practices for Designing and Building End-to-End Integration Flows

• 20.1 General Guidelines for Design, Development, and Management of AIA Processes
  • 20.1.1 Interpreting Empty Element Tags in XML Instance Document
  • 20.1.2 Purging the Completed Composite Instances
  • 20.1.3 Syntactic / Functional Validation of XML Messages
  • 20.1.4 Provide Provision for Throttling Capability
  • 20.1.5 Artifacts Centralization
  • 20.1.6 Separation of Concerns
  • 20.1.7 Adapters Inside ABCS Composite OR as Separate Composite
  • 20.1.8 AIA Governance
• 20.2 Building Efficient BPEL Processes
  • 20.2.1 Using BPEL as "Glue", Not as a Programming Language
  • 20.2.2 Avoiding Global Variables Wherever Possible
  • 20.2.3 Avoiding Large FlowN
  • 20.2.4 Controlling the Persistence of Audit Details for a Synchronous BPEL Process
  • 20.2.5 Using Non-Idempotent Services Only When Absolutely Necessary
  • 20.2.6 Defining the Scope of the Transaction
  • 20.2.7 Disabling the Audit for Synchronous BPEL Process Service Components
  • 20.2.8 Including No Break-Point Activity in a Request-Response Flow

21 Oracle AIA Naming Standards for AIA Development

• 21.1 General Guidelines
  • 21.1.1 XML Naming Standards
• 21.2 Composites
• 21.3 Composite Business Process
• 21.4 Enterprise Business Services
• 21.5 Enterprise Business Flows
• 21.6 Application Business Connector Service
  • 21.6.1 Requester Application Business Connector Service
  • 21.6.2 Provider Application Business Connector Services
• 21.7 JMS and Adapters
  • 21.7.1 AQ JMS (Additional Attributes)
  • 21.7.2 Adapter Services Naming
  • 21.7.3 Participating Application Service
• 21.8 DVMs and Cross References
  • 21.8.1 DVMs
  • 21.8.2 Cross References
• 21.9 BPEL
  • 21.9.1 BPEL Activities
  • 21.9.2 Other BPEL Artifacts
• 21.10 Custom Java Classes
• 21.11 Package Structure
• 21.12 Deployment Plans

22 Editing Transformations Using Mapping Editor

• 22.1 Overview of Mapping Editor
• 22.2 Administering the Mapping Editor
  • 22.2.1 Enabling the Mapping Editor
  • 22.2.2 Deploying the AgileAPI.jar File as a Shared Library
• 22.3 Working with the Search For Mapping Page
• 22.4 Editing Transformations
  • 22.4.1 Mapping Editor Page
  • 22.4.2 Building Mappings (Examples)
• 22.5 Editing Rules for Mapping Editor
  • 22.5.1 Definitions
  • 22.5.2 Read-only Sentences
  • 22.5.3 Drag and Drop or Typing
  • 22.5.4 Inserting a Row
  • 22.5.5 Deleting
  • 22.5.6 Editing Rules for For-Each
  • 22.5.7 Allowing Changing Execution Context
  • 22.5.8 Adjusting Relative Paths when Execution Context Changes
• 22.6 Understanding Customization Layer
• 22.7 Deploying Edited Transformations
• 22.8 Removing Customizations

A Delivered Oracle AIA XPath Functions

• A.1 aia:getSystemProperty()
  • A.1.1 Parameters
  • A.1.2 Returns
  • A.1.3 Usage
• A.2 aia:getSystemModuleProperty()
  • A.2.1 Parameters
  • A.2.2 Returns
  • A.2.3 Usage
• A.3 aia:getServiceProperty()
  • A.3.1 Parameters
  • A.3.2 Returns
  • A.3.3 Usage
• A.4 aia:getEBMHeaderSenderSystemNode()
  • A.4.1 Parameters
  • A.4.2 Returns
  • A.4.3 Usage
• A.5 aia:getSystemType()
  • A.5.1 Parameters
  • A.5.2 Returns
  • A.5.3 Usage
• A.6 aia:getErrorMessage()
  • A.6.1 Parameters
  • A.6.2 Returns
  • A.6.3 Usage
• A.7 aia:getCorrectiveAction()
  • A.7.1 Parameters
  • A.7.2 Returns
  • A.7.3 Usage
• A.8 aia:isTraceLoggingEnabled()
  • A.8.1 Parameters
  • A.8.2 Returns
  • A.8.3 Usage
• A.9 aia:logErrorMessage()
  • A.9.1 Parameters
  • A.9.2 Returns
  • A.9.3 Usage
• A.10 aia:logTraceMessage()
  • A.10.1 Parameters
  • A.10.2 Returns
  • A.10.3 Usage
• A.11 aia:getNotificationRoles()
  • A.11.1 Parameters
  • A.11.2 Returns
  • A.11.3 Usage
• A.12 aia:getAIALocalizedString()
  • A.12.1 Parameters
  • A.12.2 Returns
  • A.12.3 Usage
• A.13 aia:getConvertedDate()
  • A.13.1 Parameters
  • A.13.2 Returns
  • A.13.3 Usage
• A.14 aia:getConvertedDateWithTZ()
  • A.14.1 Parameters
  • A.14.2 Returns
  • A.14.3 Usage

B XSL for Developing CAVS-Enabled Oracle AIA Services

• B.1 AddTargetSystemID.xsl
• B.2 SetCAVSEndpoint.xsl