Requester-Side ABCS Implementing ABCS

Understanding Application Business Connector Services 4-9

4.5.1 Requester-Side ABCS

The requester-side ABCS has the following core responsibilities: ■ Enrichment or augmentation of the ABM. This may be required in situations in which the ABM received from the participating application does not contain all of the required content. The enrichment can be done by issuing additional calls to the participating application to get more information. For example, a CRM application might pass only the order identifier as part of the ABM. The interface for ProcessOrder EBS might warrant that the entire order object be passed as the payload. In this situation, the ABCS is responsible for interacting with the participating application to get all of the required information to enrich the ABM. ■ Transformation of requester application-specific ABMs into EBMs. ■ Creation of an EBM that encompasses the previously mentioned EBM. ■ Population of the message header with the appropriate values. For more information, see Section 2.2.1, EBM Architecture . ■ Invocation of any extension handler that you may have registered. You can use the extension handler to perform any additional transformations. The extension handler is passed to the EBM and the transformed EBM is passed back as the response. This extension handler enables you to perform additional transformations on the EBO before the EBS is invoked. ■ Invocation of the EBS. The EBS is responsible for taking an EBM and providing the response using an EBM. ■ Transformation of an EBM into an ABM. ■ Invocation of any extension handler that you may have registered. This extension handler could be used to perform any additional transformations. The extension handler is passed to the ABM and the transformed ABM is passed back as the response. This extension handler enables you to perform additional transformations on the ABM before the ABM is passed back to the calling application. ■ Perform any necessary validations to ensure that the ABM that must be passed to the participating client application complies with the constraints enforced by the participating application. ■ Return the response to the calling application. Figure 4–2 illustrates the high-level flow of activities in a requester-specific ABCS. The diagram makes an assumption that the EBS with which it is interacting employs a request-response interaction style. Note that the steps for running the extension to do additional transformations are optional. 4-10 Concepts and Technologies Guide for Oracle Application Integration Architecture Figure 4–2 Requester-Specific ABCS Implementing the Request-Response Style Interaction Pattern Figure 4–3 depicts the high-level flow of activities in a requester-specific ABCS. The diagram makes an assumption that the EBS with which it is interacting employs a fire-and-forget interaction style. Note that the steps for running the extension to do additional transformations are optional. Understanding Application Business Connector Services 4-11 Figure 4–3 Requester-Specific ABCS Implementing the Fire-and-Forget Style Interaction Pattern

4.5.2 Provider-Side ABCS