Dedicated TRIRIGA Workflow Agents

Starting with IBM TRIRIGA Application Suite 11.3 version, you can create additional dedicated TRIRIGA Workflow Agents using the optional wfagents property of the spec of the TRIRIGA CR.

apiVersion: tririga.ibm.com/v1
kind: Tririga
metadata:
  name: my-tririga
  namespace: ibm-tas
spec:
  ...
  wfagents:
    - name: dwfa1
      members:
        - class: user
          name: myUserName1
        - class: user
          name: myUserName2
        - class: group
          name: myGroupName1
        - class: group
          name: myGroupName2
    - name: dwfa2
      members:
        - class: user
          name: myUserName3
    - name: dwfa3
      members:
        - class: group
          name: myGroupName3                   
  ...

Each item in the spec.wfagents array represents a dedicated workflow agent. The spec.wfagents[i].name string is the name of the dedicated workflow agent and the spec.wfagents[i].members array is the list of users and groups which the workflow agent is dedicated to. If the item represents a user, set the spec.wfagents[i].members[j].class property equal to user. If the item represents a group, set the spec.wfagents[i].members[j].class property equal to group. In both cases, the spec.wfagents[i].members[j].name property is the name of the user or of the group. If the spec.wfagents array is present, it cannot be empty, i.e. at least one item must be defined. Also, the members array of each one of the included items, cannot be empty, i.e. at least one user or group must be assigned to the dedicated workflow agent. Each spec.wfagents[i].name must have a unique name and should be a part of the dedicated WFAgent POD.

Best practices

• Restrict a user to only a single agent. Sharing users across multiple WFAgents is not recommended because all workflows should be executed by one process.
• Usage of groups is possible but not recommended. Make sure all users are added to the group before creating a dedicated Workflow Agent. If new users are added to the group, the WFAgent POD must be restarted to pick up new changed.

Deleting previously added WFAgent pod from TRIRIGA does not reflect the changes in the UI (Agents Page). You have to remove the WFAgent pod manually from the Admin Console.

Known Limitation

Deleting previously added WFAgent pod from TRIRIGA does not reflect the changes in the UI (Agents Page). You have to remove the WFAgent pod manually from the Admin Console.