Oracle

GCS Fusion Applications

Hands-On Exercise
Tech 2 : Logging/Tracing
Fusion Application Logging
UI / WebServices / ESS

Document Contact

Karanbir Dhillon

Organization

Global Customer Support -FAST

Version Number

1.0

Last Revision By

Karanbir
DhillonKARANBIR
DHILLONKARANBIR DHILLON

Total Pages :

42

Table of Contents
Table of Contents........................................................................................................................ 2
Document Information................................................................................................................. 3
Fusion Application Logging Configurations..................................................................................4
Fusion Application Logging Configurations in logging.xml........................................................4
Fusion Application Logging Configurations via EM..................................................................6
Enabling Fusion Application Logging.........................................................................................12
Enabling Fusion Application Logging from Fusion UI.............................................................12
Enabling Fusion Application Logging from Profile Options UI................................................15
Enabling Fusion Application Logging from Profile Options Database PL/SQL Another Option
............................................................................................................................................... 19
Generating Fusion Application Log Files for Fusion UI..............................................................21
Review Fusion Application Logs................................................................................................22
Review Fusion Application Logs from EM.............................................................................22
Review Fusion Application Logs on Server...........................................................................25
Review Logs from LogSpy.....................................................................................................26
Scenario Multiple users running Fusion Apps Logging .............................................................27
How to get Fusion Application Logging for a specific source code.............................................29
Fusion Application Logging for ADF WebServices....................................................................32
Fusion Application Logging for ESS - Java................................................................................34
Fusion Application Logging for ESS PL/SQL..........................................................................39

Document Information
Document Participants
Karanbir Dhillon

Author(s)
Contributor(s)
Reviewer(s)/Approver(s)
Benefited/Affected Organization(s)

Global Customer Support - FAST

Revision History
Version
1.0

Modified
Date
09/03/2010

Who
Karanbir
Dhillon

Changed
Section(s)
All

Change Summary
New Document

Fusion Application Logging Configurations

Fusion Application Logging Configurations in logging.xml
Each Managed Server has logging. xml file in { Weblogic Domain}
/config/fmwconfig/servers/{Managed Server Name} and the AppsLogger Contents are
present there ie the Logger Details and the Handler details.
Steps to do :1. Login to the below machine using PUTTY
Hostname : adczab08
User/password : app1000/APP1000
2. Navigate to the Marketing Server logging.xml folder
/ds08/app1000/junerun/install/instance/domains/CRMDomain/config/fmwconfig/serv
ers/MarketingServer_1
[app1000@adczab08 ~]$cd
/ds08/app1000/junerun/install/instance/domains/CRMDomain/config/fmwconfig/servers/
MarketingServer_1
[app1000@adczab08 MarketingServer_1]$ pwd
/
ds08/app1000/junerun/install/instance/domains/CRMDomain/config/fmwconfig/servers/M
arketingServer_1
3. Review the logging.xml file
[app1000@adczab08 MarketingServer_1]$ ls -ltr logging.xml
-rw------- 1 app1000 gapp1000 15317 Jun 16 08:36 logging.xml

In the logging.xml AppsLogger logger details :<logger level="ALL" name="oracle.apps" useParentHandlers="false">

<handler name="apps-handler"/>
</logger>

<logger level="SEVERE" name="oracle.apps.appslogger.internallogger"

useParentHandlers="false">
<handler name="apps-handler"/>
</logger>
In the logging.xml information about Log Handlers See the Path of the Log file
and the File Size and Max File Size. Also the Attributes being logged.
<log_handler class="oracle.core.ojdl.logging.ODLHandlerFactory" name="appshandler">
<property name="supplementalAttributes" value="APPS_USER_NAME,
APPS_SESSION_ID, APPS_THREAD_NAME, APPS_SOURCE, APPS_USER_ID,
APPS_ROLE_IDS, APPS_AUTO_LOG, APPS_JOB_REQUEST_ID,
APPS_JOB_DEFINITION_NAME, APPS_JOB_PACKAGE_NAME,
APPS_JOB_DEFINITION_APP, APPS_COMPOSITE_NAME,
APPS_COMPONENT_NAME, APPS_COMPOSITE_INSTANCE_ID,
APPS_COMPONENT_INSTANCE_ID, APPS_PRODUCT_FAMILY, APPS_PRODUCT,
APPS_INDUSTRY, APPS_TERRITORY, APPS_DB_CONNECTION_URL"/>
<property name="encoding" value="UTF-8"/>
<property name="path" value="${domain.home}/servers/${weblogic.Name}/logs/apps/
${weblogic.Name}-diagnostic.log"/>
<property name="maxFileSize" value="10485760"/>
<property name="maxLogSize" value="104857600"/>
</log_handler>

If the changes are made to logging.xml the Managed Server has to be bounced to
read the changes. It is recommended to make the changes via EM not updating
logging.xml

Fusion Application Logging Configurations via EM

1. Login to EM of Fusion Applications Domain
http://adczab08.us.oracle.com:39001/em
Userid / Password - weblogic/junerun1
2. Navigate to Farm_CRMDomain-> Weblogic Domain -> CRMDomain -> MarketingCluster
-> MarketingServer_1

3. Then go to Log Configuration ie WebLogic Server -> Logs -> Log Configuration

