Jump to: navigation, search

sml Section

This section must be called sml.

heartbeat-period

Default Value: None
Valid Values:

0


This method of detecting an unresponsive application is not used by this application.


3-604800


Length of timeout, in seconds; equivalent to 3 seconds—7 days.

Changes Take Effect: Immediately

Specifies the maximum amount of time, in seconds, in which heartbeat messages are expected from an application. If Local Control Agent (LCA) does not receive a heartbeat message from the application within this period, it assumes the application is not responding and carries out corrective action.

This option can also be used to specify the maximum heartbeat interval for threads registered with class zero (0). This thread class is reserved for use by the Management Layer only.

If this option is not configured or is set to 0 (zero), heartbeat detection is not used by this application.

Warning: Use this option with caution, and only with those applications that support this functionality. Failure to use this option properly could result in unexpected behavior, from ignoring the options to an unexpected restart of the application.

heartbeat-period-thread-class-<n>

Default Value: None
Valid Values:

0

Value specified by the heartbeat-period in the application that is used.

3-604800

Length of timeout, in seconds; equivalent to 3 seconds—7 days.

Changes Take Effect: Immediately

Specifies the maximum amount of time, in seconds, in which heartbeat messages are expected from a thread of class, <n> registered by an application. If a heartbeat message from the thread is not received within this period, the thread is assumed to be not responding, and therefore, the application is unable to provide service.

If this option is not configured or is set to 0 (zero), but the application has registered one or more threads of class, <n>, the value specified by the value of the heartbeat-period for the application is also applied to these threads.

Refer to the application-specific documentation to determine what thread classes, if any, are used.

Warning: Use this option with caution, and only with those applications that support this functionality. Failure to use this option properly could result in unexpected behavior, from ignoring the options to an unexpected restart of the application.

hangup-restart

Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately

If the value of the option is set to true (the default value), specifies that LCA restarts the unresponsive application immediately, without any further interaction from Solution Control Server. If the value of the option is set to false, specifies that LCA only generates a notification that the application has stopped responding.

Warning: Use this option with caution, and only with those applications that support this functionality. Failure to use this option properly could result in unexpected behavior, from ignoring the options to an unexpected restart of the application.

suspending-wait-timeout

Default Value: 10
Valid Values: 5-600
Changes Take Effect: Immediately

Specifies a timeout (in seconds) after the Stop Graceful command is issued to an application during which the status of the application should change to Suspending, if the application supports a graceful shutdown. If the status of the application does not change to Suspending before the timeout expires, it is assumed that the application does not support a graceful shutdown, and it is stopped ungracefully.

Use this option if you are unsure whether the application supports a graceful shutdown.

Warning: Genesys recommends that you do not set this option for any Management Layer component (Configuration Server, Message Server, Solution Control Server, or SNMP Master Agent) or any DB Server. These components, by definition, do not support graceful shutdown, so this option is not required.

This page was last edited on March 26, 2013, at 03:57.
blog comments powered by Disqus