Native execution endpoints and jobs

The WebSphere Extended Deployment Compute Grid can be composed of both WebSphere Application Servers and native execution endpoints. A WebSphere Application Server runs on a server platform as a dedicated collection of containers and application services that support the Java 2 Enterprise Edition (J2EE) programming and component model.

A native execution endpoint is a server platform on which native execution jobs can run as part of a grid job. J2EE applications conform to the J2EE packaging model and run on the Compute Grid in a WebSphere Application Server. These applications are deployed to WebSphere Application Servers using WebSphere administrative interfaces.

In Compute Grid, a grid job must be composed entirely of J2EE type or native execution jobs. The two cannot be mixed in the same grid job. The J2EE type is further classified into two subtypes, transactional batch and compute intensive, neither of which can be combined with the other in the same grid job.

Native execution endpoints

Native execution endpoints are machines hosting the middleware agent and federated into a WebSphere cell. The Middleware agent install and federation process is used to establish these nodes. Applications on these nodes can be run by WebSphere Extended Deployment grid jobs. Grid jobs can run on both native execution endpoints and WebSphere nodes, subject to job requirements and advertised capabilities of the nodes.

Native execution jobs

Native execution jobs are unconstrained by programming and component models. Any program that can run as a background command on Unix-type or Windows systems fits the category of a native execution job. Native execution jobs can be implemented in Java, native-compiled languages, such as C++ and COBOL, and scripts.