Abstract: A computer-implemented method is provided for defining interesting portions of a workflow of a business or other type of process. Using a tracking profile editor, a portion of a given workflow is selected and associated with a named process part. Items of payload data to be used in reports are selected from a message schema associated with the given workflow. A profile is generated based on the given workflow and the selected items of payload data. A tracking profile compiler receives the created tracking profile and generates a star schema, a flattened view and OLAP cube based on the tracking profile. An interceptor extracts monitored workflow events and stores event information to a tracking stream, based on the tracking profile. A tracking service extracts information pertaining to the monitored events from the tracking stream and stores the information in the queryable database. The OLAP cube and the flattened view are updated based on the information written to the queryable database.

Abstract: Validating executable data for interactions among a plurality of process artifacts at design time. A data context is created to include the plurality of process artifacts. The data context carries interaction rules among the plurality of process artifacts. The executable data from a data source is associated with the plurality of process artifacts in the created data context. A subset of the interaction rules is selected corresponding to at least one of the plurality of process artifacts. The associated executable data is validated when the associated executable data is in accordance with the selected subset of the interaction rules.

Abstract: A meta-model representing a business process. Operative expressions are defined for identifying the business process. The business process includes a plurality of activity sequences. Metadata is collected associated with the defined operative expressions. The collected metadata is formatted according to a schema. The meta-model representing the business process is provided to a user as a function of the formatted metadata and the defined operative expressions such that the user can interact with the business process using the defined operative expressions.

Abstract: Multi-dimensional aggregation on event streams for generating reports based on metadata about what events are available. An aggregation definition tool receives the event stream and, responsive to user input, identifies events of interest and specifies a correlation pattern for defining activities from the events. A user interface permits a user to define a desired dimensional structure of the reports and a mapping between data items in the events and the dimensional structure.

Abstract: Identifying a transaction from a real time event stream having latency. A method of the invention receives events from the real time event stream where events define a plurality of transactions to be identified. Each of the transactions includes a first event and a second event; the first event has a first latency relative to the real time event stream and the second event has a second latency relative to the real time event stream. The first event is identified from the received real time event stream, and a time is record when the first event is received. The method determines a time period during which the second event occurs as a function of the first latency, the recorded time of the first event, and the second latency. The transaction having the first and second events is identified based on the determined time period of the second event.

Abstract: Event data associated with state data corresponding to an instance of a process is collected by an interceptor associated with a server that performs an operation to modify the state data. The server performs a single transaction with the database to store both the modified state data and the associated event data, the transaction either succeeding or failing, whereby if the transaction succeeds, then both the state data and the event data are stored at the database, and if the transaction fails, then both the state data and the event data are not stored at the database. The event data stored at the database is then transmitted to a tracking service for conversion into a query-able format.

Abstract: System and method for identifying a pattern. A method of the invention compiles a pattern description where the pattern description defines a series of a first event and a second event relating to the first event. The first event is received and includes a type parameter data, a time parameter data, and a substance parameter data. A system of the invention includes a script component for associating or attaching a first script to the first event. The first script defines the type, time, and substance parameters of the second event as a function of the parameters of the first event according to the pattern description. A pattern recognition engine executes the attached first script and the executed script identifies the second event and thereby identifies the pattern.

Abstract: System and method for notifying a user of an occurrence of a defined condition in a process. The process includes a plurality of event records associated with the process; each of the plurality of event records includes a plurality of data fields having data relating to the process. A subset of the plurality of event records is defined where the subset relates to the defined condition. The data in the defined subset is updated at a predetermined time interval. The user is notified when the updated data of the defined subset indicates that the defined condition has occurred. The subset may alternatively be defined as a function of a current time, a last run time and the defined condition.

Abstract: A system and method for notifying a user of an event indicated by aggregated data relating to a status of activities, where the aggregated data is stored in a plurality of independently managed applications. An interface receives from the user an identification of an event relating to the aggregated data. The interface also receives from the user a threshold for the identified event. An aggregation component collects the aggregated data relating to the identified event. A notifying component notifies the user when the aggregated data collected by the aggregation component indicates that the threshold is satisfied. The system also includes a chronicle for recording values of past events and the notifying component notifies the user of the identified event as a function of the recorded values in the chronicle, aggregated data relating to the identified event and the threshold.

Abstract: Business activity management of monitoring multiple instances of a business activity and navigating business activity data in a distributed system. A system includes a plurality of databases storing data relating to multiple instances of a monitored business activity. A user interface receives a request from a user for business activity data independent of which database stores the requested data. An activity monitoring component for navigating to one of the databases as a function of defined relationships to retrieve the requested business activity data. The user interface displays the retrieved data to the user based on the user's permission.

