What are the two potential extensibility points for a requester ABCS supporting a request/response MEP?

Question

Options

• AJust before the transformation of ABM to EBM
• Bjust before the invocation of the ABCS
• CJust before the invocation of the application service
• Djust before the transformation of EBM to ABM

• A
  80% (20)
• B
  12% (3)
• C
  8% (2)

Explanation

Explanation: For request/response Requester ABCS, you can hook your custom code to four extensibility points: * Just prior to the execution of transformation of application business message (ABM) to Enterprise Business Message (EBM). Use this configuration property name: ABCSExtension.PreXformABMtoEBM. (A) * Just prior to the invocation of the enterprise business service (EBS). Use this configuration property name: ABCSExtension.PreInvokeEBS. * Just prior to the execution of transformation of EBM to ABM and after invoking the EBS. Use this configuration property name: ABCSExtension.PostInvokeEBS. (D) * 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. Note:An ABCS, regardless of whether it is requester or provider specific, can invoke custom code a minimum of either two or four times during its execution. These serve as extensibility points. The ABCS supporting request-response pattern in either synchronous or asynchronous mode has four extensibility points. An ABCS supporting fire-and-forget patterns has two extensibility points. You can develop "add-ins" and have them hooked to these extensibility points. These "add-ins" - customer-developed services- behave as an extension to the delivered ABCS. Each extension point allows one hook so only a single customer extension can be plugged in. Application Integration Architecture Foundation Pack: Developing Extensible ABCS

No community discussion yet for this question.