This task exports and imports process instances of a given BPM Process Execution Engine.
All instances of all active processes are exported. Deprecated instances are neither exported nor imported.
This task needs access to a BPM Directory, so it must be
contained in a fuego:session element.
Because process metadata is retrieved from the Directory, the processes must be deployed for this task to work.
When importing, a properties file may be specified for mapping instance variable names. This allows for instance variables to be imported with a name different from the original.
Example 1: Export instances in one file per Engine table in the database
...
<!-- Open a session to the BPM Directory -->
<fuego:session passportref="fuego.passport">
<fuego:instancesmanager directoryPath="/tmp/export/"
action="export"
engineid="${export.engineid}"/>
</fuego:session>
...
Example 2: Import instances exported in Example 1
...
<fuego:session passportref="fuego.passport">
<fuego:instancesmanager directoryPath="/tmp/export/"
action="import"
engineid="${import.engineid}"/>
</fuego:session>
...
| Attribute | Description | Type | Required? |
| engineid |
Name (id) of the BPM Engine.
Deprecated: use serverid |
String | No |
| serverid | Name (id) of the BPM Engine. | String | Yes |
| fieldsmappingfile | Properties file containing the mapping between old instance variable names to new names. | File | No No mapping is done by default. |
| directorypath | Directory name where the output files will be generated (export) or the import files will be read from (import). | File | Yes |
| action |
Whether to execute an export or an import.
Possible values are [export,import] |
String ["import", "export", "importbin", "exportbin"] | Yes |
| counterstep | Number of steps in which the progress is shown. | int | No Defaults to 100. |
| Attribute | Description | Type | Required |
| name | Name of the Organizational Unit | String | Yes |