Abstract: Instance data is transmitted for Payload/Milestone events and for Enable-Continuation events. Payload/Milestone event data contains information describing an instance and/or providing a time of one or more portions of the processing of an instance. Included in the Enable-Continuation event data is an identifier associated with an instance by a first application and an identifier associated with the same instance by another application. The identifiers are placed in a continuation data table which is used to index the appropriate record of an instance data table. Out-of-order data for an instance is hidden from view until sequentially prior data for the instance is received.

Abstract: A computer-implemented method is provided for defining interesting portions of a workflow of a business or other type of process. Using a tracking profile editor, a portion of a given workflow is selected and associated with a named process part. Items of payload data to be used in reports are selected from a message schema associated with the given workflow. A profile is generated based on the given workflow and the selected items of payload data. A tracking profile compiler receives the created tracking profile and generates a star schema, a flattened view and OLAP cube based on the tracking profile. An interceptor extracts monitored workflow events and stores event information to a tracking stream, based on the tracking profile. A tracking service extracts information pertaining to the monitored events from the tracking stream and stores the information in the queryable database. The OLAP cube and the flattened view are updated based on the information written to the queryable database.

Abstract: A computer-implemented method is provided for defining interesting portions of a workflow of a business or other type of process. Using a tracking profile editor, a portion of a given workflow is selected and associated with a named process part. Items of payload data to be used in reports are selected from a message schema associated with the given workflow. A profile is generated based on the given workflow and the selected items of payload data. A tracking profile compiler receives the created tracking profile and generates a star schema, a flattened view and OLAP cube based on the tracking profile. An interceptor extracts monitored workflow events and stores event information to a tracking stream, based on the tracking profile. A tracking service extracts information pertaining to the monitored events from the tracking stream and stores the information in the queryable database. The OLAP cube and the flattened view are updated based on the information written to the queryable database.

Abstract: A computer-implemented method is provided for defining interesting portions of a workflow of a business or other type of process. Using a tracking profile editor, a portion of a given workflow is selected and associated with a named process part. Items of payload data to be used in reports are selected from a message schema associated with the given workflow. A profile is generated based on the given workflow and the selected items of payload data. A tracking profile compiler receives the created tracking profile and generates a star schema, a flattened view and OLAP cube based on the tracking profile. An interceptor extracts monitored workflow events and stores event information to a tracking stream, based on the tracking profile. A tracking service extracts information pertaining to the monitored events from the tracking stream and stores the information in the queryable database. The OLAP cube and the flattened view are updated based on the information written to the queryable database.

Abstract: In a method and system for debugging a program, a debugging module is loaded into a normal thread of execution of the program. A user may then send commands to the debugger module from a command console module operating in a safe separate process. The debugger module receives the commands and converts them into function calls to objects that are accessible by the program. This allows the user to interact manually with the objects and achieve substantially the same responses from the object as the program itself would have obtained during its normal execution. Thus the user can effectively debug the program without having to know the internal structure of any of its constituent objects.

Abstract: A system and method of remotely debugging an orchestration service instance providing a means for establishing a communications connection with a computer, wherein the computer is executing a business process service instance. Stored tracking information regarding the orchestration service instance is read, and the orchestration service instance is remotely debugged by way of the communications connection and according to the stored tracking state information.

Abstract: Multiple aggregation groups, which can be multiple partitions in an aggregated data table, are formed. Each group includes multiple aggregation records; each aggregation record includes an aggregation of values contained by a different subset of multiple database records. While an aggregation group is accessed by a single program thread during an aggregation group update transaction, no other threads are allowed to access that group. The aggregation groups are combined into a single table of aggregation records. Each of the multiple database records may correspond to an instance of an organizational activity and include a field having a value indicating the corresponding instance to be in one of several process states. Each aggregation group may further include time-sorted aggregation records, each time-sorted aggregation record containing an aggregation value for instances in one of the several process states during a time period associated with the time-sorted aggregation record.

Abstract: Challenges associated with maintaining information about multiple instances of an activity are addressed. Separate database tables are maintained for data corresponding to active instances of an organization's activities and for data corresponding to inactive instances of an organization's activities. Multiple database tables can be maintained for data corresponding to inactive instances of an activity. In another aspect, data from the active instances table and one or more inactive instances tables are processed to generate combined analysis data.

Abstract: A computer-implemented method is provided for defining interesting portions of a workflow of a business or other type of process. Using a tracking profile editor, a portion of a given workflow is selected and associated with a named process part. Items of payload data to be used in reports are selected from a message schema associated with the given workflow. A profile is generated based on the given workflow and the selected items of payload data. A tracking profile compiler receives the created tracking profile and generates a star schema, a flattened view and OLAP cube based on the tracking profile. An interceptor extracts monitored workflow events and stores event information to a tracking stream, based on the tracking profile. A tracking service extracts information pertaining to the monitored events from the tracking stream and stores the information in the queryable database. The OLAP cube and the flattened view are updated based on the information written to the queryable database.