Workflow Bridge Collection Agent(3.1)
The Workflow Bridge real-time collection agent collects data sent by a Workflow Bridge Forwarding agent.
Setting | Description |
|---|---|
Workflow Bridge Profile | This is the profile to use for communication between the workflows. For information about how to configure a Workflow Bridge profile, see Workflow Bridge Profile. All workflows in the same workflow configuration can use separate profiles. For this to work, the profile must be set to Default in the Workflow Table tab found in the Workflow Properties dialog. For further information on the Workflow Table tab, refer to Workflow Table(3.0). To select a profile, click on the Browse... button, select the profile to use, and then click OK. |
Port | This is the default port that the collecting server will listen to for incoming requests. A valid port value is between 1 and 65535. If you have a collecting workflow configuration with several workflows, you have to open the Workflow Properties, and set the WFB Collector - Port field to Default. Then you can enter the different ports you want to use for the different workflows in the workflow table. Note! Note! |
Stream ID | Workflow Bridge collection and forwarding agents use Stream IDs to manage connections between multiple workflow instances. Instead of creating separate profiles for each pair of workflows, you can use a single profile and assign a Stream ID to ensure that the correct workflows are linked. This is particularly useful when scaling your system, as it allows new workflow instances to automatically find their corresponding counterparts. Example – Configuring a Stream ID in Workflow Bridge Collection and Forwarding Agents Scenario: You need to scale your system by adding multiple instances of connected workflows. Instead of manually configuring separate Workflow Bridge profiles for each instance, you can use Stream IDs to automatically pair workflows. For example, if three processing workflows (A, B, and C) need to send data to three corresponding collection workflows (X, Y, and Z), you can define stream IDs like "A-X", "B-Y", and "C-Z". This ensures each processing workflow sends data to the correct collection workflow while maintaining a simpler, more scalable configuration. |
Transaction Behavior
In the batch forwarding to real-time collection scenario, the Workflow Bridge real-time collection agent routes the states retrieved from the Workflow Bridge batch forwarding agent to the collection workflow. These are the states:
initialize
beginBatch
drain
endBatch
commit
deinitialize
cancelBatch
rollback
The collection workflow must handle all the states and send a reply to the batch forwarding workflow by returning the corresponding WorkflowState UDR. For more information regarding the states, see Workflow Monitor (3.0).
Input/Output Data
The agent consumes and emits WorkflowStateUDR and ConsumeCycleUDR types.
MIM
For information about the Usage Engine MIM and a list of the general MIM parameters, see Administration and Management(3.0) .
Publishes
The agent does not publish any MIM resources.
Accesses
The agent does not access any MIM resources.
Agent Message Events
There are no agent message events for this agent.
For information about the agent message event type, see Agent Event(3.0).
Debug Events
Debug messages are dispatched in debug mode. During execution, the messages are displayed in the Workflow Monitor.
You can configure Event Notifications that are triggered when a debug message is dispatched. For further information about the debug event type, see Debug Event(3.0).
The agent produces the following debug events:
The collector started at <local:address>
This message is displayed when a collector is started.
The collector started at <address>
This message is displayed when a connection has been released.
Client <Worfklow Bridge client> connected to <local:address>
This message is displayed when a forwarding agent disconnects from a collector.
The collector stopped.
This message is displayed when a collector is stopped.
Load Balancing
In order to enable load balancing, you should make the load ID column appear in the workflow table via the workflow properties window.
Configure separate Load IDs for each workflow and save. In the forwarding workflow, you can then use these load IDs in the APL for directing certain UDRs to certain workflows.
In order to enable load balancing, you should make the load ID column appear in the workflow table via the workflow properties window.
Configure separate Load IDs for each workflow and save. In the forwarding workflow, you can then use these load IDs in the APL for directing certain UDRs to certain workflows.