Skip to main content

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

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/txkrun.pl -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.



$ADMIN_SCRIPTS_HOME/adautocfg.sh

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">
</connection-pooling>
<security-config use="none">
</security-config>
</connector-factory>


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">
</connection-pooling>
<security-config use="none">
</security-config>
</connector-factory>


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



<user>
<name>ASADMIN</name>
<display-name>Default Apps SOA User</display-name>
<description>Used by SOAProvider for DB connection</description>
<credentials>!<NEW PASSWORD></credentials>
</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"

8. Restart the Applications Tier.



$ADMIN_SCRIPTS_HOME/adstpall.sh apps/apps_password

$ADMIN_SCRIPTS_HOME/adstrtal.sh apps/apps_password
 

Diagnostics

1. Enable FND Logging for ISG.



vi $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/config/oc4j.properties
 

# Added for SOA Debugging
#
AFLOG_ENABLED=true
AFLOG_LEVEL=1
AFLOG_MODULE=fnd.soa%
AFLOG_FILENAME=/tmp/SOALog.log

OR


  •  cd $INST_TOP/ora/10.1.3/j2ee/oafm/config/oc4j.properties
  • Add following property at the end of the file:
  • SOA_ENABLE_STANDALONE_LOGGING=TRUE
  • Bounce oafm container using script $ADMIN_SCRIPTS_HOME/adoafmctl.sh.
  • 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.



$ADMIN_SCRIPTS_HOME/adoafmctl.sh stop

$ADMIN_SCRIPTS_HOME/adoafmctl.sh start


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`_iAS1013.zip \
$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/* \
$CONTEXT_FILE




If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more