Abstract: Certain example embodiments relate to a complex event processing, CEP, system, including an error correction component configured to receive a stream of events including at least one event from at least one event source. The error correction component is configured to detect at least one error in the at least one event. The error correction component is configured to emit a corrected stream of events including at least one event, which can then be processed by at least one event processing application.

Abstract: The present technology relates to a method for granting a user secure access to one or more resources accessed by a process. The process is defined in a Service-Oriented Architecture (SOA) registry and includes one or more process-steps, where each process-step accesses one or more resources stored in an SOA repository.

Abstract: System and method for managing a plurality of web services. The system may include a registry with a description for at least one of the plurality of web services, wherein the description of the at least one web service may comprise a first endpoint for a first runtime condition and a second endpoint for a second runtime condition.

Abstract: Monitoring a software system based on a service oriented architecture (SOA). The method may involve system components communicating with each other via sending messages. The method may include receiving a monitoring message by a monitoring component where the monitoring message may be sent from a system component of the software system. The method may further include providing an ontology including at least one interpretation rule for the message by the monitoring component. The method may also include reacting of the monitoring component in accordance with the at least one interpretation rule.

Abstract: Certain example embodiments described herein relate to techniques for introducing semantic concepts into complex event processing (CEP) systems and/or methods. In an event processing system, for example, an event bus is configured to receive a stream of events, each having a predefined event type. An event processing agent is configured to execute predefined queries on the events, with each query conforming to a query language, and with the query language being enhanced via a semantic extension corresponding to an ontology. An ontology management component in communication with the event processing agent stores mappings (optionally specified at design time) between concepts of the query language and concepts of the ontology that enhances the query language.

Abstract: The present invention concerns a method for replicating data of a database server (10) by at least one replication server (20), the method comprising the following steps performed by the at least one replication server (20): a. sending a database request (40) to the database server (10), wherein the database request (40) comprises metadata (421c, 421d) indicating replication data requested by the at least one replication server (20); and b. receiving a database response (40?) from the database server (10), wherein the database response (40?) comprises the requested replication data indicated by the metadata (421c, 421d).

Abstract: A registry for a service oriented architecture (SOA) comprising a plurality of processing objects. The registry may include a plurality of non-formalized operation requirements for the plurality of SOA objects, a plurality of technical assertions for the plurality of SOA objects, and a plurality of links, linking each non-formalized operation requirement to at least one technical assertion of the registry.

Abstract: A computing system includes a service-oriented architecture (SOA) registry that includes an SOA-application description, an abstract component description, a concrete component description, and a platform description. The SOA-application description is related to the abstract component description of a component of the SOA-application. The concrete component description includes a requirement of a respective component for a target platform. The platform descriptor describes a property of the target platform. The computing system is configured to deploy the SOA-application and its respective components to the target platform in accordance with the concrete descriptions.

Abstract: Certain example embodiments relate to importing assets into a service-oriented architecture (SOA) registry. An SOA system includes a repository for storing a plurality of files relating to real assets, and a registry containing metadata and/or other information about these real assets, including at least one registry asset per real asset. Each registry asset has a registry asset type. A generic import module is configured to (a) receive as input one or more import specifications, with each import specification defining how information from an external specification file of an asset type is to be extracted to create one or more registry assets of one or more corresponding target registry asset types, (b) generate one or more registry assets of one or more target registry asset types based on a corresponding import specification, and (c) register the generated one or more registry assets of the one or more target registry asset types.

Abstract: Certain example embodiments relate to a system for secure complex event processing (CEP). The system includes an input adaptor configured to receive at least one input event from at least one external source system. The at least one input event comprises at least one event-specific disclosure permission concerning data of the input event. A CEP engine is configured to process the at least one input event and to produce at least one corresponding complex output event. A security enforcer is configured to remove data from the at least one output event that is not in accordance with the at least one event-specific disclosure permission defined in the corresponding at least one input event. An output adaptor is configured to send the at least one output event to at least one external target system.

