Abstract: A system for servicing a request from a client includes at least two proxy servers, each having a corresponding proxy server configured as a buddy proxy server, and being adapted to act as a primary proxy server for servicing the request and to forward the request to a backend server. The system includes a load balancer adapted to: forward the request to a primary proxy server; forward the request to a failover proxy server in the event of failure of the primary proxy server; and forward a response from the primary proxy server or the failover proxy server to the client. The system includes a backend server adapted to receive a request from a proxy server and to send a response to the proxy server. The failover proxy server is adapted to process the request depending on a status of a matching previously stored request.

Abstract: A novel manner of handling an error or exception caused by the unavailability of a slot or crypto hardware or communication network between server and hardware. As per this scheme, in the event of the unavailability of a particular slot in the hardware, the server may disable the SSL request processing within the server by setting a global “SSL Unavailable” flag. All the existing SSL requests within the server can be en-queued. If the error is because of unavailability of master slot, the server can establish a connection with a backup slot. If the error is because of unavailability of crypto hardware or communication network, then server may start a healer thread that will poll for the state of the hardware. If the exception is because of hardware reset, then server may cleanup earlier connection information and re-establish connection with the hardware, and enable SSL services.

Abstract: A method, system, and computer usable program product for analyzing test coverage of code changes are provided in the illustrative embodiments. A first source code is received. A second source code is received. The second code includes a changed code in comparison with the first source code. The changed code is identified. A set of test cases is executed on the second code. Information about the test coverage of the changed code is produced. Additionally, a determination may be made whether to produce code coverage information for the entire second source code or only the changed code. Using the set of test cases, code coverage information for the second source code may be computed, forming complete code coverage information. The information about the coverage of only the changed code may be selected from the complete code coverage information.

Abstract: A method for online automatic relocation of LDAP entries and subtrees in a distributed directory environment. The online relocation method is for homogeneous LDAP directory partition servers where source and target partition servers have the same schema rules and definitions. When the method is to be applied in a directory environment where servers have different set of schema, then a “rules file” or a “policies file” that contains mapping of schema attribute-value pairs and objectclasses of a source directory server with the schema attribute-value pairs and objectclasses of a destination directory server should be supplied to the relocation tool.