Runtime Modification of the Workflow Configuration
Usage Engine includes two mechanisms by which an operator can modify a workflow that is already running.Â
While a workflow is executing, it is possible to change the configuration of certain agents in their respective Configuration tabs which is available in the Monitor mode of the Workflow Designer.Â
These changes will be automatically sent to the running workflow and provisioned into the agent that is being reconfigured.Â
In this case, the changes are applied without affecting the execution of the workflow.Â
The example below shows how this is performed for the TCP/IP Agent of an active Workflow. In this scenario, the IP address used for listening on incoming requests is changed.Â
Runtime modification
Usage Engine includes a mechanism through which it is possible – while the workflow is running – to send a signal to an agent to instruct it to perform some action without affecting the active workflow.Â
The example below shows how this capability is used to instruct an Aggregation agent to execute the instructions within the command block for all sessions that have a timeout condition configured. This can be used, for example, to implement the capability to force a hard-flush of sessions in a Charging Gateway deployment.Â
Executing command block from monitor mode in the graphical user interface:
Command block
A command block can also be executed from the command line interface, by using the wfcommand. This enables the workflow logic to be executed based on input from the Command Line Interface.Â