In this post we will discuss on key steps that we need to follow to install Integrated SOA Gateway (ISG) on a standalone SOA Weblogic server.
Oracle E-Business Suite Integrated SOA Gateway (ISG) enables supported interface types published in Oracle Integration Repository. These interfaces can be transformed into SOAP and REST web services.
Oracle E-Business Suite SOAP Services
- SOAP-based web services are deployed on Oracle SOA Suite running on Oracle WebLogic Server
- Steps to configure SOAP services span across Oracle E-Business Suite as well as Oracle SOA Suite
- Interface types enabled for SOAP services are PL/SQL, Concurrent Program, XML Gateway (Inbound), and Business Service Object.
Oracle E-Business Suite REST Services
- REST-based web services are deployed on an Oracle E-Business Suite application server.
- They do not depend on Oracle SOA Suite and Oracle E-Business Suite Adapter so the configuration steps for REST services are required to be performed only on Oracle E-Business Suite
- Interface types enabled for REST services are PL/SQL, Java Bean Services, Application Module Services, Concurrent Program, and Open Interface Tables and Views.
Below steps are not very detailed steps but are just representation of what to expect and in what sequence.
High Level steps to install ISG Application with Oracle EBS:
EBS SIDE STEPS:
ALL THE BELOW STEPS TO BE DONE ON EBS SIDE EXCEPT THE FIRST STEP:
- Install and configure Oracle SOA Suite 11g or Oracle SOA Suite 12c on a separate Oracle WebLogic Server
- Ensure that your Oracle E-Business Suite instance is on the latest AD TXK Delta level. Refer to My Oracle Support Knowledge Document 1617461.1, Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2.
- Apply the latest consolidated Patch 29832501:R12.OWF.C, ISG Consolidated Patch for Release 12.2 (19_3_1), to your instance if they are not already applied. This patch is required for your instance regardless of a single node or a multi-node environment. Please note that this patch has two prerequisite patches listed in the patch readme which require adop phase=fs_clone to be run after application.
- Enable ASADMIN user with the Integration Administrator role (or the Integration Repository Administrator role in Release 12.2.3)
- Execute the txkSoaConfigUtility.xml script on EBS side and provide required parameters. If your instance is configured with multiple nodes, perform this step on each Oracle E-Business Suite node of the multi-node environment.
- Verify that the values of the profile options are set as suggested. Few important profile options to verify are: FND: Validate User Type, FND: Validate IP address, SQLNet Access, FND: Desktop Nodes allowed
- Stop and restart the oafm and oacore Oracle E-Business Suite managed servers
- Verify that the current setup on Oracle E-Business Suite is correct by generating XSD’s for a BSO service
- Execute the ant txk_integration_packager.xml script to register the external server with the Oracle E-Business Suite instance and to generate a DBC file for trusting the external Oracle SOA Suite host. This script will generate and package Desktop DBC file, isg_contextfile.properties, TXKFMWGenericConfigUtility.class, and txkISGConfigurator.xml, in a zip file “EBS_BPEL_payload.zip” located at $INST_TOP/logs/appl/rgf/TXK/EBS_BPEL_payload.zip.
- Use tcp.validnode_checking to restrict access to Oracle E-Business Suite database from external nodes
- Run adop fs_clone on Oracle E-Business Suite 12.2 enabled for Online Patching to copy the SOAP configurations done above to the other file system.
ISG SOA SIDE STEPS:
ALL THE BELOW STEPS TO BE DONE ON ISG SOA SIDE:
- Assuming Oracle E-Business Suite is TLS (HTTPS) enabled, verify if the CA certificate to be imported from issuing authority is valid on EBS side
- Import the CA certificate of the issuing authority from Oracle E-Business Suite into Oracle SOA Suite. You will use keytool command for it.
- Modify the setDomainEnv script for SSl related parameters
- Create a temporary folder (for example, <TEMP>) on the Oracle SOA Suite server.
- Create a folder called <DBC> on the Oracle SOA Suite server for the DBC file.
- Copy the EBS_BPEL_payload.zip file created as part of the EBS steps from Oracle E-Business Suite $INST_TOP/logs/appl/rgf/TXK/EBS_BPEL_payload.zip) to the <TEMP> folder in the Oracle SOA Suite server. Unzip the EBS_BPEL_payload.zip file in the <TEMP> folder.
- Copy the DBC file from <TEMP>/appsutil/<CONTEXT>/bpel to the <DBC> folder and Rename the DBC file in DBC folder from <SID>_<MACHINE1>.dbc to <SID>.dbc.
- Change directory to <TEMP>/appsutil/<CONTEXT>/bpel/oracle/apps/fnd/txk/util and Copy txkISGConfigurator.xml and isg_contextfile.properties to <TEMP>/appsutil/<CONTEXT>/bpel.
- Update the context file isg_contextfile.properties from the <TEMP>/appsutil/<CONTEXT>/bpel directory as per right details
- Download Patch 29832529 (ISG Application Patch for 12.2 (19_3_1) to the <TEMP>/appsutil/<CONTEXT>/bpel folder and unzip it to extract the files.
- Execute the txkISGConfigurator.xml setup script from the <TEMP>/appsutil/<CONTEXT>/bpel folder. This script will ask for multiple details like SOA Weblogic, link, user, password etc.
- Stop and restart all Oracle SOA Suite administration and managed servers from the command prompt.
Reference:
- Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID 1311068.1)
- 1317697.1: “Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12.2”
- 12.2 E-Business Suite Integrated SOA Gateway Troubleshooting For REST, Java Web Service Invocation, And Other ISG Related Exceptions (Doc ID 2177901.1)
- 12.2 E-Business Suite Integrated SOA Gateway ‘REpresentational State Transfer’ (REST) Services Setup, Troubleshooting, And Diagnostics (Doc ID 2233038.1)
- Oracle Multitenant DB 4 : Parameters/SGA/PGA management in CDB-PDB - July 18, 2020
- Details of running concurrent requests in Oracle EBS - May 26, 2020
- Oracle Multitenant DB 3 : Data Dictionary Architecture in CDB-PDB - March 20, 2020
Thanks for sharing this amazing article!!