environment.properties

File location: %LACFGDIR%\environment.properties

The environment.properties file provides support for and configuration of the application servers. Most of the properties in this Java-formatted file are automatically established by the installation process for either the Landmark technology package or a Landmark application package. Some of the properties currently have no external management user interface and can only be managed through manual editing of the file.

Many of the properties in this file are valid for only one of the supported application servers. This is indicated in the description.


The following values apply to any application server deployment.
`J2EE_SERVER=servertype`
	`WS85` The application server specification, as defined by the Landmark installation process.
`com.lawson.mail.transport.protocol=protocol`
	The mail transport protocol to use, as defined by the Landmark installation process. The default is `SMTP`.
`com.lawson.mail.smtp.host=url`
	The host name of the mail transport server, as defined by the Landmark installation process.
`com.lawson.mail.mime.address.strict= TRUE\|FALSE`
	The mail protocol usage flag, as defined by the Landmark installation process. The default is `FALSE`.
`com.lawson.mail.debug=TRUE\|FALSE`
	The Mail processing debug support flag, as defined by the Landmark installation process. The default is `FALSE`.
`com.lawson.mail.store.protocol=protocol`
	The store protocol to use when storing e-mails sent from Landmark, such as `imap` for Internet Message Access Protocol (IMAP).
`com.lawson.mail.protocol.host=host`
	The host for storing the e-mails for a given protocol.
The following values apply to WebSphere deployment.
`com.lawson.was.home=path`
	The installation directory for the WebSphere install, as defined by the Landmark installation process. This is also the value provided during the original IBM WebSphere installation. Commonly the same value would be set as the environment variable %WAS_HOME%. This environment variable can be conveniently used in other scripted operations. The default is %WAS_HOME%.
`com.lawson.was.host=hostname`
	The host name for the WebSphere deployment manager, as defined by the Landmark installation process. The default is localhost.
`com.lawson.was.port=portNbr`
	The deployment manager SOAP service port, as defined by the Landmark installation process. Along with the com.lawson.was.host value, this value provides the details for the WebSphere deployment manager SOAP-based JMX service connection. This connection is used to communicate with the deployment manager process during Environment technology deployment and during configuration and application deployment. The default is 8879.
`com.lawson.was.soap.timeout=numberOfSeconds`
	The SOAP request timeout value in seconds (0 is no timeout). If unreliable network communications lead to lost request responses, then setting a value here will cause the deployment client process to force a termination. If too short a value is set, it might not be possible to complete a deployment successfully on a slower system due to premature termination of JMX request processing. The default is 0.
`com.lawson.was.sync-delay=numberOfSeconds`
	Setting this to 120 seconds or greater can enable you to avoid error message 105 occurrences during installation.
`com.lawson.was.profile-name=name`
	The profile name of the management process profile in WebSphere. The name must be defined as a profile within the directory path provided in `com.lawson.was.home`. When a full IBM WebSphere ND product is used this would commonly be the profile name of the deployment manager profile. The default is no entry.
`com.lawson.was.application-server=nodename`
	The server cluster defined in the deployment manager cell or the managed or base application server node in the application server, as defined by the Landmark installation process. To use a cluster name the installation must be licensed to full clustering support. The entity identified here is the management entity used to provide servlet container services to the Landmark installation. The default is no entry.
`com.lawson.was.dmgr.jvm-init-mem=heapsize`
	Optional. The initial (minimum) heap setting for the deployment manager process, in MB. This parameter must be set by manual entry in this file. This setting is used to configure the -Xms and -Xmx JVM parameters for the deployment manager process. If this entry exists, the value will be used to update the appropriate IBM WebSphere configuration settings. If no entry exists, the deployment manager process will be configured to a default setting of `com.lawson.was.dmgr.jvm-init-mem=128` and `com.lawson.was.dmgr.jvm-max-mem=512`. This provides an initial and minimum setting of 128MB and a maximum setting of 512MB.
