Integrated SOA Gateway Setup in EBS R12.1.3

Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.1.3 [Metalink ID 556540.1]


1. Source the file $INST_TOP/ora/10.1.3/.env and then apply the following patches to the Oracle Application Server 10.1.3.5 Oracle Home:

i) Patch 13800972: Merge Request on Top of 10.1.3.1.0 for Bugs 8857799 9223438 12352047 (Patch 13800972 is also compatible with Oracle Application Server 10.1.3.5.0.)

ii) Patch 9371120: Web Service Framework Takes More Time for Giving the Response

iii) Patch 7366746: WLP: Enabling "Use SAML Authority: Verify Signature" Doesn't Require SAML Token

iv) Patch 15914125: Merge Request on Top of 10.1.3.5.1 for Bugs 9187189 9668283 13248533


2. Apply the following Oracle E-Business Suite patches:

i) Patch 13347633:R12.OWF.B: Performance Issues in PIM Load

ii) Patch 13957925:R12.OWF.B: One-off:13029726:12.1.3: SQL Exception in SOA Monitor Page

iii) Patch 14063221:R12.OWF.B: Consolidated Fixes on Top of 11688301:R12.OWF.B

iv) Patch 9139673:R12.OWF.B: IREP Issues When APPLSYS Schema Name is Changed

v) Patch 13516999:R12.OWF.B: Performance Degradation of Web Service Calls Hosted in R12 SOA Gateway

vi) Patch 14741766:R12.TXK.B: Need to Add a New Property for Session in OC4J.Properties


3. Set applications environment and stop all application tier processes.

i) From the applications instance $APPL_TOP, set the environment by running the APPS.env script 

ii) Stop all application tier processes for the instance by running the script $ADMIN_SCRIPTS_HOME/adstpall


4. Run TXK development script to install Oracle Application Server Adapter for Oracle Applications as shown below:

i) $FND_TOP/bin/txkrun.pl -script=CfgOC4JApp -applicationname=pcapps -oracleinternal=Yes -oc4jpass=welcome -runautoconfig=No

Note: If the 'oc4jadmin' password for the OAFM oc4j instance is not known, then reset the password in the file $INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml before running the script. Take the backup of system-jazn-data.xml before resetting the password. Replace the modified system-jazn-data.xml with backup of system-jazn-data.xml after running the script.

For example, if you want to reset the password to '!welcome', below should be the entry:


oc4jadmin
OC4J Administrator
23C8E4F0BDDE11DCBFB8AF3B7E0DDB2D
OC4J Administrator
!welcome

5. Run TXK deployment script to install forms-c4ws.ear and configure container Forms-c4ws J2EE group correctly, as shown below:

i) $FND_TOP/bin/txkrun.pl -script=DeployForms-c4ws

6. Enable the new container forms-c4ws. (By default, the new OC4J container forms-c4ws will be disabled.)

i) To enable the new container forms-c4ws, modify the following values of context variables in the $CONTEXT_FILE:

Set 's_forms-c4wsstatus' to "enabled".
Set 's_forms-c4ws_nprocs' to "1".

Note: The 's_forms-c4ws_display' context variable is used by the forms-c4ws OC4J instance. It must be set properly in order to use the Java APIs for Forms interfaces. This display must always be accessible during runtime. It should be set to an active and authorized X Windows display, and should point to a machine that is always available to the application instance.

7. Run AutoConfig script present in $ADMIN_SCRIPTS_HOME on the application tier. For example, $ADMIN_SCRIPTS_HOME/adautocfg.sh

8. Start all application tier processes for the instance by running the script $ADMIN_SCRIPTS_HOME/adstrtal

9. Enable ASADMIN user using the following steps:

i) Log on to Oracle E-Business Suite using sysadmin/sysadmin.

ii) Select the User Management responsibility in the Navigator.

iii) Click the Users link from the navigation menu to open the User Maintenance window.

iv) Locate 'ASADMIN' user by entering information in the search area to retrieve the 'ASADMIN' user.

v) Click the Update icon next to the ASADMIN user to open the Update User window.

vi) Remove the Active To date field and click Apply.

vii) Click the Reset Password icon next to the ASADMIN user to open the Reset Password window.

viii) Enter new password twice and click Submit.

10. After activating the ASADMIN user, verify if the ASADMIN user has the 'Apps Schema Connect Role' (UMX
APPS_SCHEMA_CONNECT) role in wf_user_roles.

If the 'Apps Schema Connect Role' role is not present in the wf_user_roles for the ASADMIN user, then run the 'Workflow Directory Services User/Role Validation' concurrent program to grant the role.

11. Reset the 'ASADMIN' password in the file system.

i) After 'ASADMIN' user is enabled from Oracle E-Business Suite, update the file

$INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml as shown below to reset the password:


ASADMIN
Default Apps SOA User
Used by SOAProvider for DB connection
!


Note: The password should be preceded by a '!' (Exclamation) so that when OAFM is started,
it gets encrypted. For example, if your password is 'welcome', then you should write it in the above file as "!welcome".

12. Bounce the middle tier.


Issues:

$FND_TOP/bin/txkrun.pl -script=DeployForms-c4ws issue was fixed by fixing jvm option for OC4J in opmn.xml file under IAS_ORACLE_HOME/opmn/conf