Bulk Processing

For advice on modern batch processing see the following redbooks:

• Batch Modernization on z/OS

  Many different technologies are available in a batch environment on z/OS systems. This book demonstrates these technologies and shows how the z/OS system offers a sophisticated environment for batch. In this practical book, we discuss a variety of themes that are of importance for batch workloads on z/OS systems and offer examples that you can try on your own system.

  Review this Redboook (SG24-7779)

• Batch Processing with WebSphere Compute Grid: Delivering Business Value to the Enterprise

  Batch processing remains a mission critical workload for many enterprises. Existing batch applications have developed over time in a 'home-grown' and silo'd fashion, with each application providing the underlying services required for the processing to occur. With today's emphasis on reducing costs while satisfying ever-growing demands for business agility and increased efficiency, pressure has been placed on enterprises to improve the operations, development and maintenance of their batch systems. New requirements must also be addressed such as reduced windows for operation and increases in data that makes it imperative for batch systems to scale and perform.
  WebSphere Compute Grid can provide the answer to these requirements for improved batch processing, while ensuring that enterprises will remain agile, scalable, and cost efficient. WebSphere Compute Grid delivers a complete, cloud-enabled batch-processing platform for the enterprise.

  Review this Redbook (REDP-4566-00)

Return to Process-Centric.

• Patterns for e-business naming conventions

• New assignment

  Updated: 03-12-2010
  The Bulk Processing business pattern has been classified under the new Process-Centric business pattern.

• Introduction

  Updated: 03-12-2010
  The Bulk Processing business pattern has been introduced to P4eb.

• Feasibility:
  This material will help you determine the high-level shape of a Process-Centric solution, and can ensure your approach looks similar to other successful implementations. Reuse of prior approaches can be an effective way to begin most major projects. Obviously, modifications will be needed for any unique requirements of a given set of partners. This pattern provides a drill-down from high-level architecture to low-level designs and guidance.

• Risk:
  Basing new projects on prior designs and ideas helps to lower the risk of failure. Creating or inventing approaches for each project tends to result in a lower success rate. Frequently, projects begun "from scratch" simply do not work and have major exposures in such areas as security, performance, availability, undefined requirements, and cost overrun.

• Cost-benefit:
  By starting with reasonably complete architecture you can save considerable development time and can obtain assurance that the end solution will have a much higher chance of success. Actual savings will vary, but project teams have realized a 10% to 50% reduction of work effort in their design and architecture phases alone.