The current document is directed to a new class of performance-monitoring tools referred as load response performance counters (LRPCs). Load response performance counters are implemented to periodically run a task within a computer system in order to apply a specific load to a particular subsystem or component of the computer system and to measure, at intervals, a response time for completing the task. By monitoring the response times, various types of problems, anomalies, and bottlenecks associated with the subsystem or component can be identified and characterized. The design and implementation of particular LRPCs can be precisely tailored to particular components and subsystems at any of many different hierarchical levels, granularities, and temporal ranges in order to monitor system operation and function.

A system, method, and computer program product are provided for maintaining versioning of web services and XML (Extensible Markup Language) schemas associated with a plurality of independent sub-organizations. In use, a versioning history of a plurality of web services is tracked across a plurality of sub-organizations associated with an organization. Further, a new version of a web service to be introduced in at least one of the sub-organizations is identified. Additionally, a baseline web service version to use for the new version of the web service is automatically identified based on a tracked versioning history of the web service. Furthermore, an existing state of WSDL (Web Services Definition Language) documents and XSD (XML Schema Definition) documents is validated to ensure compliance with a dependency scheme associated with the tracked versioning history of the web service. Moreover, the baseline web service version and dependencies to use for the new version of the web service is recommended to a user, and an impact of introducing the new version of the web service is indicated, such that consistency of the versioning history of the plurality of web services across the plurality of sub-organizations is capable of being maintained.

A system for centralized testing of web-based agent desktops has been devised. The invention uses a test control portal. The test control portal acts as the interface between the client interaction software systems testing system and analyst controlled test device, executes an extensive set of robust test directive commands with underlying routines to be used to specify test conditions without the use of programming ability on the part of the analyst, uses a robust set of report item and format choice designators to allow easy selection of a range of report content and styles.

An apparatus comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: manage an application service using a management web portal; request, using the management web portal, the application service with a given service level agreement from a catalogue of offered application services; and communicate, using the management web portal, with an application service management function; wherein the application service management function is configured to translate the service level agreement of the requested application service to a specification of an application slice, and to trigger a creation of an application slice instance by contacting an application slice management function.

Obtaining a performance metric in a system for conveying web content from a server node to a terminal node along one or more network nodes, involving an inspecting of a data flow transmitting said web content toward the terminal node for extracting web content records. The extracted web content records are correlated to at least one web session. The extracted web content records are associated to a performance of one or more of said nodes. The performance metric is calculated from the correlated and associated web content records for at least one web session and one or more of said nodes.

Application generation and integration application generation methods are disclosed. An application generation function includes automatically providing a set of software artifacts to an application developer that may be used as an aid to providing an application with augmented capabilities for an end-user. The augmented capabilities configured to adhere to certain rules regarding certification criteria and requirements of a multi-tenant cloud infrastructure. Generated applications and plug-in capabilities may further be required to meet certification criteria applicable to an application store hosted within a cloud infrastructure.

Described embodiments provide systems and methods for hosting multiple cloud-based services at a common network address. The systems and methods receive a request addressed to a uniform resource identifier (URI) including a domain name that is one of a plurality of different domain names mapped to a common network address. The systems and methods identify each of a service name and a controller name embedded in the URI, and identify a controller service instance using the service name and controller name from the URI, from a mapping of a plurality of controller server instances to respective service names and controller names. The systems and methods invoke an interface to the identified service instance, and pass data from the received request to the identified service instance via the interface.

Systems and methods for providing web service instances to support traffic demands for a particular web service in a large-scale distributed system are disclosed. An example method includes determining a peak historical service load for the web service. The service load capacity for each existing web service instance may then be determined. The example method may then calculate the remaining service load after subtracting the sum of the service load capacity of the existing web service instances from the peak historical service load for the web service. The number of web service instances necessary in the large-scale distributed system may be determined based on the remaining service load. The locations of the web service instances may be determined and changes may be applied to the large-scale system based on the number of web service instances necessary in the large-scale distributed system.

Described herein are systems and methods of identifying and classifying performance bottlenecks for web applications. Such systems and methods use classification and analysis of performance testing data and data instrumentation via arithmetic and/or machine learning. Data is integrated from different sources including system data, historical and real time sources. Performance variations are analyzed as load changes and the impact of these variations on different sectors of the Application stack are analyzed. Bottlenecks are identified and classified based on the sector in the software stack and recommendations for optimization of an Application under Test are presented to address the bottlenecks are presented.

Disclosed herein are system, apparatus, article of manufacture, method, and/or computer program product embodiments for creating and managing a software application. In an embodiment, an application template may first be identified. Application creation configuration information for a new software application may then be determined based on the identified application template. Application source code information may be generated based on the application creation configuration information and stored in a provisioned application source code data store. A build of the application source code information may then be initiated to generate the software application. An application infrastructure configured to host the software application may be provisioned in an infrastructure services provider system, and the software application may be automatically deployed to the provisioned application infrastructure including appropriate security concerns. Additionally, application infrastructure and deployment telemetry may be generated to monitor health of software application and associated infrastructure.