IBM WebSphere WebSphere Extended Deployment

siemens800

Welcome to the WebSphere Extended Deployment, Version 6.1Information Center
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1/index.jsp?topic=/com.ibm.websphere.gridmgr.doc/info/scheduler/ccgtws.html
 
 

<span style="font-family: Arial, sans-serif;">

• WebSphere Extended Deployment Version 6.1
  
  
  
  • Welcome to the documentation
    
    
    
    • Information center tour
      
    • Prerequisite software for the information center
      
    • Accessibility features
      
    • Viewing information in different languages
      
    • Navigating in the information center
      
    • Searching this documentation
      
    • Book marking topics in this documentation
      
    • Identifying new and changed information
      
    • Using this documentation offline
      
    • Where do I find information?
      
    • Your suggestions are welcome
      
    
    
  
  
• WebSphere Extended Deployment Operations Optimization Version 6.1
  
• WebSphere Extended Deployment Compute Grid Version 6.1
  
• WebSphere Extended Deployment Data Grid Version 6.1
  
• ibm.com: About IBM - Privacy - Contact
  

  

http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1/index.jsp?topic=/com.ibm.websphere.gridmgr.doc/info/scheduler/ccgtws.html
Tivoli Workload Scheduler
 

<span style="font-size: 13px;"> [size=0.75em]Extended Deployment Compute Grid, Version 6.1
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS
Understanding the integration of an external workload scheduler and WebSphere Extended Deployment

Many customers already use an external workload scheduler to manage batch workloads on z/OS. While Java batch executed inside a WebSphere Application Server environment is attractive, a way to control WebSphere Compute Grid jobs through an external workload scheduler is important.
<div style="margin-top: 1em; margin-bottom: 1em;" class="section">Understanding Compute Grid applications

Compute Grid is a component of WebSphere Extended Deployment Version 6.1 that provides a complete enterprise Java batch programming solution. It includes a concise, yet powerful, Plain Old Java Object (POJO) based programming model, simple packaging and deployment model, full-feature job control language, sophisticated job scheduler, robust execution environment, and comprehensive workload management and administrative tools. These all combine to make WebSphere Extended Deployment Compute Grid the most complete Java batch solution available today.
As the following image shows, a batch job is a series of program executed in the background under control of a job manager. Each program consumes zero, one or more input data sources and produces zero, one or more output data sinks. The z/OS operating system is an example of a mature batch job processing environment. WebSphere Extended Deployment Compute Grid generalizes this processing model and make it available in a WebSphere/Java 2 Enterprise Edition (J2EE ) environment.


A WebSphere Extended Deployment Compute Grid application is a POJO class that implements a batch interface and is invoked by the WebSphere Extended Deployment batch container. It has access to container services that expose batch data streams (BDS), which represent data sources and sinks. Typically, the purpose of such an application is to perform bulk operations on a large set of records. A job definition describes a series of steps, where each step invokes a batch POJO. The job definition describes both the order of step execution and the batch data streams that are inputs/outputs and are used by each step.
A Compute Grid job executes inside a WebSphere Application Server in a special container called the batch container, as shown in the following image: