Abstract: A method and system for validating business solutions by evaluating the business services from which the solution is composed, aggregating these evaluations in accordance with a service composition structure, and comparing the aggregated evaluation to target objectives for the business solution, where the service evaluations and the target objectives use the same metrics, which are surrogates for the business solution objectives. A business solution has a Business Level Agreement (BLA) which states business objectives. A business service has a Business Service Level Agreement (BSLA) which states operational objectives. A business solution is seen as a composition of business services. Therefore, the BLA is validated by evaluating and then aggregating the BSLA's for all business services from which the business solution is composed, and then comparing the aggregation against target values of the surrogates.

Abstract: A hybrid approach for capturing meta data about Business Processing Monitoring (BPM) artifacts is based on a combination of a relational meta data model and a semantic net. Meta data about metrics and situations and their dimensional context are first captured in the method. Then, relational meta data are used to describe a generic data schema for metrics, situations and their dimensional context. The meta data from semantic nets are used to extend the meta data definitions. Data from a data warehouse are searched and managed with the schema described and managed with the relational and semantic net meta data.

Abstract: A method is provided for systematic and dynamic configuration of an On Demand Operating Environment (ODOE) and the business solutions built upon the ODOE. The method provides a configuration specification that defines an On Demand Configuration Language (ODCL). An editor enables the business user to describe the consistency constraints applicable to the business in terms of the ODCL. This language is then used to transform the high-level business consistency constraints to low-level configuration parameters applicable to services and hosted business solutions in the ODOE. These services and hosted business solutions are organized into a plurality of layers to facilitate development of the configuration specification and better enable controls over consistent implementation of configuration changes. A two phase configuration commitment protocol is provided to ensure the consistent implementation of interdependent configuration parameters applicable to the services and hosted business solutions within the ODOE.

Abstract: An enterprise system includes a plurality of artifacts (e.g., persons, objects, databases, autonomous elements, intelligent agents, information systems, etc), and a smart distance (e.g., a distance which may optimize the performance of the enterprise system) between the plurality of artifacts.

Abstract: Automomic business processes management solutions have capabilities to adapt themselves to changes in the business environment. These autonomic business solutions are built by wiring together autonomic solution components called BPbots (Business Process robots). BPbots are granular solution components representing an aspect of a business process. In general, BPbots consist of two parts, an execution module and a managerial module. The execution module represents the standard, non-autonomic solution component, such as a standard process flow model describing the long-running flow or business adapter describing the communication of the solution with service providers (such as applications). The managerial module is responsible for the autonomic behavior of the BPbot. The managerial component has the ability to monitor the execution module, analyze the performance, plan new, more appropriate execution patterns and change the behavior of the execution module according to the new plan.

Abstract: A method and system for enterprise monitoring maps monitor events to elements of a component business model of the enterprise and displays the mapped events using the component business model. Rules are used to determine whether events captured from a monitor source are monitor events. An enterprise monitor metamodel linking monitor artifacts and elements of a component business model is used to annotate monitor events with data from the component business model of the enterprise.

Abstract: A model-driven and QoS-aware infrastructure facilitates the scalable composition of Web services in highly dynamic environments. An exception management framework supports two modes of exception management for business processes, providing a novel policy-driven approach to exception management implemented in the system infrastructure. Exception management is implemented in the system infrastructure, with exception handling policies supplied by individual business processes. Using the exception management framework, developers define exception policies in a declarative manner. Before a business process is executed, the service composition middleware integrates the exception policies with normal business logic to generate a complete process schema. This policy driven-approach can significantly reduce the development time of business processes through its separation of the development of the business logic and the exception handling policies.

Abstract: A managed policy driven virtual data space for managing artifacts relationships and sharing artifacts among services. A policy model is used to represent business artifacts, sharing of the artifacts, and subscription of other artifacts that is of interest to current artifact and, to represent the various state of the artifact. An active shared space provides support functionality for the policy model, such as artifact lifecycle management. The active shared space also provides the support of sharing of such artifact with external/internal services and other artifacts. The active shared space also controls the artifacts storage in the relational database for archiving purposes. Active shared space also provides the mechanism of subscribing to various artifacts and publishing the availability of artifact for services and other artifacts itself.

Abstract: Meta-Rules are a special set of business rules whose purpose is to enable business rules selection and subsequent rule invocation by a business rules manager. Contained within a Meta-Rule are business policy and other information that enables the selection of a business rule used by a business application. Meta-rules allow the system to dynamically select and identify specific business rules to be executed within a given business application. By enabling a higher level of abstraction, and relying on rules to resolve specific business rule selection and invocations, Meta-rules further separate the binding of business knowledge and practice from application programming logic. The application programmer is freed from having specific knowledge of the business rule; all that is required is an assertion that a rule is to be used.

