Introduction to Enabling Requester ABCS for Extension

13-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack This section describes the mechanism for creating ABCSs with extensible services, which enables you to have service implementations that require no modifications to the delivered ABCS.

13.1.1 Introduction to Enabling Requester ABCS for Extension

For requestresponse Requester ABCS, you can hook your custom code to four extensibility points: 1. Just prior to the execution of transformation of application business message ABM to Enterprise Business Message EBM. Use this configuration property name: ABCSExtension.PreXformABMtoEBM. 2. Just prior to the invocation of the enterprise business service EBS. Use this configuration property name: ABCSExtension.PreInvokeEBS. 3. Just prior to the execution of transformation of EBM to ABM and after invoking the EBS. Use this configuration property name: ABCSExtension.PostInvokeEBS. 4. Just prior to the invocation of callback service or response return and transforming EBM to ABM. Use this configuration property name: ABCSExtension.PostXformEBMtoABM. The third and fourth extension points are available only in ABCS implementing request-response pattern. For Fire and Forget Requester ABCS, you can hook your custom code to two extensibility points: 1. Just prior to the execution of transformation of application business message ABM to EBM. Use this configuration property name: ABCSExtension.PreXformABMtoEBM. 2. Just prior to the invocation of the enterprise business service EBS. Use this configuration property name: ABCSExtension.PreInvokeEBS. For more information about configuration parameters, see section 15.1.3.1. Figure 13–1 depicts the high-level flow of activities in a requester-specific ABCS. The diagram assumes that the EBS with which it is interacting employs a request-response interaction style. Note that the steps for executing the customer extension to do additional tasks are optional. Completing ABCS Development 13-3 Figure 13–1 Extending the Request-Response Interaction Style Figure 13–2 shows the high-level flow of activities in a requester-specific ABCS. The diagram assumes that the EBS with which it is interacting employs a fire-and-forget interaction style. Note that the steps for executing the customer extension to do additional tasks are optional. 13-4 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 13–2 Requester-Specific ABCS Using Fire-and-Forget Interaction Style The first extensibility point made available to the implementers of the requester ABCS can be used to perform custom message inspection. This extensibility point can be used to inject code to perform tasks such as custom validation, message alteration, message filtering and so on. The custom code has access to the ABM that is about to be transformed and can return either an enhanced ABM or raise a fault. The second extensibility point can be used to perform custom message augmentation. The extensibility point can be used to inject code to perform tasks such as EBM enhancement, custom validation and so on. The custom code has access to EBM that is about to be used for invocation of EBS and can return either an enhanced EBM or raise a fault. The third extensibility point can be used to inject code to perform tasks such as custom validation, message alteration, message filtering and so on. The custom code has access to EBM that is about to be transformed to ABM. The custom code can return either an altered EBM or raise a fault. The fourth extensibility point can be used to inject code to perform tasks such as ABM enhancement, custom validation and so on. The custom code has access to ABM that is about to be used for invocation of callback services. The custom code can return either an altered ABM or raise a fault

13.1.2 Introduction to Enabling Provider ABCS for Extension