|
Invokes a LiveCycle service using parameters read from
each record of a JDBC query. A database cursor reads the input items.
This approach is often the simplest and most efficient for reading
the input items, although not all databases and application server
environments support it.
For information about the General and Route Evaluation property
groups, see
Common operation properties
.
Job Identification properties
Property that identifies the job run.
Run Identifier
A
string
value that uniquely identifies
this job run among all job runs with the same parameters. If null
or empty, a unique value is generated.
Service Operation properties
Properties that identify the service and operation to invoke
for each batch item read.
Service
The name of the LiveCycle service
or process that will be invoked for each batch item that is read.
Operation
The operation to invoke for
each batch item that is read. When the service is a process, the
value is always
invoke
. When the service is a Document
Service Component, the value is the name of the service operation.
Static Service Parameters properties
Properties that identify static service parameters.
Static Parameters
A map that contains
the parameters that are applied to the LiveCycle service that is
called for each item.
Batch Input properties
Properties that identify the input data source and input
SQL.
Input Data Source
Input items are read
from this data source.
Input SQL
An SQL statement where each
row of the result set is mapped to a batch input item.
Batch Output properties
Properties that identify the output data source and output
SQL.
Output Data Source
Output parameters for
each batch item can be written to this data source. If null or empty,
no output is written at the batch level.
Output SQL
An SQL statement that writes
output parameters to the output data source. The SQL statement may
use named parameters that correspond to input or output parameters,
for example, "insert into mytable (c1, c2) value (:param1, :param2)".
Optimization properties
Properties that identify the partition strategy, its parameters,
and commit interval.
Partition Strategy
Determines how the
input items will be partitioned for parallel processing. Use any
of the following values:
-
No Partitioning. Input
items are processed sequentially
-
Each Partition has a specified number of input items
-
The input items are split into a specified number of partitions
Partition Strategy Parameters
Arguments
used by the partitioning strategy. Each partition has a specified number
of input items. The input items are split into a specified number
of partitions. This is an integer value.
Commit Interval
The number of items that
will be processed before the batch processing state is committed
to persistent store. Setting this value too low may use more resources. Setting
this value too high may risk transaction time outs. If a failure
occurs, the batch processor needs to retry processing those items.
Result properties
Batch processing return code. Can return any of the following
values:
-
COMPLETED
-
FAILED
-
STOPPED
-
UNKNOWN
-
ALREADY_RUNNING
-
RESTART_FAILED
-
ALREADY_COMPLETE
Exceptions
This operation can throw a BatchProcessorException.
|
|
|
