Application Interfaces Support for Logging and Monitoring

Understanding Application Business Connector Services 4-5 For example, perhaps a single business-level activity cannot be mapped to a single API or operation in the server application. The provider application might have very fine-grained operations and might also require that transaction management be handled by calling applications. In this case, the provider ABCS probably has a chatty conversation with the provider application. The provider ABCS is also responsible for state management. This type of ABCS can be implemented only through BPEL technologies and not through Mediator services. Although Oracle AIA allows for the existence of this type of ABCS, Oracle highly recommends that much of this application logic be encapsulated within native applications as opposed to having them handled in ABCS.

4.4.2 Support for EBMs

Because the EBS operates only on EBMs, you need to determine whether the applications that implement the services provide support for EBMs. In scenarios in which the application-provided services provide native support for EBMs, the effort for transforming the EBO into an EBM is minimal. In situations in which the applications that implement the services do not provide EBM support, you should determine whether their services can provide inherent support for EBMs. If these applications cannot provide support for EBMs, transformation-related work must be done by the ABCS.

4.4.3 Application Interfaces

Perform a check to determine how the participating applications intend to allow the business logic to interact with the Mediator. Some applications may have inherent support for web service interfaces. This is the preferred scenario. The WSDL defines the interface that is used to communicate directly with the application business logic. In this situation, the ABCS uses the web service interface to invoke the application business logic. In the case of packaged applications such as Siebel, PeopleSoft, J.D. Edwards, and SAP, the much-preferred route is to use the respective packaged-application adapters. These adapters can be deployed as J2CA resource adapters. This is a better solution than using the conventional SOAP interface. In situations in which the participating applications do not expose their business logic as web services, interactions with these applications must occur by means of technology adapters such as database adapters, advanced queuing AQ adapters, and so forth. Investigate whether the services exposed by the participating applications provide support for proprietary message formats, technologies, and standards. If the applications that implement the functionality do not have inherent support for standards and technologies such as XML, SOAP, and JMS, then the transformations need to happen in the ABCS. For example, the application might be able to receive and send messages only through files, and EDI is the only format that it recognizes. In this case, the ABCS becomes responsible for integrating with the application using a file adapter, translating the EDI-based message into XML format, and exposing the message as a SOAP message. For more information, see Establishing Resource Connectivity in the Oracle Fusion Middleware Developers Guide for Oracle Application Integration Architecture Foundation Pack. 4-6 Concepts and Technologies Guide for Oracle Application Integration Architecture

4.4.4 Support for Logging and Monitoring

The ABCS is responsible for facilitating logging and monitoring capabilities. The ABCS invoke the convenience services for logging and auditing. For more information, see Oracle Fusion Middleware Infrastructure Components and Utilities Users Guide for Oracle Application Integration Architecture Foundation Pack.

4.4.5 Support for Insulating the Service Provider