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
The provider-side Application Business Connector Service has the following core responsibilities:
■
Transformation of an EBM into a provider application-specific ABM.
■
Invocation of any extension handler that you may have registered. You can use this extension handler 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 to the provider application business service.
■
Performance of any necessary validations to ensure that the ABM that must be passed to the participating provider application complies with the constraints
enforced by the participating application.
■
Invocation of the provider application business service. One or multiple calls may be made to the provider application business service.
For more information, see Section 4.4, Architectural Considerations.
■
Transformation of an ABM into an EBM. The response message sent by the provider application must be returned to the caller application. In this case, it
would be EBS. Because EBS expects only EBM as the output, the transformation must be done to transform the ABM into an EBM.
■
Creation of an EBM that encompasses the previously mentioned EBO.
■
Population of the message header section with the appropriate values.
4-12 Concepts and Technologies Guide for Oracle Application Integration Architecture
For more information, see Section 2.2.1, EBM Architecture
.
■
Invocation of any extension handler that you may have registered. You can use this extension handler to perform any additional transformations. The
EBM is passed to the extension handler and the transformed EBM is passed back as the response. This extension handler enables you to perform additional
transformations on the EBM before the document is passed to the EBS.
■
Return of the document to the EBS. Figure 4–4
depicts the high-level flow of activities in a provider-specific ABCS. The diagram makes an assumption that the EBS with which it is interacting employs a
request-response interaction style.
Figure 4–4 Provider-Specific ABCS implementing Request-Response Style Interaction
Pattern
Understanding Application Business Connector Services 4-13
Figure 4–5 depicts the high-level flow of activities in a provider-specific ABCS. The
diagram makes an assumption that the EBS with which it is interacting employs a fire-and-forget interaction style.
Figure 4–5 Provider-Specific ABCS Interacting with Fire-and-Forget Interaction Style
4.6 Reviewing Implementation Technologies for ABCS
