Abstract: Various embodiments of systems, computer program products, and methods to monitor a network to identify network issues are described herein. In an aspect, requests are routed to access a sample application at predetermined time intervals via different defined network paths between a monitoring application unit and the sample application in a network. Response codes associated with execution of the requests are received from the sample application via the corresponding defined network paths. Execution results of the requests to include the response codes and execution time of the requests corresponding to the different defined network paths are recorded. Further, the execution results for a time period are analyzed to identify network issues in the network. Identifying the network issues includes identifying problematic network paths based on the analysis of the execution results, and identifying problematic network components in the problematic network paths by analyzing the problematic network paths.

Abstract: The present disclosure involves systems, software, and computer implemented methods for calculating hashes of archive files and their file entries. In one example, a method may include receiving an archive file which includes at least one compressed file, storing the archive file by sending a first copy of the archive file stream to a first processing thread which stores the archive file in a local file system, and applying a hash function to the archive file and the at least one compressed file to create hash values corresponding to the archive file and the at least one compressed file by sending a second copy of the archive file stream to a second processing thread, which applies the hash function to the archive file and the at least one compressed file to create the hash values and is executed in parallel to the first processing thread.

Abstract: A test application running on a first platform in a first data center is configured for disaster recovery. A first request is sent to the test application, including determining that the first request is processed by a first test application instance in the first data center. A second request is sent to the test application to generate test data. A third request is sent to a second platform in a second data center to switch traffic for the test application from the first instance to a second instance running in the second data center. A fourth request is sent to the test application, including determining that the fourth request is processed by the second instance. A fifth request is sent to the test application to validate data replicated from the first data center to the second data center. A determination is made as to whether disaster recovery is successful.

Abstract: Account data comprising metadata for primary application instances running at a primary active cloud environment instance (ACEI) is stored. Application data associated with the primary application instances is stored at primary databases (DBs). The account and application data are transferred to secondary DBs at a secondary ACEI. The secondary ACEI may be a backup instance to substitute services provided by the primary ACEI in case of unavailability. For example, the location where the primary ACEI is hosted may be affected by a disaster. To failover a primary data center hosting the primary ACEI, a database takeover to the secondary DBs is performed. The secondary ACEI is configured correspondingly to the primary ACEI based on the transferred account data. Secondary application instances corresponding to the primary application instances are started at the secondary ACEI. Requests directed to the primary application instances are redirected to the secondary application instances.

Abstract: Methods and system are disclosed that bypass a maintenance mode of an application, for some users. In one aspect, multiple requests may be received to establishing a connection with multiple applications at a load balancer component. Upon receiving the received requests, a request processing and inspection unit and an intelligent control unit may be instantiated. The request processing and inspection unit may preprocess or process the received requests. The preprocessed or processed requests may be forward to the intelligent control unit. Based on a determination of header information and a content of the received requests, the intelligent control unit may determine whether to execute a routine to bypass a maintenance mode of an application and direct the requests to establish connection with the application or to execute a routine related to the maintenance mode of the application.

Abstract: In one respect, there is provided a method. The method can include: determining that a second instance of the cloud-based application is deployed at a second cloud platform landscape; replicating, at a second database at the second cloud platform landscape, at least a portion of data from a first database at the first cloud platform landscape, the data from the first database being associated with the first instance of the cloud-based application; and configuring a domain name system (DNS) service to include a primary universal resource locator (URL) for the first instance of the cloud-based application and a secondary URL for the second instance of the cloud-based application, the primary URL and the secondary URL both being associated with a custom domain of the cloud-based application. Related systems and articles of manufacture are also disclosed.

Abstract: Various embodiments of systems, computer program products, and methods to replicate data in a distributed environment are described herein. In an aspect, the data from a first persistent storage unit associated with a primary data center is received. Further, at least a part of the received data is determined to be replicated by filtering the data based on one or more predetermined conditions. The determined part of the data is transmitted to replicate in a second persistent storage unit associated with a secondary data center to recover the part of the data during failure of the primary data center.

Abstract: Account data comprising metadata for primary application instances running at a primary active cloud environment instance (ACEI) is stored. Application data associated with the primary application instances is stored at primary databases (DBs). The account and application data are transferred to secondary DBs at a secondary ACEI. The secondary ACEI may be a backup instance to substitute services provided by the primary ACEI in case of unavailability. For example, the location where the primary ACEI is hosted may be affected by a disaster. To failover a primary data center hosting the primary ACEI, a database takeover to the secondary DBs is performed. The secondary ACEI is configured correspondingly to the primary ACEI based on the transferred account data. Secondary application instances corresponding to the primary application instances are started at the secondary ACEI. Requests directed to the primary application instances are redirected to the secondary application instances.

Abstract: A client system requests to upload an input data stream to a server system. The input data stream is split to a sequence of chunks. The chunks are transferred in parallel by a number of connections from the client system to the server system. At the server system, the transferred chunks are merged into an output stream according to the sequence. The output stream represents the rebuilt input stream.

Abstract: A resource registry provides nondeterministic operation environment affording flexible access for resource execution and status monitoring on the cloud. The resource registry service provides generic resource management utilizing registration, updating, and unregistration by resource providers. A requester for an operation may register in the resource registry, an operation resource having parameters defined in metadata. The resource registry notifies a registered resource listener of this registration of the operation resource. The resource listener may then execute the operation according to parameters defined in the operation resource. The resource listener returns a response to the resource registry, concerning a result of execution of the operation. The resource registry updates this status in the metadata of the operation resource. The requester is then able to look up the operation resource's metadata to determine current status of the operation.

