Connector jobs can be triggered from the platform instead of being scheduled directly within the connector. This allows data requests to be initiated and managed centrally from the platform, which is useful when connector jobs need to run in response to platform events or as part of a process chain.
This capability is available on Version 2 connectors and later.
How it works
The platform stores remote execution requests in a designated object. The connector periodically polls this object for new requests and runs the specified job at the requested time. Once executed, the connector reports the outcome back to the platform via a status update, which is processed through a configured file handler and import process.
Prerequisites
The connector authenticates with the platform using its client certificate. The certificate distinguished name and public certificate must be registered with the platform before remote execution can be used. See Client Certificates for Connectors.
Platform configuration
To support remote connector execution, the following must be configured in the platform:
An object to store remote execution requests
A process to monitor and update execution status from connector responses
A file handler to receive status updates from the connector
Contact support or your implementation team for the specific object structures and process templates required for your instance.
Connector configuration
Enable remote execution in the platform OData credentials file (platform-odata-credentials.properties):
Property | Description | Default |
| Enable remote execution polling | false |
| Object used to store remote execution requests |
|
| Identifier used when polling for requests — must match the value used when creating requests on the platform side | connector |
| How frequently the connector checks for new requests | 1 minute |
Creating execution requests
Requests can be created manually or generated by a platform process. Each request record contains the following fields:
Field | Description |
Connector Name | Identifies which connector should run the job |
Query Name | The name of the query configured on the connector |
Execution Date and Time | When the connector should run the job |
Parameters | Optional parameters required by the query; multiple parameters can be provided |
Status | Set to Queued for new requests |
Message | Populated by the connector once the job is processed |
Execution behaviour
The connector picks up requests with a status of Queued and schedules them for the specified execution time. If the execution time has already passed when the connector polls, it runs outstanding requests in order of their scheduled time.
Once executed, the connector processes the request using the same mechanism as a locally scheduled job.
Status updates
The connector reports back to the platform with one of the following statuses:
Accepted — the request has been validated and scheduled
Rejected — the request could not be processed due to invalid configuration or parameters
Success — the job completed successfully
Status updates are processed through the configured file handler and associated import process.