Introduction to Oracle E-Business Suite Integrated SOA Gateway

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 services.

With service enablement feature, integration interfaces published in the Oracle Integration Repository can be transformed into SOAP and REST based web 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:

• Display all Oracle E-Business Suite integration interface definitions through Oracle Integration Repository

• Support custom integration interfaces from Oracle Integration Repository

• Provide service enablement capability (SOAP and REST services) for seeded and custom integration interfaces within Oracle E-Business Suite

• Use the Integration Repository user interface to perform design-time activities such as generate and deploy Oracle E-Business Suite web services

• Support synchronous and asynchronous (callback without acknowledgement only) interaction patterns for SOAP-based services

  Note: In this release, only PL/SQL APIs can be enabled with the support for asynchronous service pattern.

• Support synchronous interaction pattern for REST-based services

  Note: In this release, only PL/SQL APIs, Concurrent Programs, Java Bean Services, Application Module Services, Business Service Objects, Open Interface Tables, and Open Interface Views can be exposed as REST services.

• Support multiple authentication types for inbound service requests in securing web service content

• Enforce function security and role-based access control security to allow only authorized users to process administrative functions

• Provide centralized, user-friendly logging configuration for the services generated through service provider from Oracle E-Business Suite Integrated SOA Gateway

• Audit and monitor Oracle E-Business Suite inbound service operations from Service Monitor

• Audit and monitor outbound service invocations from Oracle E-Business Suite through Service Invocation Monitor

• Leverage Oracle Workflow Business Event System to enable service invocation from Oracle E-Business Suite

Major Components of Oracle E-Business Suite Integrated SOA Gateway

Oracle E-Business Suite Integrated SOA Gateway has the following essential components in enabling Oracle E-Business Suite services. The relationship between these essential components can be illustrated in the following diagram:

Web Service Architecture in Oracle E-Business Suite

• Oracle Integration Repository (Service Broker), 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 various interface types including PL/SQL, XML Gateway, Concurrent Program, Business Event, Open Interface Table/View, EDI, Business Service Object (formerly known as Service Beans) and Java APIs.

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

  Application users can browse these interface definitions and services through Oracle Integration Repository and view the interface details. Users who have the Integration Administrator role can perform design-time operations, monitor the services, and view log messages.

• Service Provider (previously known as SOA Provider) is the primary engine underlying the web services. It is the engine that performs the actual service generation and deployment behind the scene.

• Service Invocation Framework serves as a service consumer to send a request through the invocation of a web service from Oracle E-Business Suite. By leveraging Oracle Workflow Java Business Event System (JBES) and seeded Java rule functions, this framework provides an infrastructure that facilitates SOAP and REST service invocation and consumption from Oracle E-Business Suite.

Additionally, Oracle E-Business Suite Integrated SOA Gateway provides the following monitoring and auditing tools to help monitor and view SOAP and REST services in and out from Oracle E-Business Suite:

• Service Monitor: Audit and monitor inbound Oracle E-Business Suite service operations provided through Oracle E-Business Suite Integrated SOA Gateway.

• Service Invocation Monitor: Audit and monitor outbound Oracle E-Business Suite service invocations provided through Service Invocation Framework.

Oracle E-Business Suite Web Service Development Life Cycle

Oracle E-Business Suite Integrated SOA Gateway provides a capability of allowing various users to perform different tasks and to monitor and manage service integration throughout the entire service deployment life cycle.

• At development phase, users who have the Integration Developer role can create custom interfaces, and annotate custom interface's definitions. Users who have the Integration Administrator role can validate and upload annotated custom interfaces to the Integration Repository where all the registered interfaces, regardless of custom or Oracle packaged ones, can be viewed and accessed by all users.

• At design time, users who have the Integration Administrator role can generate SOAP services with desired operation patterns, and deploy them to Oracle SOA Suite by attaching an appropriate security policy. For interfaces that can be exposed as REST services, the administrator can select desired service operations before deploying them to Oracle E-Business Suite.

• At runtime, web service clients send request messages to invoke Oracle E-Business Suite services enabled through the service provider provided through ISG. After authenticating and authorizing the users who request the services, services can be invoked.

  Users who have the Integration Administrator role are responsible for monitoring and managing the entire service deployment life cycle.