SOA问题处理

R12.1: How To Generate SOA Log For Debugging SOA Provider Issues (文档 ID 828753.1)

转到底部

In this Document

Goal

Solution

APPLIES TO:

Oracle E-Business Suite Integrated SOA Gateway - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Oracle EBusiness Suite Integrated SOA Gateway - Version: 12.1.1

GOAL

How to generate SOA log for debugging any issues with SOA Provider in Integrated SOA Gateway,12.1.1? This log file is helpful when there are errors during Service Generation/Deployment or in cases where the call to Native Services fails.

SOLUTION

SOA Logs can be generated either from the back end or the front end UI:

1. From the Front End :

Log on to Oracle Applications with the username that has the System Administrator responsibility access privilege.
Select the System Administrator responsibility from the Navigator and choose Oracle Applications Manager > Logs.
Click Log Setup to open the Java System Property Settings page.
Click the Site link and enable log for
Midtier Log File Name: Enter the file name that one would like on the middletier, for example, '/tmp/SOALog.log'.
Module=Enter an appropriate module name, for example, 'fnd/soa%'.
Ask the System Administrator to bounce the oafm container.
Perform any SOA specific action, such as generation of any API.

Look for logs in the file specified in the Middle tier Log File Name field. In case one is not able to get the logs using this method try method2 of getting the log from back end.

2. From the Back End :

Telnet to environment and in $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

---------------------------------------------------------------------------------------------------------------------------------------------------

Enable ASADMIN user using the following steps:

Log in to Oracle E-Business Suite as a user name sysadmin.
Select the User Management responsibility in the Navigator.
Click the Users link from the navigation menu to open the User Maintenance window.
Locate 'ASADMIN' user by entering information in the search area to retrieve the 'ASADMIN' user.
Click the Update icon next to the ASADMIN user to open the Update User window.
Remove the Active To date field and click Apply.
Click the Reset Password icon next to the ASADMIN user to open the Reset Password window.
Enter new password twice and click Submit.
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.

Reset the 'ASADMIN' password in the file system.
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:

<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 your password is 'welcome', then you should write it in the above file as "!welcome".

Bounce the middle tier

巴特西

SOA问题处理

APPLIES TO:

GOAL

SOLUTION

最新文章

热门文章