`com.lawson.was.dmgr.jvm-max-mem=heapsize`
	Optional. The maximum heap setting for deployment manager process (when running managed deployment), in MB. This parameter must be set by manual entry in this file. This setting is used to configure the -Xms and -Xmx JVM parameters for the deployment manager process. If this entry exists, the value will be used to update the appropriate IBM WebSphere configuration settings. If no entry exists, the deployment manager process will be configured to a default setting of `com.lawson.was.dmgr.jvm-init-mem=128` and `com.lawson.was.dmgr.jvm-max-mem=512`. This provides an initial and minimum setting of 128MB and a maximum setting of 512MB.
`com.lawson.was.servername.jvm-init-mem=heapsize`
	Optional. The initial (minimum) heap setting for a named server process, in MB. This parameter must be set by manual entry in this file. This setting is used to configure the -Xms and -Xmx JVM parameters for the named server process. If this entry exists, the value will be used to update the appropriate IBM WebSphere configuration settings. If no entry exists, the server processes will be configured to a default setting of `com.lawson.was.servername.jvm-init-mem=256` and `com.lawson.was.servername.jvm-max-mem=1024`. This provides an initial and minimum setting of 256MB and a maximum setting of 1024MB.
`com.lawson.was.servername.jvm-max-mem=heapsize`
	Optional The maximum heap setting for named server process, in MB. This parameter must be set by manual entry in this file. This setting is used to configure the -Xms and -Xmx JVM parameters for the named server process. If this entry exists, the value will be used to update the appropriate IBM WebSphere configuration settings. If no entry exists, the server processes will be configured to a default setting of `com.lawson.was.servername.jvm-init-mem=256` and `com.lawson.was.servername.jvm-max-mem=1024`. This provides an initial and minimum setting of 256MB and a maximum setting of 1024MB.
`com.lawson.was.vhost.dataarea-enterpriseappname=virtualhost`
	The default virtual host to map WAR modules to for the named application, as defined by the application installation process. The default is no entry.
`com.lawson.was.vhost.dataarea-enterpriseappname.webappname=virtualhost`
	The virtual host to map the specified web application module in the named application to, as defined by the application installation process. The default is no entry.
`com.lawson.was.opfConnectionPool.maxConnections=xxx`
	The maximum number of connections allowed in the pool. This parameter must be set by manual entry in this file. This property controls the maximum number of database connections that can be open at the same time. Database connections are pooled and reused based upon the combination of data area name and user (actor) name, so this number needs to be large enough to support the expected maximum concurrently active user / data area combinations. Typically a user will have two data area connections, one to the system data area and one to the application data area for the application accessed, so a useful rule of thumb is to configure two times the expected number of active users plus some reserve. The default is 20.
`com.lawson.was.opfConnectionPool.minConnectons=xxx`
	The minimum number of connections retained in the pool. This parameter must be set by manual entry in this file. Unused database connections will be automatically closed and removed after a configured idle timeout. This helps to make the system resource usage dynamically adapt to processing load. This property sets a threshold below which data base connections will no longer be automatically closed. If the site load patterns make it advantageous to use system resources to provide quicker user response times even for infrequent user access, then setting this property will hold database connections open for faster use. The default is 0.
`com.lawson.was.opfConnectionPool.reapTime=xxx`
	The pool reap time in IBM WebSphere (seconds). This parameter must be set by manual entry in this file. This property controls how frequently the connection pool management functions are executed. It should be defined to a shorter time period than the other timeout values in order to ensure that the management processing completes correctly. Setting this to too short an interval will increase the overhead CPU usage of WebSphere with little useful benefit. The default is 60 seconds.
`com.lawson.was.opfConnectionPool.connectionTimeout=xxx`
	The pool connection time out in IBM WebSphere (seconds). This parameter must be set by manual entry in this file. If a user processing request enters the system and needs a database connection at a time when the maximum number of database connections are already in use, the processing request will be queued and wait for an available database connection. This property sets a maximum time for the wait period. If no database connection comes available within this time, the processing request will be terminated with an error. The default is 300 seconds.
`com.lawson.was.opfConnectionPool.unusedTimeout=xxx`
	The pool unused time out in IBM WebSphere (seconds). This parameter must be set by manual entry in this file. This property controls the amount of time an idle database connection will be kept open in the pool in the hope of reuse. Increasing the value will tend to use more resources but provide better response times for less frequent processing requests. Decreasing the value will free up resources for other users faster but provide slightly slower response for less frequent processing requests. The default is 300 seconds.
