A generic batch step works with one input and one output
stream. This step during each iteration of the batch loop reads a
single entry from the BDS Input Stream passes it to the BatchRecordProcessor
for processing. The BatchRecordProcessor returns the processed data
which is then passed to the BDS output stream.
About this task
Use the following properties to implement the generic
batch step.
Table 1. Required properties
Property name |
Value |
Description |
BATCHRECORDPROCESSOR |
Java™ class
name |
Class implementing the BatchRecordProcessor
interface
|
Table 2. Optional properties
Property |
Value |
Description |
debug |
true or false (default is false) |
Enable tracing and debugging on the step
|
EnablePerformanceMeasurement |
true or false (default is false) |
Measure time spent within the step
|
Procedure
- Implement the interfacecom.ibm.websphere.batch.devframework.steps.technologyadapters.BatchRecordProcessor to
provide the business logic for the step. In the xJCL for the step,
declare a property BATCHRECORDPROCESSOR with the value set to the
implementation of the interface. For example:
...
<props>
<prop name="BATCHRECORDPROCESSOR" value="com.ibm.websphere.batch.samples.tests.steps.InfrastructureVerificationTest"/>
</props>
...
- Set the BDS input stream logical name to inputStream and
a BDS output stream logical name to outputStream. The logical names
are declared in the xJCL. For example:
<batch-data-streams>
<bds>
<logical-name>inputStream</logical-name>
<props>
....
</bds>
<bds>
<logical-name>outputStream</logical-name>
<props>
...
</bds>
</batch-data-streams>
- While using the BatchPackager for packaging, the application
for the job step class, jobstepclass, must be set to com.ibm.websphere.batch.devframework.steps.technologyadapters.GenericXDBatchStep.
For example:
ejbname.1=IVTStep1
jndiname.1=ejb/GenericXDBatchStep
jobstepclass.1=com.ibm.websphere.batch.devframework.steps.technologyadapters.GenericXDBatchStep