Abstract: Monitoring a software system based on a service oriented architecture (SOA). The method may involve system components communicating with each other via sending messages. The method may include receiving a monitoring message by a monitoring component where the monitoring message may be sent from a system component of the software system. The method may further include providing an ontology including at least one interpretation rule for the message by the monitoring component. The method may also include reacting of the monitoring component in accordance with the at least one interpretation rule.

Abstract: Managing the lifecycle of a service oriented architecture (SOA). The method may include selecting a subset of a plurality of objects of the SOA for lifecycle management in accordance with the requirements of an organization implementing the SOA, and assigning a lifecycle property to each member of the subset of the plurality of objects of the SOA.

Abstract: Monitoring a software system based on a service oriented architecture (SOA). The method may involve system components communicating with each other via sending messages. The method may include receiving a monitoring message by a monitoring component where the monitoring message may be sent from a system component of the software system. The method may further include providing an ontology including at least one interpretation rule for the message by the monitoring component. The method may also include reacting of the monitoring component in accordance with the at least one interpretation rule.

Abstract: Certain example embodiments relate to a system for secure complex event processing (CEP). The system includes an input adaptor configured to receive at least one input event from at least one external source system. The at least one input event comprises at least one event-specific disclosure permission concerning data of the input event. A CEP engine is configured to process the at least one input event and to produce at least one corresponding complex output event. A security enforcer is configured to remove data from the at least one output event that is not in accordance with the at least one event-specific disclosure permission defined in the corresponding at least one input event. An output adaptor is configured to send the at least one output event to at least one external target system.

Abstract: Certain example embodiments described herein relate to techniques for the attachment of priorities and/or reaction time limits to various entities of a system such as, for example, events, event types, queries, etc. The system's processing may be tailored behavior to match these boundary conditions while at the same time increasing (and sometimes even maximizing) the rate of events processed. Advantageously, the system may be made to adapt its behavior to the current situation, which is changeable and may even be changing quite frequently, e.g., as in connection with a potentially rapidly changing stream. Users may in certain example embodiments specify policies to control this adaptation in certain example embodiments and, thus, in certain example instances, events (including events of special interest) may be handled appropriately, even in response to changing conditions.

Abstract: Runtime execution of one or more tasks defined in a workflow process language. The method may include obtaining a description of the task from a process ontology (PO). The PO may define a hierarchical taxonomy of executable tasks, where each task refers to at least one frame of a hierarchical frame taxonomy of the PO. The method may further include identifying at least one parameter as described in the frame description to which the task refers, resolving the value of the at least one parameter, and executing the most specific applicable version of the task contained in the task taxonomy of the process ontology.

Abstract: A method for the consistent control of policies assigned to objects of a service oriented architecture is disclosed. Each policy may include one or more assertions, and the method may include identifying one or more operational dependencies between at least two SOA objects, analyzing the assigned policies of the at least two SOA objects to determine any inconsistency, and issuing a warning to a user if an inconsistency has been determined.

Abstract: The present invention concerns a method for generating at least one processing specification (30) for a stream (10) of data items (100a, 100b, . . . , 100n) captured by a sensor (5), wherein the method comprises the following steps: a. generating a plurality of proposed window specifications (20) and generating the at least one processing specification (30) based on at least one of the proposed window specifications (20); b. wherein the plurality of proposed window specifications (20) is generated based on a similarity metric adapted for identifying similar pairs of data items (100a, 100b, . . . , 100n) in the stream (10) of data items.

Abstract: The present invention concerns a method for replicating one or more data items of a primary database system (10), the method comprising the following steps performed by the primary database system (10); a. providing replication data (102, 104) to at least one replication database system (20), the replication data (102, 104) being usable for replicating the one or more data items of the primary database system (10) by the at least one replication database system (20); and b. adding lock data (103) to the replication data (102, 104) sent in step a., wherein the lock data (103) relates to at least one lock on the one or more data items.

Abstract: The present invention concerns a method for mass-deleting a plurality of data records (20) from a database system (1), wherein the method comprises the following step performed during a processing of a mass delete request: a. creating (120) a data structure (40) comprising an identifier of each of the plurality of data records (20) to be deleted and inserting (130) a pointer to the data structure (40) into a transaction log(50) of the database system (1).