Procedure

Implement the following interface to provide the business logic for the step:

com.ibm.websphere.batch.devframework.steps.technologyadapters.BatchRecordProcessor

The xJCL for the step should 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>
...

Implement the following interface to provide the threshold policy for the step:

com.ibm.websphere.batch.devframework.thresholdpolicies.ThresholdPolicy

Declare the ThresholdPolicy to use in the xJCL as shown in the following code snippet:

...  
<props>		 		           
   <prop name="threshold_policy" 
      value="com.ibm.websphere.batch.devframework.thresholdpolicies.PercentageBasedThresholdPolicy"/>  
</props>  
...

You can also use the product implementations such as the following:

com.ibm.websphere.batch.devframework.thresholdpolicies.PercentageBasedThresholdPolicy

com.ibm.websphere.batch.devframework.thresholdpolicies.RecordBasedThresholdPolicy

Set the BDS input stream logical name to inputStream and a BDS output stream logical name to outputStream and the BDS output stream for errors to errorStream.

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>
    <bds>
	<logical-name>errorStream</logical-name>
	<props>
	...
     </bds>
</batch-data-streams>

While using the BatchPackager for packaging, the jobstepclass for the application must be set to the following value:

com.ibm.websphere.batch.devframework.steps.technologyadapters.ThresholdBatchStep

For example:

ejbname.1=IVTStep1
jndiname.1=ejb/MyThresholdBatchStep
jobstepclass.1=com.ibm.websphere.batch.devframework.steps.technologyadapters.ThresholdBatchStep