Batch jobs that use a single input file are initiated by
running runbatch.sh with arguments to define
the input file and options.
- Navigate to the $home/bin directory
that holds the runbatch.sh script.
- Run the runbatch.sh script with arguments
that follow the format:
runbatch.sh <Input URL> <Output URL> [<batch_ext> <batchLoadPropertyFile> <instance>]
Where:- <Input URL> is the batch input source, such
as a filename.
- <Output URL> is the batch output destination,
such as a folder or a file.
- <batch_ext> (optional) is the name of a batch
extension properties file that contains additional batch properties.
These properties will be used at runtime to override the default properties
configured in Batch.properties. This properties
file must be available in the batch processor JVM classpath.
- <batchLoadPropertyFile> (optional) is the
name of the batch load properties file that resides on the physical InfoSphere® MDM server and contains the properties used in context when passing
through the Request/Response framework. This properties file must
be available in the physical InfoSphere MDM server JVM classpath. Properties can be prefixed by an instance
name. In this way, a single batch load properties file can contain
different groupings of properties based on the instance name prefix.
- <instance> (optional) is the instance name
used as a prefix for each property in the batch load properties file.
If the <instance> argument is specified at runtime,
the batch load properties that are prefixed by the given instance
name will be used.