Unless otherwise specified, jobs submitted via the Compute App will use the default execution service. The Compute Interface also allows the client to specify which execution service to use. Administrators can also mark certain execution services as requiring authorization, which allows only users with the correct authority group to access them. If the client tries to submit a compute job to a service they do not have permission to use, the request is rejected.
Two default execution services called PRIMARY and SECONDARY are configured during installation. Developers might choose to route longer jobs to PRIMARY and shorter jobs to SECONDARY as a way to improve throughput and avoid blocking.
To add an execution service:
In the Execution Services section of the Execution Services admin page, click NEW EXECUTION SERVICE.
The New Execution Worker dialog is displayed.
Complete the following fields:
Name (required): An alias for the execution service that serves as a brief identifier, such as FAST_LANE.
Enabled: Whether the execution service should be active and available for use. Deselect this option if you want to disable the execution service.
Default Service: Whether this execution service should be the default execution service for models that do not specify an execution service.
Requires Authorization: Whether to restrict access to the execution service to users with specific permissions. Access is granted via the Execution Service Authorities panel on the Authority Groups page. For more information, see Managing Authority Groups.
Click SAVE.
At any time, you can edit the execution service details by clicking the execution service in the Name column of the Execution Services section.
