Abstract: The invention provides a mechanism for convenient management for configuring and selecting servers for running modules. The invention provides a method for managing a plurality of servers including receiving a request to configure a suitable server being suitable for running a module, locating an identifier of the suitable server from a table comprising identifiers of suitable servers, configuring the suitable server to run the module.

Abstract: An extensible mechanism for executing code on one of one or more servers and in association with one of one or more client applications (i.e. “clients”). In accordance with a model of the extensible mechanism, the execution of server side code is partitioned into three stages, a view stage for determining the code for running, a server stage for determining the server to execute the code and a launcher stage to determine the client for interacting with the server to run the code. Lists of processing elements at each stage extensibly configure the mechanism to work with different types of server side code to be run, different servers to run the code and different clients with which to interact with the server running the code. By modeling the execution of server side code in stages and using lists of processing elements, the mechanism is easily extended to new code types, servers and launchers.

Abstract: Embodiments of the present invention separates raw server configuration data (data describing how the server is to operate—e.g., network port number, security settings, software drivers, etc.) from server instance data (data which describes where to run a server and how to process user code—e.g., which directories to access, where the user code is located, etc.). Embodiments of the present invention may have raw server configuration data and server instance data stored as, for example, text files. A file embodying raw server configuration data may be copied and reused on multiple computer systems. Similarly, a file embodying server instance data may also be copied and reused on multiple computer systems. Embodiments of the present invention process the raw server configuration data file and the server instance file to generate an overall server configuration file which configures a server to operate in the desired manner so that user code can be successfully deployed on the configured server.

Abstract: The universal, Web browser-based Enterprise JavaBean (EJB) test client is itself a Java 2 Enterprise Edition (J2EE) application packaged in a Web archive file. This archive, when extracted, consists of a set of files that are installed on a target application server. The installation makes it possible for a user of a Web browser on a workstation remote from the application server to perform a number of tests on, and invoke, methods in EJB beans that are installed on the staging, or even production, servers. It is also possible to perform tests in real time under real conditions.

Abstract: An extensible mechanism for executing code on one of one or more servers and in association with one of one or more client applications (i.e. “clients”). In accordance with a model of the extensible mechanism, the execution of server side code is partitioned into three stages, a view stage for determining the code for running, a server stage for determining the server to execute the code and a launcher stage to determine the client for interacting with the server to run the code. Lists of processing elements at each stage extensibly configure the mechanism to work with different types of server side code to be run, different servers to run the code and different clients with which to interact with the server running the code. By modeling the execution of server side code in stages and using lists of processing elements, the mechanism is easily extended to new code types, servers and launchers.

Abstract: The invention provides a mechanism for convenient management for configuring and selecting servers for running modules. The invention provides a method for managing a plurality of servers including receiving a request to configure a suitable server being suitable for running a module, locating an identifier of the suitable server from a table comprising identifiers of suitable servers, configuring the suitable server to run the module.

Abstract: Embodiments of the invention enable the association of server configuration data with an application or project. Additionally, embodiments of the invention may enable multiple versions of server configuration data (which in some embodiments are versioned separately from the associated application or project) to be stored. Advantageously embodiments of the invention enable a server to be configured in accordance with versioned configuration data (often stored in one or more configuration files) such that the server performs in a well understood manner. This advantageous feature enables, amongst others, a developer to more quickly identify the source of any problems which may have been introduced as a result of modifications made to the application being tested.

Abstract: Embodiments of the present invention separates raw server configuration data (data describing how the server is to operate—e.g., network port number, security settings, software drivers, etc.) from server instance data (data which describes where to run a server and how to process user code—e.g., which directories to access, where the user code is located, etc.). Embodiments of the present invention may have raw server configuration data and server instance data stored as, for example, text files. A file embodying raw server configuration data may be copied and reused on multiple computer systems. Similarly, a file embodying server instance data may also be copied and reused on multiple computer systems. Embodiments of the present invention process the raw server configuration data file and the server instance file to generate an overall server configuration file which configures a server to operate in the desired manner so that user code can be successfully deployed on the configured server.

Abstract: The universal, Web browser-based Enterprise JavaBean (EJB) test client is itself a Java 2 Enterprise Edition (J2EE) application packaged in a Web archive file. This archive, when extracted, consists of a set of files that are installed on a target application server. The installation makes it possible for a user of a Web browser on a workstation remote from the application server to perform a number of tests on, and invoke, methods in EJB beans that are installed on the staging, or even production, servers. It is also possible to perform tests in real time under real conditions.