1 Introduction

Note: The "old" EDB_BATCH mechanism of the EDM server is not recommended anymore, and the Batch Client replaces the "old" batch solution of the EDM server.

The Batch Client runs a batch scenario which is implemented in Groovy to control the batch use case. The most batch use cases are designed as a loop, which uses a job table to determine if a job is present or if the process should wait for a new job.

The Agile e6.2.1.0 Batch Client supports two different modes:

1. Scenario Mode

   The Batch Client starts a defined scenario which interacts with the EDM Server to execute the batch use case.

2. ECI Server Mode

   The Batch Client provides an ECI tunnel to the EDM server and standard features like file access to the File Server.

For more details, refer to the Chapter 4, "Use Cases."

Note: For more information regarding the Batch Client architecture, refer to the section, Application Server Components of the Architecture Guide for Agile e6.2.1.0.

Note: The Agile e6.2.1.0 Batch Client is available for all server platforms of the Agile e6.2.1.0 release. For more details, refer to the Oracle Agile Engineering Data Management - Platform Support for Agile e6.2.1.0