Abstract: A method and system for staging in a cloud environment defines a default stage for integration flows. An integration flow is defined by (a) stages including (i) a live stage to follow the default stage, (ii) additional stages between the default and live stages, and (b) endpoint definitions for the live and additional stages. In response to an instruction to promote the integration flow, the integration flow is load balanced by allocating each stage to execution environment(s). Then, the integration flow is run in the execution environment(s). The load balancing includes, for each stage, (i) retrieving a list of execution environments which are available for execution of stages, (ii) selecting execution environment(s) on which to execute the stage and updating the list of available execution environments to indicate that the selected execution environment(s) is allocated, and (iii) storing the selected execution environment(s) as specific to the stage.

Abstract: At least one processing specification is generated for a stream of data items captured by a sensor. A plurality of proposed window specifications is generated. The at least one processing specification is generated based on at least one of the proposed window specifications. The plurality of proposed window specifications being generated based on a similarity metric is configured to identify similar pairs of data items in the stream of data items.

Abstract: A method and system for staging in a cloud environment defines a default stage for integration flows. An integration flow is defined by (a) stages including (i) a live stage to follow the default stage, (ii) additional stages between the default and live stages, and (b) endpoint definitions for the live and additional stages. In response to an instruction to promote the integration flow, the integration flow is load balanced by allocating each stage to execution environment(s). Then, the integration flow is run in the execution environment(s). The load balancing includes, for each stage, (i) retrieving a list of execution environments which are available for execution of stages, (ii) selecting execution environment(s) on which to execute the stage and updating the list of available execution environments to indicate that the selected execution environment(s) is allocated, and (iii) storing the selected execution environment(s) as specific to the stage.

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 concern an analysis system for analyzing at least one continuous query for at least one input data stream. The at least one input data stream includes a sequence of events captured by at least one sensor. The debugging system includes an analyzer for executing the at least one continuous query and at least one modified continuous query on the at least one input data stream, for comparing at least one output data stream produced by the at least one continuous query with at least one second output data stream produced by the at least one modified continuous query, and for indicating at least one difference between the at least one output data stream and the at least one second output data stream. The analyzer synchronizes the execution of the at least one continuous query and the at least one modified continuous query.

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: The present invention concerns an analysis system (1) for analyzing at least one continuous query (100) for at least one input data stream (200), wherein the at least one input data stream (200) comprises a sequence of events captured by at least one sensor and wherein the debugging system comprises: a. an analyzer (10), adapted for executing the at least one continuous query (100) and at least one modified continuous query (100?) on the at least one input data stream (200), for comparing at least one output data stream (300) produced by the at least one continuous query (100) with at least one second output data stream (300?) produced by the at least one modified continuous query (100?) and for indicating at least one difference between the at least one output data stream (300) and the at least one second output data stream (300?); b. wherein the analyzer (10) is adapted for synchronizing the execution of the at least one continuous query (100) and the at least one modified continuous query (100?).

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 invention concerns a SOA-registry (1) for the automatic deployment of at least one SOA-application onto at least one platform, the at least one SOA-application comprising one or more components, the SOA-registry (1) comprising: a. at least one SOA-application description (A1) being related to one or more abstract component descriptions (AC1, AC2, AC3) describing the components of the at least one SOA-application; b. at least one concrete component description (CC11, CC12, CC21, CC22, CC31) for each of the one or more abstract component descriptions (AC1, AC2, AC3), the at least one concrete component description (CC11, CC12, CC21, CC22, CC31) comprising one or more requirements of the respective component on a target platform; and c. at least one platform descriptor (P1, P2) comprising one or more properties of the at least one platform.

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: An application framework for composing applications involving a plurality of webservices. The application framework comprises: 1) a layout editor adapted to create a graphical user interface of an application comprising a plurality of pages, each page comprising at least one element for interaction with a user to generate or modify a set of data; 2) a control layer editor, adapted to create for each page of the graphical user interface a corresponding code fragment receiving and processing the set of data relating to the respective page; and 3) a generator generating an orchestration sequence from the plurality of code fragments, wherein the processing of the orchestration sequence by an engine involves the invoking of the plurality of webservices.