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 :
- java -Ddebug=true -jar Launcher.jar
The information will be displayed in standard output.
Note: when the SLA has been configured as a Windows service, this extra JVM argument must be added to the service configuration > Java Options.