A batch scaling solution requires you to use a combination of new agents and some existing agents that have had configuration setting updates. The key things to note are:
All storage related to the new agents is in Kafka. This includes transactions and backend working storage.
Workflows containing these new agents can be scaled without any configuration changes. The system will automatically handle the re-balancing of which workflows use which partition.
You cannot mix standard Inter WF agents with scaling Inter WF agents in the same workflow. This is because workflows with standard Inter WF agents save the state in
and workflows with batch agents save the state in Kafka.
Key agents used in scalable workflows
Agent Name | Description |
|---|---|
Scalable Inter WF Collection Agent  | This is a newly created agent specifically for batch scaling workflows. It functions similarly and has the same configuration as the standard Inter Workflow Collection Agent. |
Scalable Inter WF Forwarding Agent  | This is a newly created agent specifically for batch scaling workflows. It functions similarly and has the same configuration as the standard Inter Workflow Forwarding Agent. |
Aggregation Agent  | A new Kafka storage option has been added to the existing Aggregation Agent. When setting up your batch scaling solution, you must add this storage option to the agent configuration, see ‘Storage Tab’ in https://infozone.atlassian.net/wiki/x/chwcEg. |
Duplicate UDR Agent  | A new Kafka storage option has been added to the existing Duplicate UDR Agent. When setting up your batch scaling solution, you must add this storage option in the agent configuration. See 'Storage tab' in https://infozone.atlassian.net/wiki/x/yYkkEg. |
Subsections
This section contains the following subsections: