Abstract: Merging directory information from a user directory to a common directory includes based on a rule associated with contents of a user directory of a local database, extracting a department indicator from the user directory, mapping the department indicator to a corresponding user record in a common directory of a registry database, and based on the department indicator, marking the user record in the common directory with a department that corresponds to the contents from the user directory with a department for controlling access to that user record in the registry database.

Abstract: Merging directory information from a user directory to a common directory includes based on a rule associated with contents of a user directory of a local database, extracting a department indicator from the user directory, mapping the department indicator to a corresponding user record in a common directory of a registry database, and based on the department indicator, marking the user record in the common directory with a department that corresponds to the contents from the user directory with a department for controlling access to that user record in the registry database.

Abstract: Merging directory information from a user directory to a common directory includes based on a rule associated with contents of a user directory of a local database, extracting a department indicator from the user directory, mapping the department indicator to a corresponding user record in a common directory of a registry database, and based on the department indicator, marking the user record in the common directory with a department that corresponds to the contents from the user directory with a department for controlling access to that user record in the registry database.

Abstract: Merging directory information from a user directory to a common directory includes based on a rule associated with contents of a user directory of a local database, extracting a department indicator from the user directory, mapping the department indicator to a corresponding user record in a common directory of a registry database, and based on the department indicator, marking the user record in the common directory with a department that corresponds to the contents from the user directory with a department for controlling access to that user record in the registry database.

Abstract: Merging directory information from a user directory to a common directory includes based on a rule associated with contents of a user directory of a local database, extracting a department indicator from the user directory, mapping the department indicator to a corresponding user record in a common directory of a registry database, and based on the department indicator, marking the user record in the common directory with a department that corresponds to the contents from the user directory with a department for controlling access to that user record in the registry database.

Abstract: Merging directory information from a user directory to a common directory includes based on a rule associated with contents of a user directory of a local database, extracting a department indicator from the user directory, mapping the department indicator to a corresponding user record in a common directory of a registry database, and based on the department indicator, marking the user record in the common directory with a department that corresponds to the contents from the user directory with a department for controlling access to that user record in the registry database.

Abstract: Merging directory information from a user directory to a common directory includes based on a rule associated with contents of a user directory of a local database, extracting a department indicator from the user directory, mapping the department indicator to a corresponding user record in a common directory of a registry database, and based on the department indicator, marking the user record in the common directory with a department that corresponds to the contents from the user directory with a department for controlling access to that user record in the registry database.

Abstract: Merging directory information from a user directory to a common directory includes based on a rule associated with contents of a user directory of a local database, extracting a department indicator from the user directory, mapping the department indicator to a corresponding user record in a common directory of a registry database, and based on the department indicator, marking the user record in the common directory with a department that corresponds to the contents from the user directory with a department for controlling access to that user record in the registry database.

Abstract: Transaction storm detection includes receiving a series of transactions in a data stream for an authenticated network session. A detection engine determines whether the transactions form a transaction storm. In response to determining that the transactions are a transaction storm, metrics associated with the transaction storm are presented. One or more actions may be specified to be applied in a subsequently detected transaction storm.

Abstract: A transaction storm detection engine is configured to receive a series of transactions in a data stream for an authenticated network session. The detection engine determines whether the transactions form a transaction storm. In response to determining that the transactions are a transaction storm, metrics associated with the transaction storm are presented. One or more actions may be specified to be applied in a subsequently detected transaction storm.

Abstract: A method, system, and program product are provided for minimizing replication when a new server is replicated with. A replication application for a client computer having a replica of a database thereon is executed by a processor in a computer to receive for a replication service comprising a plurality of servers containing replicas of the database, an indication of each healthy server in the replication service and a determined period of time within which replication is assured to have been completed for each healthy server. The replication application updates a replication history after successful completion of each replication by adding an entry comprising an identification for the server replicated with and a timestamp for the time of replication and by adding an entry for each other healthy server in the replication service containing an identification for the respective server and an imputed timestamp adjusted for the determined period of time.

