› Manage Core Worker service profiles

Manage Core Worker service profiles

Define CoreWorker service profiles to control how the CoreWorker functions so that you can adjust the settings as required and apply them to any deployment. You can add, modify, and delete the Core Worker service profiles and associate a service profile with a deployment.

Add a Core Worker service profile

You can add a service profile for the CoreWorker. As the CoreWorker can only access a data center, the CoreWorker service profiles are stored within a data center.

  1. On the header bar, click Settings > Service Profiles.

    The Service Profiles page displays a list of Core Worker service profiles names if any. The default Data Center (On Premise Datacenter Database) appears as you can configure only one data center in On-Premise Multi-Tenancy.

  2. Set the service profile refresh interval to Refresh Deployments With Assigned Profiles After a specified time in seconds and click Update.

    The refresh interval is updated.

    This settings is not specific to an individual service profile but to a deployment. You can set the refresh interval only after adding the service profiles.

  3. To add a Core Worker service profile, click Create.

    The Add Core Worker Service Profile page appears and displays the settings with default values as given in the following table.

    Setting

    Description

    Default value

    Profile name

    Enter a name for the profile.

    Empty

    General

    Worker task poll interval (seconds)

    Specifies how often the system should check for the in-memory worker tasks that are due.

    1

    Database worker task poll interval (seconds)

    Specifies how often the system should poll for the due database worker tasks.

    1

    Worker task timeout interval (seconds)

    Specifies how often the system checks for timed-out worker tasks.

    300

    Maximum evaluate job task size

    Specifies the maximum number of Evaluate Job tasks to take.

    50

    Thread pool monitoring interval (seconds)

    Defines how often a thread pool should monitor the threads in it. Currently, the monitoring is done to check for thread timeout is monitored, and only for thread pools of the Automatic activity type.

    60

    Archive delete worker tasks to retrieve

    Specifies the number of Archive Jobs and DeleteItem non-system level worker tasks to retrieve for execution.

    50

    Archive delete retry interval (seconds)

    Specifies the thread pool name for automatic activities.

    0

    Upgrade jobs thread pool size

    Specifies the size of the Upgrade job thread pool. If the thread pool size is full, the core worker waits until the space to add more tasks is available.

    4

    Activity Timeout

    Activity timeout interval (minutes)

    Defines the duration after which an activity is timed out. The activity is only freed once the corresponding task executes.

    60

    Poll time activities reset interval (seconds)

    Specifies how often the Core Worker checks for timed-out activities.

    300

    Import Connector

    Import connector name

    Allows administrators to explicitly specify the import connection a Core Worker should use. This setting is useful when multiple Core Workers are set up.

    All

    Maximum messages/documents to import

    Specifies the maximum number of documents or messages to import for document ingestion.

    50

    Automatic Activities

    Maximum work queue task size

    Specifies the maximum number of tasks that can be taken by the Core Worker.

    50

    Maximum number of activities to lock

    Specifies the number of automatic activities to lock when the CoreWorker polls for the execution of automatic activities.

    32

    Activity order

    Specifies the order in which the activities are taken for processing.

    Activity Due Date, Priority

    Auto activities pool name

    Specifies the thread pool name for automatic activities.

    None

    Auto activities pool ID

    Specifies the thread pool ID for automatic activities.

    None

    Message Connector

    Maximum direct ingest threads

    Specifies the maximum number of direct import threads per tenant.

    1

    Direct ingest burst duration (seconds)

    Specifies the maximum duration since the start of a worker thread where the available massages are continuously imported. The worker thread usually terminates the earlier messages if no input is due for polling. If this duration is reached, the worker thread completes after the current import/poll operation.

    600

    Direct ingest timeout (seconds)

    Specifies the maximum run duration of direct import worker threads. The worker threads are cancelled if this time-out expires. The maximum run duration must be higher than the expected worst-case duration for reception and import of a message.

    7200

    Direct ingest confirm timeout (seconds)

    Specifies the maximum duration between each retry.

    600

Update a Core Worker service profile

You can change the values for the CoreWorker service profile settings.

  1. On the Service Profiles page, on the list of profiles, click the profile name to update.

    The Update Core Worker Service Profile page appears.

  2. Update the values for the settings such as needed.
  3. Click Save.

Delete a Core Worker service profile

  1. On the Service Profiles page, on the list of profiles, click the profile to delete.
  2. Click Delete.
    On confirmation, the service profile is deleted.

Associate a Core Worker service profile

You can associate a Core Worker service profile with a deployment (production deployment or any of the additional deployments) so that you can change how the Core Worker service is performing.

  1. On the header bar, click Configuration > Data Centers.

    The Data Centers page appears with the default data center name, (On Premise Datacenter Database).

  2. On the Data Centers page, click the data center name.
  3. Under Service Profiles, by default, the Core Worker Service Profile is set to None (Default System Settings). Select a different service profile as needed and click Save.

    The Core Worker service profile is associated with the deployment once the service profile refresh interval has passed. The Core Worker functions as per the settings defined in the selected profile across all environments on that deployment and for all tenants using the environments on that deployment.

    When you edit a data center and remove the profile associated with a deployment, the Core Worker service uses the default settings from the Core Worker Service configuration file (Agility.Server.Core.WorkerService.exe.config).