Oracle E-Business Suite Integrated SOA Gateway Overview

Oracle E-Business Suite Integrated SOA Gateway Overview

Building on top of Oracle Fusion Middleware and service-oriented architecture (SOA) technology, Oracle E-Business Suite Integrated SOA Gateway (ISG) is a complete set of service infrastructure to provide, consume, and administer Oracle E-Business Suite web services.

With service enablement feature, integration interfaces published in the Oracle Integration Repository can be transformed into SOAP and REST based services.

By leveraging Oracle SOA Suite running on Oracle WebLogic Server, Oracle E-Business Suite Integrated SOA Gateway provides greater capabilities and infrastructure for exposing various integration interfaces within Oracle E-Business Suite as SOAP services. SOAP-based services are described in WSDLs and are deployed to Oracle SOA Suite for service consumption.

Unlike SOAP services, REST services, without the dependency on Oracle SOA Suite, are developed with the infrastructure of Oracle E-Business Suite. REST services described in WADLs are directly deployed to an Oracle E-Business Suite WebLogic environment. They can be used for user-driven applications such as Oracle E-Business Suite mobile applications.

Oracle E-Business Suite Integrated SOA Gateway provides Service Invocation Framework to invoke and consume web services provided by other applications.

Major Features

Oracle E-Business Suite Integrated SOA Gateway can do the following:

Major Components Features and Definitions

Oracle E-Business Suite Integrated SOA Gateway provides two major service offerings:

Oracle E-Business Suite Integrated SOA Gateway Functional Flow Diagram

the picture is described in the document text

To better understand Oracle E-Business Suite Integrated SOA Gateway, the next sections explain essential components and how each component is used.

Enabling Oracle E-Business Suite Web Services

Service enablement is the key feature within Oracle E-Business Suite Integrated SOA Gateway. It provides a mechanism that allows native packaged integration interface definitions resided in Oracle Integration Repository to be transformed into web services. SOAP services are deployed from the Integration Repository to Oracle SOA Suite allowing more consumptions over the web. REST services are deployed to Oracle E-Business Suite.

The basic concept of web service components is illustrated in the following diagram:

Web Service Components

the picture is described in the document text

Oracle Integration Repository and Service Enablement

Oracle Integration Repository, an integral part of Oracle E-Business Suite, is the centralized repository that contains numerous interface endpoints exposed by applications within the Oracle E-Business Suite. It supports the following interface types:

Oracle E-Business Suite Integrated SOA Gateway leverages Oracle Integration Repository to provide the capabilities of service generation and deployment, as well as service life cycle management.

Note: Not all the interface types resided in the Integration Repository can be service enabled. The supported interface types for service enablement are XML Gateway, PL/SQL, Concurrent Program, Business Service Object, Application Module Services, Java Bean Services, Open Interface Tables, and Open Interface Views.

As mentioned earlier, security services are pregenerated REST services from Oracle Application Object Library. Therefore, there is no need to enable the security services from the repository as required by other supported interface types.

Web Service Security

To protect application data from unauthorized access, Oracle E-Business Suite integrated SOA Gateway enforces the security rules through subject authentication and authorization:

Additionally, input message header (such as SOAHeader and RESTHeader) is used to pass the application context needed in invoking Oracle E-Business Suite services as part of the subject authorization.

Service Monitor

Service Monitor is a centralized, light-weight service monitoring and management tool.

It fetches data and statistics for each instance of service request and response messages and lets administrators monitor all inbound Oracle E-Business Suite service invocations provided through Oacle E-Business Suite Integrated SOA Gateway. Use Service Monitor to view the runtime request and response data received and sent directly to Oracle E-Business Suite for REST services and the runtime messages passed through Oracle SOA Suite for SOAP services.

For more information about Service Monitor, see Monitoring and Managing Inbound Service Invocation Messages Using Service Monitor.

Service Invocation Framework

By leveraging Oracle Workflow Java Business Event System (JBES), Service Invocation Framework (SIF) provides the capability of invoking SOAP and REST services from Oracle E-Business Suite.

It provides an infrastructure allowing developers to interact with SOAP and REST services through service endpoint descriptions. For detailed implementation information, see Implementing SOAP and REST Service Invocation Framework.

Service Invocation Monitor

Service Invocation Monitor is also a service monitoring and management tool. It tracks all outbound service invocations from Oracle E-Business Suite through Service Invocation Framework.

Administrators use Service Invocation Monitor to view each instance of the runtime request and response messages sent and received through Service Invocation Framework. For more information about Service Invocation Monitor, see Monitoring and Managing Outbound Service Invocation Messages Using Service Invocation Monitor.

Native Service Enablement Architecture Overview

Oracle E-Business Suite Integrated SOA Gateway employs essential components that enable service integration at design time and runtime, and ease the service management throughout the entire service deployment life cycle.

Service Provider is the primary engine enabling the Oracle E-Business Suite services. It is the engine that performs the actual service generation and deployment behind the scene for both SOAP and REST services.

The high level service enablement diagram can be illustrated in the following diagram:

the picture is described in the document text

SOAP Service Enablement Architecture and Design Time

SOAP services, once successfully generated, are deployed to an Oracle SOA Suite WebLogic environment. The seamless integration between Oracle E-Business Suite and Oracle SOA Suite forms the Oracle E-Business Suite Integrated SOA Gateway architecture.

the picture is described in the document text

At design time, an integration developer or integration administrator can select a desired interface and perform the service generation from the repository.

Once the service artifact has been generated, an integration administrator can deploy the service from Oracle Integration Repository to an Oracle SOA Suite WebLogic environment where the soa-infra application is running.

Note: Users with different roles can perform various tasks in Oracle E-Business Suite Integrated SOA Gateway. Each user role representing a unique permission or permission set can be granted to appropriate users. For example, an integration administrator defined by the Integration Administrator role can perform design-time operations, and other administrative tasks. For information on user roles and how to grant roles to users, see Assigning User Roles and Role-Based Access Control (RBAC) Security for Oracle E-Business Suite Integrated SOA Gateway.

REST Service Design Time

Without the dependency on Oracle SOA Suite, REST services are developed based on Oracle E-Business Suite technology infrastructure.

At design time, an integration administrator can select desired methods to be exposed as REST service operations before deploying them to Oracle E-Business Suite.

Additionally, the administrator can undeploy the service if needed.

Service Enablement Runtime

Oracle E-Business Suite integration interfaces can be exposed as web services and interacted with web service clients at runtime.

When service consumers or web service clients send request messages at runtime, before invoking deployed services in the managed servers, all service-related security and policies are enforced. After authenticating the requests, Oracle E-Business Suite web services can be invoked. Service response messages will be sent back to the web service clients if needed.

For each service operation, SOAP request and response messages passed through Oracle SOA Suite and REST messages received directly to Oracle E-Business Suite are captured in Service Monitor where all Oracle E-Business Suite service activities processed at runtime can be monitored.

For more information on how to monitor web service messages in Service Monitor, see Monitoring and Managing Inbound Service Invocation Messages Using Service Monitor.

Additionally, Oracle E-Business Suite Integrated SOA Gateway can consume external services. Each instance of the runtime request and response messages sent and received through service invocation framework can be tracked and monitored in Service Invocation Monitor. For more information about Service Invocation Monitor, see Monitoring and Managing Outbound Service Invocation Messages Using Service Invocation Monitor.

Web Service Clients

Customers or third parties can use the following standard web service client technologies or tools to invoke Oracle E-Business Suite services: