This topic describes the steps required to build and package a batch application using the Plain Old Java Object (POJO) programming model.
As an option, you can use the following scripts to replace steps 3 - 5 located in the following Procedure section:
Set the Java virtual machine custom propertycom.ibm.websphere.ejbcontainer.expandCMPCFJNDIName. See Java virtual machine custom properties .
WSBatchPackager.sh -properties=<properties file name> [-debug]
or
WSBatchPackager.sh -appname=<application name> -jobsteps="{{<ejb name>, <jndi name>, <POJO step class> [, jar file, utility jars]}, ...}" -jarfile=<jarfile containing POJO step classes> -earfile=<output ear file name> [-utilityjars=<semicolon separated utility jars>] [-epjndiname=<endpoint/checkpoint datasource jndi name>] [-nonxadsjndiname=<non-xa datasource JNDI name for CursorHoldableJDBCReader>;<non XA datasource JNDI name 2>;...] [-debug]
Alternatively, packager can be invoked as shown below:
java -jar batchpackager.jar -properties=<properties file name> [-debug]
or
java -jar batchpackager.jar -appname=<application name> -jobsteps="{{<ejb name>, <jndi name>, <POJO step class> [, jar file, utility jars]}, ...}" -jarfile=<jarfile containing POJO step classes> -earfile=<output ear file name> [-utilityjars=<semicolon separated utility jars>] [-epjndiname=<endpoint/checkpoint datasource jndi name>] [-nonxadsjndiname=<non-xa datasource JNDI name for CursorHoldableJDBCReader>;<non XA datasource JNDI name 2>;...] [-debug]
appname=testBatchApp jarfile=c:\\websphere\\appserver\\temp\\pojoclasses.jar earfile=TestBatchAppEAR ejbname.1=POJOStep1 jndiname.1=ejb/POJOStep1 jobstepclass.1=com.ibm.ws.batch.sample.POJOStep1.class ejbname.2=POJOStep2 jndiname.2=ejb/POJOStep2 jobstepclass.2=com.ibm.ws.batch.sample.POJOStep2.class