Introduction
Job Runner allows users to create and upload arbitrary Node.js code within the Squiz DXP, empowering users to solve complex integration problems inappropriate for a workflow-based model.
What problem does the service solve?
Over 30% of Squiz Content Management users have been observed to employ CRON jobs that make direct Content Management PHP calls for various operations. This approach is not supported in the Squiz DXP environment. Job Runner solves this developer challenge by providing a way of uploading custom jobs within the DXP environment. With the addition of the Job Scheduler service, developers can control when jobs run in a similar way to how the old CRON job system operated.
Key parts of the service
The Job Scheduler part of the service is accessed through the Job Runner user interface.
Jobs are managed through the companion command line interface.
The API offers an alternative method of accessing the service. Developer can create integrations that operate independently from Squiz Content Management, which wasn’t possible through the CRON job method.
Key benefits of the service
Job Runner is connected to the Logs service and Event service. This integration offers the following benefits:
-
Logs for all job executions are available in the Logs Service.
-
Jobs can be triggered in response to events in other applications. For example, a job can be configured to run automatically whenever a Content Management page is updated.
Additionally, jobs are designed to run in sandboxed environments. The code within the Job Runner Service cannot interact with other API services without a valid API Token with the correct scope.