Abstract. Complex Event Processing (CEP) is a defined set of tools and techniques for analyzing and controlling the complex series of interrelated events that drive modern distributed information systems. This emerging technology helps IS and IT professionals understand what is happening within the system, quickly identify and solve problems, and more effectively utilize events for enhanced operation, performance, and security. CEP can be applied to a broad spectrum of information system challenges, including business process automation, schedule and control processes, network monitoring and performance prediction, and intrusion detection.This talk is about the rise of CEP as we know it today, its historical roots and its current position in commercial markets. Some possible long-term future roles of CEP in the Information Society are discussed along with the need to develop rule-based event hierarchies on a commercial basis to make those applications possible. The talk gives empahsis to the point that "Rules are everywhere" and that mathematical formalisms cannot express all the forms that are in use in various event processing systems.

is an event-based concurrent, objectoriented language speci cally designed for prototyping system architectures. Two principle design goals are 1 to provide constructs for de ning executable prototypes of architectures, and 2 to adopt an execution model in which t h e concurrency, synchronization, data ow, and timing properties of a prototype are explicitly represented. This paper describes the partially ordered event set poset execution model and outlines with examples some of the event-based features for de ning communication architectures and relationships between architectures. Various features of Rapide are illustrated by excerpts from a prototype of the X Open distributed transaction processing reference architecture. Keywords| Rapide, architecture de nition languages, partially ordered event sets, architecture, prototyping, concurrency, simulation, formal constraints, constraint-based speci cation, event patterns, causality.

| This paper discusses general requirements for architecture de nition languages, and describes the syntax and semantics of the subset of the Rapide language that is designed to satisfy these requirements. Rapide is a concurrent event-based simulation language for de ning and simulating the behavior of system architectures. Rapide is intended for modelling the architectures of concurrent and distributed systems, both hardware and software. In order to represent the behavior of distributed systems in as much detail as possible, Rapide is designed to make the greatest posible use of event-based modelling by producing causal event simulations. When a Rapide model is executed it produces a simulation that shows not only the events that make u p the model's behavior, and their timestamps, but also which events caused other events, and which e v ents happened independently. The architecture de nition features of Rapide are described here: event patterns, interfaces, architectures and event pattern mappings. The use of these features to build causal event models of both static and dynamic architectures is illustrated by a series of simple examples from both software and hardware. Also we give a detailed example of the use of event pattern mappings to de ne the relationship between two architectures at di erent levels of abstraction. Finally, w e discuss brie y how Rapide is related to other event-based languages. Keywords| Rapide, architecture de nition languages, partially ordered event sets, architecture, prototyping, concurrency, simulation, formal constraints, event patterns, causality.

This paper describes the Rapide concepts of system architecture, causal event simulation, and some of the tools for viewing and analysis of causal event simulations. Illustration of the language and tools is given by a detailed small example. 1 Introduction Rapide-1.0 LKA + 95 , LV95 is a computer language for de ning and executing models of system architectures. The result of executing a Rapide model is a set of events that occurred during the execution together with causal and timing relationships between events. The production of causal history as a simulation result is, at present, unique to Rapide among event-based languages. Sets of events with causal histories are called posets partially ordered event sets. 1 Simulators that produce posets provide many new opportunities for analysis of models of distributed and concurrent systems. Rapide-1.0 is structured as a set of languages consisting of the Types, Patterns, Architecture, Constraint, and Executable Module languages. This set of languages is called the Rapide language framework. The purpose of the framework is twofold: i to encourage multi-language systems, ii to de ne language components that may be applied to, or migrated into, other event generating systems. Towards i, w e a n ticipate that the Executable Module, Constraint o r A r c hitecture sublanguages may b e c hanged in fairly substantial ways, and that the Executable Module and Constraint sublanguages may b e i n terchanged with other languages provided certain compatibility requirements are met. Towards ii, for example, the use of constraints expressed in terms of event patterns will have many applications to systems that generate events, not just the Rapide simulator. Such applications could include monitoring distributed object systems based on CORBA or other commercial middleware for security, for conformance to standards, and for many other properties. The Types language provides the basic features for de ning interface types and function types, and for deriving new interface type de nitions by inheritance from previous ones. Its semantics This project is funded by D ARPA under ONR contract N00014-92-J-1928 and AFOSR under Grant AFOSR91-0354

No abstract

No abstract

No abstract

No abstract