Appendix A This section helps you understand 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. See Working With Startup and Shutdown Rule Functions for related information.This section assumes cache OM. It provides the main milestones only and focuses on nodes running inference agents.
− 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.If a backing store is in use (Cache OM only), cache data is recovered from the backing store and populates cache servers (and JVMs of any other storage enabled agents).(Cache OM only) Inactive Nodes If all agents in an engine (node) are inactive, then this ends the startup sequence for that engine.
6. 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 Understanding Conflict Resolution and Run to Completion Cycles 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 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.
9. Finally, inbound channel listeners activate and accept incoming events and the system is now fully started up.
Copyright © TIBCO Software Inc. All Rights Reserved.