Instead of using the Messaging Service client for transferring documents, an ImageMaster job can be used for document transfers to SAP. This job is listed in the AdminClient’s job section.
The job can be configured according its schedule and behavior. All use cases supported by the ImageMaster Messaging Service client can be accomplished as well with this job. The job is automatically created during installation without an active schedule.
In the AdminClient section Jobs this job is listed with the following details:
-
Name: executeTransferJobs
-
Implementation Class: com.tsystems.ima.erp.msg.core.jobs.process.Job
| Element | Value | Default | Description |
|---|---|---|---|
|
<skipAssign> |
true | false |
false |
Skip assign step when executing the job. |
|
<assignDeferred> |
true | false |
false |
Assign transfer tasks in state “nostart” to a transfer group. |
|
<assignDocumentType> |
string |
empty |
Assign only transfer tasks for documents of a specific document type to a transfer group. |
|
<configurationName> |
string |
empty |
Consider (assign and run) only transfer tasks for documents affected by a specific configuration. |
|
<transferGroupCount> |
integer |
10 |
Define the number of transfer groups that shall be created / processed per run. 0 means no limit. |
|
<transferGroupSize> |
integer |
1000 |
Define the size of a single transfer group. This will be considered by the assign step. |
|
<skipRun> |
true | false |
false |
Skip run step when executing the job. |
|
<runFailed> |
true | false |
false |
(Re-)run only previously failed documents. |
|
<skipFailed> |
true | false |
false |
Skip previously failed documents. |
|
<transferGroupId> |
uuid |
empty |
Define the ID of the transfer group that shall be re-executed. |
|
Table 274: Messaging Service – ImageMaster job configuration for “executeTransferJobs” |
|||