Constructing ABM Schemas Analyzing the Participating Application Integration Capabilities

11-6 Developers Guide for Oracle Application Integration Architecture Foundation Pack 9. Decide what must be done when a subset of instances present in that message encounter failure.

11.2.2 Constructing ABM Schemas

The ABM schemas are created by the participating applications. Consider the following points when defining the ABMs: ■ Construct messages that are durable and long-lasting because frequent changing of the ABM definition puts duress on ABCS development. ■ Ensure reusability of business components across multiple ABMs to promote reusability of transformation maps. ■ Design ABMs to pass the following system data: – System Instance - connection information that helps identify the system ID registered in the system registry – Locale - language code in which the request is sent – Sender information - contextual details pertaining to the origination of the message ■ Design ABMs that are extensible

11.2.3 Analyzing the Participating Application Integration Capabilities

To analyze the participating application integration capabilities: After identifying the participating applications, you must analyze the integration capabilities of each participating application and how each application exposes its data. 1. Work with the application providers developers to decide the best way to interact with the application to attain the needed functionality. The interactions can be inbound or outbound. The interaction mechanism can be one of these: ■ Web Service using SOAPHTTP ■ EventsQueues ■ JCA Adapter ■ Database Adapter For more information about various types of connectivity to different resources, see Chapter 21, Establishing Resource Connectivity. 2. Obtain relevant details from the applications in situations in which the interactions between the participating applications and the ABCS happen through a message queue adapter, database adapter, or JCA adapter. These details are used in configuring the adapters. The configuration results in the WSDL creation. Care must be taken to ensure that the environment-specific details are configured in relevant resource files on the server and not directly in the WSDLs. 3. Identify the available functionality within the participating applications as well as the mapping between EBMs and application business objects map operations. A one-to-one, one-to-many, or many-to-one mapping between the two may exist. Designing Application Business Connector Services 11-7 4. Tabulate the mapping between the Enterprise Business Object EBO attributeselements and the application objects attributeselements in a spreadsheet. Remember these points when creating the transformation maps: 5. For an ABM being mapped to an EBM, ensure that an attempt is made to populate all of the data elements present in the ABM to the relevant elements in the EBM. In situations in which the ABM does not have all of the content to supply all of the data elements in the EBM, you must work with the respective requester application teams to identify the application services that could be used to enter the content in the EBM. For example, a Siebel application invoking the CreateOrder ABCs might supply only the Siebel Customer ID in the ABM that is being passed as the payload. However, the EBM to be passed as a payload to the CreateOrder EBS operation expects all the information regarding the Customer. So the CreateOrder ABCS is responsible for invoking a Siebel service to retrieve complete Customer details from the Siebel application and populate the EBM. Although the integration platform provides support for this pattern, we highly recommend that you work with the participating application to ensure that the payload being passed to the ABCS is as close to the shape of the EBM as possible to minimize the chattiness.

11.3 Identifying the MEP