Abstract: An information processing system comprises a legacy application, a web services consumption copybook, and a set of application program interfaces for enabling the legacy application to access a selected web service via a web services consumption server. The web services consumption copybook represents data structures of the selected web service. The system can either connect to or include a set of web service proxies that each correspond to a web service available via a network connection. A web services consumption server is optionally used to route service requests from the application to the appropriate web service proxy. The system can also optionally include a developer tool for adapting legacy systems or environments to be able to consume web services using modern protocols thus allowing the migration of legacy subsystems to a networked loosely-coupled environment.

Abstract: A system and method for constructing and deploying a business activity monitoring (BAM) dashboard associated with an event-based process are disclosed. A configuration module receives an event-based process identifier for an event-based process and data, such as inputs or outputs, for the event-based process. A generation module then generates a dashboard description that includes the identifier and an associated dashboard template having one or more dashboard components. This dashboard description is used by a dashboard server to automatically generate a BAM dashboard for monitoring the event-based process by using the association between the dashboard template and the event-based process to display data associated with the event-based process using one or more dashboard components.

Abstract: A system providing a reproducible package of a web service scenario having at least one web service client and at least one web service coupled to said network. A collector extracts a set of message exchanges between the web service client and the web service, and a closure builder captures a service description. A workspace repository coup stores the set of message exchanges and the service description to create the reproducible package of the web service scenario. According to one embodiment, the reproducible packages provide mechanisms to share and replay XML message-based scenarios for distributed applications.

Abstract: A system and method for constructing and deploying a business activity monitoring (BAM) dashboard associated with an event-based process are disclosed. A configuration module receives an event-based process identifier for an event-based process and data, such as inputs or outputs, for the event-based process. A generation module then generates a dashboard description that includes the identifier and an associated dashboard template having one or more dashboard components. This dashboard description is used by a dashboard server to automatically generate a BAM dashboard for monitoring the event-based process by using the association between the dashboard template and the event-based process to display data associated with the event-based process using one or more dashboard components.

Abstract: In a preferred embodiment of the present invention, the replication horizon and other data propagation-related information is tracked through the use of a “pulse” and “echo” approach.

Abstract: A compliance system for design and testing of web services, having an artifact repository storing a set of artifacts and coupled to a runtime engine. The runtime engine includes a rules engine, a results processor and a manager interface, wherein the runtime engine applies a set of encoding requirements to the set of artifacts and a conformance output is generated.

Abstract: A fault-tolerant messaging system comprises a primary broker, a first network, a back up broker, and a second network. The primary broker and the back up broker are coupled to the first network for communication with clients thus creating a messaging system. The primary broker and the back up broker are also coupled to the second network for replicating state from the primary broker and the back up broker, and also sending transaction events immediately to maintain synchronization. The brokers further comprise a replication module for communicating state between the primary broker and the back up broker, a recovery module for performing recovery on the back up broker upon failure of the primary broker, and a fault-tolerant connection module for establishing a fault-tolerant connection between the primary broker and the back up broker over the second network. The present invention also includes a number of novel methods for performing fault tolerance.

Abstract: Transactional database replication techniques are disclosed that do not require altering of the database management system implementation. A replicator module includes a dynamic membership manager, which is configured to manage the persistent membership of a coordination group. The persistent membership can be, for example, a durable set of sites that can replicate changes amongst themselves. Changes from sites not in the persistent membership are discarded. The set of recovered members is a subset of the persistent membership. The persistent membership changes incrementally by either removing or adding members. Failed members may still be part of the persistent membership. The dynamic membership manager module manages the modification of the persistent membership, initialization of replicas, and propagation of membership information.

Abstract: A system integrator for modeling an object instance of a COBOL data set, the object instance including representations of OCCURS DEPENDING ON clauses or REDEFINE clauses. The system comprises a client interface module, an import module, an object model module and modeler module. The client interface module generates an interface and receives a copybook selection and a set of REDEFINE criteria. The import module receives the copybook selection and imports a copybook from a database. The object model module receives the copybook and the set of REDEFINE criteria, and creates a customized object model for the copybook. The modeler module receives the customized object model and a set of COBOL data, and forms an object instance equivalent to the set of COBOL data, the object instance including representations of a OCCURS DEPENDING ON clause or REDEFINE clause.

Abstract: An information processing system comprises a legacy application, a web services consumption copybook, and a set of application program interfaces for enabling the legacy application to access a selected web service via a web services consumption server. The web services consumption copybook represents data structures of the selected web service. The system can either connect to or include a set of web service proxies that each correspond to a web service available via a network connection. A web services consumption server is optionally used to route service requests from the application to the appropriate web service proxy. The system can also optionally include a developer tool for adapting legacy systems or environments to be able to consume web services using modern protocols thus allowing the migration of legacy subsystems to a networked loosely-coupled environment.

Abstract: Techniques are disclosed for debugging heterogeneous applications in a distributed environment. In one embodiment, an architecture for debugging heterogeneous applications in a distributed environment is configured to enable both location transparency and dynamic exposure of service state. Regardless of where the physical application state resides, the architecture describes or otherwise provides a mechanism that allows seamless debugging and troubleshooting of distributed applications. The location of the state is transparent to the debugger and the application being debugged. In addition, the architecture enables an individual service to expose its state dynamically at run-time. It is possible for the service to expose its state in a self-describing fashion, allowing service state to be exposed in the architecture regardless of the service environment.

