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: A computer implemented method, an apparatus, and a computer usable program product are provided for configuring and modeling server connection and deployment information in an enterprise tooling environment. A software model is provided that comprises a connections object, which includes a plurality of connection objects and deploy spec objects. Each of the connection objects is specific to a backend server type. A deploy controller is provided at run time to examine the connections object for a connection object. A backend resource manager is loaded for a specific application server. If a connection object is present, the backend resource manager loads a connection interpreter, which transforms development time connection information in the connection object to the run time connection information in corresponding deploy spec object and connection factory spec object. The backend resource manager then writes the deployment information to the configurations files of the application server.

Abstract: A computer implemented method, an apparatus, and a computer usable program product are provided for configuring and modeling server connection and deployment information in an enterprise tooling environment. A software model is provided that comprises a connections object, which includes a plurality of connection objects and deploy spec objects. Each of the connection objects is specific to a backend server type. A deploy controller is provided at run time to examine the connections object for a connection object. A backend resource manager is loaded for a specific application server. If a connection object is present, the backend resource manager loads a connection interpreter, which transforms development time connection information in the connection object to the run time connection information in corresponding deploy spec object and connection factory spec object. The backend resource manager then writes the deployment information to the configurations files of the application server.

Abstract: A computer implemented method, an apparatus, and a computer usable program product are provided for configuring and modeling server connection and deployment information in an enterprise tooling environment. A software model is provided that comprises a connections object, which includes a plurality of connection objects and deploy spec objects. Each of the connection objects is specific to a backend server type. A deploy controller is provided at run time to examine the connections object for a connection object. A backend resource manager is loaded for a specific application server. If a connection object is present, the backend resource manager loads a connection interpreter, which transforms development time connection information in the connection object to the run time connection information in corresponding deploy spec object and connection factory spec object. The backend resource manager then writes the deployment information to the configurations files of the application 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 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.