• No replies
782 Posts

Pinned topic XD Compute Grid Value Proposition and some common use-cases

‏2008-01-22T16:32:25Z |

Value Proposition for WebSphere XD Compute Grid

1. Delivers an enterprise java batch execution environment built on WebSphere (zAAP eligible batch on z/OS)

2. Enables the incremental migration of COBOL to Java (on z/OS) thereby reducing the risks associated with a batch modernization project

3. Integrates with existing enterprise batch schedulers such as Tivoli Workload Scheduler (TWS), CA7, Control-M, Zeke to help deliver a robust, cost-effective, WebSphere-based batch execution environment

4. Enables new execution patterns including: Dynamic OLTP and Batch runtime environment built on WebSphere; highly parallel batch jobs; and many others.

5. Integrates with the overall SOA strategy of reuse by enabling one to share business logic across both the OLTP and Batch paradigms.

6. Delivers high-performance batch processing by leveraging the System-z, z/OS, and WAS z/OS performance optimizations gained when executing within close proximity of the data.

Some common use-cases

1. Batch Modernization -- Pursuing batch modernization projects has been of particular interest of z/OS customers. The purpose of these projects is to migrate from a native z/OS batch runtime, typically developed in programming languages like C, C++, PL/I, and COBOL, to Java.

2. Highly Parallel Batch Jobs -- Leveraging the Dispatcher-worker architecture of Compute Grid to execute highly parallel batch jobs. A highly-parallel batch job is defined as a single, large batch job that can be broken into discrete chunks; each chunk can be executed concurrently across a grid of resources. With Compute Grid, a single job to process 100,000,000 bank account records can be broken down into jobs that process a separate partition of the original data. For example, that job of 100,000,000 records can be broken into 100 jobs of 1,000,000 records.

3. Dynamic OLTP + Batch Runtime -- On z/OS, XD Compute Grid integrates with WebSphere for z/OS and the underlying z/OS operating system and leverages its inherent dynamic runtime. For distributed platforms, XD Compute Grid integrates with WebSphere XD Operations Optimization to deliver a virtualized and goals-oriented infrastructure.

4. Batch as a Service -- WebSphere XD delivers features for resource usage accounting and reporting, on z/OS, these features integrate with the features already available on the platform (workload management, RMF, SMF, and so on). On distributed platforms, XD Compute Grid integrates with XD Operations Optimization to provide usage accounting.

5. Replace Existing, Homegrown Batch Frameworks -- IT Operations, prior to the introduction of enterprise batch runtimes like WebSphere XD Compute Grid, took it upon themselves to build their own homegrown batch solutions. These home-grown infrastructures are being replaces with XD Compute Grid in an effort to eliminate code maintenance and execution costs.

6. Sharing business logic across OLTP and Batch -- Business services, defined as discrete tasks responsible for executing some business function, can be shared across both the batch and OLTP runtimes. Batch execution environments are typically independent of the OLTP runtime, especially within the context of J2EE middleware like WebSphere; WebSphere XD Compute Grid delivers a batch execution runtime built on J2EE application servers, and this technology therefore brings together two traditionally disparate worlds, the effect of which is the ability to share business services across them

Message was edited by: Snehal Antani
Updated on 2008-02-25T12:33:06Z at 2008-02-25T12:33:06Z by SystemAdmin