Logging Files
Your Landmark system includes several files for setting up logging and tracing, and also numerous log files that are created when the system is in operation.
Log Configuration Files
These configuration files are located in %LADIR%\system unless otherwise noted.
| File | Description |
|---|---|
| AGSInfoConfiguration.xml |
For configuration of transaction processing logging. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| AsyncConfiguration.xml |
For configuration of Async processing logging. (Async refers to the background execution processor.) Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| BatchJobConfiguration.xml |
For configuration of batch job logging. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| DataExporterConfiguration.xml |
For configuration of data export logging. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher number include even lower priority messages. |
| DataExporterFactoryConfiguration.xml |
For configuration of logging for the data exporter factory. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| DataImporterConfiguration.xml |
For configuration of data import logging. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| DataImporterFactoryConfiguration.xml |
For configuration of logging for the data importer factory. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| DataViewDeserializerLogConfiguration.xml |
For configuration of data view deserializer logging. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| EffectiveDateProcess.xml |
For configuration of logging for effective date processing. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| GridAdapterLogConfiguration.xml |
For configuration of logging for the Grid adapter program. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| LPSConfiguration.xml |
For configuration of logging for the Lawson Process Server. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| M3InfoConfiguration.xml |
For configuration of logging for the M3 MI socket related processing. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| SecurityLoggerConfiguration.xml |
For configuration of security processing logging. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| SecurityTracerConfiguration.xml |
For configuration of security processing tracing to an XML file (securitytrace.xml). Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| WatchInfoConfiguration.xml |
For configuration of Watch logging to an XML file. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| WASLoggerConfiguration.xml |
For configuration of WebSphere application server logging to an XML file (was.log). Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher number include even lower priority messages. |
| WSInfoConfiguration.xml |
For configuration of WS logging to an XML file. Use this file to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions. For the logging or tracing levels, "1" means fatal error message only, "2" includes error messages, "3" includes warning messages, "4" includes informational messages, and higher numbers include even lower priority messages. |
| dblog.cfg | You can monitor runtime errors (debug) and SQL trace information (trace), and you can collect timed statistics (timestats) data. The administrator configures the content and location of the log files using parameters in the %LACFGDIR%\dblog.cfg file. Each logging function can be configured separately. |
Log Files
These log files are located in %LALOGDIR% unless otherwise noted.
| File | Description |
|---|---|
| AGS.log | The default name of the log file set up through AGSInfoConfiguration.xml. |
| Async.log | The default name of the log file set up through AsyncConfiguration.xml. |
| BatchJob.log | The default name of the log file set up through BatchJobConfiguration.xml. |
| DataExporter.log | The default name of the log file set up through DataExporterConfiguration.xml. |
| DataExporterFactory.log | The default name of the log file set up through DataExporterFactory.xml. |
| DataImporter.log | The default name of the log file set up through DataImporterConfiguration.xml. |
| DataImporterFactory.log | The default name of the log file set up through DataImporterFactoryConfiguration.xml. |
| DataViewDeserializer.log | The default name of the log file set up through DataViewDeserializerLogConfiguration.xml. |
| EffectiveDateProcess.log | The default name of the log file set up through EffectiveDateProcess.xml. |
| GRID_HOME\log\grid-node-Name-Number.log | Logs for each grid node. |
|
GRID_HOME\log\grid-registry-Number.log GRID_HOME\log\grid-agent-Number.log GRID_HOME\log\grid-router-routerName-Number.log |
Log files for the grid agent, grid registry, and grid routers. |
| M3MISocket.log | The default name of the log file set up through M3InfoConfiguration.xml. |
| WATCHES.log | The default name of the log file set up through WatchInfoConfiguration.xml |
| WSClient.log | The default name of the log file set up through WSInfoConfiguration.xml |
| %LADIR%\system\ldsconfig\org.eclipse.update\install.log | The log file for the installation of Eclipse for the Landmark Application Designer. |
| %LADIR%\system\install.log | The log file for the installation of the Landmark Environment. |
| ladb.log | Contains database error messages. |
| lps.log | The default name of the log file set up through LPSConfiguration.xml. |
| was.log | Contains a record of Landmark deployment activities to WebSphere. |
| security.log | One of the standard log files for the security server. Contains security access messages. |
| security_authen.log | Logs startup and shutdown activity of Lase. |
| security_IPaddress_randomNbr.log | Date specific log files for the security server. |
| WebSphere logs | For troubleshooting purposes, you can examine the log files for your WebSphere application servers. See WAS_HOME\profiles\profileName\logs\serverName. |
| Web server logs | See the documentation for your web server for the location of any log files. |