Abstract: This system detects and corrects looping problems in a publish-subscribe messaging network. This system requires a token which uniquely identifies a node in this network or universally unique in this messaging network. This system maintains a list of Universally Unique Identifiers (UUID) as a metadata attached to each publish-subscribe message (“publication”). As a node forwards a publication to another node, it is required to append its own UUID to this list or discard the message if its UUID already is in the attached list. Several nodes could form a broker cooperative aggregate node and have a unique identifier for all the nodes in the cooperative if they have an internal mechanism for preventing publication looping.

Abstract: A tracking system includes a business system using a plurality of application modules each including a computer for processing a transaction including a plurality of steps. A messaging system includes a messaging computer program embodied in a computer readable medium in each of the computers for communicating between the computers. The messaging system generates queues of messages being communicated between the computers. The messaging system can be configured by an administrator to generate tracking data about the messages being communicated between the computers. A tracking module is included in one of the computers, and has the messaging computer program and a tracking computer program embodied in the computer readable medium for specifying status data for retrieval from the messaging queues, receiving the status data from the messaging queues into a tracking queue, and storing the status data in a data storage system.

Abstract: Provided are methods, data processing systems, recovery components and computer programs for recovering from storage failures affecting data repositories. At least a part of the recovery processing is performed while the data repositories are able to receive new data and to allow retrieval of such new data. Although new data items may be received into the repository and retrieved therefrom during recovery processing, updates to the data repository which were performed before the failure and which are then restored to the repository by the recovery processing are restored within a recovery unit of work and are inaccessible to processes other than the recovery process until successful completion of the recovery unit of work. The recovery processing ensures that the recovered repository is consistent with the state of the repository at the time of the failure, but is available for addition and retrieval of new data items before completion of the recovery processing.

Abstract: Method for logging diagnostic information, for use in a transactional environment having function for sending a transactional and re-sendable request to an application program. A counter is associated with the request, wherein a value associated with the counter is updated when an error occurs in the environment. The environment also comprises a counter threshold. The method utilizes a comparator, responsive to sending the request, for comparing the value associated with the counter against the counter threshold; a tracing control component, responsive to the value associated with the counter meeting the counter threshold, for enabling a tracing program; and a logging component, responsive to re-sending the request, for logging diagnostic information generated by the tracing program.

Abstract: A method for providing atomicity for a unit of work involving a plurality of participants, the method comprising the steps of: sending a prepare request to at least one participant, wherein the request comprises data required for recovery prurposes of the unit of work; and on recovery of the unit of work, recovering the unit of work comprising: obtaining the data from the at least one participant; and using the obtained data to recover and preserve the atomicity of the unit of work.

Abstract: A computer system with a first messaging application communicates a message to another computer system with a second messaging application via a coupling facility storage device. If the message does not exceed a predetermined threshold, the message is put onto the queue in the coupling facility. If the message does exceed a predetermined threshold, the message is put onto a log associated with the first messaging application and readable by the second messaging application. A pointer to the message is put onto the queue in the coupling facility. The pointer can be used to access the message in the log.

Abstract: A system, method, apparatus, and computer program product uses at least one of a plurality of message transmitters to achieve high availability message transmission. The plurality of message transmitters are each operable to transmit a message to a subscriber. In accordance with a determination, for example, of the value of the connections, the message is copied and transmitted to the plurality of the message transmitters so that at least one of the plurality of message transmitters transmits the copy to the subscriber. The at least one message transmitter may be selected by analyzing the message and determining an associated rule based on characteristics of the message.

Abstract: A tracking system includes a business system using a plurality of application modules each including a computer for processing a transaction including a plurality of steps. A messaging system includes a messaging computer program embodied in a computer readable medium in each of the computers for communicating between the computers. The messaging system generates queues of messages being communicated between the computers. The messaging system can be configured by an administrator to generate tracking data about the messages being communicated between the computers. A tracking module is included in one of the computers, and has the messaging computer program and a tracking computer program embodied in the computer readable medium for specifying status data for retrieval from the messaging queues, receiving the status data from the messaging queues into a tracking queue, and storing the status data in a data storage system.

Abstract: A method for detecting and correcting looping problems in a publish-subscribe messaging network is disclosed. The messaging network requires a token which uniquely identifies a node in this messaging network or universally unique in this messaging network. The messaging network maintains a list of Universally Unique Identifiers (UUID) as a metadata attached to each publish-subscribe message (“publication”). As a node forwards a publication to another node, it is required to append its own UUID to this list or discard the message if its UUID already is in the attached list. Several nodes could form a broker cooperative aggregate node and have a unique identifier for all the nodes in the cooperative if they have an internal mechanism for preventing publication looping.

Abstract: A method for resolving a unit of work involving a plurality of participants, the method comprising the steps of: generating logic comprising an identifier generator; aggregating the logic with an owning application of a unit of work; and in response to the owning application initiating the unit of work, generating, by the identifier generator, an identifier associated with the unit of work.

Abstract: Methods, apparatus and computer programs for flexible topic identification in a publish/subscribe communications network. Publishers and subscribers are able to specify their intentions regarding the topic classification schemes to be used by a publish/subscribe broker during subscription matching, and the broker is responsive to the specified intentions of either or both of the publisher or the subscriber to invoke a respective subscription matching component. The invoked matching components each implement a subscription matching process that is consistent with a specified topic classification scheme.

Abstract: A method for resolving a unit of work involving a plurality of participants, for use in a publish/subscribe system having a plurality of participants that subscribe to a first topic and at least one component having access to an outcome associated with the unit of work. The component publishes, to the first topic, a first message comprising a first outcome associated with the unit of work. If there is a failure associated with a first participant, a second participant use the published outcome to recover the unit of work.