4. See the Runtime Logger for oracle.apps and see the Handler it is using by expanding
the Root Logger then oracle.

5. Click on the Handler or navigate to Log Files and click on the Handler name to see
details

6. Can make changes to the File Size, Path, etc and click OK which will update the
logging.xml as discussed earlier of the Managed Server. See Eg the File Size changed

to 100MB and max to 1000MB. The default format of ODL is Text can be changed to
XML also.
NOTE : Please do not make changes as will affect others

If any changes are made and saved you will a confirmation box.

Enabling Fusion Application Logging

Enabling Fusion Application Logging from Fusion UI
1. Review the Sales Campaign Flow Document for Login Details to Sales Campaign URL.
2. Once logged in Navigate to Help -> Supportability -> Set Supportability Levels

3. It will pop up the Set Supportability Window.

4. Enable the Applications Logging and Change the Logging Level to save FINEST and
Logging Module Everything ie %
NOTE : If already enabled ignore it

5. Click OK to Apply the same which will save the Application Logging Profile. This will
enable the logging for the logged in user only.
6. You need to Logout of the Application and Log back in to get the Apps Logger files
created. Currently in our Env logout is not working so make sure you close the browser
and when you navigate back to the SalesCampaign URL you should see login box. Now
do any activity in the UI the Fusion Application Logging will be done in the Handler seen
earlier.

Enabling Fusion Application Logging from Profile Options UI

1. Login to URL
http://adczab14.us.oracle.com:40628/fnd/faces/SetupDemo_UIShellPage
User/Password : SALES_ADMIN/Welcome1
2. Navigate to Profiles -> Managed Administrator Profile Values

3. Search for the Profile Option Name AFLOG%

4. Edit the Profile Options say AFLOG_LEVEL for SITE, User etc and save and then
when the user Logs in will get AppsLogger file created in appropriate level. Lets take
Scenario where Admin wants to change for the user SALES_ADMIN the Log level to
FINEST where as for the SITE the Log Level is Severe.
NOTE : If the option is already set ignore it

Enabling Fusion Application Logging from Profile Options Database PL/SQL

Another Option
Connect to Fusion Database via SQLDeveloper :Hostname : adczab12
SID : adczab12
Port : 1522
User : fusion
Password : junerun1
The FND Profile values can be changed by PL/SQL. To see the values SQL
select p.profile_option_name, l.level_name, v.level_value, v.profile_option_value
from FND_PROFILE_OPTION_VALUES v, FND_PROFILE_OPTIONS_B p, FND_PROFILE_OPTION_LEVELS l
where p.profile_option_id = l.profile_option_id
and p.application_id = l.application_id
and l.profile_option_id = v.profile_option_id
and l.application_id = v.application_id
and l.level_name = v.level_name
and p.profile_option_name like 'AF%';

To update the Profile using PL/SQL for AFLOG_LEVEL for SITE to 1000.
DECLARE
X_NAME VARCHAR2(200);
X_VALUE VARCHAR2(200);
X_LEVEL_NAME VARCHAR2(200);
X_LEVEL_VALUE VARCHAR2(200);
v_Return BOOLEAN;
BEGIN
X_NAME := 'AFLOG_LEVEL';
X_VALUE := '1000';
X_LEVEL_NAME := 'SITE';
X_LEVEL_VALUE := 'SITE';
v_Return := FND_PROFILE.SAVE(

X_NAME => X_NAME,

X_VALUE => X_VALUE,
X_LEVEL_NAME => X_LEVEL_NAME,
X_LEVEL_VALUE => X_LEVEL_VALUE
);
IF (v_Return) THEN
DBMS_OUTPUT.PUT_LINE('v_Return = ' || 'TRUE');
ELSE
DBMS_OUTPUT.PUT_LINE('v_Return = ' || 'FALSE');
END IF;
END;

To update the Profile using PL/SQL for AFLOG_LEVEL for User SALES_ADMIN to Finest.
Note need the GUID of the user. It is in PER_USERS table.
DECLARE
X_NAME VARCHAR2(200);
X_VALUE VARCHAR2(200);
X_LEVEL_NAME VARCHAR2(200);
X_LEVEL_VALUE VARCHAR2(200);
v_Return BOOLEAN;
BEGIN
X_NAME := 'AFLOG_LEVEL';
X_VALUE := '300';
X_LEVEL_NAME := 'USER';
X_LEVEL_VALUE := ' C207BB06AFF8AC902FC7F9803EB6EB49';
v_Return := FND_PROFILE.SAVE(
X_NAME => X_NAME,
X_VALUE => X_VALUE,
X_LEVEL_NAME => X_LEVEL_NAME,
X_LEVEL_VALUE => X_LEVEL_VALUE
);
IF (v_Return) THEN
DBMS_OUTPUT.PUT_LINE('v_Return = ' || 'TRUE');
ELSE
DBMS_OUTPUT.PUT_LINE('v_Return = ' || 'FALSE');
END IF;
END;

Generating Fusion Application Log Files for Fusion UI

Once the AppsLogger is enabled for the User or Site logout and login again and do the
Flow to create the AppsLogger.
Eg : Going through Sales Campaign Flow

Review Fusion Application Logs

