| See Change Record This document contains information about the setup and configuration steps for Oracle E-Business Suite Integrated SOA Gateway release 12.1.2 and release 12.1.3 in a multinode environment. The following topics are included in this document: Overview Oracle E-Business Suite environments can be scaled up to handle large numbers of concurrent users by load-balancing across multiple application middle tier servers. To support service enablement through multiple nodes within Oracle E-Business Suite, Oracle E-Business Suite Integrated SOA Gateway enhances SOA Provider to allow instance specific service artifacts that were stored on a single node to be transferred and synchronized across various nodes of Oracle E-Business Suite. What is a Multinode Environment? A node is referred to as a server that runs a set of Oracle E-Business Suite Release 12 application processes or database processes. From Oracle E-Business Suite Integrated SOA Gateway's perspective, a single node environment means that the application tier or middle tier that hosts various services runs on a single node whereas in a multinode environment, all the application processes run on multiple nodes. For example, we can have multiple nodes of Oracle Application Server but with a single node of Oracle E-Business Suite database. The following diagram represents a hardware load balancer configuration with a single entry point to load balance the Web application running on application servers 1 and 2. In this configuration, all users access Oracle E-Business Suite application via a single URL. Using Hardware Load Balancers with Single Web Entry Point
Steps described in this document apply to single node behind load balancer as well. | Note: For information on configuring Oracle E-Businss Suite Release 12 with multinodes, see the "Using Load-Balancer with Oracle E-Business Suite Release 12", My Oracle Support Knowledge Document 380489.1. For more information about Oracle E-Business Suite Integrated SOA Gateway, see the following Knowledge Documents on My Oracle Support: - 556540.1: Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12
- 726414.1: Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12
- 1144313.1: Setting Up SAML Token Security for Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3
- 1096553.1: Oracle E-Business Suite Integrated SOA Gateway Release Notes for Release 12.1.3
- 953482.1: Oracle E-Business Suite Integrated SOA Gateway Release Notes, Release 12.1.2
- 1196642.1: Configuring Oracle E-Business Suite Integrated SOA Gateway Release 12.1.1 in a Multinode Environment
- 815196.1: Oracle E-Business Suite Integrated SOA Gateway 12.1.1 Consolidated One-Off
- 946192.1: Oracle E-Business Suite Integrated SOA Gateway 12.1.1 Integration Repository Parser One-Off
- 565922.1: Oracle E-Business Suite Integrated SOA Gateway Release Notes, Release 12.1.1
| One Time Configuration Steps for Oracle E-Business Suite Integrated SOA Gateway 12.1.2 and 12.1.3 Perform the following steps for enabling Oracle E-Business Suite Integrated SOA Gateway 12.1.2 and 12.1.3 in a multinode environment: - Complete the setup tasks for Oracle E-Business Suite Integrated SOA Gateway 12.1.2 and 12.1.3 on each node of the multinode environment. These tasks are described in the "Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12", My Oracle Support Knowledge Document 556540.1.
- All setup and configuration steps that are supposed to be done through Oracle E-Business Suite user interface need to be performed only ONCE.
- All setup and configuration steps that are supposed to be done through Backend (Middle tier access) need to be performed on EVERY node of the multinode environment.
On any node, find the EXTERNAL_URL by looking up value of variable "s_external_url" in $CONTEXT_FILE. Test URL: Once your setup steps are completed, validate your setup through the following Test URL: EXTERNAL_URL/webservices/SOAProvider/?testquery For example, Test URL: http://myhost.com/webservices/SOAProvider/?testquery This URL should return "TEST RESPONSE". If "TEST RESPONSE" is not returned, then one or more setup steps are missing on one or more nodes. Check the setup tasks based on My Oracle Support Knowledge Document 556540.1. - Apply patch 9300051:R12.OWF.B: Deployment of Web Services Fails When Using Hardware Load Balancing (For Oracle E-Business Suite Integrated SOA Gateway 12.1.2 Only)
- Perform the following steps on EACH node of the multinode environment:
- Take backup and modify file $FND_TOP/admin/template/oc4j_properties_1013.tmp.
- If SSL is configured on the node of the multinode environment, then set the following: SOA_SERVER_URL=%s_url_protocol%://%s_hostname%.%s_domainname%:%s_webssl_port%
- If SSL is not configured on the node of the multinode environment, then set the following: SOA_SERVER_URL=%s_url_protocol%://%s_hostname%.%s_domainname%:%s_webport%
- Take backup and modify file $FND_TOP/admin/template/oafm_oc4j_properties_1013.tmp.
- If SSL is configured on the node of the multinode environment, then set the following: SOA_SERVER_URL=%s_url_protocol%://%s_hostname%.%s_domainname%:%s_webssl_port%
- If SSL is not configured on the node of the multinode environment, then set the following: SOA_SERVER_URL=%s_url_protocol%://%s_hostname%.%s_domainname%:%s_webport%
- Run AutoConfig. For information on how to run AutoConfig, see "Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12", My Oracle Support Knowledge Document 387859.1 for details.
Service Generation and Deployment in a Multinode Environment Oracle E-Business Integrated SOA Gateway supports service enablement for various integration interface types. This enablement process is normally performed through the Integration Repository user interface (UI). However, it is recommended that the service generation and deployment be performed through backend processing in a multinode environment. This is because in a multinode environment, if a service is generated through the UI, we may not know in which node the service artifact will be actually generated and the user would have to check it on each node. Therefore, the service generation and deployment steps on a multinode environment described in this section are executed through the backend in any one node. After a service is generated and deployed through the backend, a WSDL link for the service would be available on the Interface Details page in the Integration Repository user interface. | Note: The backend processing on service enablement applies to all integration interface types that can be service enabled and follow these manual steps. The Business Service Object (BSO) services can only be Deployed through the backend processing. | Detailed instructions on how to generate and deploy a service using the backend script are described in the following sections: Manual Steps to Generate a Service Perform the following steps to generate a service through the backend processing: 1. Find irep_name of the service to be generated. For PL/SQL APIs, irep_name is the 'Internal Name' as shown on the Interface Details page of a PL/SQL API in the Integration Repository user interface. | Note: Use the exact irep_name as it is without changing its case. | - Perform the following steps on the first node (can be any one node) of a multinode environment:
- cd $FND_TOP/bin.
- Run soagenerate.sh irepname=<irep_name>. For example, soagenerate.sh irepname=FND_GLOBAL
| Note: soagenerate.sh is a standalone script used to generate WSDL services for all the integration interfaces that can be service enabled through backend processing except BSO service type. For setup prerequisites on using this script, see the "Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12", My Oracle Support Knowledge Document 726414.1. | - See log file ServiceGenerator.log for details. Look for statement "Service Generated" for successful generation. It means that the service is successfully generated. Also, look for 'classId' for this service in log file.
For example, "irepName is FND_GLOBAL. Generating service with classId = 1728". Notice that the classId is 1728. - If a service is generated successfully, the following directory should be created:
$INST_TOP/soa/PLSQL/<classId> For example, $INST_TOP/soa/PLSQL/1728 Zip the directory <classId> as <classId>.zip and put it in the directory $INST_TOP/soa/PLSQL. - Perform the following steps on ALL other nodes of a multinode environment:
- ftp to the first node as described in the Step 2 of this section.
- cd to $INST_TOP/soa/PLSQL.
- Get <classId>.zip.
- Unzip <classId>.zip in $INST_TOP/soa/PLSQL.
Manual Steps to Deploy a Service Perform the following steps to deploy a service including a BSO service: - Find irep_name of the service to be deployed. For example:
- For PL/SQL APIs, irep_name is the 'Internal Name' as shown on the Interface Details page of a PL/SQL API in the Integration Repository user interface.
- For Business Service Object (BSO) integration services, irep_name is the 'Qualified Name' as shown on the Interface Details page of a BSO service in the Integration Repository user interface.
- Perform the following steps on ALL nodes of a multinode environment:
- cd $FND_TOP/bin.
- Run soadeploy.sh irepname=<irep_name>. For example:
- soadeploy.sh irepname=FND_GLOBAL
- soadeploy.sh irepname=/oracle/apps/fnd/rep/ws/IntegrationRepositoryService
See log file ServiceDeployer.log for details. Look for statement "Service Deployed" for successful deployment. It means that the service is successfully deployed.
| Date | Description | | July 24, 2014 | Updated the step 2 in the Manual Steps to Deploy a Service section. | | April 23, 2013 | Updated the Overview section that steps described in this document apply to single node behind load balancer as well. | | April 9, 2013 | Updated step 3 in the One Time Configuration Steps for Oracle E-Business Suite Integrated SOA Gateway 12.1.2 and 12.1.3 section. | | May 3, 2012 | This document applies to both ISG release 12.1.2 and release 12.1.3; therefore, modified the document title by adding release 12.1.3. | | September 7, 2011 | Updated the Overview section. | | May 4, 2010 | Published document. |
Oracle Copyright Notice
Copyright © 2010, 2014 Oracle. All rights reserved. Trademark Notice
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
|