158 WebSphere Application Server V8.5 Concepts, Planning, and Design Guide
WSGRID does not return until the underlying job is complete, providing a synchronous
execution model.
Because the external scheduler can manage JCL jobs, it can manage a JCL job that started
WSGRID. Using this pattern, the external scheduler can indirectly manage a job. An optional
plug-in interface in the job scheduler enables a user to add code that updates the external
scheduler operation plan. This update reflects the unique state of the underlying job, such as
job started, step started, step ended, or job ended. The WSGRID program is written with
special recovery processing. If the JCL job is canceled, the underlying job is canceled also,
ensuring that the lifecycles of the two jobs are synchronized.
Enterprise integration includes the following key features:
WebSphere Application Server V8.5 includes a special “connector” for Tivoli Workload
Scheduler and competing workload schedulers.
Tivoli Workload Scheduler and WebSphere Batch provide a common deployment pattern.
WebSphere Batch allows full control of the enterprise workload scheduler.
Figure 6-11 shows the workload coming from Tivoli Workload Scheduler directly to the job
scheduler, using a workload connector.
Figure 6-11 Enterprise integration functional diagram
Java virtual machine
WebSphere Application Server
WebSphere Application Server
Foundation Services level
(security, transaction, data access, logging, and so forth)
WebSphere Application Server
Java virtual machine
BATCH container
IBM batch
container
classes and APIs
Batch
Controller
Batch
application
WebSphere Application Server
Java virtual machine
BATCH container
IBM batch
container
classes and APIs
Batch
Controller
WebSphere Application Server
Java virtual machine
BATCH container
IBM batch
container
classes and APIs
Batch
Controller
Tivoli
Workload
Scheduler
Batch
Workload
connector
Other
workload
WebSphere Application Server v 8.5 Cell
Batch
application
Batch
application
Batch
scheduler