Inter Workflow (3.0)

The Inter Workflow profile enables you to configure the storage server that the Inter Workflow forwarding and collection agents use for communication.

It is safe to accumulate a lot of data in the storage server directory. When the initial set of directories has been populated with a predefined number of files, new directories are automatically created to avoid problems with file system performance.

The Inter Workflow profile is loaded when you start a workflow that depends on it. Changes to the profile become effective when you restart the workflow.


Files collected by the Inter Workflow agent depend on, and are connected with, the Inter Workflow profile in use. If an Inter Workflow profile is imported to the system, files left in the storage connected to the old profile will be unreachable.


The Inter Workflow profile configuration contains the following settings:

External ReferencesClick on this button in the top button panel to Enable External References in an agent profile field. For further information, see the section Enabling External References in an Agent Profile Field in  External Reference (3.0) .

Storage Host

From the drop-down list, select either AutomaticPlatform, or an activated EC.

Using Automatic means that the storage will use the EC where the first workflow accessing this profile is started. Following workflows using the same profile will use the same EC for storage until the first workflow accessing the profile is stopped. The EC where the next workflow accessing this profile is started will then be used for storage. The location of the storage will therefore vary depending on the start order of the workflows.


Below is an example of a scenario where Automatic is used as storage host with the following setup:

  • Workflow 1 is running on EC1 with Interworkflow Forwarding agent

  • Workflow 2 is running on EC2 with Interworkflow Collection agent

  1. Workflow 2 is started.

    EC2 will be used for storage

  2. Workflow 1 is started.

    EC2 is still used for storage.

  3. Workflow 1 is stopped.

    EC2 is still used for storage.

  4. Workflow 2 is stopped.

    No EC is used for storage.

  5. Workflow 1 is started.

    EC1 is used for storage.


The workflow must be running on the same EC as its storage resides. If the storage is configured to be  Automatic , its corresponding directory must be a shared file system between all the ECs.

Root Directory

The absolute pathname of the directory on the storage handler where the temporary files will be placed.

If this field is greyed out with a stated directory, it means that the directory path has been hard coded using the property. This property is set to false by default.

For further information about all available system properties, see EC Properties(3.0).

Max Bytes

An optional parameter stating the limit of the space consumed by the files stored in the Root Directory. If the limit is reached, any Inter Workflow forwarding agent using this profile will abort.

Max Batches

An optional parameter stating the maximum number of batches stored in the Root Directory. If the limit is reached, any Inter Workflow forwarding agent using this profile will abort.

Compress intermediate data

Select this check box to compress the data sent between the Inter Workflow agents.

The data will be compressed into *.gzip format with compression level 5.

Named MIMs

A list of user defined MIM names. These variables do not have any values assigned. They are populated with existing MIM values from the Inter Workflow forwarding agent. This way, MIMs from the forwarding workflow can be passed on to the collecting workflow.