Configuration

Configuration is likely the single most important topic for an engine in terms of its usefulness to the client and overall usability. The key is identifying the use for a particular configuration setting and applying it to the right layer. Putting the configuration on master data too finely forces a user to update millions of values when they want to change a behavior in general. Putting the configuration only when the engine runs possibly forces to run the engine many times if different parts of the network need different behavior. Putting configuration at every level will result in a complex configuration nightmare that the engine – and the user – has to evaluate to understand what needs to be calculated.

• Configuring an Engine via the Run Engine UI or the JMX Console

• Configuring an Engine Using Scenarios

• Configuring an Engine via the IXM Engine Configuration