Patent application number | Description | Published |
20100146243 | Transaction Aware, Flexible Interface For A State Correlation And Transition Execution Engine - The subject matter disclosed herein provides methods and apparatus, including computer program products, for state alignment and transaction coupling to enable reliable communication between an application, such as a backend system, and a correlation engine (or rules engine). In one aspect there is provided a method. The method may provide a first interface to receive information from an adapter for an application separate from a state correlation engine and provide a second interface to receive information from the state correlation engine to the adapter. The first and second interfaces may provide state alignment between the application and the state correlation engine. Related systems, apparatus, methods, and/or articles are also described. | 06-10-2010 |
20100153345 | Cluster-Based Business Process Management Through Eager Displacement And On-Demand Recovery - Methods and apparatus, including computer program products, are provided for transporting processes within a distributed computing system, such as a cluster. In one aspect, the computer-implemented method may receive an event at a first node. The event may correspond to a process instance for handling the received event. The process instance may be transported from a second node to the first node. The process instance may be transported from a persistence when the process instance is inactive and, when the process instance is active, the process instance may be persisted to enable transport to the first node. Related apparatus, systems, methods, and articles are also described. | 06-17-2010 |
20100153481 | Failover Mechanism For Distributed Process Execution - Methods and apparatus, including computer program products, are provided for distributed process execution. In one aspect, the computer-implemented method may provide an indication announcing that a structural change to the cluster will occur. The indication may enable at least one node of the cluster to respond with an existing view. The existing view may include a first set of authoritative data representing existing processes handled at the at least one node. The method may also include providing, to at least one of the nodes, an index representing a subsequent view of the cluster after the structural change. The subsequent view may include a second set of authoritative data representing processes handled at the at least one node after the structural change. The method may also activate the subsequent view of the cluster. Related apparatus, systems, methods, and articles are also described. | 06-17-2010 |
20110154301 | Multidimensional Debugger - A computer system for programming applications in a programming environment, including, a computer adapted to execute software to form a programming environment enabling creation of a software application using multiple programming languages, a multidimensional debugger installed on the computer; wherein the multidimensional debugger is made up from two or more debuggers each for use in debugging a different programming language, wherein the two or more debuggers use a common work memory to share information; and wherein the two or more debuggers use a common user interface. | 06-23-2011 |
20120072884 | CONVERTING BUSINESS PROCESS MODELS TO COMPONENT MODELS IN A SERVICE ORIENTED ARCHITECTURE DOMAIN - Process artifacts and elements in a business process model, such as a Business Process Modeling Notation (BPMN) compliant model, may be analyzed, converted into component model building blocks for developing applications, and enriched with technical metadata. The component model building blocks may be Service Component Architecture (SCA) Assembly Model building blocks, which may include artifacts, components, composites, and other elements. The building blocks may be structured in an output file, which may be a Simple Capabilities Description Language (SCDL) file, according to the Service Component Architecture (SCA) Assembly Model based on an order provided in the business process model. Business process model elements may be mapped to corresponding component model building blocks, such as SCA artifacts, composites, or components, through a lookup table or database. | 03-22-2012 |
20120110583 | DYNAMIC PARALLEL LOOPING IN PROCESS RUNTIME - Systems and methods for dynamic parallel looping in process runtime environment are described herein. A currently processed process-flow instance of a business process reaches a dynamic loop activity including a repetitive task to be executed with each loop cycle. A predefined expression is evaluated on top of the current data context of the process-flow instance to discover a number of loop cycles for execution within the dynamic loop activity. A number of parallel activities corresponding to the repetitive task recurrences are instantiated and executed in parallel. The results of the parallel activities are coordinated to confirm that the dynamic loop activity is completed. | 05-03-2012 |
20120130906 | DEPLOYMENT MECHANISM FOR NON-VERSIONING BUSINESS PROCESS ARTIFACTS - According to some embodiments, it may be detected that a deployment archive to be deployed to a runtime server includes first and second business process artifacts, wherein the first artifact supports versioning and the second artifact does not support versioning. A version identifier to be associated with the second artifact may then be calculated, and at least one prior version identifier of the second artifact, associated with at least one prior deployment of the deployment archive to the runtime server, may be determined based on information from a version history database. The deployment archive containing the first and second artifacts may then be deployed to the runtime server along with the prior versions of the second artifact associated with the determined prior version identifiers. A new version history may then be stored in the version history database by adding the newly calculated version identifier to the at least one determined prior version identifier. | 05-24-2012 |
20120284287 | Systems and Methods for Business Process Logging - The present disclosure involves systems, software, and computer implemented methods for filtering business process logging information at runtime. One process includes receiving a set of logging information associated with execution of at least one entity, the at least one entity associated with a business process model defining a set of business process entities for performing a defined business process, identifying a process log filter rule associated with the entity, applying the identified process log filter rule to the received set of logging information to generate a filtered set of logging information associated with execution of the entity, and storing the filtered set of logging information in a process log associated with the execution of the entity. Identifying a process log filter rule associated with the entity can include identifying an entity property and determining at least one process log filter rule corresponding to the identified entity property. | 11-08-2012 |
20120284316 | SYSTEMS AND METHODS FOR BUSINESS PROCESS LOGGING - The present disclosure involves systems, software, and computer implemented methods for assigning business process logging granularities. One process includes identifying a business process model where the business process model defines a set of business process entities operable when executed to perform a defined business process, identifying a logging granularity rule set associated with the identified business process model, determining at least one entity property associated with at least one business process entity in the identified business process model, and automatically assigning the at least one business process entity in the identified business process model with a logging granularity level associated with the at least one determined entity property based at least in part on the identified logging granularity rule set. The logging granularity levels can correspond to an amount of logging-related information to be collected at runtime for a particular business process entity. | 11-08-2012 |