WebSphere Extended Deployment packages and deploys long-running applications as Java 2 Platform, Enterprise Edition (J2EE) Enterprise Archive (EAR) files.
Deploying a long-running application is similar to deploying a transactional J2EE application. Long-running applications are hosted in a long-running execution environment.
The logic for the execution environment is packaged as a single J2EE application, GEE.ear. Deploy this J2EE application to a dynamic cluster to let the dynamic cluster host the long-running applications that are deployed to it.
The deployment target is automatically enabled on the Compute Grid endpoints when you install or deploy a Compute Grid application, whether it is a compute-intensive or a batch application. For example, if you create a dynamic cluster (assuming you are in the Compute Grid/Operations Opitimization environment; a static cluster will be created in the Compute Grid environment) to host a grid application, then install the grid application on the dynamic cluster (or static cluster), the grid application is automatically detected during the installation of it. The system application (GEE) will automatically be deployed to this same dynamic cluster. Moreover, the GEE will automatically be removed from this dynamic cluster when the last grid application is uninstalled from it.
As a best practice, do not deploy transactional applications
to a dynamic cluster meant for long-running work.
Long-running applications often consume
large amounts of memory and / or CPU and the transactional application is
likely to perform poorly. Conversely, you can also deploy a long-running application to
a dynamic cluster intended for transactional work. In this case, the absence
of the long-running execution environment on the dynamic
cluster prevents the long-running application from
receiving any jobs from the long-running scheduler.
You can configure your long-running execution environment with
the administrative console, or through scripting.