Locating the security server log files on your system

Lawson Security generates log files on both the security server and the servlet container.

Security server events versus servlet container events

The log file on the security server contains message related to the security server, for example, a message that results from an actions performed using the Lawson Security Administrator.

The log file on the servlet container logs messages related to the runtime, for example, a messages that results from an unsuccessful transaction attempt with a Lawson application.

Default log file names and locations

By default, a security server log file is created on both the security server and on the servlet container in the locations specified below:

On the security server, the name and location of the log file is:

LAWDIR/system/lase_server_1_1.log

where "1" is the number of the JVM that created the file and where "1" is the number of the log file (if multiple log files are used). If multiple log files are not used, the "_1" will be omitted from the file name.

On the servlet container, the name and location of the log file is:

LAWDIR/system/lase_server_0_1.log

where "0" is the number of the JVM that created the file and where "1" is the number of the log file (if multiple log files are used). If multiple log files are not used, the "_1" will be omitted from the file name.

Servlet container log file name and location if logdir JVM property is used

Note: The capability described in this section requires Lawson System Foundation 9.0 or higher.

You can customize the output directory for security log files generated by the servlet container. Customizing this location enables users who do not have access to LAWDIR/system (a location often restricted to the special user "lawson") to view security log files. Customizing might be beneficial in a situation where, for example, SOX compliance requires tight permissions on the LAWDIR/system directory. However, many Lawson customers will find it useful to retain the default location of log files. In this situation, do not perform the configuration described in this section

To customize log file location: After the service pack has been installed, add the Lawson-delivered JVM property, com.lawson.logdir to the Lawson environment variables section of the JVM. (For configuration details, consult your WebSphere documentation.)

When com.lawson.logdir has been configured, your location for log files generated on the servlet container will be different. In addition, all log files, whether they are generated on the security server or the servlet container will have the name lase_server_0.log.

The following explains where log files will be located after the logdir JVM property has been configured.

Type of log file Location
Security server log file: Logs security events

On servlet container: com.lawson.[logdir value]/lase_server_0_1.log

On the machine where Lawson Core Technology (LCT) is installed: LAWDIR/system/lase_server_0_1.log

SSO log file: Logs single sign-on log-in events and exists only if you have implemented tracing

On servlet container: com.lawson.[logdir value]/sso_0.log

On the machine where Lawson Core Technology (LCT) is installed: LAWDIR/system/sso_0.log

Note:  This topic discusses only the security server log file. But, if you use SSO tracing, the logdir JVM property will also apply to the SSO log file.)