White Papers

Behavioral differences
28 Updating Firmware using OpenManage Enterprise APIs
The equivalent action to clicking on “Check Compliance” is to issue a POST on
/api/JobService/Actions/JobService.RunJobs with the payload specified below
{
"JobIds": [27734]
}
Once this completes the inventory will be refreshed and subsequent calls to check the compliance against
/api/UpdateService/Baselines(<BaselineID>)/DeviceComplianceReports should succeed and indicate current
status.
In OpenManage Enterprise when the firmware update job completes, an inventory task is kicked off
automatically – this enables future requests on the baseline compliance to be “current” as data has been
refreshed. If all the internal jobs have completed, then the compliance data remains current. If the internal
auto-spawned baseline job (after the inventory task completes) is still running, the POST operation to run the
same job will fail with an error message indicating that the job may already be running. This needs to be
gracefully handled by the application or the script but no impact to compliance data and the data remains
current. If the POST operation is kicked off before the internal auto-spawned baseline job, it’s possible that
the internal job will fail and reflect an error in the UI though there is no impact to compliance data and it stays
current