Abstract: A test application running on a first platform in a first data center is configured for disaster recovery. A first request is sent to the test application, including determining that the first request is processed by a first test application instance in the first data center. A second request is sent to the test application to generate test data. A third request is sent to a second platform in a second data center to switch traffic for the test application from the first instance to a second instance running in the second data center. A fourth request is sent to the test application, including determining that the fourth request is processed by the second instance. A fifth request is sent to the test application to validate data replicated from the first data center to the second data center. A determination is made as to whether disaster recovery is successful.

Abstract: In one respect, there is provided a method. The method can include: determining that a second instance of the cloud-based application is deployed at a second cloud platform landscape; replicating, at a second database at the second cloud platform landscape, at least a portion of data from a first database at the first cloud platform landscape, the data from the first database being associated with the first instance of the cloud-based application; and configuring a domain name system (DNS) service to include a primary universal resource locator (URL) for the first instance of the cloud-based application and a secondary URL for the second instance of the cloud-based application, the primary URL and the secondary URL both being associated with a custom domain of the cloud-based application.. Related systems and articles of manufacture are also disclosed.

Abstract: Various embodiments of systems, computer program products, and methods to monitor a network to identify network issues are described herein. In an aspect, requests are routed to access a sample application at predetermined time intervals via different defined network paths between a monitoring application unit and the sample application in a network. Response codes associated with execution of the requests are received from the sample application via the corresponding defined network paths. Execution results of the requests to include the response codes and execution time of the requests corresponding to the different defined network paths are recorded. Further, the execution results for a time period are analyzed to identify network issues in the network. Identifying the network issues includes identifying problematic network paths based on the analysis of the execution results, and identifying problematic network components in the problematic network paths by analyzing the problematic network paths.

Abstract: Various embodiments of systems, computer program products, and methods to replicate data in a distributed environment are described herein. In an aspect, the data from a first persistent storage unit associated with a primary data center is received. Further, at least a part of the received data is determined to be replicated by filtering the data based on one or more predetermined conditions. The determined part of the data is transmitted to replicate in a second persistent storage unit associated with a secondary data center to recover the part of the data during failure of the primary data center.

Abstract: The present disclosure describes methods, systems, and computer program products for retrying message delivery in a network. One computer-implemented method includes determining a retry window (RW) for one or more retry attempts to send a message to a target system, determining a minimum silent interval (MSI) representing the minimum permitted time interval between two successive retry attempts, dividing the RW into one or more time slots of N duration, randomly determining, by a hardware processor, a point-in-time within a time slot starting from the beginning time of the time slot, and sending a message as a retry attempt to the target system at the point-in-time.

Abstract: The present disclosure involves systems, software, and computer implemented methods for calculating hashes of archive files and their file entries. In one example, a method may include receiving an archive file which includes at least one compressed file, storing the archive file by sending a first copy of the archive file stream to a first processing thread which stores the archive file in a local file system, and applying a hash function to the archive file and the at least one compressed file to create hash values corresponding to the archive file and the at least one compressed file by sending a second copy of the archive file stream to a second processing thread, which applies the hash function to the archive file and the at least one compressed file to create the hash values and is executed in parallel to the first processing thread.

Abstract: An operation execution request is created by an operation requester at an operations service module. The operation execution request is stored by the operations service module. A polling message for the operation execution request is received. The polling message includes a name of an operation. A response including the operation execution request and corresponding operation data is returned. An execution service schedules internally the operation for execution. The execution service sends an acknowledgement message to acknowledge the operation execution request. The operation data and corresponding operation execution request is locked for execution by other execution services. The execution service executes the operation with the operation data and provides result of the operation execution. The operations service module updates status of the operation execution request. The updated status is provided to the operation requester upon polling for status of the operation execution request.

Abstract: A resource registry provides nondeterministic operation environment affording flexible access for resource execution and status monitoring on the cloud. The resource registry service provides generic resource management utilizing registration, updating, and unregistration by resource providers. A requester for an operation may register in the resource registry, an operation resource having parameters defined in metadata. The resource registry notifies a registered resource listener of this registration of the operation resource. The resource listener may then execute the operation according to parameters defined in the operation resource. The resource listener returns a response to the resource registry, concerning a result of execution of the operation. The resource registry updates this status in the metadata of the operation resource. The requester is then able to look up the operation resource's metadata to determine current status of the operation.

Abstract: Various embodiments of systems and methods to process customized deployment scenarios in a shared computing environment are described. In one aspect, a deployment request is received at the shared computing environment by a client associated with a customized deployment scenario. In a response, a deploy service of the shared computing environment is instantiated. In another aspect, one or more custom deploy processors are identified by the deploy service, where the one or more custom deploy processors correspond to one or more customized deployment scenarios. In yet another aspect, a part of a deployable content passed to the one or more custom deploy processors by the deploy service, is deployed to the shared computing environment by at least one corresponding custom deploy processor.

Abstract: Some examples of security cloud computing environments can be implemented as methods. A processor of a first computer system that lacks permission to store data in a cloud computing environment receives data to be stored in the cloud computing environment. The data is received from a second computer system implementing the cloud computing environment and having permissions to store data in the cloud computing environment. The processor of the first computer system determines that the received data is safe for storage in the cloud computing environment. The processor of the first computer system determines that the received data is safe for storage in the cloud computing environment. The processor of the first computer system provides a notification to the second computer system indicating that the received data is safe for storage in the cloud computing environment, and an identifier that points to the stored data at the computer-readable storage medium.