SLFJ Logging
BigMemory Go uses the SLF4J logging facade, so you can plug in your own logging framework. The following information pertains to Ehcache logging. For information about SLF4J in general, refer to the
SLF4J website.
With SLF4J, users must choose a concrete logging implementation at deploy time. The options include Maven and the download kit.
Note:
In respect of considerations concerning EU General Data Protection Regulation (GDPR), be aware that in cases of incorrect login procedure or other error scenarios, LDAP username and IP address may be logged in the tmc-security log file. Amongst other events, such data may be collected for reasons of configuring messages based on such logs. LOG4J offers possibilities for log-purging and log-retention, which may offer useful strategies to avoid unwanted loss or exposure of sensitive data possibly conflicting with regulations.
Concrete Logging Implementation use in Maven
The maven dependency declarations are reproduced here for convenience. Add one of these to your Maven POM.
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-jdk14</artifactId>
<version>1.5.8</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
<version>1.5.8</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-simple</artifactId>
<version>1.5.8</version>
</dependency>
Concrete Logging Implementation use in the Download Kit
The slf4j-api jar is in the kit along with the
BigMemory Go jars so that, if the app does not already use SLF4J, you have everything you need. Additional concrete logging implementations can be downloaded from
SLF4J website.