Abstract: A system for maintaining a two-site configuration for continuous availability over long distances may include a first computing site configured to execute a first instance associated with a priority workload, the first instance being designated as an active instance; a second computing site configured to execute a second instance of the priority workload, the second instance being designated as a standby instance; a software replication module configured to replicate a unit of work data associated with the priority workload from a first data object associated with the active instance to a second data object associated with the standby instance, and a hardware replication module configured to replicate an image from a first storage volume to a copy on a second storage volume, wherein the first storage volume is associated with the first computing site, and the second storage volume is associated with a third computing site.

Abstract: A computer program product for managing replication configurations includes program instructions to receive a replication configuration for replicating data, wherein the replication configuration defines at least a target table in a target database based on a source table in a source database. The program instructions initialize a federated view, wherein the federated view is based on at least the source table in the source database as defined in the replication configuration. The program instructions utilize the federated view to satisfy requesting applications, where requesting applications obtain data from the federated view. The program instructions to, responsive to determining the replication of data is in spec, utilize the target table in the target database to satisfy requesting applications.

Abstract: A computer-implemented method, carried out by one or more processors, for managing replication configurations. In an embodiment, the method comprises receiving, by one or more processors, a replication configuration for replicating data, wherein the replication configuration defines at least a target table in a target database based on a source table in a source database; initializing, by one or more processors, a federated view, wherein the federated view is based on at least the source table in the source database as defined in the replication configuration; utilizing, by one or more processors, the federated view to satisfy requesting applications, where requesting applications obtain data from the federated view; responsive to determining the replication of data is in spec, utilizing, by one or more processors, the target table in the target database to satisfy requesting applications.

Abstract: An application-level thread dispatcher that operates in a main full-weight thread allocated to an application is established. The application-level thread dispatcher initializes a group of application-level pseudo threads that operate as application-controlled threads within the main full-weight thread allocated to the application. The application-level thread dispatcher evaluates run-time performance of the application.

Abstract: A system for maintaining a two-site configuration for continuous availability over long distances may include a first computing site configured to execute a first instance associated with a priority workload, the first instance being designated as an active instance; a second computing site configured to execute a second instance of the priority workload, the second instance being designated as a standby instance; a software replication module configured to replicate a unit of work data associated with the priority workload from a first data object associated with the active instance to a second data object associated with the standby instance, and a hardware replication module configured to replicate an image from a first storage volume to a copy on a second storage volume, wherein the first storage volume is associated with the first computing site, and the second storage volume is associated with a third computing site.

Abstract: A system for providing reliable availability of a general workload and continuous availability of a priority workload over long distances may include a first computing site configured to execute a first instance associated with the priority workload, wherein the first instance is designated as an active instance, a second computing site configured to execute a second instance of the priority workload, wherein the second instance is designated as a standby instance, a third computing site configured to restart a third instance associated with the general workload, and a workload availability module configured to synchronize a portion of data associated with the third instance with a corresponding portion of data associated with the second instance.

Abstract: A computer-implemented method, carried out by one or more processors, for managing replication configurations. In an embodiment, the method comprises receiving, by one or more processors, a replication configuration for replicating data, wherein the replication configuration defines at least a target table in a target database based on a source table in a source database; initializing, by one or more processors, a federated view, wherein the federated view is based on at least the source table in the source database as defined in the replication configuration; utilizing, by one or more processors, the federated view to satisfy requesting applications, where requesting applications obtain data from the federated view; responsive to determining the replication of data is in spec, utilizing, by one or more processors, the target table in the target database to satisfy requesting applications.

Abstract: An application-level thread dispatcher that operates in a main full-weight thread allocated to an application is established. The application-level thread dispatcher initializes a group of application-level pseudo threads that operate as application-controlled threads within the main full-weight thread allocated to the application. The application-level thread dispatcher determines that at least one application-level pseudo thread meets configuration requirements to operate within a separate operating system-level thread in parallel with the main full-weight thread. In response to determining that the at least one application-level pseudo thread meets the configuration requirements to operate within the separate operating system-level thread in parallel with the main full-weight thread, the at least one application-level pseudo thread is dispatched from the main full-weight thread to the separate operating system-level thread by the application-level thread dispatcher.

Abstract: A method for implementing a change capture system using an event publishing system as a database recovery log is provided. The method may include determining a set of data based on a description of events for which change capture is possible. The method may also include selecting at least one item of data from within the determined set of data, wherein the at least one item of data requires change capture to be performed. Additionally, the method may include identifying at least one published event, wherein the at least one published event is produced by the event publishing system. The method may include instructing the event publishing system to deliver the at least one identified published event to the change capture system. Furthermore, the method may include receiving the at least one identified published event. The method may also include processing the at least one published event.

Abstract: A method for implementing a change capture system using an event publishing system as a database recovery log is provided. The method may include determining a set of data based on a description of events for which change capture is possible. The method may also include selecting at least one item of data from within the determined set of data, wherein the at least one item of data requires change capture to be performed. Additionally, the method may include identifying at least one published event, wherein the at least one published event is produced by the event publishing system. The method may include instructing the event publishing system to deliver the at least one identified published event to the change capture system. Furthermore, the method may include receiving the at least one identified published event. The method may also include processing the at least one published event.

