This section outlines the main actions that occur during engine startup and shutdown (in normal circumstances). In any particular project only some of the actions may be required. For example, a project may have no startup rule functions.Except where noted, this section assumes cache OM and inference agent startup and shutdown. It provides the main milestones only.
When Cache OM is used, you must start a node that has storage enabled first. In production systems that would be a dedicated cache agent engine. (In test deployments this could be another type of agent node with local storage enabled.)In a situation where all cache agents are stopped but engines running other types of agents are running, you must restart all engines.
− The version of the JAR files it is using, and the version of the JAR files that the EAR file was built with.
− If persistence OM is used, the location of the Berkeley DB software it is using, and information about what was recovered from the database.
2. Cache OM with backing store only: Recovery stage. When the minimum number of cache servers 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 Recovery state ends, the cluster enters Ready state.
3. All inference agents build their Rete networks by evaluating conditions against all Cache Plus Memory objects (if any).(Cache OM only) Inactive (Standby) Nodes If all agents in an engine are inactive, then this ends the startup sequence for that engine.
7. 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 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.
10. Finally, inbound channel listeners activate and accept incoming events and the system is now fully started up.
Copyright © TIBCO Software Inc. All Rights Reserved.