9.45.2 Inter Workflow Profile
- Jenni Wallin
- Former user (Deleted)
- Karthik Bangalore
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.
Note!
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.
Configuration
To create a new Inter Workflow profile configuration, click the button in the upper left part of the Desktop window, and then select from the menu.
Inter Workflow profile configuration
The contents of the menus in the menu bar may change depending on which configuration type that has been opened. The Inter Workflow profile uses the standard menu items and buttons that are visible for all configurations, and these are described in 2.1 Menus and Buttons.
The Edit menu is specific for Inter Workflow profile configurations.
| Item | Description |
|---|---|
External References
| Select this menu item to Enable External References in an agent profile field. For further information, see the section Enabling External References in an Agent Profile Field in 8.11 External Reference Profile . |
The Inter Workflow profile configuration contains the following settings:
| Item | Description |
|---|---|
Storage Host | From the drop-down list, select either Automatic, Platform, or an activated EC/ECSA. Using means that the storage will use the EC/ECSA where the first workflow accessing this profile is started. Following workflows using the same profile will use the same EC/ECSA for storage until the first workflow accessing the profile is stopped. The EC/ECSA 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. Example Below is an example of a scenario where Automatic is used as storage host with the following setup:
Note! The workflow must be running on the same EC/ECSA as its storage resides. If the storage is configured to be Automatic , its corresponding directory must be a shared file system between all the EC/ECSAs. |
Root Directory | 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 Example - Using the mz.preset.interwf.storage.path property To enable the property and state the directory to be used: mzsh topo set val:common.mz.preset.interwf.storage.path '/mydirectory/iwf'
mzsh topo unset val:common.mz.preset.interwf.storage.path For further information about all available system properties, see /wiki/spaces/MZD73/pages/5608376 . |
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 if you want 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. |