How does the MEG chaining work?
Many factors determine whether WBI should route a transaction through a particular Meg, including condition rules, priority numbers, and extra rule keys. For more information on MEG chaining, see the Architecture section. • How do I setup a MEG? Each MEG has four properties: name, condition, priority, and enabled. The name is used for tracing/messaging information; the condition specifies when WBI should route the transaction through this MEG; the priority value orders MEGs when several match a given transaction; and the enabled property turns the MEG on and off. These properties can be set individually using setName, setCondition, setPriority, and setEnabled, or they can all be set at once using setup. For more information on setting up a MEG, see the Programming section. • What kind of syntax do the condition rules use? Which variables do they test? Condition rules are simple statements combined with boolean operators.
Many factors determine whether WBI should route a transaction through a particular Meg, including condition rules, priority numbers, and extra rule keys. For more information on MEG chaining, see the Architecture section. • How do I setup a MEG? Each MEG has four properties: name, condition, priority, and enabled. The name is used for tracing/messaging information; the condition specifies when WBI should route the transaction through this MEG; the priority value orders MEGs when several match a given transaction; and the enabled property turns the MEG on and off. These properties can be set individually using setName, setCondition, setPriority, and setEnabled, or they can all be set at once using setup. For more information on setting up a MEG, see the Programming section. • What kind of syntax do the condition rules use? Which variables do they test? Condition rules are simple statements combined with boolean operators. Some of the variables which can be used in the statements include
