Infor Lawson configuration, log, and audit files
This section describes the configuration, property, touch, log, and audit files that are a part of the Infor Lawson system. In addition, some third-party product files are listed as well if those files have Infor Lawson-specific entries. These files are located in %LAWDIR%\system unless noted otherwise.
Configuration Files
| File | Component or Product | Description |
|---|---|---|
| univ.cfg | Infor Lawson Environment | Contains parameters used by the Environment. Most of these parameters are for Environment groups, and the display of programs in LID. |
| latm.cfg | Infor Lawson Application Server | Contains parameters that affect the running of the application server and application programs. For example, you may need to adjust the time out settings and the minimum and maximum times programs can stay open. |
| ladb.cfg | Infor Lawson Database Server | Contains parameters that affect the running of the database server (ladb). If you have a large system, you may need to change these settings as well as the related kernel parameters. The ladb.cfg also contains parameters for timed statistics, which enable you to monitor database performance. |
| lajs.cfg | Infor Lawson Job Server | Contains parameters that affect the running of the batch server (lajs). Several parameters affect the global behavior of the job server, such as timeout settings, the frequency with which the job queue is checked, and the maximum number of jobs that can be running. Other parameters affect the report files, including the permissions for the files, whether XML versions are created, and what date format is used in CSV files. |
| ladebug.cfg | Infor Lawson Debug Server | Contains parameters that control the debug server (ladebug). These include parameters to turn debugging on and to control the ports used for debugging. |
| laserv.cfg | Infor Lawson Services | Contains entries for the Infor Lawson servers that should be started when the Environment service is started. For example, typically it contains entries for ladb, lainetd, latm, lajs, and perhaps ladebug. |
| lainetd.cfg | Infor Lawson Internet Service | Contains information needed for the login process for the Infor Lawson Interface Desktop (LID). Generally, you do not need to edit it. |
| install.cfg | Infor Lawson Environment installation | Stores the settings used for the Infor Lawson Core Technology installation. These settings are then available if you need to reinstall. |
| queue.cfg | Infor Lawson Compile Queue Server | Stores settings used by the compile queue server, such as maximum number of concurrent compile jobs. |
| rtllist.cfg | Right-to-left system file |
Stores language and dialect names. It is recommended to use the enablertl and locdef utilities and not edit this file directly.
|
| iosconfig.xml | Internet Object Services | Stores the location of the persistent data directory and the Lawson Portal help files directory, and settings for data area database driver performance. It also stores the names of the broker and agent classes for the IOS services. You should not change these names. |
| portalconfig.xml | Infor Lawson user interface (portal) |
Stores Lawson Portal configuration values. Most of these values are set by the Lawson Portal administrator through the Lawson Portal Roles Manager. Located in /lawson/portal within the document root directory. |
| perms.cfg | Permissions for Environment programs and directories | The perms.cfg file is created by the permsmaint utility to store permissions information about Environment programs and directories. After it is created, you can edit the permission settings and then run permsmaint in order to apply the settings. |
| ladirs.cfg | Permissions for Infor Lawson application programs and directories | The ladirs.cfg file is created by the permsmaint utility to store permissions information about application programs and directories. After it is created, you can edit the permission settings and then run permsmaint in order to apply the settings. |
| NONSTDLIB.cfg | Infor Lawson qcompile program | Contains the names of any procedure libraries that contain code that does not match Infor Lawson standards. When you run the qcompile program, it will process the listed non-standard libraries as text. The NONSTDLIB.cfg file is located in %LAWDIR%\ProductLine. |
| appservercache.xml | Internet Object Services | The appservercache.xml file contains settings used for the caching of secured fields and tabs. In general, you do not need to change these settings. |
| lsservice.properties | Infor Security | Contains basic system and port settings needed by the Info security server. |
| SecurityLoggerConfiguration.xml | Infor Security | Use to adjust the log and trace setting, set the name of the log file, and enable or disable logging functions for security logging. |
| security_status.log | Infor Security | Logs changes when security within the LSF environment is turned on or turned off. The changes are tracked when the action is performed using the LSA tool, ISS web page, or lsconfig command. The log is written to even if your security auditing is turned off. |
| ls_logging.properties | Infor Security | Allows you to control the level of detail in the Infor Security log file, and also to set up multiple log files (for example, different log files for different types of Infor Security activity). Changes do not take affect until the security server is stopped and started. |
| sso_tracing.properties | Single Sign-On | Use to turn single sign-on tracing on and off,and to set the types of services that will be traced. The options for services are FSSO, BSSO, API, and SSSO. |
| RMApiInit.properties | Resource Management | Contains settings used by Resource Management, especially settings that control the relationship between Resource Management and your LDAP. For example, you can control whether Resource Management can change any data in LDAP that is shared between Infor Lawson and systems outside of Infor Lawson. |
| server_model_LDAS. properties | Process Server | Stores a list of the abstract interfaces or classes used by Process Server for data access through the Thin DB API service. You should not edit this file. |
|
Database driver configuration files (IBM, ORACLE, MICROSOFT) |
Infor Lawson Database Server | Contains parameters needed by the Database server and drivers. There is a separate database driver configuration file for each data area, including GEN, LOGAN, and your application product line data areas. The database driver configuration files are located within %LAWDIR% in the directories for the data areas. |
| rpt.cfg | Infor Lawson reports | Contains report configuration options that apply to all report programs in your system. You can also create addtional report configuration files that apply to all programs within a product line, all programs within a system code, or only an individual program. The rpt.cfg file is located in %LAWDIR%\system. See Infor Lawson Administration: Jobs and Reports for the location of additional report configuration files. |
| bpm.properties | Process Server | Contains settings for basic server, host, and ports for Process Server, as well as thread pool size, tracing, and logging options for the Process Server servers. |
| pfserv.cfg | Process Server | Contains classpath and start/stop information needed by the Process Server servers. |
| webrpt.cfg | Internet Object Services/Lawson Reports | Contains parameter used by IOS WebRpt application to enable printing by privileged user for batch jobs. |
| Process Server connector configuration files | Process Server | These files include FileClient.cfg, FourGLClient.cfg, and ScanFileClient.cfg. They contain the configuration settings for the FileClient, FourGLClient, and ScanFileClient connectors, including server, port, login, and flow information as well as settings unique to each connector. |
Touch Files
| File | Component or Product | Description |
|---|---|---|
| BANNERPGBRK | Lawson reports |
You can force a banner page break when report files are printed with the presence of the BANNERPGBRK file. Located in %LAWDIR%\ProductlineName. |
| CRYSTAL | Lawson reports |
This touch file in the %WEBDIR%\lawson\xtra directory on the application server allows the creation of additional XML reports for Lawson Business Intelligence in the print file directory. OLE DB Object Services and Crystal Reports use the additional ADO reports that are created when this touch file is in place. This touch file applies to all reports, so the additional ADO reports will be created, even though you may not be using a specific report as a data source for your OLE DB/Crystal Reports. If the XMLREPORTS parameter in lajs.cfg is set to OFF and the CRYSTAL touch file exists, the XML and ADO files are not created until the user attempts to access the report. If the XMLREPORTS parameter in lajs.cfg is set to ON and the CRYSTAL touch file exists, the XML and ADO files are created when the report job runs. |
| CSV_DFLT_NEW_EXT | Lawson reports |
This touch file sets the default extraction method used to create CSV files when you create CSV files through lashow. The existence of this touch file means that the extraction method will be the same as that used to create CSV files through the Lawson Portal Both extraction methods (the initial default for lashow and the default for the Lawson Portal) include the report groups that are found between the top of the page and the first occurrence of the selected group. The lashow method writes a line to the CSV file only when the selected group is encountered in the report. The Lawson Portal method will write a line whenever a second occurrence of the report group is encountered. |
| CSV_DFLT_UPGRPS_KEYS | Lawson reports | This touch file sets the default for the Extract Report Values from Upper Groups setting to Key Fields Only rather than All Fields. This is useful if the CSV output contains columns you do not need. |
| ARCHIVEOFF | Lawson reports |
This touch file turns off the creation of report map archive files. Report map archive files are copies of the report maps. They include a reference to the timestamp on report files, so that when you want to drill on the data in a print file or want to create a CSV file from a print file, the system has a version of the report map that matches the print file. If you turn off this feature and then recompile report programs, you may not be able to use the Drill Around or CSV file creation features for older print files. It is located in %LAWDIR%\productline\rptmap\default\archive. |
| DTLSECURITY | Lawson security | The presence of this touch file causes Lawson user security to check the detail lines of a detail form for data security restrictions (company/process level security). |
| PRINTRCVOFF | Lawson reports |
This touch file turns off the functionality of the PRINTRCCVON touch file. The default is OFF, so you only need to use this touch file if you have used PRINTRCVON at a higher level in the product line hierarchy. Located in %LAWDIR%\ProductlineName or %LAWDIR%\ProductlineName\SystemCode, depending on whether you want to affect all reports in the product line or all reports produced by programs within one system code. |
| PRINTRCVON | Lawson reports |
You can use the PRINTRCVON file to generate print and work file recovery routines in the program shell at compile time. This automatically enables the print and work file recovery feature the next time the program runs after compiling. Located in %LAWDIR%\ProductlineName or %LAWDIR%\ProductlineName\SystemCode, depending on whether you want to affect all reports in the product line or all reports produced by programs within one system code. |
| QUEUEFSTREAD | Lawson Environment | If you create this touch file, lapm will not perform version checking on the Lawson Interface Desktop. This eliminates an error that prevents you from logging into LID. |
| XTRAOFF | The XTRAOFF touch file in the %WEBDIR%\lawson\xtra directory on the application server prevents the creation of all XML reports. Lawson recommends this configuration if you only use the Lawson Interface Desktop (LID) and do not use the Lawson Portal or Lawson Business Intelligence. |
Logging and Auditing Files
| File | Component or Product | Description |
|---|---|---|
| ios_logging.xml and ios_logging.properties | Internet Object Services | Allows you to control the level of detail in the ios log file, and also to set up multiple log files (for example, different log files for different types of IOS activity). |
| ios.log | Internet Object Services | The default log file for Internet Object Services. Its contents are determined by the settings in the ios_logging.properties file. |
| lase.log | Infor Security | Contains a record of startups and shutdowns of the security server that are triggered by the C API. |
| lase_server_n.log | Infor Security | Contains logging event information, including which properties file was used to control the current logging configuration as well as the detail the ls_logging.properties file indicates should be logged. |
| SSO_variable.log | Single Sign-On | Contains information related to Single Sign-On activity. Its contents are determined by the settings in the sso_tracing.properties file. |
| security.log and security_authen.log | Infor Security | The default names for the logging files whose contents are configured through the SecurityLoggerConfiguration.xml file. |
| queue.log | Compile Queue Server | Stores information about the stopping and starting of the compile queue server as well as any error messages from compiles. |
| install logs | Installation | When you install the Infor Lawson Core Technology, the install program creates an install log, detailing all activity of the installation, including errors. These files are named install_nnnnnnnnn.log and are stored in %LAWDIR%\system or maybe your install directory. Application installs may have different install log. |
| rpt.log | Infor Lawson reports | If report logging is turned on through the report options configuration files, this log file contains report map exception events. |
| webrpt.log | Infor Lawson reports run through the Lawson Portal |
If this log file exists, logging information for the webrpt program is stored in it. The webrpt program is called when users view or print reports in the Lawson Portal. This file is in %GENDIR%\cgi-bin. |
| Process Server log files | Process Server | These include em.out, em.log, pflow.out, pflow.log, wfs.log, pfserver.log, pfschd.log and pfrmi.out. They contain start, stop, and error information for the Process Server. You can view the .out files with a text editor. You must view the .log files through the Event Management Console. |
| Process Server trace files | Process Server | These include em.trc, pfserver.trc, and wfs.trc. They provide detailed information about the Process Server activity. You must view the trace files through the Event Management Console. |
| ProcessFlow workunit activity logs | Process Server |
These include pfengine.log, .wulog files, and .plog files.The .wulog files contain information on individual workunit activity, and the .plog files contain information on flow activity by workunit. The pfengine.log combines all of the information from these files. These files are located in %LAWDIR%\bpm\wflog. |
| Process Server workunit error logs | Process Server |
These include pfengine.err, .wuerr files, and .perr files. The .wuer files contain errors on individual workunits, and the .perr files contain errors on flow activity by workunit. The pfengine.err combines all of the information from these files. These files are located in %LAWDIR%\bpm\wflog. |
| Process Server connector log files | Process Server | These files include FileClient.log, FourGLClient.log, and ScanFileClient.log. They log any activity for the FileClient, FourGLClient, and ScanFileClient connectors. |
| Process Server connector error files | Process Server | These files include FileClient.err, FourGLClient.err, and ScanFileClient.err. They contain error information for the FileClient, FourGLClient, and ScanFileClient connectors. |
| job logs | Each running of a job creates a job log. These are stored in %LAWDIR%\system\joblog. | |
| audit_variable.audit | Infor Security |
Archive files for Infor Security auditing information. The actual file name is built from the criteria you select when creating the archive. If you decide to archive all records, the file name will be audit_all.audit. If you decide to archive selected records, the file name will be similar to the following: audit_user1_prior20050405_RUNTIME.audit. For more information, see Infor Lawson Administration: Resources and Security. |
| ladebug.log | Infor Lawson Debug Server | Contains information related to the running of the debug server. |
Third-Party Files
This is a partial listing of files used by third-party products that are needed by the Infor Lawson system.
| File | Component or Product | Description |
|---|---|---|
| java.security | Java SDK and BouncyCastle |
Contains an entry for the BouncyCastle security policy used by Single Sign-On. This file is located at %LAW_JAVA_HOME%\jre\lib\security. |
| web server log files | Web servers | Varies by web server. |
| vertex.cfg | Vertex | The vertext.cfg file stores the configuration settings for the Vertex Sales Tax Q Series software. |
| services |
Windows |
Contains entries for each service, linking it to a port and protocol. For Infor Lawson, it contains the lalogin service for the Infor Lawson Interface Desktop. It is located in the Windows\system32\drivers\etc directory. |