WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


The long-running execution environment

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. A long-running applications is hosted in along-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 long-running execution environment when you install or deploy a long-running application, whether it is a compute-intensive or a batch application. For example, if you create a dynamic cluster 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 product application (GEE) will automatically be deployed to this same dynamic cluster. Use the removeGEE.py to remove the GEE from this dynamic cluster.

[Version 6.0.1 only] You can configure your long-running execution environment with the administrative console, or through scripting.




Related concepts
Managing Compute Grid jobs and their environment
Related tasks
Developing Compute Grid applications
Creating the grid endpoint database
Concept topic    

Terms of Use | Feedback

Last updated: Oct 16, 2009 11:03:44 AM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/prodovr/cbglrexenv.html