How to Develop Transport Adapters When to Put Adapters in a Single Composite

Completing ABCS Development 13-17 adapters can be deployed as JCA resource adapters. This solution is better than using the conventional SOAP interface. ■ In situations for which the participating applications do not expose their business logic as Web services, interactions with these applications must occur using technology adapters such as database adapters, JMS adapters, and so forth. Transport adapters allow connectivity to the systemsapplications that were not originally developed using Web services technologies. Some examples of applications that can use adapters are: ■ Systems that use non-xml for communication ■ Packaged software ■ Database systems ■ Data sources or persistent stores such as JMS, and so on Investigate whether or not the services exposed by the participating applications provide support for proprietary message formats, technologies, and standards. If the applications that implement the functionality do not have inherent support for standards and technologies such as XML, SOAP, and JMS, then the transformations must happen in the ABCS. For example, the application might be able to receive and send messages only using files, and EDI is the only format it recognizes. In this case, the ABCS is responsible for integrating with the application using a file adapter, translating the EDI-based message into XML format, exposing the message as a SOAP message. When to Use Adapters for Message Aggregation In some situations, you must combine responses to a request that originated from multiple sources. For example, for convergent billing in the telecommunication solution, the Application Business Connector Service for the getBillDetails EBS might have to retrieve details from multiple participating applications. For more information about the Message Aggregation design pattern, see Chapter 25, Working with AIA Design Patterns . When to Use Adapters for Event Aggregation The Event Aggregation model provides a comprehensive methodology for the business use case in which events, entity, or message aggregation is needed. In such scenarios, multiple events are raised before the completion of a business message, and all such fine-grained message events are consolidated into a single coarse-grained event. In such use cases, a requester ABCS is invoked by an event consumer adapter service, which feeds the requester ABCS with an aggregated event message. For more information about the event aggregation design pattern, see Chapter 25, Working with AIA Design Patterns .

13.3.2 How to Develop Transport Adapters

Here are the high-level steps from the ABCS perspective. To develop JMS Consumer Adapter: 1. Add JMS adapter in the Exposed Services swim lane. 2. Configure the JMS adapter service with the help of Adapter Configuration wizard. 13-18 Developers Guide for Oracle Application Integration Architecture Foundation Pack 3. Add a BPEL component in the Components swim lane. 4. Wire the BPEL component to the JMS adapter service. 5. Wire the BPEL component to the Referenced Service. 6. Open the BPEL component in design mode and add invoke activity to invoke the JMS adapter partner link. 7. Complete the coding for the BPEL process. For more information about JMS Adapters, see Oracle Fusion Middleware Configuring and Managing JMS for Oracle WebLogic Server. To develop Portal DB Adapter: 1. Add a BPEL component in the Components swim lane. 2. Add DB adapter as external reference service in the References swim lane. 3. Configure the adapter service with the help of Adapter Configuration wizard. 4. Wire the BPEL component to the db adapter service. 5. Open the BPEL component in design mode and add invoke activity to invoke the db adapter partner link. 6. Complete the coding for the BPEL process.

13.3.3 When to Put Adapters in a Single Composite

In principle, an ABCS composite is a component implemented along with other components and wires between those components. For example, you can implement a Requester ABCS composite using: ■ A BPEL process component representing the ABCS process flow. ■ BPEL or Mediator-based adapter components representing the adapters used or required by the process component. ■ Both the process component and the adapter components promoted as Services of the composite in which they are defined. An ABCS and a TransportAdapter service can be in the same composite and when they are, the composite name is the same as that of the ABCS. Alternatively, you can develop an ABCS service and a TransportAdapter service as separate composites. AIA recommends that you put adapters that are interfaced with ABCS in a different composite from that of ABCS when the same transport adapter service could be used with multiple ABCSs.

13.3.4 Planning Version Adapters