If some part of your BI4 system should stop working, one of the most useful ways to help the SAP support engineers analyze the problem is to capture APS logs. The process is very easy and this blog, plus accompaning video, describes the 8 steps .
1. Log on to the Central Management Console (CMC) using the URL http://<servername>:8080/BOE/CMC
2. From the pull-down list box choose “Servers”. This provides various groupings of BOE services. The Adaptive Processing Server (APS) is a core service and thus is listed in most Service Categories… but the easiest to choose is “Analysis Services”.
3. For “Analysis Services” the APS is the only server. Right-click on “<servername>.AdaptiveProcessingServer” and select “Properties” from the pop-up context menu.
4. The properties that you see will depend on the services you have enabled and may differ from those shown in the video below. Scroll down and look for the “TraceLog Service”.
5. There are 4 levels of verbosity with logging; None, Low, Medium and High. When troubleshooting the Log Level should be set to “High”.
6. Click on “Save & Close”. Logging will start immediately.
7. By default, in Windows the logs are stored in:-
<SystemDrive:>\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects XI 4.0\logging
For Linux the logs are stored in:-
…where $BOBJEDIR is the SAP BusinessObjects Enterprise installation directory.
8. The APS log files are named “aps_<servername>.AdaptiveProcessingServer_trace.<number>.glf” were the largest number is the most recent file. The log file can be opened in any text editor.
[For easier viewing, we recommend you toggle on “Full screen” mode and switch to 720p HD]
If a problem is reproducable, the best way to capture the required logging information is to complete the above to turn on logging, then immediately perform the steps to reproduce the problem, then immediately go back and set the Log Level to None. Then attach the latest “aps_<servername>.AdaptiveProcessingServer_trace.<number>.glf” to your support ticket.
If you do unfortunately have issues, hopefully this blog will help you capture the information you need for the support engineers quickly.