Legacy platform

Time-triggered transaction reference

Sterling Order Management System Softwareprovides a collection of time-triggered transactions, which are utilities that perform a variety of individual functions, automatically and at specific time intervals.

Some transactions enable you to collect statistical data regarding the application's health. This data is collected periodically, using the value specified for the yantra.statistics.persist.interval attribute in the yfs.properties file. By default, statistics collection set to on. To override this property, add an entry in the <INSTALL_DIR>/properties/customer_overrides.properties file. For additional information about overriding properties that use the customer_overrides.properties file, see Configuring Property Files topic.

Some transactions enable you to collect statistical data regarding the application's health. This data is collected periodically, using the value specified for the yantra.statistics.persist.interval attribute in the yfs.properties file. By default, statistics collection set to on. To override this property, add an entry in the <INSTALL_DIR>/properties/customer_overrides.properties file. For additional information about overriding properties using the customer_overrides.properties file, see Configuring Property Files topic. .

For more information about statistics persistence, see the Configuring for Performance Management topic. For more information about the specific statistics parameters used, see the applicable time-triggered transactions.

The time-triggered transactions that are described in this chapter are unique transactions, that may or may not be document type specific. For document-specific transactions, the nomenclature helps define which unique transaction it is based on: a transaction ID is in the format Unique_Transaction_ID.Document_Type_Code. For example, the transaction ID for Purge Return is PURGE.0003, indicating that it is based on the unique transaction PURGE, for document type 0003, which is Return Order. Therefore, in order to be able to configure Purge Return, you must look for the PURGE transaction ID in this chapter, which is Order Purge.

Sterling Order Management System Software provides the following types of time-triggered transactions:

Sterling Order Management System Software tracks the following statistics for each time-triggered transaction:

  • ExecuteMessageCreated - The number of jobs added to the JMS queue in a given time interval.
  • ExecuteMessageSuccess - The number of jobs that were run successfully in a given time interval.
  • ExecuteMessageError - The number of jobs that failed to run in a given time interval.
  • GetJobsProcessed - The number of GetJob messages that were processed in a given time interval.
    Note: Some of the statistics collected and tracked in Release 9.1 for time-triggered transactions, monitors, and integration and application servers may change with the next release of Sterling Order Management System Software.