Abstract: An application-level thread dispatcher that operates in a main full-weight thread allocated to an application is established. The application-level thread dispatcher initializes a group of application-level pseudo threads that operate as application-controlled threads within the main full-weight thread allocated to the application. The application-level thread dispatcher determines that at least one application-level pseudo thread meets configuration requirements to operate within a separate operating system-level thread in parallel with the main full-weight thread. In response to determining that the at least one application-level pseudo thread meets the configuration requirements to operate within the separate operating system-level thread in parallel with the main full-weight thread, the at least one application-level pseudo thread is dispatched from the main full-weight thread to the separate operating system-level thread by the application-level thread dispatcher.

Abstract: A data processing system and method of operation are disclosed. The data processing system includes a first site for processing data; a second site for processing data; and a transaction replay program configured to send a copy of data from the first site to the second site. A processor defines a maximum replication latency threshold and a reset threshold for the system, estimates a replication latency of a workload the system, switches the system to a first replication latency state when the estimated replication latency rises above the maximum replication latency and switches the system out of the first replication latency state to a second replication latency state when the estimated replication latency falls below the reset threshold.

Abstract: A computer system for managing a plurality of workloads executing on both a primary system and on a secondary system, and synchronizing both a plurality of software data and hardware data stored on the primary system with the secondary system is provided. The computer system may include receiving a region switch request and stopping the execution of the plurality of workloads on the primary system; suspending the replication of the plurality of software and hardware data stored on the primary system with the plurality of software and hardware data stored on the secondary system; and switching the replication of the plurality of software data and the plurality of hardware data that occurs from the primary system to the secondary system to occur from the secondary system to the primary system. The computer system may include activating the execution of and synchronizing the plurality of workloads on the secondary system.

Abstract: Embodiments of the disclosure are directed to methods, systems and computer program products for performing a planned workload switch. A method includes receiving a request to switch a site of an active workload and stopping one or more long running processes from submitting a new request to the active workload. The method also includes preventing a new network connection from accessing the active workload and processing one or more transactions in a queue of the active workload for a time period. Based on a determination that the queue of the active workload is not empty after the time period, the method includes aborting all remaining transactions in the queue of the active workload. The method further includes replicating all remaining committed units of work to a standby workload associated with the active workload.

Abstract: A computer-implemented method, carried out by one or more processors, for managing replication configurations. In an embodiment, the method comprises receiving, by one or more processors, a replication configuration for replicating data, wherein the replication configuration defines at least a target table in a target database based on a source table in a source database; initializing, by one or more processors, a federated view, wherein the federated view is based on at least the source table in the source database as defined in the replication configuration; utilizing, by one or more processors, the federated view to satisfy requesting applications, where requesting applications obtain data from the federated view; responsive to determining the replication of data is in spec, utilizing, by one or more processors, the target table in the target database to satisfy requesting applications.

Abstract: Continuous workload availability between sites at unlimited distances, which includes receiving a unit of work data. Once the unit of work data has been received the workload that the unit of work data is directed to is determined, and a primary site of a plurality of sites to process the unit of work is chosen. If the processing of the unit of work data is successful, then one of one or more processing systems of the primary site are selected to process the unit of work data, and the unit of work data is replicated to at least one other site. The primary site is separated from each of the plurality of sites by a distance greater than a metropolitan area network (MAN) and operations occur within a customer acceptability window.

Abstract: A continuous availability system including a controller module executing on a computer processor, the system is configured to receive a unit of work and to select a primary site from a plurality of sites to process the unit of work. Once a site is selected the system is further configured to select one of one or more processing systems from the primary site to process the unit of work. The system is additionally configured to replicate the unit of work to at least one other site once the unit of work is completed at the primary site. The system is configured to operate even when the primary site is separated from each of the plurality of sites by a distance greater than a metropolitan area network and the operations occur within a customer acceptability window.

Abstract: A system for maintaining a two-site configuration for continuous availability over long distances may include a first computing site configured to execute a first instance associated with a priority workload, the first instance being designated as an active instance; a second computing site configured to execute a second instance of the priority workload, the second instance being designated as a standby instance; a software replication module configured to replicate a unit of work data associated with the priority workload from a first data object associated with the active instance to a second data object associated with the standby instance, and a hardware replication module configured to replicate an image from a first storage volume to a copy on a second storage volume, wherein the first storage volume is associated with the first computing site, and the second storage volume is associated with a third computing site.

Abstract: A system for providing reliable availability of a general workload and continuous availability of a priority workload over long distances may include a first computing site configured to execute a first instance associated with the priority workload, wherein the first instance is designated as an active instance, a second computing site configured to execute a second instance of the priority workload, wherein the second instance is designated as a standby instance, a third computing site configured to restart a third instance associated with the general workload, and a workload availability module configured to synchronize a portion of data associated with the third instance with a corresponding portion of data associated with the second instance.

Abstract: Embodiments of the present invention provide a method, system and computer program product for consistent replication of transactional updates. In an embodiment of the invention, a method for consistent replication of data in a transaction processing system is provided. The method includes recording entries in a replication log of different data updates and corresponding transactions and additionally recording entries in the replication log indicating whether or not the transactions have been backed out. The method also includes replicating only those data updates referenced in the log which do not correspond to transactions indicated in the log to have been backed out. For instance the additionally recorded entries in the replication log indicate when a transaction has been backed out. Alternatively, the additionally recorded entries in the replication log indicate when a transaction has been committed.