Housekeeping

To prevent the Orchestra runtime database from becoming overcrowded, runtime data will be deleted or archived to a dedicated archive database after a specified period. This means that the information regarding processes may not always be available in the monitor.

If LTA is enabled, the data will be moved to a separate Orchestra LTA database, preventing potential data loss.

The housekeeping settings and the Long Time Archive can be configured in the environment settings.

danger

If the Long Time Archive (LTA) feature is not active, entries will be deleted from the Orchestra runtime tables after a certain time.

Configuration Groups

This section explains the groups available under the "Housekeeping" category in the environment settings.

SystemEvent

These are the housekeeping settings for system events. The entries for system events displayed in the monitor depend on the settings within this group.

BusinessTransaction

These are the housekeeping settings for business transactions. Business transactions are transactions explicitly created in a process using startTA and undoTA. Currently, this feature is not frequently utilized.

ProcessCleanup

These are the housekeeping settings for process events. These settings address all types of processes, differentiating between successful and aborted ones.

MessageStore

These are the housekeeping settings for the message store. Messages are managed independently of the processes, which is why they have their own group. For more information, please see the next chapter, as there may be differences based on the version you are using.

ESB

These are the housekeeping settings for the Enterprise Service Bus (ESB). This is only relevant for cell communication. Orchestra protocols signal the sending of messages to prevent duplicates. This cleanup process occurs here.

LongtimeArchive

These are the housekeeping settings for the Long Time Archive. indicated by the name, this section pertains to the Long Time Archive. There is no distinction made between processes and messages in LTA.

Correlation Between Processes and Messages

At runtime, a message is associated with a process. Messages should only be deleted after their corresponding processes have been removed. Therefore, messages remain in the database for as long as their related processes exist. In older versions of Orchestra, processes and messages were treated completely independently, which involved the MessageStore.cleanup parameter. Consider the following parameters in the environment settings:

<parameter name="ProcessCleanup.SUCCESS.cleanup" value="1,HOUR" type="PERIOD"/>
<parameter name="MessageStore.cleanup" value="10,MINUTE" type="PERIOD"/>

In newer versions, messages are retained for the sum of ProcessCleanup.SUCCESS.cleanup and MessageStore.cleanup. The MessageStore.cleanup parameter should not be configured to a value smaller than 10 minutes. It is recommended not to modify the default parameters provided.