Thursday May 09, 2013

Configuring Integrated SOA Gateway in Multinode EBS Environments

The E-Business Suite's three-tier architecture consists of application tier services such as Web Application Services (oacore, oafm, Forms), Web Entry Point Services, Batch Processing Services, Root Services and database tier processes and data. A node represents a physical server with a set of processes. When application and database processes are distributed across multiple servers, it is called a multi-node installation. Generally, a hardware load-balancer is used to distribute EBS traffic between multiple nodes.

Load-balanced multi-node EBS environment

Oracle E-Business Suite Integrated SOA Gateway (ISG) provides a SOA-based infrastructure to provide and consume web service in EBS. The Integrated SOA Gateway can be configured for use in multi-node EBS environments; see:

Configuring Oracle E-Business Suite Integrated SOA Gateway Release 12.1.2 and Release 12.1.3 in a Multinode Environment (Note 1081100.1)

This document's steps for web service generation and deployment in multi-node environments should be followed for each EBS Public API exposed as web service.

How to set up Integrated SOA Gateway in multi-node environment

Service Provider:  ISG generates web service artifacts and stores them in the Instance Home (INST_TOP). Regardless of whether a shared file system is used in EBS multi-node installation, ISG’s Service Provider should be configured to synchronize web service artifacts across all EBS application tier nodes.

Service Invocation Framework:  ISG stores metadata about the web service to be invoked in database tables. However, if the target web service resides outside a corporate firewall, then you need to ensure that the EBS host has access to WSDL and target web service endpoints required for sending SOAP requests. This requires setting up Proxy Host and Port at appropriate EBS application tiers; see the "Setup Tasks" section in Chapter 9 in this guide:

Oracle E-Business Suite Integrated SOA Gateway Implementation Guide [Part E12169-06].

Proxy Host and Port setup should be done for each node in a multi-node environment.


Related Articles

Wednesday Jul 18, 2012

New Whitepaper: Defining Web Applications Desktop Integrators That Return Error Messages

Oracle Web Application Desktop Integrator (Web ADI) is Oracle E-Business Suite's solution for integrating E-Business Suite applications with desktop applications such as Microsoft Excel, Word and Projects.  "Integrators" encapsulate the metadata and other information needed to integrate a particular Oracle E-Business Suite task with a desktop application.  You can use the Desktop Integration Framework (DIF) to create custom integrators for Oracle Web ADI in Oracle E-Business Suite Release 12.1.2. The ability to create custom importers was added in EBS 12.1.3.

I am pleased to announce the release of a new white paper that provides a step-by-step tutorial on how to use the Desktop Integration Framework to define a Microsoft Excel-based integrator.  The example in the tutorial shows how to define an importer that returns error messages for any spreadsheet rows that failed to import into an E-Business Suite database. It describes the steps in 3 phases: 

  • Preparing that database and application objects

This phase provides the sample code to create a custom table and PL/SQL package which will be used for importing the data from a Microsoft Excel spreadsheet into an E-Business Suite table. It also describes the steps to create an FND Lookup code and its value, which will be used to map error codes and their corresponding messages.

  • Phase A: Defining an integrator that downloads and uploads data

This phase provides the steps to create a basic integrator using the Web ADI Desktop Integration Framework. It describes the steps to define the integrator's Interface, Content, Uploader, Layout, and Mapping.

  • Phase B: Defining an integrator importer that returns error messages

This phase provides the steps to define importer. It extends the integrator definition to process the data uploaded in the interface table and return error messages back to the desktop document for any rows that failed to import.

Screenshot of SQL query definition screen

The intended audience of this document is custom desktop integrator developers who are familiar with Oracle E-Business Suite and Oracle Web Applications Desktop Integrator.

Your feedback is welcome

We are very interested in hearing about your experiences with this new tool.  Please post your comments here or drop me an email at email.jpg

Download the new whitepaper

The white paper is available in two places -- Oracle Learning Library (OLL) and My Oracle Support:


Related Articles



« June 2016