2/42

List of Examples

• 2-1 AIASystemRegistration.xml
• 2-2 AIAInstallProperties.xml
• 2-3 <delete> Element in AIASystemRegistration.xml
• 2-4 System Registration Task in Generated Deployment Plan
• 2-5 SQL Content Extracted by AIA Deployment Driver
• 2-6 Sample SQL Content Extracted by AIA Deployment Driver
• 3-1 SQL Statement Used to Insert Lookup Values into AIA_LOOKUPS_B
• 3-2 SQL Statement Used to Insert Lookup Values into AIA_LOOKUPS_TL
• 3-3 SQL Statement to Insert Internationalized Text for Lookup Values into AIA_LOOKUPS_TL
• 4-1 Reference Element for AIAAsyncErrorHandlingBPELProcess
• 5-1 AIAInstallProperties.xml File Adjustments
• 5-2 adf-config.xml File
• 5-3 Sample HarvesterSettings.xml to Harvest Design-Time Composites into Project Lifecycle Workspace and Oracle Enterprise Repository
• 5-4 Sample HarvesterSettings.xml Used to Harvest Design-Time Composites into Project Lifecycle Workbench Only
• 5-5 AIAInstallProperties.xml File Adjustments
• 5-6 Sample adf-config.xml
• 5-7 oramds:// Protocol Used in HarvesterSettings_#.xml
• 5-8 Sample HarvesterSettings.xml Used to Harvest Custom-Built Deployed Composites into Oracle Enterprise Repository:
• 7-1 Project Lifecycle Workbench Seed Data Schema
• 8-1 Sample Deployment Plan File
• 8-2 Deployment Policy File
• 9-1 Sample ODI BOM
• 9-2 Structure of a Property in AIAInstallProperties.xml
• 9-3 Structure of a Password Field in AIAInstallProperties.xml
• 9-4 Sample Deployment Plan
• 9-5 Sample Syntax of OdiImportObject
• 10-1 Setting the transaction flag on the BPEL component
• 10-2 First Annotation Element for Every composite.xml File
• 10-3 A Skeletal Service Element in composite.xml with Annotations
• 10-4 A Skeletal Reference Element in composite.xml with Annotations
• 10-5 An Example of Service Annotation Element
• 10-6 An Example of Service Annotation Element When It Has a Transport Adapter
• 10-7 An Example of Reference Annotation Element
• 10-8 An Example of Reference Annotation Element when it has a Transport Adapter
• 10-9 A Sample WSDL Annotation
• 10-10 Transformation Enabled to Accommodate Transformations for Custom Element
• 11-1 Custom Function Implementation to Get the Current Date
• 11-2 User Defined Extension Functions Config File
• 13-1 First Annotation Element for Every composite.xml File
• 13-2 A Skeletal Service Element in a composite.xml with Annotations
• 13-3 A Skeletal Reference Element in a composite.xml with Annotations
• 13-4 Interface Details Annotation Element Example
• 13-5 ImplementationDetails Annotation Element Example
• 13-6 Service Element in Requester ABCS Composite Annotation Example
• 13-7 Reference Element in Requester ABCS Composite Annotation Example
• 13-8 Service Element in a Provider ABCS Composite Annotation Example
• 13-9 Reference Element in Provider ABCS Invoking Participating Web Service Annotation Example
• 13-10 Reference Element in Provider ABCS Invoking Utility Service Annotation Example
• 13-11 Reference Element in Provider ABCS Invoking Non-SOAP Service Annotation Example
• 13-12 Transport Adapter Composite Annotation Example
• 13-13 Transport Details Populated in Reference Element Annotation Example
• 13-14 Transport Details Populated in Reference Element Using JMS Adapter Annotation Example
• 13-15 Service Element in EBF Composite Annotation Example
• 13-16 Reference Element in EBF Composite Annotation Example
• 13-17 Service Element in Composite Business Process Composite Annotation Example
• 13-18 Reference Element in Composite Business Process Composite Annotation Example
• 16-1 Binding.ws Element for BPEL-Based Service
• 16-2 URL of the Concrete WSDL for BPEL-Based Service
• 16-3 Binding.ws Element for Mediator-Based Service
• 16-4 URL of the Concrete WSDL for Mediator-Based Service
• 16-5 Service Configuration Properties File
• 16-6 Example of Configuration File for Service-Specific Properties
• 16-7 Componenttype File Pointing to Abstract WSDLs in the MDS
• 16-8 Componenttype File for a Composite with a Reference
• 16-9 Composite.xml Pointing to Abstract WSDLs in the MDS
• 16-10 Example of composite.xml Pointing to Abstract WSDLs in the MDS
• 16-11 Referenced Service WSDLs with No partnerLinkType Elements Pointing to Abstract WSDLs in the MDS
• 16-12 DataArea Business Payload in the Instance XML Document
• 16-13 Content Payload of a Single Object Query
• 16-14 Defining SortElements for Single QueryCriteria
• 16-15 Defining SortElements for Multiple QueryCriteria
• 16-16 Example of Query with Single QueryCriteria Element and Single QueryExpression
• 16-17 Example of Query with Multiple QueryCriteria
• 16-18 Requesting a Single Return to QueryInvoice Message
• 16-19 Requesting Specific Message Return to QueryInvoice Message
• 17-1 Wiring the BPEL Component to the External Reference Component
• 17-2 Servlet to Test Extension
• 17-3 Defining Service-Level Configuration Properties for the Provider ABCS
• 17-4 Defining Namespace Prefixes in the BPEL Process
• 17-5 Adding an Assignment
• 17-6 Adding <scope> for Each PartnerLink
• 17-7 Populating the wsa:EndpointReference Element
• 17-8 Setting the Transaction Flag on the Callee BPEL Component
• 17-9 Setting Transaction Properties on the BPEL Adapter Interface
• 17-10 Transaction Settings in the composite.xml of the Requester ABCS
• 17-11 Transaction Settings for Asynchronous MEP
• 17-12 Transaction Properties Set on Adapter Component
• 19-1 Example of Message Exchange Pattern Identification for EBF
• 21-1 Condition Expression on the GatewayID Element
• 24-1 URL for Calling the Siebel Application and Passing Login Information in the SOAP Header
• 24-2 SOAP Header
• 24-3 Response to SOAP Header
• 24-4 Example of a Version 1 TargetNameSpace
• 24-5 Required Custom Attributes
• 24-6 Sample Custom Attributes
• 24-7 Example of a Version 0 TargetNameSpace
• 24-8 Example of a Version 1 TargetNameSpace
• 25-1 Creation of an XREF View in the XREF Database
• 25-2 XML Request Input for AIAAsyncErrorHandlingBPELProcess
• 25-3 Update application.xml in ORACLE_HOME\j2ee\home\applications\axis2\META-INF
• 25-4 Sample SOAP Request for the OdiInvoke Web Service
• 25-5 SOAP Response Returned by the Scenario Execution
• 26-1 Domain Value Map Lookup Call to Fetch Currency Code
• 26-2 Sample Code Illustrating Logic Designed to Handle Missing or Empty Elements
• 26-3 Statement Without xsl:If
• 26-4 Statement With xsl:If
• 26-5 Sample Code Showing Hard-Coded System IDs - Not Recommended
• 26-6 Sample Code Showing Use of Variables Instead of Hard-Coded System IDs - Recommended
• 26-7 Transformation Enabled to Accommodate Transformations for Custom Element
• 26-8 Industry Extensible Transformation Template
• 26-9 BusinessComponentID Populated by the EBM
• 26-10 EBMID
• 26-11 EBOName
• 26-12 RequestEBMID
• 26-13 CreationDateTime
• 26-14 VerbCode
• 26-15 Message Processing Instruction Population
• 26-16 Sender Element Code Sample
• 26-17 Target Element Code Sample
• 26-18 Request EBM for Request-Response Use Case
• 26-19 Response EBM for Request-Response Use Case
• 26-20 Request EBM for Asynchronous Use Case
• 26-21 Create Account Request EBM
• 26-22 Create Account Response EBM
• 26-23 Create Customer Request EBM
• 26-24 Create Customer Response EBM
• 26-25 ProcessOrder Request EBM
• 26-26 Process Order Response EBM
• 26-27 Populating EBM Tracking Information
• 27-1 Elements to be Added to composite.xml
• 27-2 Sample Fault Policy File with Fault Policies Defined
• 27-3 Association in fault-bindings.xml
• 27-4 Fault Definition in the Fault Policy XML File
• 27-5 subLanguageExecutionFault Fault Handling
• 27-6 Conditions Element in the Fault Policy
• 27-7 Default Condition Configuration Used to Call the aia-ora-java action
• 27-8 Business Fault Message
• 27-9 Catch-All Block Construction
• 27-10 EBM-to-EBM XSL Code Example
• 27-11 Example of How to Assign the JMS Message ID to the ABM
• 27-12 Example of How to Concatenate Data and Assign it to the ABM
• 27-13 Example Illustrating Three ABM Fields Used to Hold Three Resubmission Values
• 27-14 Code Used to Extract Resubmission Values and Assign Them to EBM Header Element
• 27-15 AIA Fault Message with an ECID Defined
• 27-16 Java Snippet to Invoke the Oracle AIA Error Handler
• 27-17 Sample Fault Policy Using the aia-no-action No-op Action
• 27-18 IAIAErrorHandler Interface Class
• 27-19 IAIAErrorHandlerExtension Interface Class
• 28-1 Custom Element Acting as Placeholder
• 28-2 Adding an Extension to EBO or EBM Schemas
• 28-3 Adding New Transformations for Customer-defined Custom Elements
• 28-4 Custom XSL Template Definition
• 29-1 <soap:Envelope> Content
• 29-2 Security Header for Authentication
• 29-3 Sample AIASecurityConfigurationProperties.xml
• 29-4 Example of AppContext Mapping Service
• 29-5 Example of SEBL AppContext information Sent to the Security Service
• 30-1 ABM -> EBM Transformation
• 30-2 ABM -> EBM transformation
• 30-3 EBM -> ABM Transformation
• 30-4 Using Local Variables
• 30-5 Setting the bpel.config.auditLevel Property in the composite.xml
• 31-1 soaDataSource-jdbc.xml file
• 31-2 Configuring the Polling Interval in the adf-config.xml
• 31-3 Manually Updating the cache-config in adf-config.xml
• 31-4 Tuning JMS Adapters Using the composite.xml Property File
• 31-5 Tuning AQ Adapters Using the composite.xml Property File
• 31-6 Binding Property in the composite.xml
• 31-7 Sample JVM Configurations
• A-1 Node Set Returned for aia:getEBMHeaderSenderSystemNode()
• A-2 XSLT Example for aia:getEBMHeaderSenderSystemNode()
• A-3 Module Configuration Properties
• A-4 BPEL Usage Example for aia:getAIALocalizedString()
• B-1 AddTargetSystemID.xsl
• B-2 SetCAVSEndpoint.xsl