Practices Guide

Lifecycle Controller Integration―Best Practices Specification
131
E) CreateSystemConfigJob(): Apply the pending values, pass ScheduledStartTime of
TIME_NOW, to invoke the reboot to apply the new attribute values immediately.
NOTE: This method also allows the user to schedule when to apply the attribute value change. If
the schedule is TIME_NOW, the PendingValue will be applied to the CurrentValue of the attribute
immediately. There is no reboot required for setting system attributes as indicated in the output
parameter RebootRequired.
F) Poll jobstatus for Completed: GET the InstanceID of from E). See section 2.3 for a
definition of
GET.
G) Repeat C) to confirm successful execution of the method by examining PendingValue
property of the attributes that were set by this step.
28.7 Apply Pending System Attribute Values
See the previous section, Setting and Applying System Attributes, for a use case for this
method.
28.8 Delete Pending System Attribute Values
Use the following procedure below to delete pending configurations/values set by the
setAttribute(s) method.
Applies to: LC1.5.0+
Prerequisites for script: none
Script: DeletePendingSystemInfoConfiguration.win
A) The Lifecycle Controller remote service must be in a “ready” state before executing 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) GetSystemViews(): ENUMERATE the DCIM_SystemAttributes class to view all available
FQDDs. See section 2.2 for a definition of
ENUMERATE .
C) DeletePendingSystemConfiguration(): Invoke the DeletePendingSystemConfiguration()
method on the DCIM_SystemManagementService class to delete pending configurations on
ALL system attributes.
A return message of “No pending data present to delete” indicates that there is no pending
configuration to delete for the respective FQDD.