Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agent name

Description

Scalable Inter Workflow Collection Agent

include image

This is a newly created agent specifically for batch scaling workflow groups. It functions similarly and has the same configuration as the https://infozone.atlassian.net/wiki/x/fRgkEgagent.

diff agents but same config with MIMs

The key difference is…

Scalable Inter Workflow Forwarding Agent

include image

This is a newly created agent specifically for batch scaling workflow groups. It functions similarly and has the same configuration as the https://infozone.atlassian.net/wiki/x/uBckEg agent.

  • diff agents but same config with MIMs

File Collection AgentThe key difference is…

File Collection Agent

Collects files from a local file system and inserts them into a workflow. Initially, the source directory is scanned for all files matching the current filter. See the following for more information on File Collection agents, https://infozone.atlassian.net/wiki/x/PoIkEg https://infozone.atlassian.net/wiki/x/GYkkEg https://infozone.atlassian.net/wiki/x/BYQkEg https://infozone.atlassian.net/wiki/x/6JwkEg https://infozone.atlassian.net/wiki/x/MRwkEg https://infozone.atlassian.net/wiki/x/Y44kEg https://infozone.atlassian.net/wiki/x/5pAkEg https://infozone.atlassian.net/wiki/x/IrkkEg.

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. Some use cases may need to switch to the new profile. See, Aggregation Agent(4.3).

Duplicate UDR Agent

A new Kafka storage option has been added to the Duplicate UDR Agent. When setting up your batch scaling solution you must add this storage option in the agent configuration. See Duplicate UDR(4.3).

...

Child pages (Children Display)
depth1
allChildrentrue
style
sortAndReverse
first0
Info

Questions:

Can agents other than those in the table above be used in a scaling WF?

In the aggregation agent description, we advise that some use cases may require the user to switch to the new profile. when would this need to happen?

What is the key difference between the Regular Inter WF Agents and the new agents (is it that the new scalable agents will be able to partition the data?)