Engine Startup Sequence
The following actions comprise the engine startup sequence:
- System information is displayed in consoles and is recorded in the log file:
- Cache OM with backing store only: Recovery stage. When the minimum number of cache agents is started (as defined by the Cache Agent Quorum CDD setting), the cluster enters the Recovery state. Various caches are preloaded from the backing store, according to preload settings. When the Recovery state ends, the cluster enters the Ready state.
- All inference agents build their Rete networks by evaluating conditions against all Cache Plus Memory objects if any. For (Cache OM only) Inactive (Standby) Nodes: if all agents in an engine are inactive, then this ends the startup sequence for that engine.
- Channels start up for outbound traffic. Inbound listeners do not start yet.
- Scorecards are created.
- Startup functions execute (for example, they initialize values of scorecards).
- The first RTC cycle occurs and all rule actions that are eligible to execute now execute. (Scorecards and startup rule functions can cause rules to be eligible to execute. Depending on the state of entities recovered from the backing store, the RTC will take more or less time.) See TIBCO BusinessEvents Architect’s Guide for more details about RTC cycles.
- The engine startup advisory event is asserted, and its RTC occurs (as needed).
- Time events (if any) are asserted:
- The clock starts for repeating time events and they are created and asserted at the specified intervals.
- Rule-based time events (recovered or scheduled in a startup action) are asserted after the specified delay. The delay begins when the rule or rule function action executes, so, at startup, it is possible for time events to have passed their start time, and they are asserted immediately.
- Inbound channel listeners activate and accept incoming events and the system is now fully started.
Copyright © TIBCO Software Inc. All Rights Reserved.