`com.lawson.was.opfConnectionPool.agedTimeout=xxx`
	The aged connection timeout before a physical connection is force-removed (seconds). This parameter must be set by manual entry in this file. This property controls whether database connections will be forced to close after some set lifetime, regardless of whether they are being used or not. The only exception to forced closing of the database connection is if it is currently active within a transaction, in which case it will be force closed when the transaction finalizes. For Lawson usage this should normally be set to 0, so that database connection cleanup is only done according to the unused timeout of idle connections. Other values risk confusion between the connection pool management and Lawson database record caching mechanisms. The default is 0 seconds.
`com.lawson.was.opfConnectionPool.purgePolicy=xxx`
	The connection pool purge policy for connection errors. This parameter must be set by manual entry in this file. This property controls what clean up is done when a connection encounters an error with back-end processing. Valid values are "EntirePool" or "FailingConnectionOnly." EntirePool means that all connections in the pool are closed if any connection throws an error exception. FailingConnectionOnly means that only the connection that encountered the failure is closed. The default setting for Lawson means that only the connection in error is closed. The default is `FailingConnectionOnly`.
`com.lawson.was.webserver.dataarea-enterpriseapp.module=node:webserver`
	This parameter describes the module mapping for each module in WebSphere. Each value contains the name of the WebSphere node and the name of the web server. A parameter's value can contain more than one node/web server pair, separated by commas. The values are used when you deploy updates in order to set up the module mapping.
The following values apply to Async Framework configuration.
`async.framework.active=true\|false`
	A global switch for the Async Framework. When this parameter is `true`, the other Async parameters can be set to `false` to turn off individual items. When this parameter is `false`, the other Async parameter can be set to `true` to turn on individual items. In contrast to earlier release of Landmark, the Async Framework provides the only background processing system for Landmark. Setting this parameter to `false` will result potentially in a loss of functionality. The default is `true`.
`async.framework.setaction.active=true\|false`
	When this parameter is `true`, the system will use the Async Framework for Set Action execution. The default is the value from `async.framework.active`.
`async.framework.effectivedate.active=true\|false`
	When this parameter is `true`, the system will use the Async Framework for Effective Date execution. The default is the value from `async.framework.active`.
`async.framework.execjob.active=true\|false`
	When this parameter is `true`, the system will use the Async Framework for Batch execution. The default is the value from `async.framework.active`.
`async.framework.process.requests.delay.ms=int`
	The requests.delay property is used to determine how long to wait until setting up ActionTriggers and processing the Queues those triggers reside in. The default is 5000 milliseconds.
`async.framework.process.consistency.delay.ms=int`
	The consistency check is used to sweep the Async system for orphaned triggers and clean up if needed. The default is 30000 milliseconds.
`async.framework.ags.active=true\|false`
	When this parameter is `true`, the system will use the Async Framework for S3 Lawson Application Transaction execution. The default is the value from `async.framework.active`.
`async.framework.email.active=true\|false`
	When this parameter is `true`, the system will use the Async Framework for E-mail execution. The default is the value from `async.framework.active`.
`com.lawson.async.queue.dataarea=true\|false`
	When this parameter is `true`, the system creates separate default, S3 transaction, and e-mail queues for each data area. The default is `false`.
The following values apply to PDF font usage
`com.lawson.pdf.unicode.font`
	By default, server-side PDF generation uses the arialunicodems font. If this is not available or is not desired, you can change the font with this property. The font is embedded in the PDF if allowed. If embedding is not allowed due to licensing restrictions, a different font must be used.
`com.lawson.pdf.font.directory`
	Optionally specifies the directory where the font specified in `com.lawson.pdf.unicode.font` resides. This is only needed if the font is not in one of the standard directories the PDF generator looks in. Standard font directories are: c:\windows\fonts (does not recurse) c:\winnt\fonts (does not recurse) d:\windows\fonts (does not recurse) d:\winnt\fonts (does not recurse)