Running batch samples

You can run the batch samples using the runbatch command.

1. Navigate to the client folder by entering the command cd/<client_folder> where <client_folder> contains the client side files (see step 1 in Configuring the Batch Client-side Sample). Ensure thatWAS_HOME for WebSphere® Application Server, is already defined as an environment variable, otherwise set its values in the runbatch.bat (or runbatch.sh) script. Run the command:
   • In Windows:

     bin\runbatch.bat personsearchtest.txt personsearchtest.out personsearch

   • In UNIX:

     bin/runbatch.sh ./personsearchtest.txt. /personsearchtest.out personsearch

2. Monitor the run on the command window and if there are any errors, review the error logs.
3. If the run is successful, depending on the setting of the WriterQueue in the Batch.properties, either an output folder or an output file will be created.

   If WriterQueue is set to com.dwl.batchframework.queue.FileWriterQueue, compare the contents of the file personsearchtest.out with personsearchtest.out.sample file. If they are the identical, the search sample is successful. If the contents are not identical, review the error codes to determine what is wrong.

   However, if WriterQueue is set to com.dwl.batchframework.queue.WriterChainedQueue, an output folder personsearchtest.out is created. The successful and failed transactions are listed in the batchLoadSuccess.out and batchLoadFail.out respectively

4. Use the run command to run the party update test, replacing the input, output and properties file with the respective file names for that test.
   Note: Some of the test cases in the test input are negative test cases, therefore, if the error codes returned are identical to the one in the sample output file, it represents the successful execution of the negative test case.