Review Fusion Application Logs from EM
1. Login to EM of Fusion Applications Domain
http://adczab08.us.oracle.com:39001/em
Userid / Password - weblogic/junerun1
2. Navigate to Farm_CRMDomain-> Weblogic Domain -> CRMDomain -> MarketingCluster
-> MarketingServer_1

3. Navigate to View Log Messages ie WebLogic Server -> Logs -> View Log Messages

4. There you can Add fields and values and search on Message Types and select and
unselect Targets

Review Fusion Application Logs on Server

Login to the below machine using PUTTY
Hostname : adczab08
User/password : app1000/APP1000
Navigate to -> {Application Weblogic Domain}/servers/{Managed Server
Name}/logs/apps and there all the AppsLogger log files will be present

[app1000@adczab08 apps]$ pwd

/
ds08/app1000/junerun/install/instance/domains/CRMDomain/servers/MarketingServer_1/logs/a
pps
[app1000@adczab08 apps]$ ls -ltr
total 32240
-rw-r----- 1 app1000 gapp1000 10479989 Aug 13 14:30 MarketingServer_1-diagnostic-1.log
-rw-r----- 1 app1000 gapp1000 22485172 Aug 26 17:16 MarketingServer_1-diagnostic.log
One Line from the AppsLogger Log

[2010-08-26T17:16:20.221-07:00] [MarketingServer_1] [TRACE:16] [] [oracle.apps] [tid:

14] [userId: SALES_ADMIN] [ecid: 004ZgC5oNXlEkJQRyaz0D00003kc000MOo,0:1]
[SRC_CLASS: oracle.apps.fnd.applcore.log.AppsODLHandler] [APPS_AUTO_LOG:
false] [APPS_DB_CONNECTION_URL:
jdbc:oracle:thin:@adczab12.us.oracle.com:1522:adczab12] [SRC_METHOD: publish]
[APPS_SOURCE:
crmCommon.workMgmt.core.publicModel.common.util.OwnerModuleFilter.doFilter]
[APPS_THREAD_NAME: [ACTIVE].ExecuteThread: '1' for queue:
'weblogic.kernel.Default (self-tuning)'] [APP: EarMarketing#V2.0] [APPS_TERRITORY:
US] [APPS_SESSION_ID: 8EC4044D86112F83E04014905FC41A22]
[APPS_ROLE_IDS: ANONYMOUS_ROLE_GUID] [APPS_USER_NAME:
SALES_ADMIN] [APPS_USER_ID: C207BB06AFF8AC902FC7F9803EB6EB49]
[APPS_PRODUCT: MKL] [URI: /marketing/faces/SalesCampaignDashboard] Exiting
with ()
For Understanding of Format of log refer to
http://fmwdocs.us.oracle.com/doclibs/fmw/E10285_01/appslib7/doc.1111/e10308/s
up_logging.htm and Section Log Message Structure.

Review Logs from LogSpy

Navigate to LogSpy URL http://adczab08:39001/diag/
Click on Logs Link ie URL http://adczab08:39001/diag/LogSpy
You can see Logs for all Managed Servers in the Domain or Filter by specific Managed Server.

Can Limit the various Logs file and search within particular files.

Scenario Multiple users running Fusion Apps Logging

All users log files goes in the same Log file and when searching search for the
APPS_USER_NAME
1. Execute Sales Campaign Flow with User A with Apps Logging Enabled
2. Execute Sales Campaign Flow with User b with Apps Logging Enabled
3. Try to find in the EM or direct logs on servers lines corresponding to each User.
See User SALES_ADMIN Log lines

See User SALES_REPRESENTATIVE log lines

How to get Fusion Application Logging for a specific source code

The Logging Module Field in Set Supportability Levels or the AFLOG_MODULE Profile
is where need to set the Source Code for which Logging needs to be done.
1. Login to the Fusion Sales Campaign UI and there in the Logging Module field put the
string for the Code eg %crm% and Click OK.

2. Optionally from the Profiles Ui, add the User and the Profile value %crm%

3. Now Launch the Sales Campaign flow and will see very few lines gets logged as
compared to % done earlier.
Now if you do the Application flow the AppsLogger file will be have only where Modules
have crm in it. See sample lines
[2010-08-26T18:01:01.379-07:00] [MarketingServer_1] [TRACE:16] [] [oracle.apps] [tid: 11]
[userId: SALES_ADMIN] [ecid: 004ZgE_z231EkJQRyaz0D00003kc000MUu,0:1] [SRC_CLASS:
oracle.apps.fnd.applcore.log.AppsODLHandler] [APPS_AUTO_LOG: false]
[APPS_DB_CONNECTION_URL: jdbc:oracle:thin:@adczab12.us.oracle.com:1522:adczab12]
[SRC_METHOD: publish] [APPS_SOURCE:
crmCommon.workMgmt.core.publicModel.common.util.OwnerModuleFilter.setProductInApplSes
sion] [APPS_THREAD_NAME: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default
(self-tuning)'] [APP: EarMarketing#V2.0] [APPS_TERRITORY: US] [APPS_SESSION_ID:
8EC3A5285F11D0C9E04014905FC448BC] [APPS_ROLE_IDS: ANONYMOUS_ROLE_GUID]
[APPS_USER_NAME: SALES_ADMIN] [APPS_USER_ID:
C207BB06AFF8AC902FC7F9803EB6EB49] [APPS_PRODUCT: MKL] [URI:
/marketing/faces/SalesCampaignDashboard] Exiting with ()
[2010-08-26T18:01:02.006-07:00] [MarketingServer_1] [TRACE:16] [] [oracle.apps] [tid: 11]
[userId: SALES_ADMIN] [ecid: 004ZgE_z231EkJQRyaz0D00003kc000MUu,0:1] [SRC_CLASS:
oracle.apps.fnd.applcore.log.AppsODLHandler] [APPS_AUTO_LOG: false]
[APPS_DB_CONNECTION_URL: jdbc:oracle:thin:@adczab12.us.oracle.com:1522:adczab12]
[SRC_METHOD: publish] [APPS_SOURCE:
crmCommon.workMgmt.core.publicModel.common.util.OwnerModuleFilter.doFilter]
[APPS_THREAD_NAME: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-

tuning)'] [APP: EarMarketing#V2.0] [APPS_TERRITORY: US] [APPS_SESSION_ID:

