Get SLA debug information

Get SLA debug information

Generalities

The Semantic Layer Agent (SLA) is a component of 360Suite that bridges SAP SL SDK with our processes.
It is brought by two artifacts: Laucher.jar and SemanticLayerAgent-{version}.jar. 
These two artifacts are mandatory to ensure you are running the SLA on a 32bit JVM for BI 4.1 and 4.2 and on a 64bit JVM for BI 4.3 and later.

Log information

When running a task that needs the SLA, if it ends up with a warning log, the root cause will be available in {SLA-DIR}/logs/agent.log.
On a standard installation on Windows, it can be found in C:\Program Files (x86)\360.Suite{BIVersion}\SLA\log\agent.log.

Additional debug information

You can get additional debug information such as the JVM that is running the SLA by addind the -Ddebug=true JVM argument when you start the SLA.
Example : 
  1. java -Ddebug=true -jar Launcher.jar
The information will be displayed in standard output.
Info
Note: when the SLA has been configured as a Windows service, this extra JVM argument must be added to the service configuration > Java Options.

    • Related Articles

    • SLA Unable to Connect to CMS (FWM 01009)

      Overview When using 360Suite Semantic Layer Agent (SLA), the task fails with a RemoteException indicating a communication error with the CMS. This issue typically occurs after installing SLA on a Windows host and configuring RMI settings, even when ...

    • Database Debug Mode (on Microsoft Windows)

      Condition Database issues arise and detailed logs are needed for debugging and fixing problems. Solution Cause The database may be corrupted or other technical issues arise. Remedy 1. Open a Windows command line or PowerShell prompt. 2. Access the ...

    • SLA Installer Fails on 64-Bit Systems When Using BOBJ 4.2 (32-Bit)

      Symptoms Issue When installing the SLA (Semantic Layer Agent) on a 64-bit Windows system that has SAP BusinessObjects 4.2 (32-bit) installed, the SLA service may fail to start. This issue is due to an architecture mismatch: the SLA installer expects ...

    • Converting Oracle based MSU UNX to SSU fails with "driver could not be loaded error"

      Symptom When you launch a MSU to SSU conversion on a universe based on an Oracle ODBC connection. On WebPatform 2023.1.1 : The task ends in success When you retrieve the - Converted universe, you have an empty Data foundation On WebPlatform 2023.2 ...

    • FAQ: Migrate to the new 360Eyes for SAP BusinessObjects Audit Job

      Context Version 2025.2 introduced changes to the behavior of 360Eyes Jobs. Previously, we had a list of jobs consisting of: - CMS - Webi - Crystal - Universe - IA & Other Each job had an option to extract audit information. This could sometimes lead ...