Managing Daemons

To manage daemons, open the Daemons view from the Administration Perspective launch panel. The view displays the five daemons used in the Infinity Process Platform context:

For detailed information on these daemons, please refer to the chapter Daemons in the Administrative Concepts section of the Infinity Process Platform Documentation - Concepts. Daemons in the Administrative Concepts of the Concepts part.

Daemons Table

This table displays the following information about these daemons:


Figure: The Daemons View


Figure: The Daemons View

Starting a Daemon

To start a daemon, select the Start Daemon button in the Actions column of the according daemon.


Figure: Starting a Daemon

After a daemon has been started, the entries in the corresponding row in the Daemons view must change accordingly, displaying a new start time and status set to Running.


Figure: Daemon changed to Running State.

Stopping a Daemon

To stop a daemon, select the Stop Daemon button in the Actions column of the according daemon.


Figure: Stopping a Daemon

After a daemon has been stopped, the entries in the corresponding row of the Daemons view must change accordingly, clearing the start and last execution times and displaying the status set to Stopped.

Note

It could be necessary to stop the daemon to avoid problems during deployment or cleaning up the audit trail, even though it is displayed as Stopped. This is the case when the acknowledge state is not displayed as OK at the same time.

Adjusting the Number of Retries

To prevent that a daemon operation fails immediately if the database is busy, a number of retries is determined. Per default, a daemon retries operations three times. You can adjust this number to your requirements by setting the property Stardust.Engine.Daemon.Acknowledge.Retry in your server-side carnot.properties file. To adjust the time delay between the retries, you can use property Stardust.Engine.Daemon.Acknowledge.Delay. The default time delay is 500 ms.

If all retries failed, the daemon will be stopped and a mail will be sent to all administration users if the mail server is configured correctly.

Acknowledge State

The Acknowledge State reflects the communication capability of the daemons. An OK message means that the daemon was able to perform the command, while a Failure message means that the daemon has received the command, but was unable to successfully execute it. A Response Requested message in most of the cases reflects a "zombie" daemon, i.e. the daemon was started but the process executing it terminated without updating the audit trail.

Adjusting the Number of Retries for Operation Acknowledgments

You have the option to adjust the number of retries to get a daemon operation acknowledgment. Set the property <daemon_name>.AckRetries in your carnot.properties file to a number of retries you would like to be used. The default value is 10 retries.

Adjusting the Waiting Time between Daemon Operation Acknowledgments

To change the number of seconds to wait between two daemon operation acknowledgments, set the property <daemon_name>.AckWait in your carnot.properties file accordingly. The default value is 2 seconds.

Execution State

The Execution State shows the execution result of the daemon. An OK message shows that the daemon executed without problems, a Warning message specifies that a problem occurred during daemon run but the daemon could continue to run, while a Fatal message specifies that the daemon has stopped due to a fatal execution error.