White Papers

APIs
23 Updating Firmware using OpenManage Enterprise APIs
Attribute Name T
y
pe Description Required
catalogID String Catalog ID derived from
enumeratin
g
catalo
g
s
Yes
operationName String Type of operation (install
firmware
)
Yes
complianceUpdate Boolean Indicates if this update must
match compliance
Yes
signVerify Boolean Indicates if the DUP signature
must be verified
Yes
stagingValue Boolean If “true” stages updates and runs
them on the next reboot of the
s
y
stem
Tar
g
ets
ID Integer Identifier of the device to be
updated
Yes
Data String String identifying component to
be updated (seen from the
component compliance report ID
“SourceName” field)
For multiple components
separate each value by a semi-
colon
Yes
Tar
g
etT
y
pe
ID Inte
g
er Numeric device t
y
pe ID Yes
Name Strin
g
Device/Group Yes
Example: Request Payload
{
"Id":0,
"JobName":"Update Firmware: single device, single component",
"JobDescription":"Firmware Update Job: for single device, single component",
"Schedule":"startNow",
"State":"Enabled",
"JobType":{
"Id":5,
"Name":"Update_Task"
},
"Params":[
{
"JobId":0,
"Key":"complianceReportId",
"Value":"6"
},
{
"JobId":0,