You can change the server logging level to capture various levels of system messages for one or more system areas. These system messages can be an indicator of system health.
Logging detailed information consumes more system resources, so SAP recommends that you change the log level only when you suspect a serious problem, or are testing a theory. In most situations, logging errors and warnings is sufficient.
| Component | Description |
|---|---|
| Foundation | Logs system messages for core SAP Mobile Platform Server functionality. |
| Security | Logs system messages that are related to SAP Mobile Platform security. |
| Hybrid Application Management | Logs system messages that relate to managing hybrid apps through the Management Cockpit or API, and client interactions for requesting and downloading updated hybrid apps. |
| B2C Framework | Logs system messages that are related to the Business-to-Consumer framework used for Mobiliser logs. Mobiliser must be enabled to set log levels. |
| B2C Application Services | Logs system messages that are related to the Business-to-Consumer services used for Mobiliser logs. Mobiliser must be enabled to set log levels. |
| Admin | Logs system messages that are related to SAP Mobile Platform administration. |
| Statistics | Logs system messages that are related to usage statistics. |
| Integration Gateway | Logs server-side system messages for plug-ins integrated with SAP Mobile Platform Server, such as data sources (SAP and OData), and third-party systems and protocols (such as SOAP, JDBC, HANA Cloud, and NetWeaver PI). |
| Other | Controls all other loggers not covered here. This is implemented by having a single logger named ROOT in this component, setting the level of the root logger affects any logger that does not fall under one of the loggers have been assigned a level explicitly |
| Agentry user.* | Logs system messages related to Agentry application users. |
| Agentry Server | Logs system messages related to Agentry applications. |
| Agentry Server.BackEnd.* | Logs system messages related to the Agentry back-end data source connections, such as SQL or Java. |
| Agentry WebSockets Front End | Logs system messages related to server/client communication using WebSockets connection type. |
| Agentry WebSockets Front End.connection.* | Logs system messages related to server/client connections. |
| Log Level | Description |
|---|---|
| Path | For tracing execution flow. Used, for example, in the context of entering and leaving a method, looping, and branching operations. |
| Debug | For debugging purposes, includes extensive and low level information. |
| Info | Informational text, used mostly for echoing what has been performed. |
| Warn | The application can recover from the anomaly, and fulfill the task, but requires attention from the developer or operator. |
| Error | The application can recover from the error, but cannot fulfill the task due to the error. |
| Fatal | The application cannot recover from the error, and the severe situation causes fatal termination. |