System management yfs.properties
Use the customer_overrides.properties file
to override properties in the System Management category of yfs.properties.
The following table contains the System Management yfs.properties and descriptions.
| Property | Values | Description |
|---|---|---|
| System Management | ||
| rmi.portrange | <minport> - <maxport> Default = 0 |
In a deployment with servers in two different network zones,
the firewall between them must be configured to allow Remote Method
Invocation (RMI) communication between them. When you specify a port
range, a single, unused port in that range will be selected for use.
You can specify multiple ranges separated by a comma. If an open port
cannot be found, an exception will occur. If you specify 0, any available
port in the RMI range can be selected for use. Do not specify the
0-1023 range or the 1024-49151 range. Example: rmi.portrange=49152-49162, 49170, 49180-49190 |
| The next four properties are for the Health Monitor. The health monitor will raise the configured alerts when the api/appServer response time or the agent Pending Job count crosses the threshold. | ||
| yantra.hm.api.threshold | <number of milliseconds> Default = 20000 milliseconds |
api threshold in milliseconds, this is the system default value used for average response time for appservers. If this value is not specified 20000 milliseconds will be assumed. |
| yantra.hm.agent.threshold | <job size> Default = 10000 |
System default value used for the pending jobs size for agents. If this value is not specified, 10000 will be assumed. |
| yantra.hm.appserver.threshold | <number of milliseconds> Default = 8000 milliseconds |
Appserver threshold in milliseconds, this is the system default value used for average response time for api's/services. If this value is not specified 8000 milliseconds will be assumed. |
| yantra.hm.purge.interval | <number of days> Default = 30 days |
Health Monitor purge interval, this is the system default value used for purging heartbeat and snapshot records. if this value is not specified 30 days purge interval is assumed. |
| yantra.statistics.collect | Valid values = n, N, y, or Y Default = N |
Property to turn on Statistics logging. Example: yantra.statistics.collect=Y |
| yantra.statistics.persist.interval | Valid values for minutes (M/m) = 1, 2, 3, 4, 5, 6, 10, 12,
15, 20, or 30 Valid values for hours (H/h) = 1, 2, 3, 4, 6, 8, or 12 |
Property to determine statistics logging time interval. Format
of the property is Xm or Xh where X is an integer between 1 and 60
and M/m for minutes or H/h for hours. If any unrecognized value or unit is specified, it will default to 10m (minutes). If a value of 61m or greater is specified, it will be reduced to 60m. If a value of 25h or greater is specified, it will be reduced to 24h. If the units are minutes (M/m), then the value is rounded up or down to the nearest equal divisor of 60 minutes. If the units are hours (H/h), then the value is rounded up or down to the nearest equal divisor of 24 hours. Example: yantra.statistics.persist.interval=10m |
| yantra.shutdown.wait.timeout | <number of milliseconds> Default = 0 |
Set this property to specify the maximum time
that the shutdown process should wait for consumer transactions to
finish before proceeding with the shutdown. If a consumer transaction
does not finish before the specified time, the shutdown will proceed,
issuing a rollback on the session/message. The default value for this property is zero (0), which maps to an indefinite wait. Example: yantra.shutdown.wait.timeout=30 |
| api.configuration.dump.mode | Valid values = ON_ERROR, ON_VERBOSE, ON_ERROR_AND_VERBOSE,
or NONE Default = ON_VERBOSE |
ON_ERROR - If an error occurs during the execution
of an API, then irrespective of the tracing level that is configured
for the API in System management Console, certain data such as API
input, error details, configuration data, and select master data that
was accessed during the API execution, is dumped in the form of an
XML into a separate log file. The default location of the log file
is in the ffdc directory present inside the log directory. ON_VERBOSE - If an API is run with VERBOSE level of tracing enabled in System Management Console, then at the end of the successful execution of the API, certain data such as API input, configuration, and select master data that was accessed during the API execution, is dumped in the form of an XML into the standard log file. ON_VERBOSE is the default value for the api.configuration.dump.mode property. ON_ERROR_AND_VERBOSE - This level provides the features of both ON_ERROR and ON_VERBOSE modes. NONE - This level does not collect any configuration or master data. |
| systemlogger.rotatelogs | Flag indicating whether to rotate the system log after it has
reached its maximum size. If this flag is set to false the below two
attributes will be ignored and logger will continue to write in just
one log file. Set this flag to true to let the below properties take
effect. Example: true |
|
| systemlogger.maxlogsize | Maximum number of write operations after which the log messages
will be logged in a new log file. Example: 100000 |
|
| systemlogger.maxnumlogs | Maximum number of log files after which the oldest log file
should be deleted. If the value of this flag is set 10, the 11th log
file is created and the first log file will be removed. Example: 10 |
|
| yfs.heartbeat.refresh.interval | Valid values for minutes (M/m) = 1, 2, 3, 4, 5, 6, 10, 12,
15, 20, or 30 Valid values for minutes (H/h) = 1, 2, 3, 4, 6, 8, or 12 Default = 10 m |
Property to determine heartbeat refresh time interval. Format of the property is Xm or Xh
where X is an integer between 1 and 60 and M/m for minutes or H/h for hours. If any unrecognized
value or unit is specified, it will default to 10m (minutes). If a value of 61m or greater is
specified, it will be reduced to 60m. If a value of 25h or greater is specified, it will be reduced
to 24h. If the units are minutes (M/m), then the value is rounded up or down to the nearest equal
divisor of 60 minutes. If the units are hours (H/h), then the value is rounded up or down to the
nearest equal divisor of 24 hours. Example: Note: IBM® recommends that the value of this property should be set greater than the value of the yantra.statistics.persist.interval property. |
| yfs.heartbeat.serverid.usegeneratedkey |
Valid values = true or false Default = false |
If the property is set to true, then for each JVM, the server id is generated based on a unique random number, which helps in broadcasting the cache correctly. Additionally, setting this property to true, facilitates enabling traces for logs, without having to restart the App server. |
| yfs.pricing.upgrade.complete | Valid values = Y or N Default = N |
As part of upgrade, a SQL query creates seller
assignments for all existing price lists that do not have a seller
assignment. This property indicates whether the pricing upgrade has
been completed and therefore, whether all seller assignments have
been created. Valid values: Y - Assumption is that seller assignment is created for the pricing rule or price list defined in an older version. A pricelist or a pricing rule without a seller assignment is not used during price calculation. Set value to Y for a new installation. N - Assumption is that seller assignment is not created for the pricing rule or pricelist defined in an older version. Pricelist or pricing rule without seller assignment are considered to be applicable to all sellers. Example:
|
| jmx.enabled |
Valid values = true or false Default = true |
Used to enable or disable JMX MBean initialization during application or agent
server startup. These JMX MBeans can be used to monitor the server using a JMX client, such as
JConsole. Example:
|
| jmx.initialize.async |
Valid values = true or false Default = false |
If the value of this property is set to true, the JMX MBean initialization
happens asynchronously in a parallel thread so that the parent thread does not have to wait for the
JMX initialization to finish. Otherwise, if the value of this property is set to false, the JMS
MBean initialization happens synchronously in the parent thread. Remember: This property
is applicable only when the value of the jmx.enabled property is set to
true.
Example:
|