Worker groups

Edit online

In the Worker groups page, you can create, store, and manage worker groups.

Workers are containerized applications that run workflows. Each worker belongs to a worker group. When you run a workflow, you can select which worker group you want to run it.

The default worker group contains local workers (workers that are preinstalled in the Concert Workflows namespace). By default, this group is used to run workflows. If you prefer, you can create a worker group that contains remote workers (workers that you install on remote hosts), then use your group to run workflows.

You create, store, and manage worker groups in the Worker groups page. To access this page, complete these steps:
  1. If you are connected to another application, click Workflows.
  2. In the Concert Workflows sidebar, click Worker groups.
In the worker group list, you can perform these actions:
  • Search for a group by name.
  • Sort groups by their name, description, active workers, inactive workers, terminated workers, total workers, or by whether they validate certificates or not.
  • Enable or disable a group’s ability to validate security certificates when its workers make API requests.
  • View the list of workers for a group and sort that list by all visible columns.
    Note:
    • Active workers are considered to be fully operational, while terminated workers are treated as permanently deactivated.
    • If the number of active workers for a group is less than expected, a warning is shown. One or more of the workers might be inactive or terminated.

Creating worker groups

  1. In the Worker group page, click + Create worker group.
  2. In the dialog, provide information for the worker group.
    Name
    The name of the group.
    Description
    An optional description for the group.
    Secret
    The password, or secret, for the group.
    Confirm secret
    A copy, or confirmation, of the secret for the group.
    Expected active workers in this group
    The number of workers in this group that are expected to be in an active state.
    Note: This number is used for troubleshooting purposes. In the worker group list, if the number of active workers for a group is less than the expected number, a warning is shown.

    For example, if you want your new group to use three workers, you set the expected active workers to 3, install the three workers, and connect them to the new group. In the worker group list, if the number of active workers for your group is less than 3, a warning is shown.

    Attention: In the dialog, take note of the following items, because you will need them if you want to install a remote worker that connects to the new group:
    • The highlighted Concert Workflows server hostname.
    • The name of the new group.
    • The new group's secret.
  3. Optional: Download the stand-alone remote worker installation package by clicking Download remote worker. For more information about remote workers, see Remote workers.
  4. Optional: Define proxy configuration for this worker group.
    Note: These proxy settings apply only to network traffic between Concert Workflows workers and the internet (for example, requests to external services via workflow integration blocks). They do not apply to traffic between remote workers and your Concert Workflows host. For information about routing traffic from remote workers to your Concert Workflows host through a proxy server, see Customizing worker behavior.
    1. Expand the Proxy settings section.
    2. Optional: In the Proxy settings for this worker group section, configure a proxy server for this worker group.
      1. If the Override global proxy settings switch is shown, turn it on.

        This switch is shown only if a global proxy server is configured for your Concert Workflows instance. For more information about global proxy settings, see Proxy settings.

      2. Turn on the Enable proxy settings for this worker group switch.
      3. Enter the connection details for the proxy server.

        Requests from workers in this group will be routed through this server.

    3. Optional: Exclude hosts from the proxy server (global or group-specific) that applies to this worker group.
      1. In the Excluded hosts section, turn the Exclude hosts from the proxy switch on.
      2. Specify the hosts that you want to exclude and click + Add host after each one.

        Requests from workers in this group to each specified host will bypass the proxy server and connect to the host directly.

      Tip: Make sure that the Exclude hosts from the proxy switch is on. Otherwise, the specified hosts will not be excluded.
  5. Optional: Assign role permissions for this worker group.
    1. Expand the Permissions section.
    2. Select your preferred roles from the list to grant them access to the worker group. By default, these two roles are available:
      admin
      Allows only administrators to access the worker group.
      everyone
      Allows all users to access the worker group.
  6. Click Save. The new group is shown in the list.
  7. Optional: Update a group's details, except its name, by clicking the Actions menu, then clicking Edit.
    Warning: If possible, do not modify the details of the default worker group. Modifying the default worker group's details can affect system operation if the workers are not properly reconfigured.
  8. Optional: View a group's history, including a details about all of the workers it contained in its lifespan, by clicking Actions > History.
  9. Optional: Delete the group by clicking Actions > Delete.
    Warning: If possible, do not delete the default worker group. Deleting the default worker group can affect system operation if the workers are not properly reconfigured.