Abstract: Transaction storm detection includes receiving a series of transactions in a data stream for an authenticated network session. A detection engine determines whether the transactions form a transaction storm. In response to determining that the transactions are a transaction storm, metrics associated with the transaction storm are presented. One or more actions may be specified to be applied in a subsequently detected transaction storm.

Abstract: A transaction storm detection engine is configured to receive a series of transactions in a data stream for an authenticated network session. The detection engine determines whether the transactions form a transaction storm. In response to determining that the transactions are a transaction storm, metrics associated with the transaction storm are presented. One or more actions may be specified to be applied in a subsequently detected transaction storm.

Abstract: A method, device, and program product are provided for inter-site database replication. A replicating server tracks other servers that it needs to replicate with and the sites where the other servers are located. In response to an indication to replicate, the replicating server determines whether each of the other servers is at the same location as the replicating server or a different location from the replicating server. The replicating server replicates with each of the other servers at the same site as the replicating server, and the replicating server replicates with only one of the servers at each different site. The replicated server at each different site replicates with the other servers at the site of the replicated server.

Abstract: A method, system, and program product are provided for minimizing replication when a new server is replicated with. A replication application for a client computer having a replica of a database thereon is executed by a processor in a computer to receive for a replication service comprising a plurality of servers containing replicas of the database, an indication of each healthy server in the replication service and a determined period of time within which replication is assured to have been completed for each healthy server. The replication application updates a replication history after successful completion of each replication by adding an entry comprising an identification for the server replicated with and a timestamp for the time of replication and by adding an entry for each other healthy server in the replication service containing an identification for the respective server and an imputed timestamp adjusted for the determined period of time.

Abstract: A method, system, and program product are provided for minimizing replication when a new server is replicated with. A replication application for a client computer having a replica of a database thereon is executed by a processor in a computer to receive for a replication service comprising a plurality of servers containing replicas of the database, an indication of each healthy server in the replication service and a determined period of time within which replication is assured to have been completed for each healthy server. The replication application updates a replication history after successful completion of each replication by adding an entry comprising an identification for the server replicated with and a timestamp for the time of replication and by adding an entry for each other healthy server in the replication service containing an identification for the respective server and an imputed timestamp adjusted for the determined period of time.

Abstract: A method, system, and program product are provided for minimizing replication when a new server is replicated with. A replication application for a client computer having a replica of a database thereon is executed by a processor in a computer to receive for a replication service comprising a plurality of servers containing replicas of the database, an indication of each healthy server in the replication service and a determined period of time within which replication is assured to have been completed for each healthy server. The replication application updates a replication history after successful completion of each replication by adding an entry comprising an identification for the server replicated with and a timestamp for the time of replication and by adding an entry for each other healthy server in the replication service containing an identification for the respective server and an imputed timestamp adjusted for the determined period of time.

Abstract: A method, device, and program product are provided for inter-site database replication. A replicating server tracks other servers that it needs to replicate with and the sites where the other servers are located. In response to an indication to replicate, the replicating server determines whether each of the other servers is at the same location as the replicating server or a different location from the replicating server. The replicating server replicates with each of the other servers at the same site as the replicating server, and the replicating server replicates with only one of the servers at each different site. The replicated server at each different site replicates with the other servers at the site of the replicated server.

Abstract: A method, computer program product, and system for routing computer network traffic include associating, on a routing device, a unique identifier with at least one application server running an application. Network traffic that includes the unique identifier and an intended network address may be received. In response to receiving the network traffic at least one of the application servers associated with the unique identifier may be identified. The network traffic may be forwarded to at least one of the application servers associated with the unique identifier.

Abstract: A method, computer program product, and system for routing computer network traffic include associating, on a routing device, a unique identifier with at least one application server running an application. Network traffic that includes the unique identifier and an intended network address may be received. In response to receiving the network traffic at least one of the application servers associated with the unique identifier may be identified. The network traffic may be forwarded to at least one of the application servers associated with the unique identifier.