Abstract: Systems and methods for monitoring and controlling business level SLAs (Service level Agreements), and more particularly, systems and method for monitoring and controlling business level SLAs using probe points, KPIs (Key Performance Indicators) and business commitments. An XML (extensible Markup Language)-based specification referred to as BPCL (Business Process Commitment Language) is used to describe business commitments. BPCL specifications are used by a business process management (BPM) system to configure, monitor, and control business processes based on business commitments. Business Commitments and BPCL provide a path toward model-based management for dynamic e-business solutions.

Abstract: An architecture, system, and method are provided for a commitment loop solution for on demand business activity management. A Business Performance Management (BPM) loop is defined as a set of nodes each relating to different tasks for processing performance management trigger data generated by a business entity in real time, where the beginning or sensing element of the loop is triggered by a token (representing a business event from a business process) and the ending or executing element provides a business action to be implemented by the business entity. The token is passed from node to node sequentially in a particular order around the loop. Processing of the data represented by the token is governed by policies, which can be changed dynamically and follow a life cycle. On demand business activity management of larger aggregates of business entities (i.e.

Abstract: A system, method, and computer readable medium for reducing message flow on a message bus are disclosed. The method includes determining if at least one logical operator in a plurality of logical operators requires processing on a given physical processing node in a group of physical nodes. In response to determining that the logical operator requires processing on the given physical processing node, the logical operator is pinned to the given physical processing node. Each logical operator in the plurality of logical operators is assigned to an initial physical processing node in the group of physical processing nodes on a message bus.

Abstract: Systems and methods for monitoring and controlling business level SLAs (Service level Agreements), and more particularly, systems and method for monitoring and controlling business level SLAs using probe points, KPIs (Key Performance Indicators) and business commitments. An XML (extensible Markup Language)-based specification referred to as BPCL (Business Process Commitment Language) is used to describe business commitments. BPCL specifications are used by a business process management (BPM) system to configure, monitor, and control business processes based on business commitments. Business Commitments and BPCL provide a path toward model-based management for dynamic e-business solutions.

Abstract: A method and apparatus are disclosed for correlating structured event data, comprising the steps of selecting aggregation elements and creating a structured template utilizing the selected aggregation elements. The structured event data is then translated to name-value pair sets based on the structured template. In one exemplary embodiment, the structured template is created by searching the structured event data for repeatable node-value pairs. In one aspect of the invention, a region tree is created, wherein intermediate nodes represent shared fragments, leaf nodes represent regions, and wherein regions are a unique set of nodes whose sub-tree can have multiple occurrences. In another aspect of the invention, the translation of the structured event data comprises the steps of parsing the structured event data in depth first search order; and forming regions based on an aggregation element set.

Abstract: A managed policy driven virtual data space for managing artifacts relationships and sharing artifacts among services. A policy model is used to represent business artifacts, sharing of the artifacts, and subscription of other artifacts that is of interest to current artifact and, to represent the various state of the artifact. An active shared space provides support functionality for the policy model, such as artifact lifecycle management. The active shared space also provides the support of sharing of such artifact with external/internal services and other artifacts. The active shared space also controls the artifacts storage in the relational database for archiving purposes. Active shared space also provides the mechanism of subscribing to various artifacts and publishing the availability of artifact for services and other artifacts itself.

Abstract: A method and system for enterprise monitoring maps monitor events to elements of a component business model of the enterprise and displays the mapped events using the component business model. Rules are used to determine whether events captured from a monitor source are monitor events. An enterprise monitor metamodel linking monitor artifacts and elements of a component business model is used to annotate monitor events with data from the component business model of the enterprise.

Abstract: A method (and structure) of querying one or more Web-based data sources, includes receiving a query statement including at least one query, parsing the input query to identify a target data source for each query, and dispatching each query to a respective one of the data sources for a target data source search. The query statement further includes an aggregate operator defining at least one logical operation to be performed on a result returned from the target data source searches.

Abstract: A method (and system) of adaptive action management for business solutions includes detecting a business situation, adaptively deciding an action for a detected business situation using information from a knowledge base, and invoking an action service for implementing the action.

Abstract: A method, system, and computer program product for associating events. A provided event dataset includes events occurring in each of N successive time intervals (N?3). Association rules pertaining to successive events in the event dataset are deduced. Sequences of events are generated from the association rules. Clusters of the sequences of events are formed. Sequences of the clusters are created. The clusters of the sequences may be used: to identify at least one event occurring in a time interval of the N time intervals as being a probable cause of at least one event occurring in a later-occurring time interval of the N time intervals; or to predict an occurrence of at least one event in a time interval occurring after the N time intervals, wherein the at least one event had occurred within the N time intervals.

Abstract: A hybrid approach for capturing meta data about Business Processing Monitoring (BPM) artifacts is based on a combination of a relational meta data model and a semantic net. Meta data about metrics and situations and their dimensional context are first captured. Then, relational meta data are used to describe a generic data schema for metrics, situations and their dimensional context. The meta data from semantic nets are used to extend the meta data definitions. Data from a data warehouse are searched and managed with the schema described and managed with the relational and semantic net meta data.