State Modeler
State Modeler is based on the UML-standard definition for state models. A state model is a directed graph. States are represented by nodes and state transitions are represented by connectors.
A state model allows you to model the life cycle of a concept instance — that is, for each instance of a given concept, you can define what states the instance passes through and how it will transition from state to state.
For example, consider an order process. It is modeled using a state model that is associated with an Order concept.
In the above example, when a customer places an order, TIBCO BusinessEvents receives a simple event and creates a new instance of the Order concept. Through the life of the Order instance, it passes through a credit-check state, an inventory-check state, a fulfillment state, and so on until the customer has received and paid for the order.
As these order activities take place, TIBCO BusinessEvents receives new events, correlates the events to the existing instance, modifies one or more property values within the instance, and changes the state of the instance.
TIBCO BusinessEvents ships with a simple state model example, which you can open and examine. It also includes a document with instructions for creating the example yourself. This will help to familiarize you with the TIBCO BusinessEvents State Modeler. This and other examples are stored in the BE_HOME/examples directory.
- State Modeler Functions
The State Modeler includes its own set of functions, which are located in the Standard function registry view, under Instance > StateMachine. - State Models and Concepts
Each state model is owned by a concept. One concept can own multiple state models, but has only one main state model. The main state model can call the other state models. - State Models and Rules
State models define behaviors relating to a concept during its lifecycle. The TIBCO BusinessEvents rule language is used to define many of these behaviors. - State Machines at Runtime
At runtime a state model executes as a state machine, which begins in the start state. - Types of States
There are different type of states a concept instance passes though in the state model. - Adding Regions in a Concurrent State
By default, a concurrent state has two regions, but more can be added to it. - Transitions
The states in a state model are connected by transitions. - Call State Machine Resource
To call a state machine from another state machine, at design time you add a Call State Model node. You insert the node like any other state in a state model and link it to other states using transitions. - State Model Timeouts and State Timeouts
You can define timeouts at the state model level and for each of its states, except for the start, end, and Call State Model nodes.