Dynamic Tracking Data Scanner

Dynamic Tracking Data Scanner Details

The Dynamic Tracking Data Scanner tests for optimization and efficiency in handling business processes and messages.

Size Process Data

The Size Process Data test determines whether the number of pages of persisted business process data is excessive. For large business processes that are consistently persisted, you might consider reducing the amount of persisted data. Examine the process data structure in process runs, and use the Release service to purge unnecessary data at certain points in the workflow.

The Size Process Data test has a severity of 1, WARNING.

Halted Process

The Halted Process test determines whether the number of halted processes that occurred is too large.

The Halted Process Test has a severity of 2, ERROR.

Interrupted Process

The Interrupted Process test determines whether the number of interrupted processes that occurred is too large.

The Interrupted Process test has a severity of 2, ERROR.

Mailbox Old

The Mailbox Old test determines whether the number of old messages in the mailbox is too large.

The Mailbox Old test has a severity of 1, WARNING.

Mailbox Unextractable

The Mailbox Unextractable test determines whether the number of unextractable messages in the mailbox is too large.

The Mailbox Unextractable test has a severity of 2, WARNING.

Process Length

The Process Length test ensures that the length of time to process a business process is reasonable. The test compares the process time in the queue to AE_ExecuteCycle. If there are many business processes that exceed the number of steps per cycle for a queue, consider increasing the value of AE_ExecuteCycle for that queue in the customer_overrides.properties file. Otherwise, move the process to a different queue with enough steps per cycle. For more information about configuring processing cycles in queues, see Tuning Queues.

The Process Length test has a severity of 2, ERROR.

Waiting on IO Low Return Time

The Waiting on IO Low Return Time test reports an error if a business process in WAITING_ON_IO state returns to running quickly. There is overhead incurred when a business process is moved to WAITING_ON_IO and then resumed. The overhead is acceptable if the business process spends a long time blocked. If the process does not spend a long time blocked, it would be better for the system to leave the business process alone and wait for the step to complete, rather than entering WAITING_ON_IO state. The wait time is defined as the amount of time between the moment a business process begins waiting on IO and the moment the system resumes handling the business process. It is ideal for system performance if the wait time is greater than the overhead incurred by entering WAITING_ON_IO state. The test looks for processes where the wait time is less than the threshold value that is defined by this test's shortWait property.

The Waiting on IO Low Return Time test has a severity of 1, WARNING.

The Dynamic Tracking Data scanner includes tests that help you to determine what are the best practices to follow for your particular system. Tests are designed to ensure that your settings match the settings suggested for Sterling B2B Integrator, but those settings might not necessarily be the best for your particular system or improve performance, nor does a difference in suggested settings indicate a serious system error.