Reactor state

A Reactor is an executable instance of a deployed Decision Service. Corticon Server acts as the broker to one or more Reactors for each deployed Decision Service. During Decision Service execution, the Reactor is a stateless component, so all data state must be maintained in the message payloads flowing to and from the Reactor.

If a deployed Ruleflow contains multiple Rulesheets, state is preserved across those Rulesheets as the Rulesheets successively execute within the Ruleflow. However, no interaction with the client application occurs between or within Rulesheets. After the last Rulesheet within the Ruleflow is executed, the results are returned back to the client as a CorticonResponse message. Upon sending the CorticonResponse message, the Reactor is deleted from memory. A new Reactor will be created for the next incoming CorticonRequest.

As an integrator, you must keep in mind that there are only two ways for you to retain state upon completion of a Decision Service execution:

Once a Decision Service execution has completed, the Reactor itself does not remember anything about the data it just processed.