Jump to

• Request
• Response
• Examples

Rerun Job

post

/essbase/rest/v1/jobs/{id}

Reruns the job, returning job information and new job ID.

Request

Path Parameters

• id: integer(int64)

  Job ID.

Back to Top

Response

Supported Media Types

• application/json
• application/xml

200 Response

OK

Job information returned successfully for newly created job ID.

Body ()

Root Schema : JobRecordBean

Type: object

Show Source

• appName(optional): string

  Application name.

• dbName(optional): string

  Cube name.

• endTime(optional): integer(int64)

  End time of the job.

• job_ID(optional): integer(int64)

  ID number of the job.

• jobfileName(optional): string
• jobInputInfo(optional): object jobInputInfo
  Additional Properties Allowed: additionalProperties
• jobOutputInfo(optional): object jobOutputInfo
  Additional Properties Allowed: additionalProperties
• jobType(optional): string

  The type of job. Examples: dataload, dimbuild, calc, clear, importExcel, exportExcel, lcmExport, lcmImport, clearAggregation, buildAggregation, asoBufferDataLoad, asoBufferCommit, exportData, mdxScript.

• links(optional): array links
• startTime(optional): integer(int64)

  Start time of the job.

• statusCode(optional): integer(int32)

  Job status code indicating progress. Each code has a corresponding statusMessage.

  
  

  statusCode	statusMessage
  100	IN_PROGRESS
  200	COMPLETED
  300	COMPLETED_WITH_WARNINGS
  400	FAILED

• statusMessage(optional): string

  Job status message string indicating progress. Each string has a corresponding statusCode.

  
  

  statusCode	statusMessage
  100	IN_PROGRESS
  200	COMPLETED
  300	COMPLETED_WITH_WARNINGS
  400	FAILED

• userName(optional): string

  User who ran the job. Users have access to job listings based on their assigned user role. For example, if you have the Service Administrator role, you can see all jobs; if you have the User role, you can see only the jobs you ran.

{
    "type":"object",
    "properties":{
        "job_ID":{
            "type":"integer",
            "format":"int64",
            "description":"<p>ID number of the job.</p>"
        },
        "appName":{
            "type":"string",
            "description":"<p>Application name.</p>"
        },
        "dbName":{
            "type":"string",
            "description":"<p>Cube name.</p>"
        },
        "jobType":{
            "type":"string",
            "description":"<p>The type of job. Examples: <code>dataload</code>, <code>dimbuild</code>, <code>calc</code>, <code>clear</code>, <code>importExcel</code>, <code>exportExcel</code>, <code>lcmExport</code>, <code>lcmImport</code>,  <code>clearAggregation</code>, <code>buildAggregation</code>, <code>asoBufferDataLoad</code>, <code>asoBufferCommit</code>, <code>exportData</code>, <code>mdxScript</code>.</p>"
        },
        "jobfileName":{
            "type":"string"
        },
        "userName":{
            "type":"string",
            "description":"<p>User who ran the job. Users have access to job listings based on their assigned user role. For example, if you have the Service Administrator role, you can see all jobs; if you have the User role, you can see only the jobs you ran.</p>"
        },
        "startTime":{
            "type":"integer",
            "format":"int64",
            "description":"<p>Start time of the job.</p>"
        },
        "endTime":{
            "type":"integer",
            "format":"int64",
            "description":"<p>End time of the job.</p>"
        },
        "statusCode":{
            "type":"integer",
            "format":"int32",
            "description":"<p>Job status code indicating progress. Each code has a corresponding <i>statusMessage</i>.</p><br><table><tr><th>statusCode</th><th>statusMessage</th></tr><tr><td>100</td><td>IN_PROGRESS</td></tr><tr><td>200</td><td>COMPLETED</td></tr><tr><td>300</td>    <td>COMPLETED_WITH_WARNINGS</td></tr><tr><td>400</td><td>FAILED</td></tr></table>"
        },
        "statusMessage":{
            "type":"string",
            "description":"<p>Job status message string indicating progress. Each string has a corresponding <i>statusCode</i>.</p><br><table><tr><th>statusCode</th><th>statusMessage</th></tr><tr><td>100</td><td>IN_PROGRESS</td></tr><tr><td>200</td><td>COMPLETED</td></tr><tr><td>300</td>    <td>COMPLETED_WITH_WARNINGS</td></tr><tr><td>400</td><td>FAILED</td></tr></table>"
        },
        "jobInputInfo":{
            "type":"object",
            "additionalProperties":{
                "type":"object"
            }
        },
        "jobOutputInfo":{
            "type":"object",
            "additionalProperties":{
                "type":"object"
            }
        },
        "links":{
            "type":"array",
            "items":{
                "$ref":"#/definitions/Link"
            }
        }
    }
}

Nested Schema : jobInputInfo

Type: object

Additional Properties Allowed

Show Source

• object additionalProperties

{
    "type":"object",
    "additionalProperties":{
        "type":"object"
    }
}

Nested Schema : jobOutputInfo

Type: object

Additional Properties Allowed

Show Source

• object additionalProperties

{
    "type":"object",
    "additionalProperties":{
        "type":"object"
    }
}

Nested Schema : links

Type: array

Show Source

• Array of: object Link

{
    "type":"array",
    "items":{
        "$ref":"#/definitions/Link"
    }
}

Nested Schema : additionalProperties

Type: object

Nested Schema : additionalProperties

Type: object

Nested Schema : Link

Type: object

Show Source

• href(optional): string
• method(optional): string
• rel(optional): string
• type(optional): string

{
    "type":"object",
    "properties":{
        "rel":{
            "type":"string"
        },
        "href":{
            "type":"string"
        },
        "method":{
            "type":"string"
        },
        "type":{
            "type":"string"
        }
    }
}

500 Response

Internal Server Error.

503 Response

Service Unavailable

Naming exception or server exception. Job ID is incorrect or invalid.

Back to Top

Examples

The following example shows how to rerun a previously executed job ID. A new job ID is created.

This example uses cURL to access the REST API from a Windows shell script. The calling user's ID and password are variables whose values are set in properties.bat.

Script with cURL Command

call properties.bat
curl -X POST "https://myserver.example.com:9001/essbase/rest/v1/jobs/28" -H "accept: application/json" -u %User%:%Password%

Example of Response Body

{
  "job_ID": 42,
  "appName": "Sample",
  "dbName": "Basic",
  "jobType": "Export Data",
  "jobfileName": null,
  "userName": "dbmanager",
  "startTime": 1585007505000,
  "endTime": 1585007505000,
  "statusCode": 100,
  "statusMessage": "In Progress",
  "jobInputInfo": {
    "compress": false,
    "columnFormat": false,
    "dataLevel": "3"
  },
  "jobOutputInfo": {
    "scriptOutputFileName": "",
    "scriptOutputFileNamePath": "",
    "infoMessage": "",
    "errorMessage": ""
  },
  "links": [
    {
      "rel": "get",
      "href": "https://myserver.example.com:9001/essbase/rest/v1/jobs/42",
      "method": "GET"
    }
  ]
}

Back to Top