8EC3A5285F11D0C9E04014905FC448BC] [APPS_ROLE_IDS: ANONYMOUS_ROLE_GUID]
[APPS_USER_NAME: SALES_ADMIN] [APPS_USER_ID:
C207BB06AFF8AC902FC7F9803EB6EB49] [APPS_PRODUCT: MKL] [URI:
/marketing/faces/SalesCampaignDashboard] Exiting with ()
4. Lets try to limit further there using multiple Sources using Steps as above
% SalesCampaignAMImpl%,% MktResourceUtilAMImpl%
If need to enter more strings enter with comma as delimeter
5. Now try to review logs after going through Sales Campaign Flow and will see it much
smaller.

Fusion Application Logging for ADF WebServices

The ADF WebServices are from the same Model Layer on which the UI is based. So logging is
not different as done earlier from UI. Only issue is for the WebService user does not have a
Option to turn on. So the Options for enabling logging will be the User who invokes WebService
either goes through some Fusion UI and enables or Admin uses the Profile Options UI.
Will be using a DialogService used in the Sales Campaign Flow ie called by the SOA Composite
1. Enable Logging for the user used in Sales Campaign Flow to FINEST level for say
Logging Module %dialogService%
2. Then do the Sales Campaign flow and in their the SOA Composite will call multiple ADF
WebServices which will be logged
3. Verify the Logs by EM or on server (make sure the URI: /mktDialogs/DialogService ).
( NOTE : Use the URL and details as done earlier) See sample log line
[2010-08-27T18:24:12.014-07:00] [MarketingServer_1] [TRACE:32] [] [oracle.apps] [tid: 24] [userId: SALES_ADMIN] [ecid:
0000IeqIldqEsHQRya3FD01CU2Tf00000P,0:1:0x5f5e172:3:0x5f5e176:6:0x5f5e18b:4:0x5f5e1a2:4:0x5f5e1bf:5:0x5f5e1c6:2:0x5f5e
1ca:1:1] [SRC_CLASS: oracle.apps.fnd.applcore.log.AppsODLHandler] [APPS_AUTO_LOG: false]
[APPS_DB_CONNECTION_URL: jdbc:oracle:thin:@adczab12.us.oracle.com:1522:adczab12] [SRC_METHOD: publish]
[APPS_SOURCE: marketing.coreMarketing.dialogs.dialogService.applicationModule.DialogAMImpl] [APPS_THREAD_NAME:
[ACTIVE].ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'] [APP: EarMarketing#V2.0] [APPS_TERRITORY:
US] [APPS_SESSION_ID: 8ED915DDBA519475E04014905FC4234C] [APPS_ROLE_IDS:
7618B711602D0FB80256A3EAC67A73C2, 40C4AE052EC2582286A6A0FB1514656C, CD8C1F65829BF3C1A2E970B6F6203403,
849B94CDAFC1B603D4EF099C758224D5, 58BCB56BC4355120CC9EA37381DCF1D1,
8EDC2DA47525F5AD40A4EB3AEF183323, BD42E54C1C9CF20AE3B4CDE7C1A54B34,
6511982C35F07FE6AB2BE1702B9B3282, 9547206B2FF2216404B0004891B8F018, D7369A98F32454E6A6DCDCB75EE57BDE,
0AE90D97C66E97E374306D7BCBCB45C2, 9115A3F1834A872EA567296FE1B9E9B0,
EC3BB8A7FDAEC31041F50CEFBD61CEF2, 7BC26869448CCD35570CAFDF32780AD4,
35DB256AD26C8BCDC5CB491CEA52D249, ABDC589B8F6E03639BDFAA2E97C4C5D1,
118BE2813AB6C8ADD2D867836A4ECB67, 60691A13669D7505CBD3D68FE3106D01,
D72A1B807135E0A9B69280B9762C8804, 9C0E6F6F4F2F7896C6B2E4062B47598C,
6D84EBA785A38FC0FBBD7B4845BF55CB, 25F339C52C6CD304DF4EE84F262736BE,
81EF550191B91D27ABEAE386A3F20D78, 103A06CB4383B894179379D036DEACC1,
E8FFED4BD2BE4813BE1798C690DF5811, 3B60B0CE7890E7E637C0F2DA9593726A,
CABE1333B5B092760D774D7CE3DE21DE, EB50673A0047C8BB9BF1E53F8A2E05EC,
447232C6FD199B349EF89A14B0933776, D0E738C2FD4D6C8E7E43D44D21832557,
2CA8D8217E6BE0E3FFF65FB65EF95B02, 63E5519F37E1CFBAD46E00AC73DEE489,
C304FC0299BF0C469D44800E5EA6B6B7, A02267ABB367342004964A0E1160F251,
8EFC0101B11D75F86887D20FD736BECC, 4D2F5F1D32E4DCCDA0F6818E93A6B512, AUTHENTICATED_ROLE_GUID,
BCC60B58F8B6E2CC27ED3228C8C67109, 65D86186CBA1360E8AFFF209F2DAAC0D,
F97375E70E0A9294D27E3490E33886CF, D7C7A49F2DA7F4CEFB330FF3ED9E5ACD,
14D2A3400C7E8F4D1CE4FE39AB522754, E3D0AC262A18967C57E418E29F76B897,
3F3143D28B71B4BE956B91F7431AD173, 6C13B16E99BAD61820A5F7FF59D36BCB,
83A6528B846AF8CB7BC6D8ED69809879, 89FA41CBACBE5C48E04014905FC45AC9,
A77FE23C03C28A48650D34A2204DEF08, E513BEF19F07A2B569E75830F6843E71, 6A61B6EFE86126946A9C5C60951B8092,
8FC9B3BFB7872942D5184AE47811D20B, ANONYMOUS_ROLE_GUID, DE2EF4EA3265C4D52EB57CBA6F4F7F0B,
88368F2B00C3AE8B85C40F39AB0846F7, 87CB2F3675399B0B8C57AFC1B4A075FA, 73E87EC43381B7D78BAD46248007F330,
7B1BF77520376142A632887D522B8BCA, DE7867D444C846B72919C2EC1639CFD3,
AE6AFC84D95F8E998FFAF5E0B13C73F3, 907D602CFC65CDD06737A0B55AAEEF55,
7AEFEEF52BCAE8D108C32F5E0BFF234B, F784EF9D1197423DD61DB28763E2C5B8,
CB012FEE09D29A4C3B90D3D8F2F0FF70, 55DBAE2F2A5BB54D18B46FC5100D9D56,
F54DCE629C0A0445B6149FD4DF71AAF2, 6E68A131126DD4D889BE4E4B8F1DA266,
2D90A8171CCF4A75C655B75C1BA56D71, 77530D6FD31497D41F1427AC5E502D71,
89FA41CBACBD5C48E04014905FC45AC9, B64280EC670F3CEA8E729ED55B3FF0D5,
E4A500007F721B99E30362541D4F7D09, 4BE15A276E0DDDB0A8A2593AC049C7C8, 7F8C1467B72747B1B73A3F70F95526D4,
F8375ACB55BD4CA5AE5DBA1975A9F491, 84479391CC3F3F9F65286407985FEAB5,
7C2219AF723741650E5D1D3D576FDC50, 7930B04A6FE673C25B8EA7CA989E165E,
CEAC546EA03B6131685D34B92FED9ECC, 7C2C5C6D69E386395155EDD3D0753B6F,
619402D2E04B3ED636E4578885931D6D, 9A63CA50ECC2A0C058D10990F1386F86, F122B7635F0328AA382D5DD80FA999E1,
662B9DFCECB1C8A9BF86E719017E09D0, 2640CC2A3FB922F8ADFC4407E1E04038,

5EB601C9CF9A5923C809AB4F2D25E039, E09FA5EB2ABDF4507ED4CAB5E9928390,
3C752E905C29E9B309976AEDC1A8EF5E, 732F3EBDF318FEE4D0E1A6BCB8B0807B] [APPS_USER_ID:
C207BB06AFF8AC902FC7F9803EB6EB49] [APPS_USER_NAME: SALES_ADMIN] [URI: /mktDialogs/DialogService]
@Parameters - dialogId: 100000017423043

