Proceedings International Conference on Information Technology: Coding and Computing (Cat. No.PR00540)
DOI: 10.1109/itcc.2000.844197
|View full text |Cite
|
Sign up to set email alerts
|

An event driven software architecture for enterprise-wide data source integration

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Publication Types

Select...
7
2

Relationship

2
7

Authors

Journals

citations
Cited by 13 publications
(6 citation statements)
references
References 7 publications
0
6
0
Order By: Relevance
“… Enterprise Integration Components: provides an interface for the system to connect to required external services. Examples of common Enterprise Integration Components include event pre-processing, publishing and subscribing, and business process invocation [64]  Sources and Targets: specify the sources of incoming event data and the targets on which event-driven actions are performed [65]  Event Database: data storage used for storing the event data that are processed by the Event Processing Engine [63] Over the past few years many papers have been written on development of EPSs and their applications in various fields. Table 2.2 lists different types of event processing languages and their corresponding products.…”
Section: List Of Actions Event Streammentioning
confidence: 99%
“… Enterprise Integration Components: provides an interface for the system to connect to required external services. Examples of common Enterprise Integration Components include event pre-processing, publishing and subscribing, and business process invocation [64]  Sources and Targets: specify the sources of incoming event data and the targets on which event-driven actions are performed [65]  Event Database: data storage used for storing the event data that are processed by the Event Processing Engine [63] Over the past few years many papers have been written on development of EPSs and their applications in various fields. Table 2.2 lists different types of event processing languages and their corresponding products.…”
Section: List Of Actions Event Streammentioning
confidence: 99%
“…The basic principle of the pipeline & filter architecture is to use a single data flow [3], in a relatively simple format, that crosses several processes. On it, every process transforms the content of the data somehow, data is continuously inputting to the pipeline (entrance to the pipe), processes (chain of links) are executed concurrently.…”
Section: Principles Of the Used Architecturementioning
confidence: 99%
“…The work approaches the problem from a data warehouse (DW) perspective and does not describe a framework for implementing DM applications. Other DW-centric studies are presented in [4], [5]. Architectures for processing data streams or data feeds have been developed in [6], [7], [8].…”
Section: Introductionmentioning
confidence: 99%