Two programming models, transactional batch and compute-intensive, are provided by WebSphere Extended Deployment.
The transactional batch programming model requires the implementation of container-managed persistence entity bean (EJBs). In contrast, the compute-intensive programming model is implemented as a simple Plain Old Java Object (POJO) and packaged into an Enterprise Application Archive (.ear) file for deployment into the WebSphere environment.
The individual programming models provide details on how the life cycle of the application and jobs submitted to it are managed by the long-running execution environment. Central to all long-running applications is the concept of a job to represent an individual unit of work to be executed. The following topic describes how to construct an application that provides the logic to be executed by a job.