Another Option using Secured WebServices Tester :1. Enable logging for the User ie SALES_ADMIN which will be used for Dialog Webservice
2. Launch URL for SecuredService Tester
http://130.35.106.75:8090/SecuredServiceTester/
3. In the WebService URL Enter http://adczab14:40630/mktDialogs/DialogService
4. In the Username Enter SALES_ADMIN
5. In the Password Enter Welcome1
6. In the Input Payload Enter
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body
xmlns:ns1="http://xmlns.oracle.com/apps/marketing/coreMarketing/dialogs/dialogService
/types/">
<ns1:getDialogs>
<ns1:dialogId>100000017423043</ns1:dialogId>
</ns1:getDialogs>
</soap:Body>
</soap:Envelope>
7. Press the Invoke Button which will call the WebService and you will see the Output
Payload
8. Verify the Logs by EM or on server (make sure the URI: /mktDialogs/DialogService ).
( NOTE : Use the URL and details as done earlier)

Fusion Application Logging for ESS - Java

The ESS Java programs use Fusion Applications Logging similar to the ADF Model which was
used in UI Earlier. Only issue is for the ESS user does not have a Option to turn on. So the
Options for enabling logging will be the User who invokes ESS either goes through some Fusion
UI and enables or Admin uses the Profile Options UI.
1. Enable Logging for the user used in Sales Campaign Flow to FINEST level for say
Logging Module %DialogSchedule%
2. Then do the Sales Campaign flow and make sure the Campaign is submitted which
schedules the ESS request.
3. Verify the ESS request is executed and the Status is not still queued.
4. Verify the Logs by EM ( Search Logs in the ess_server1 or on server. ( NOTE : Use the
URL and details as done earlier)

See sample log line on the Server

[app1000@adczab08 apps]$ pwd
/ds08/app1000/junerun/install/instance/domains/CRMDomain/servers/ess_server1/logs/apps
[app1000@adczab08 apps]$ grep StageExecutionId *.*
[2010-08-27T18:23:45.328-07:00] [ess_server1] [TRACE:32] [] [oracle.apps] [tid: 15] [userId: SALES_ADMIN] [ecid:
004ZhWK5LlUEkJQRyaz0D00004oK0000Iz,0:1:1:100000069] [SRC_CLASS: oracle.apps.fnd.applcore.log.AppsODLHandler]
[APPS_AUTO_LOG: false] [APPS_DB_CONNECTION_URL: jdbc:oracle:thin:@adczab12.us.oracle.com:1522:adczab12]
[SRC_METHOD: publish] [APPS_SOURCE: marketing.coreMarketing.dialogs.ess.program.DialogScheduleExecutable]
[APPS_THREAD_NAME: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [APP: EarCrmEss#V2.0]
[APPS_TERRITORY: US] [APPS_SESSION_ID: 8ED7FC51E7DF8024E04014905FC42143] [APPS_ROLE_IDS:
6511982C35F07FE6AB2BE1702B9B3282, 849B94CDAFC1B603D4EF099C758224D5,
8EDC2DA47525F5AD40A4EB3AEF183323, 9547206B2FF2216404B0004891B8F018,
BD42E54C1C9CF20AE3B4CDE7C1A54B34, 58BCB56BC4355120CC9EA37381DCF1D1,
CD8C1F65829BF3C1A2E970B6F6203403, 7618B711602D0FB80256A3EAC67A73C2, 40C4AE052EC2582286A6A0FB1514656C,
D7369A98F32454E6A6DCDCB75EE57BDE, 0AE90D97C66E97E374306D7BCBCB45C2,
EC3BB8A7FDAEC31041F50CEFBD61CEF2, 9115A3F1834A872EA567296FE1B9E9B0,
7BC26869448CCD35570CAFDF32780AD4, 35DB256AD26C8BCDC5CB491CEA52D249,
ABDC589B8F6E03639BDFAA2E97C4C5D1, 118BE2813AB6C8ADD2D867836A4ECB67,
60691A13669D7505CBD3D68FE3106D01, D72A1B807135E0A9B69280B9762C8804, 9C0E6F6F4F2F7896C6B2E4062B47598C,
6D84EBA785A38FC0FBBD7B4845BF55CB, 25F339C52C6CD304DF4EE84F262736BE,
81EF550191B91D27ABEAE386A3F20D78, 103A06CB4383B894179379D036DEACC1,
E8FFED4BD2BE4813BE1798C690DF5811, CABE1333B5B092760D774D7CE3DE21DE,
3B60B0CE7890E7E637C0F2DA9593726A, EB50673A0047C8BB9BF1E53F8A2E05EC,
2CA8D8217E6BE0E3FFF65FB65EF95B02, D0E738C2FD4D6C8E7E43D44D21832557,
447232C6FD199B349EF89A14B0933776, 63E5519F37E1CFBAD46E00AC73DEE489,
C304FC0299BF0C469D44800E5EA6B6B7, A02267ABB367342004964A0E1160F251,
8EFC0101B11D75F86887D20FD736BECC, 4D2F5F1D32E4DCCDA0F6818E93A6B512, AUTHENTICATED_ROLE_GUID,

BCC60B58F8B6E2CC27ED3228C8C67109, F97375E70E0A9294D27E3490E33886CF,
65D86186CBA1360E8AFFF209F2DAAC0D, D7C7A49F2DA7F4CEFB330FF3ED9E5ACD,
14D2A3400C7E8F4D1CE4FE39AB522754, 3F3143D28B71B4BE956B91F7431AD173,
E3D0AC262A18967C57E418E29F76B897, 6C13B16E99BAD61820A5F7FF59D36BCB,
83A6528B846AF8CB7BC6D8ED69809879, 89FA41CBACBE5C48E04014905FC45AC9,
A77FE23C03C28A48650D34A2204DEF08, E513BEF19F07A2B569E75830F6843E71, 6A61B6EFE86126946A9C5C60951B8092,
8FC9B3BFB7872942D5184AE47811D20B, DE2EF4EA3265C4D52EB57CBA6F4F7F0B,
88368F2B00C3AE8B85C40F39AB0846F7, 87CB2F3675399B0B8C57AFC1B4A075FA, 73E87EC43381B7D78BAD46248007F330,
7B1BF77520376142A632887D522B8BCA, AE6AFC84D95F8E998FFAF5E0B13C73F3,
DE7867D444C846B72919C2EC1639CFD3, 907D602CFC65CDD06737A0B55AAEEF55,
F784EF9D1197423DD61DB28763E2C5B8, 7AEFEEF52BCAE8D108C32F5E0BFF234B,
55DBAE2F2A5BB54D18B46FC5100D9D56, CB012FEE09D29A4C3B90D3D8F2F0FF70,
F54DCE629C0A0445B6149FD4DF71AAF2, 6E68A131126DD4D889BE4E4B8F1DA266,
77530D6FD31497D41F1427AC5E502D71, 2D90A8171CCF4A75C655B75C1BA56D71,
89FA41CBACBD5C48E04014905FC45AC9, B64280EC670F3CEA8E729ED55B3FF0D5,
E4A500007F721B99E30362541D4F7D09, 7F8C1467B72747B1B73A3F70F95526D4, 4BE15A276E0DDDB0A8A2593AC049C7C8,
F8375ACB55BD4CA5AE5DBA1975A9F491, 7C2219AF723741650E5D1D3D576FDC50,
84479391CC3F3F9F65286407985FEAB5, 7C2C5C6D69E386395155EDD3D0753B6F,
CEAC546EA03B6131685D34B92FED9ECC, 7930B04A6FE673C25B8EA7CA989E165E,
619402D2E04B3ED636E4578885931D6D, F122B7635F0328AA382D5DD80FA999E1, 9A63CA50ECC2A0C058D10990F1386F86,
2640CC2A3FB922F8ADFC4407E1E04038, 662B9DFCECB1C8A9BF86E719017E09D0,
E09FA5EB2ABDF4507ED4CAB5E9928390, 5EB601C9CF9A5923C809AB4F2D25E039,
732F3EBDF318FEE4D0E1A6BCB8B0807B, 3C752E905C29E9B309976AEDC1A8EF5E] [APPS_USER_ID:
C207BB06AFF8AC902FC7F9803EB6EB49] [APPS_USER_NAME: SALES_ADMIN] [URI:
/marketing/faces/SalesCampaignDashboard] ***** Status Set to ACTIVE for StageExecutionId = 100000017423051
For the above Flow it executed the

JobDefinition://oracle/apps/ess/marketing/coreMarketing/dialogs/DialogScheduleJob it logs the

lines as below.
From the EM :-

From the Source Code :-

Java Code in the ESS Program for AppsLogger :if (AppsLogger.isEnabled(AppsLogger.FINEST)) {

AppsLogger.write(this, "***** Status Set to ACTIVE for StageExecutionId = " +
stageExecutionId, AppsLogger.FINEST);
}

Fusion Application Logging for ESS PL/SQL

The ESS PL/SQL logging uses the FND_LOG API.
1. Check or add the Profile Option for the PL/SQL ie AFLOG_PLSQL_FILENAME ( NOTE :
Use the Profile Options UI URL and details as done earlier)

The value above is APPLLOG_DIR/mylog.log where the APPLLOG_DIR is a directory created

in oracle database by running the create or replace directory command.
To find the Physical Location of the Directory run the below SQL on the Database ( Details
provided earlier)
select * from dba_directories
where directory_name='APPLLOG_DIR'
->>

So on the DatabaseServer Machine it will write the PL/SQL Log on /tmp/mylog.log

2. Below is the ESS PL/SQL Metadata details

From the EM

3. Submit the ESS PL/SQL Job

http://adczab14.us.oracle.com:40630/crmCommon/faces/TestHzCpuiDashboardUIShell
Username/Password : FUSION_APPS_CRM_ESS_APPID/Welcome1

Click on ESS Central UI Link on the Left

Click on Schedule a New Process Button on the right

Search for PartyHirerarchyAudit Process and select the Job Parameters as below

Submit the ESS Job clicking on Submit Button

It will give the ESS Process Instance ID.

Then Click OK to go back and do a Search and await to see it in Succeeded Status

4. Below is highlighted part of the PL/SQL Code which does logging

5. Login to the Database Server and View the Log as explained earlier ie

/tmp/mylog.log ( DB

Machine details given earlier)

Sample Line
[2010-08-30T23:51:23.2547-07:00] [apps] [TRACE:32] [] [hz.plsql.HZ_PARTY_TREE_AUDIT] [APPS_USER_ID:
52B16A28D5463B9B1E5FF00D3D6DE655] [APPS_USER_NAME: FUSION_APPS_CRM_ESS_APPID] [APPS_ROLE_IDS:
B3EAB96327AE3204879490F87AA7FDE258BCB56BC4355120CC9EA37381DCF1D18351DA279922388FE04014905FC432B0D7
369A98F32454E6A6DCDCB75EE57BDEE10F979EBCB2EFCFE1ED96CE5C69BBA3956121F3D18C9FBF3A555E28BC2FCC52E
C3BB8A7FDAEC31041F50CEFBD61CEF2D9DD045252D105EF58538400F878783450242EFF2D1E95AAEF315C9DA374566E35
DB256AD26C8BCDC5CB491CEA52D249ABDC589B8F6E03639BDFAA2E97C4C5D1118BE2813AB6C8ADD2D867836A4ECB67
2993B3D589705CF177BFE67A6279224FE0176AE4B34578054A59875BD0FD8A81D72A1B807135E0A9B69280B9762C8804F63
A25947A1347ED081F00D612A5E57FCEA2F68750E9BA3AB7BD49C0DA820C94D2EAB947088B4BD6EB6F0D5F068D7E3E25F
339C52C6CD304DF4EE84F262736BE6D84EBA785A38FC0FBBD7B4845BF55CBB3DF4B76217EF7BA0CF2B682125B2B19A48
66B76F4F321D0B44800E3D45CFF7B76AE3D452CA2392A137EC4FBFD3B8D03C529A4647E78F257BE3E277501A512D93B60
B0CE7890E7E637C0F2DA9593726AEB50673A0047C8BB9BF1E53F8A2E05EC447232C6FD199B349EF89A14B09337762CA8D
8217E6BE0E3FFF65FB65EF95B029BD547587BA25B8976458543268C0BC563E5519F37E1CFBAD46E00AC73DEE489A02267A
BB367342004964A0E1160F2518EFC0101B11D75F86887D20FD736BECCB4C3FD786001F1ED627C655E3A09E026E024FE8C9
BD4B29089B674B5C23033684D2F5F1D32E4DCCDA0F6818E93A6B512AUTHENTICATED_ROLE_GUIDF7E5BBD754587C92B
5E0D53970E8A3C6BCC60B58F8B6E2CC27ED3228C8C67109F97375E70E0A9294D27E3490E33886CFD7C7A49F2DA7F4CEF
B330FF3ED9E5ACD2AF9EA785763133B6FC1CF986CDE81BA98EBDF7D23B3EE908C7C1C4E3E976DF514D2A3400C7E8F4D
1CE4FE39AB5227543F3143D28B71B4BE956B91F7431AD173E3D0AC262A18967C57E418E29F76B8976C13B16E99BAD61820
A5F7FF59D36BCB91C2B5A1EB07CA03F722687046B7F825835BC13BB678EAF551CD7F5A96A6B919E513BEF19F07A2B569E
75830F6843E715E5E1A67BA9B40374689B5E48657A1416A61B6EFE86126946A9C5C60951B80928FC9B3BFB7872942D5184A
E47811D20BA9946E43D12B9A269F48AFBD17EE006DDE2EF4EA3265C4D52EB57CBA6F4F7F0B3781D84C425592B26EDAB2
630989D87488368F2B00C3AE8B85C40F39AB0846F773E87EC43381B7D78BAD46248007F3307B1BF77520376142A632887D5
22B8BCAA01AAC1CFD52D37CC0A27F52489E3F848BBBE46DA789A579B7C5129308C27D51AE6AFC84D95F8E998FFAF5E0B
13C73F3DE7867D444C846B72919C2EC1639CFD3A5F5826B5AB40B6081CBD6C0C6505696D1681AF88F1DB8CC619A9B9A78
BA5FE4F784EF9D1197423DD61DB28763E2C5B87AEFEEF52BCAE8D108C32F5E0BFF234B2FCFF263E867423C7BB80822FE
80F8A31ABF27CCECA6098CC4BB7A6901BFBD9955DBAE2F2A5BB54D18B46FC5100D9D56F54DCE629C0A0445B6149FD4D
F71AAF2B02CFC7A0199A44C4A1E18D1C7DD6CBA84896AFD2586DFBE780118516090044D1030F13AC14E9D7C987D8620C
DAB10C32D90A8171CCF4A75C655B75C1BA56D7188FF1916DA1D91F7D6C9E5D2082C6C907F8C1467B72747B1B73A3F70F9
5526D44BE15A276E0DDDB0A8A2593AC049C7C8F8375ACB55BD4CA5AE5DBA1975A9F49184479391CC3F3F9F65286407985
FEAB57930B04A6FE673C25B8EA7CA989E165E606386244C290CFF6F80540C2EFF4A86F122B7635F0328AA382D5DD80FA99
9E122BE583F735460B57860EE71AD349DED9A63CA50ECC2A0C058D10990F1386F8605AC72A7BD0C1415F2B8838C96D380
DC61545F1059861BE75E83FAFC709E4EDB662B9DFCECB1C8A9BF86E719017E09D02640CC2A3FB922F8ADFC4407E1E040
38E09FA5EB2ABDF4507ED4CAB5E99283905EB601C9CF9A5923C809AB4F2D25E03922ADF4FF12502C7DA99E0114D491679
2407860E79801E263E786D7D83528F0F58B6ADB8B9ED009A1C193129D055C906D3C752E905C29E9B309976AEDC1A8EF5E

732F3EBDF318FEE4D0E1A6BCB8B0807B] [APPS_TERRITORY: US] [APPS_ENCODED: N] [APPS_DB_INSTANCE: 1]

[APPS_SESSION_ID: 8EEBE0DED8A0D165E04014905FC46FBD] [APPS_SOURCE: hz.plsql.HZ_PARTY_TREE_AUDIT]
[APPS_JOB_REQUEST_ID: 65605] [APPS_JOB_DEFINITION_NAME: PartyHierarchyAudit] [APPS_JOB_PACKAGE_NAME:
oracle/apps/ess/cdm/foundation/parties/] cursor COUNT : 0