ABCS Types Introduction to ABCS

11-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 11–1 ABCS in Oracle AIA Architecture The ABCS enables participating applications to become service providers as well as service consumers. It also enables applications having nonstandard connectivity to expose their functionality as web services. For more information about ABCS, see Understanding Application Business Connector Services in the Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack..

11.1.1 ABCS Types

The two types of ABCSs are: ■ Requester ABCS ■ Provider ABCS

11.1.1.1 Requester ABCS

The requester ABCS is provided by the requesting application to interface with an EBS for performing a single business task. The service interfaces between RequestingSource application and EBS. The role of the requester ABCS is to enable Designing Application Business Connector Services 11-3 the participating application to invoke the EBS either to access data or to perform a transactional task. The requester ABCS is a service provided by the requesting application to invoke the EBS. It receives the Application Business Message ABM as payload and optionally returns the ABM as the response. The ABM can be enriched by having additional conversations with the requester application. The ABM is transformed into an Enterprise Business Message EBM using XSL. Responses received from the EBS EBM are transformed into the ABM. Non-SOAP payloads are handled by having transport adapters in between requester application and requester ABCS. Requester applications must pass system information for the ABCS to have subsequent conversations.

11.1.1.2 Provider ABCS

The provider ABCS is supplied by the provider application to interface with an EBS for performing a single business task. The service interfaces between the EBS and provider or target application. The provider ABCS: ■ Is a service supplied by the provider application to interface with the provider application ■ Receives EBM as payload ■ Optionally returns the EBM as the response The EBM is transformed into an ABM using XSL. The ABM can be enriched by having additional conversations with the provider application. Responses received from the application ABM are transformed into the EBM. Non-SOAP connectivity with the provider application is handled by having transport adapters in between the provider ABCS and the provider application. For more information about ABCS, see Understanding Application Business Connector Services in the Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack..

11.1.2 Designing ABCS - Key Tasks