|
Invokes a LiveCycle service using parameters read from
each record of a JDBC query. This method generates database queries
that read the rows in a page of input items that are processed in
one transaction. Since multiple queries are used to retrieve the
input items, this operation can be less efficient than the Run JDBC Cursor
Job operation. However, this operation can work with some databases and
application servers where the Run JDBC Cursor Job operation is not supported.
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 set of parameters
that are applied to each LiveCycle service invocation.
Batch Input properties
Properties that identify the input data source and the
input SELECT, FROM, and WHERE clauses.
Input Data Source
The JNDI name of the
JDBC data source that input items will be read from.
Input SELECT Clause
The SELECT clause
part of SQL query string. You can omit the SELECT keyword.
Do
not use the column as a sort key if the column has an alias in the
SELECT clause. For example, if you use SELECT clause= "column1,
column2, column3 as key" and a user enters "column3" or "key" as
the sort key, the JDBC Paging job will fail. The user needs to enter
"column1" or "column2" as the sort key.
Input FROM Clause
The FROM clause part
of SQL query string. You can omit the FROM keyword.
Input WHERE Clause
The WHERE clause part
of SQL query string. You can omit the WHERE keyword.
Sort Key
A unique key to use to sort and
limit page content.
Batch Output properties
Properties that identify the output data source and output
SQL.
Output Data Source
The JNDI name of a
JDBC data source that output items are written to. 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.
|
|
|
