White Papers

Version 1.2.0 13
system’s status (as reflected in the ServerStatus output parameter) and overall API status (as reflected in 320
the Status output parameter). 321
NOTE: In 11G, management applications have to invoke DCIM_LCService.GetRSStatus() or 322
GetRemoteServicesAPIStatus() method (as described in the LC Management Profile) to determine that the 323
completed job changes have been successfully reflected in the LC instrumentation API interface. 324
325
READY FOR EXECUTION
SCHEDULED
RUNNING
COMPLETED
READY
RELOADING
READY
Job Status
DM Status / RS
Status
Time
SYNC
TIME
326
Figure 4 – Configuration Job Timing Diagram 327
6.8.2 Update Job
328
The workflow below details the update job lifecycle (DCIM_SoftwareInstallationService.InstallFromURI() 329
invocation). The direct update jobs that do not required reboot transition from “Downloading” state to a 330
terminal state of “Failed” or “Completed”. Update jobs that require a reboot will go from state of 331
“Downloading” to a state of “Downloaded” or “Failed”. Once in “Downloaded” state, the update job needs 332
to be scheduled using the SetupJobQueue() method in the LC Management Profile (similar to 333
configuration jobs). 334