Page tree
Skip to end of metadata
Go to start of metadata


This page gives an overview of how to configure the most important log files used for  troubleshooting SAP Strategy management issues.


There are many configuration files that can help us to identify the root cause of problems encountered with strategy management.

 1.  Activate the log for  End to End communication


To enable end-to-end tracing, it is mandatory to change the file LSSERVER.ini and add the parameter NCSTRACE and set it to 1 as follow : NCSTRACE=1

After Enabling the log, the generated files are <uuid>.GLF.  These files ate generated under the \<install-dir>\SAP BusinessObjects\Strategy Management\ApplicationServer\LOGS directory.

 2. Activate the log for  SAP SM Listener service

The SAP SM Listener log file contains all the connection information.  To activate the log for SAP SM Listener, it is mandatory to follow the steps bellow


1. Access to Start --> Run --> RegEdit.

2. Search for the  registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lssagent.

3. Locate the ImagePath key and modify the value. At the end of the path for the lssagent.exe file, add the following: trace 2 logfile <logfile-path>.

4. restart the SAP SM Listener service to begin logging. 


3. Activate the log for  the Application Server sessions


The tracing is enabled by turning tracing on or off.  These steps should be followed to activate the logs :

1. Start the Tools utility at this URL: http://<nw_server>:<port>/strategy/tools
2. Select Application Tracing, and then select Enable for the PAS Trace setting.
3. Access to the URL http://<nw_server>:<port>/strategy/tools
4. Select JPIP Session Monitor and then select Restart JPIP.

After activating the tracing, three files  are generated provide different levels of information. The trace files are named by the username and model you are accessing as follows: 

 <modelname><app_server_user><unique_stamp>_time.txt  --> Contains all commands and the response times to process the commands in the same session.

<modelname><app_server_user><unique_stamp>_both.txt  -->  Contains all commands and the results/output from those commands.

<modelname><app_server_user><unique_stamp>_cmd.txt --> Contains all commands issued by the application.

The generated trace files can be opened  by a text editor or by using the PAS Query tool.

By the text Editor

1. Navigate to the\<install-dir>\ApplicationServer\home directory on the system where Application Server is installed.

2.Open the trace files in a text editor.

By the PAS Query tool

1.Access the URL http://<nw_server>:<port>/strategy/tools

2.  choose PAS Query.

3. In the Context dropdown list, select the model connection to work with.

4.  At the end of the context string in the Address box, enter: DQL=TYPE document <modelname><app_server_user><unique_stamp>_both.txt


Related Content