Server-side logging allows configuration of a separate log4j logger (EISInteractionLogger) to send output to a separate log file (eis.log) or to the consolidated uep.log.
This feature allows administrators and developers to correlate server side log4j logs to the user request.
The configuration of the logger is managed by directly editing the log4j.properties file. By default, log4j.properties logs in the eis.log at the WARN level.
A synchronization request can have zero or more enterprise information system (EIS) interactions depending on playback policy, uncommitted transactions, and mobile business object (MBO) associations spidering. One logging statement is written for each EIS interaction (both MBO and operations) using the new logger. If the EIS request is successful, logging is done in INFO mode, for example:
INFO: SUCCESS:<Userid>:<MBO name>[.Operation name]:<effective parameter-value pairs>: [Warning message from EIS]
When an EIS request fails, a WARNING is logged, for example:
WARN: FAILED:<Userid>:<MBO name>[.Operation name]:<effective parameter-value pairs>: <Error message from EIS>
An error message from the EIS means that the request failed, while the warning means that the EIS request succeeded but with warnings. A failure log is always accompanied by an error message from the EIS, while a success log may optionally have a warning message. Currently, only the warnings from the SAP EIS are processed.