Create a Job
post
/api/broker/Jobs
Creates a new job.
The minimum required properties in the request body are:
The minimum required properties in the request body are:
- ServerID
- PackageName
- JobName
- JobProgram
- IsScheduled
- Minutes
- Hours
- Days
- Months
- WeekDays
- StatusID
- FailoverType
- Privileged
- ApplicationConfig
Request
There are no request parameters for this operation.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object
-
ApplicationConfig: array
ApplicationConfig
The array of JSON objects containing all the configuration values for the job.
-
Days: string
The days when the job is scheduled to run, in cron format. Use a comma-separated list of integers, or * to indicate every day.Example:
1
-
FailoverType: integer
The failover type ID. Allowed Values:
- 0: Standalone
- 1: Primary
- 2: Backup
Example:0
-
Hours: string
The hours when the job is scheduled to run, in cron format. Use a comma-separated list of integers, or * to indicate every hour.Example:
1
-
IsScheduled: integer
Whether the job is scheduled (1) or not (0).Example:
0
-
JobArguments: string
The optional job program arguments.Example:
--ssl-ca=/ssl/BundleCA.crt
-
JobDescription: string
The optional human-readable job description.Example:
This is an example description
-
JobName: string
The job reference name.
To avoid confusion with numeric IDs, the name value cannot be integers only or integers prefixed with the + or - symbols only. It must contain letters or other characters. For example, 1234, +1234, and -1234 are not valid, but US1234, US+1234 and US_1234 are.Example:Data backup
-
JobProgram: string
The job program file location & name (Path of executable relative to $BASEDIR).Example:
/opt/assure1
-
Minutes: string
The minutes when the job is scheduled to run, in cron format. Use a comma-separated list of integers, or * to indicate every minute.Example:
0
-
Months: string
The months when the job is scheduled to run, in cron format. Use a comma-separated list of integers, or * to indicate every month.Example:
2
-
PackageName: string
The package name.Example:
presentation-app
-
PrimaryJobID: integer
The primary job ID specified for failover.Example:
0
-
Privileged: integer
Whether the process should be run as a privileged user (1) or not (0).Example:
0
-
ServerID: integer
The server ID specified for job association.Example:
1
-
StatusID: integer
The job status ID. Either 0 (disabled) or 1 (enabled).Example:
0
-
WeekDays: string
The weekdays when the job is scheduled to run, in cron format. Use a comma-separated list of integers, or * to indicate every weekday.Example:
6
Nested Schema : ApplicationConfig
Type:
array
The array of JSON objects containing all the configuration values for the job.
Show Source
Nested Schema : items
Type:
Show Source
object
-
BrokerApplicationConfigName: string
The application configuration name.Example:
LogLevel
-
BrokerApplicationConfigTypeID: integer
The application configuration type ID.Example:
1
-
BrokerApplicationConfigValue: string
The application configuration value.Example:
Error
-
Required: boolean
Whether the configuration value can be left blank or not.Example:
0
Response
Supported Media Types
- application/json
200 Response
Successful operation
Root Schema : schema
Match All
Show Source
-
object
SuccessfulAddOperation
The response body for a successful add operation.
-
object
type
Nested Schema : SuccessfulAddOperation
Type:
object
The response body for a successful add operation.
Show Source
-
message: string
The response message.Example:
Added record
-
success: boolean
Whether the operation was a success (true) or a failure (false).Example:
true
Nested Schema : type
Type:
Show Source
object
-
data: array
data
-
total: integer
The total number of results regardless of paging.Example:
1
Nested Schema : brokerJobsRead
Type:
Show Source
object
-
ApplicationConfig: array
ApplicationConfig
The array of JSON objects containing all the configuration values for the job.
-
BrokerJobID: integer
The job ID.Example:
1
-
Days: string
The days when the job is scheduled to run, in cron format. Can be a comma-separated list of integers, or * to indicate every day.Example:
1
-
Decouple: boolean
Allows for different combinations of primary/backup job pairings or pairing jobs across servers that are not tied together.Example:
1
-
FailoverType: integer
The failover Type ID. Allowed Values:
- 0: Standalone
- 1: Primary
- 2: Backup
Example:0
-
FailoverTypeName: string
The failover type name.Example:
Standalone
-
Hours: string
The hours when the job is scheduled to run, in cron format. Can be a comma-separated list of integers, or * to indicate every hour.Example:
1
-
IsScheduled: integer
Whether the job is scheduled (1) or not (0).Example:
0
-
JobArguments: string
The optional job program arguments.Example:
--ssl-ca=/ssl/BundleCA.crt
-
JobDescription: string
The optional human-readable job description.Example:
This is an example description
-
JobName: string
The job reference name.Example:
Data backup
-
JobProgram: string
The job program file location and name (path of executable relative to $BASEDIR).Example:
/opt/assure1
-
Minutes: string
The minutes when the job is scheduled to run, in cron format. Can be a comma-separated list of integers, or * to indicate every minute.Example:
0
-
Months: string
The months when the job is scheduled to run, in cron format. Can be a comma-separated list of integers, or * to indicate every month.Example:
2
-
PackageName: string
The package name.Example:
presentation-app
-
PrimaryJobID: integer
The primary job ID specified for failover.Example:
0
-
PrimaryJobServerID: integer
The server ID of the server primarily responsible for the job.Example:
1
-
PrimaryServerID: integer
The database ID that identifies the primary server of the given server type (presentation, collection, database) in Assure1.Servers table.Example:
1
-
Privileged: integer
Whether the process should be run as a privileged user (1) or not (o).Example:
0
-
ServerID: integer
The server ID specified for job association.Example:
1
-
ServerName: string
The server name.Example:
example.com
-
State: string
The indicator of the job state.Example:
Running
-
StateIcon: string
The icon for representing the job states.Example:
OrbGreenUp.png
-
Status: string
The status, based on the value of the StatusID property. When StatusID is 0, Status is Disabled. When StatusID is 1, Status is Enabled.Example:
Disabled
-
StatusIcon: string
The status image name based on the the statusID. If the statusID is 0, then the StatusIcon is OrbRed.png. If the statusID is 1, then the StatusIcon is OrbGreen.png.Example:
OrbRed.png
-
StatusID: integer
The job status ID. Either 0 (disabled) or 1 (enabled).Example:
0
-
WeekDays: string
The weekdays when the job is scheduled to run, in cron format. Can be a comma-separated list of integers, or * to indicate every weekday.Example:
6
Nested Schema : ApplicationConfig
Type:
array
The array of JSON objects containing all the configuration values for the job.
Show Source
Nested Schema : items
Type:
Show Source
object
-
BrokerApplicationConfigName: string
The application configuration name.Example:
LogLevel
-
BrokerApplicationConfigTypeID: integer
The application configuration type ID.Example:
1
-
BrokerApplicationConfigValue: string
The application configuration value.Example:
Error
-
Required: boolean
Whether the configuration value can be left blank or not.Example:
0
Default Response
Failed operation
Root Schema : schema
Type:
Show Source
object
-
errors: array
errors
The list of errors reported. Validation errors will be keyed by record field.
-
message: string
The response message.Example:
Exception thrown
-
success: boolean
Whether the operation was a success (true) or a failure (false).Example:
false
Nested Schema : errors
Type:
array
The list of errors reported. Validation errors will be keyed by record field.
Show Source
-
Array of:
object items
An error.
Nested Schema : items
Type:
object
An error.