Collaboration Job Controller

   Journey Manager (JM) The transaction engine for the platform.  |    System Manager / DevOps  |  All versions This feature is related to all versions.

The collaboration job controller is the scheduled job service, which runs as a single threadA thread of execution is the smallest sequence of programmed instructions that can be managed independently by a scheduler, which is typically a part of the operating system. to processes collaboration jobs. First, it selects a list of collaboration jobs that are available for processing.Then, it goes through each collaboration job in the list and calls an associated job controller service. The job controller service definition is used to process collaboration job's actions specified in each step and go (route) to the next step, until an endpoint is reached. Each collaboration job runs until a wait action is encountered, or an error is thrown during the collaboration job action or the collaboration job successfully completes. The scheduled job terminates when there are no more collaboration jobs in the list to process.

The scheduler only starts one collaboration job thread at a time. A large backlog of work may take more than a minute for the thread to complete. A new collaboration job thread won't be started until the previous one has completed.

The default collaboration job controller configuration is shown below.

The default interval is 1 minute, which is the value we recommend for production environments. However, it is useful to set this interval to 15 seconds in on a development environment to improve development and testing turnaround.

Next, learn how to manage scheduled jobs