White Papers

125 Lifecycle Controller Integration Best Practices Guide
20.2 List All Jobs in Job Store
Getting all the jobs in the job store is a matter of confirming the system is in a ready state and then enumerating the
DCIM_LifecycleJob class to view all available instances of the class.
Applies to: LC1.4.0+
Prerequisites for script: none
Script: ListAllJobs.win
A) The Lifecycle Controller remote service must be in a “ready” state before running any other WSMAN commands.
The GetRSStatus() method or the GetRemoteServicesAPIStatus() method may be used depending on the version of the
LC Management registered profile.
B) ENUMERATE the DCIM_LifecycleJob class to view all jobs. See section 2.2 for a definition of ENUMERATE.
20.3 Get Information About One Job
The URI for getting particular instance information is deterministic (i.e the InstanceID will be unique for each instance).
Job IDs are usually obtained directly from a concrete job, reboot job, or create target config job operations.
Applies to: LC1.3.0
Prerequisites for script: Set desired job variable by editing script
Script: Get1Job.win
A) The Lifecycle Controller remote service must be in a “ready” state before running any other WSMAN commands.
The GetRSStatus() method or the GetRemoteServicesAPIStatus() method may be used depending on the version of the
LC Management registered profile.
B) Use the instanceID from a concrete job, reboot job, or create target config job operation. Note: Reboot job IDs start
with RID_ instead of JID_. See section 2.3 for a definition of GET.
The instance of DCIM_LifecycleJob that contains the information on the job will be returned.
20.4 Delete All Jobs from Job Store (Job Queue) Using “JID_CLEARALL”
This workflow deletes all jobs from the job queue using by passing JID_CLEARALL as the jobID.
[LC1.5.x and prior] Running this command also restarts remote services.
Applies to: LC1.3.0
Prerequisites for script: none
Script: DeleteAllJobs.win