Abstract: A system and a method for capturing, storing and replaying data describing application of an event-based process to an event are described. As an event processing engine processes an input event, specified data is captured by a store monitor included in the event processing engine. Hence, while the event processing engine processes an input event, data describing the event processing is contemporaneously captured without affecting processing of the input event. The captured data is then stored for later access and can be used later simulate or analyze the event processing. In one embodiment, the stored data is also classified or grouped based on one or more grouping criteria (e.g., event type, timestamp) to simplify later access to the data.

Abstract: Application-level replication, the synchronization of data updates within a cluster of application servers, may be provided by having application servers themselves synchronize all updates to multiple redundant databases, precluding the need for database-level replication. This may be accomplished by first sending a set of database modifications requested by the transaction to a first database. Then a message may be placed in one or more message queues, the message indicating the objects inserted, updated, or deleted in the transaction. Then a commit command may be sent to the first database. The set of database modifications and a commit command may then be sent to a second database. This allows for transparent synchronization of the databases and quick recovery from a database failure, while imposing little performance or network overhead.

Abstract: The present invention enables desktop applications to access web services through Plug-ins and a Web Service Proxy Server. An administrator registers a web service by providing the URL of the WSDL file of the web service. The target desktop applications and the operations are identified using the WSDL file. Operations that are not compatible with the desktop applications are removed from a published list of operations. The administrator appends additional formatting information, communication standards and security policies to the WSDL file. A user accessing the web services is first authenticated and authorized. Thereafter, the user accesses the web services through Web Service Proxy Server. The communication with the web services complies with the standards and security policies specified in the WSDL files. The output data obtained from the web services are presented using template documents. These template documents are generated based on the formatting information provided in the WSDL files.

Abstract: Application-level replication, the synchronization of data updates within a cluster of application servers, may be provided by having application servers themselves synchronize all updates to multiple redundant databases, precluding the need for database-level replication. This may be accomplished by first sending a set of database modifications requested by the transaction to a first database. Then a message may be placed in one or more message queues, the message indicating the objects inserted, updated, or deleted in the transaction. Then a commit command may be sent to the first database. The set of database modifications and a commit command may then be sent to second database. This allows for transparent synchronization of the database and quick recovery from a database failure, while imposing little performance or network overhead.

Abstract: Techniques suitable for facilitating communications between various computer programs operating on various nodes in a distributed computing environment are disclosed. The techniques can be used by a traffic manager operating in such environments. The traffic manager is capable of monitoring traffic exchanged between client and server programs operating in the distributed computing environment. Moreover, the traffic manager can be used to implement a variety of desirable features across different computing environments. These computing environments are typically separated by one or more distinguishing characteristics. As will be appreciated, the traffic manager provides an integral and cost effective solution which can bridge these distinguishing characteristics as well as define and enforce policies across disparate computing environments. This is achieved by centralizing the generation of interfaces which allow interaction between any of the nodes in a distributed computing system.

Abstract: Transactional database replication techniques are disclosed. The techniques can be realized in many ways, such as in a replicator module that can be instantiated at each site in a distributed system. The techniques support a variety of data storage technologies such as traditional durable transactional databases as well as in-memory data storage systems, and a variety of data types such as relational, flat file, XML, and object-oriented data. Guaranteed levels of distributed transactional data consistency for both reads and writes are enabled for database applications. The techniques also support the ability of applications distributed across a network to perform updates concurrently, and the ability to replicate many standard database systems without needing to modify their intrinsic behavior or needing them to be aware of the replicator, and the ability to tolerate network and process failures without any change to the data consistency guarantees provided to the applications.

Abstract: Transactional database replication techniques are disclosed that do not require altering of the database management system implementation. A replicator module includes a dynamic membership manager, which is configured to manage the persistent membership of a coordination group. The persistent membership can be, for example, a durable set of sites that can replicate changes amongst themselves. Changes from sites not in the persistent membership are discarded. The set of recovered members is a subset of the persistent membership. The persistent membership changes incrementally by either removing or adding members. Failed members may still be part of the persistent membership. The dynamic membership manager module manages the modification of the persistent membership, initialization of replicas, and propagation of membership information.

Abstract: Transactional database replication techniques are disclosed that do not require altering of the database management system implementation. A replicator module includes a dynamic membership manager, which is configured to manage the persistent membership of a coordination group. The persistent membership can be, for example, a durable set of sites that can replicate changes amongst themselves. Changes from sites not in the persistent membership are discarded. The set of recovered members is a subset of the persistent membership. The persistent membership changes incrementally by either removing or adding members. Failed members may still be part of the persistent membership. The dynamic membership manager module manages the modification of the persistent membership, initialization of replicas, and propagation of membership information.

Abstract: Newly added, deleted, or changed data of a local storage in a distributed database system is prevented from being replicated until it has been approved via a specific process. Any new, deleted, or changed records are initially marked as being candidate data. The normal replication processing within the distributed database system ignores such data. In this way, the candidate data is not allowed to leave its source site, and potentially contaminate the rest of the replication network, until that data has been approved. The approval process is provided by a candidate data scanner that detects the candidate data and provides it to a candidate data resolver for processing. The candidate data resolver is architected to provide for per installation extensibility.