Processing strategies for monitor models
When you deploy a monitor model, you can decide on several combinations of options. For example, you can choose processing strategies, and you can decide whether to enable event reordering.
If you select Detailed - Show all installation options and parameters when you deploy a monitor model, you can choose from several monitor model options. One of the decisions you make while configuring these options is which processing strategy you want to use. The following sections explain these different strategies.
6.0.2 emulation processing
The 6.0.2 emulation processing mode is also known as serial consumption single-threaded processing. This mode emulates the IBM® Business Monitor version 6.0.2 style of message consumption and processing. As such, it does not support event reordering, and it does not support the failed event queue. In this mode, an event that cannot be processed causes all event processing for this monitor model version to stop until the event can be successfully processed or it is removed from the monitor model JMS queue.
This mode is always available.
Scalable processing
The Scalable processing mode was previously known as serial consumption multi-threaded processing. This mode partitions events according to an event partition path and processes multiple event streams in parallel. This mode supports event reordering and supports the failed event queue. In this mode, an event that cannot be processed causes only related events (that is, events in the same partition) to stop processing and be sent to the failed event queue. If the sequence ID expression is not guaranteed to be unique, the order of events with the same sequence ID will be the order in which they were received.
To enable the Scalable event processing strategy, every inbound event definition must have an event partition path specified.
Default settings for the processing strategies
The default setting for the processing strategy varies depending on what the monitor model supports:
- If the model supports multithreading and supports reordering, the default setting is Scalable processing with reordering.
- If the model supports multithreading but does not support reordering, the default setting is Scalable processing without reordering.
- If the model does not support multithreading or reordering, the default setting is 6.0.2 emulation processing.
In addition, if the previous version of the model is in Inactive (event queue recoverable) state, only 6.0.2 emulation processing is allowed. All other processing strategies are unavailable.