TriggerWare is the most sophisticated triggering engine available in the marketplace today. In comparison to its competition, TriggerWare offers many critical technology differentiators:

1. Generic, application-independent monitoring service that can integrate horizontally into many different domains and can even span across multiple domains. This gives TriggerWare the ability to fuse event information from many data sources.
2. Sophisticated event pattern specification capability that provides the ability to describe many useful event patterns -- events that trigger real-world decision making processes.
   
3. Dynamic event definition facilities that make it possible to change the criteria of importance on the fly, without any code rewrite or recompilation.
   
4. TriggerWare maintains complete event histories to enable one to specify new kinds of historical analysis and projections through new computations that can be added dynamically.
   
5. APIs to program decision support applications that involve events on a single workstation, a Local Area Network, or the Internet.
   

TriggerWare Architecture

TriggerWare is a client/server system with the following important architectural roles:

• Monitored systems: These are the sources of primitive events. They are monitored by the TriggerWare infrastructure. Primitive event occurrences are gathered by the Monitor.
  
• Event Definers: Composite events are defined in a language called FLEA (Formal Language for Expressing Assumptions). FLEA is the most powerful event definition language in the market, fully equivalent to first-order predicate calculus.
  
• Event Receivers: These are clients interested in occurences of specific events. In the figure they are shown together with event definers.
  
• FLEA Compiler: processes FLEA event definitions and generates the additional code necessary for the monitor to notice when those events have actually occurred. The FLEA event compiler is what makes TriggerWare both unique and efficient in processing new event criteria.
  
• Monitor: receives reports of occurrences of primitive events, and executes the code provided by the FLEA compiler to detect whether composite events have occurred, and notifies interested clients about all event occurrences.

Within the TriggerWare architecture, note that there is a single FLEA monitor and compiler, but there may be multiple event definers, monitored systems and receiver clients interested in notifications about events. In short, TriggerWare supports reasoning about distributed events across any kind of network.

How to get your TriggerWare License

The TriggerWare family of products includes:

• TriggerWare server (for SUN Solaris or Microsoft Windows 9x/NT)
• Visual editor for FLEA (Windows 9x/NT)
• TriggerWare Java applets (defining, receiving, or metering events)
• All documentation and application program interfaces, and several working examples of TriggerWare applications

To inquire about these, or to acquire a TriggerWare license, please contact Cs3 or (310) 337-3013. More documents about TriggerWare are also available.

TriggerWare Consulting and Training

TriggerWare is a generic monitoring server -- like a database for events. It must be populated with a rich model of events for any given application. Cs3 provides consulting and training services to facilitate the customization of TriggerWare to specific monitoring solutions that are critical to customers. A variety of partnering relationships are also available to those interested in incorporating the sophisticated capabilities of TriggerWare into their own products. Please contact Cs3 or (310) 337-3013.

TriggerWare White Paper           View HTML           View PDF