Validating the Setup for ASADMIN User for ISG and XML Gateway JDBC Connections in EBS Oracle Apps

If we want to validate the ASADMIN setup is correct after the Integrated SOA gateway or after cloning the EBS environment we can use below steps.

1. Enable "ASADMIN" user.

a) Log in using sysadmin/<sysadmin_pw>
b) Choose responsibility 'User Management'
c) Find user ASADMIN
d) Reset Password
e) Remove Active To date if set.
f) Apply

2. Test that ASADMIN user exist in the Database as an EBS user:

This will confirm that the ASADMIN user's password is "welcome".  Substitute it for your ASADMIN user password.

select fnd_web_sec.validate_login('ASADMIN','welcome') from dual;

3. Confirm that ASADMIN has the required role 'UMX|APPS_SCHEMA_CONNECT' to be authorized to connect to EBS.

col name for a30 head "Name"
col role for a30 head "Role"
select substr(user_name, 1, 30) name, substr(role_name, 1, 30) role
from wf_local_user_roles
where user_name='ASADMIN'

4. Run TXK deployment Script to install SOAAppsAdapter as shown below:

$FND_TOP/bin/ -script=CfgOC4JApp -applicationname=pcapps -oracleinternal=Yes -oc4jpass=welcome -runautoconfig=No
After deploying pcapps.rar to OC4J Container, CLASSPATH needs to be changed to include AppsAdapter.jar,DBAdapter.jar & AqAdapter.jar file.

5. Run autoconfig.


6. Ensure the correct data-sources.xml is being called:

vi $INST_TOP/ora/10.1.3/j2ee/oafm/application-deployments/default/AppsSOAAdapter/oc4j-ra.xml

oc4j-ra.xml that is shipped with pcapps.rar has the below content:

<connector-factory location="eis/Apps/apps1" connector-name="Oracle Applications Adapter">
<config-property name="xADataSourceName" value="jdbc/Apps1DataSource"/>
<config-property name="dataSourceName" value=""/>
<connection-pooling use="none">
<security-config use="none">

But for SOA Provider to work this needs to be manually modified to

<connector-factory location="/eis/apps/adapter" connector-name="Oracle Applications Adapter">
<config-property name="xADataSourceName" value=""/>
<config-property name="dataSourceName" value="jdbc/AppsDs"/>
<connection-pooling use="none">
<security-config use="none">

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

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

<display-name>Default Apps SOA User</display-name>
<description>Used by SOAProvider for DB connection</description>
<credentials>!<NEW PASSWORD></credentials>

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"

8. Restart the Applications Tier.

$ADMIN_SCRIPTS_HOME/ apps/apps_password

$ADMIN_SCRIPTS_HOME/ apps/apps_password


1. Enable FND Logging for ISG.

vi $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/config/

# Added for SOA Debugging


  •  cd $INST_TOP/ora/10.1.3/j2ee/oafm/config/
  • Add following property at the end of the file:
  • Bounce oafm container using script $ADMIN_SCRIPTS_HOME/
  • Perform any SOA specific action like generate.
  • SOA specific log would be created at : $INST_TOP/soa/SOALog.log

2. Shutdown and restart the OAFM container.



3. Run the following from a Unix shell with the Apps environment sourced and upload the resulting zip file under your Unix OS temp [ tmp ] directory.

zip -r /tmp/`uname -n`_`date +%m%d%y.%H%M` \
$ORA_CONFIG_HOME/10.1.3/j2ee/oafm/* \
$ORA_CONFIG_HOME/10.1.3/opmn/* \
$LOG_HOME/ora/10.1.3/opmn/* \
$LOG_HOME/ora/10.1.3/j2ee/oafm/* \

If you like please follow and comment