SOA Gateway Setup after Cloning EBS 12.1.3 Instance

After cloning EBS Application, we will need to setup Integrated SOA GateWay again

1. Reset the ASADMIN password Mandatory

A. Reset the password in the Application

Navigation path:

a. System Administrator Responsibility

b. Security

c. User

d. Define

e. Query the ASADMIN user and change the password

B. Reset the "ASADMIN" password in the file system after "ASADMIN" user is enabled from inside EBS by updating the file:

a. vi $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/config/system-jazn-data.xml

<user>

<name>ASADMIN</name>

<display-name>Default Apps SOA User</display-name>

<description>Used by SOAProvider for DB connection</description>

</user>

NOTE: The password should be preceded by a '!' (Exclamation) so that when OAFM is started, it gets encrypted. For example, if the password is "welcome", then you have to change it to "!welcome"

b. Restart the appsTier.

$ADMIN_SCRIPTS_HOME/adstpall.sh apps/apps_pw

$ADMIN_SCRIPTS_HOME/adstrtal.sh apps/apps_pw

2. Re-generate all the services

soagenerate.sh can be used to generate multiple WSDL.

a. Prepare a file with the name of all the interfaces you want to regenerated

Example:

vi /tmp/services.lst

FND_USER_PKG

FND_USER_RESP_GROUPS_API

$FND_TOP/bin/soagenerate.sh

Enter the single or multiple generate as S/M :

Enter the filename of the interface to be generated :

/tmp/services.lst

3.Re-deploy using the soadeploy.sh

Example:

$FND_TOP/bin/soadeploy.sh

Enter the single or multiple deploy as S/M :

Enter the filename of the interface to be deployed:

/tmp/services.lst

If you like please follow and comment

SOA Gateway Setup after Cloning EBS 12.1.3 Instance