Web Services Interface Guide

Dell™ Lifecycle Controller 2 Web Services Interface Guide for Linux Version: 2.1.0
178
<n1:MessageID>STOR018</n1:MessageID>
<n1:ReturnValue>2</n1:ReturnValue>
</n1:ClearForeignConfig_OUTPUT>
16.14 Applying the Pending Values for RAID-CreateTargetedConfigJob()
The CreateTargetedConfigJob() method is called to apply the pending values created by RAID
methods. The system will automatically reboot depending on the ScheduledStartTime selected. The
CreateTargetedConfigJob() jobID output with the job control section can be used to obtain its status.
Invoke CreateTargetedConfigJob() with the following parameters and syntax:
TARGET: This parameter is the FQDD of the DCIM_ControllerView (Section 16.7)
RebootJobType: There are three options for rebooting the system.
1 = PowerCycle
2 = Graceful Reboot without forced shutdown
3 = Graceful reboot with forced shutdown
Note: When a user does not want to set a reboot type when creating a target job,
users should comment out the RebootJobType in the input xml. User should not enter
“0” or give no parameter at all in the input xml.
ScheduledStartTime & UntilTime: See Section 3.2.4
EXAMPLE:
wsman invoke -a CreateTargetedConfigJob http://schemas.dmtf.org/wbem/wscim/1/cim-
schema/2/root/dcim/DCIM_RAIDService
?SystemCreationClassName=DCIM_ComputerSystem,CreationClassName=DCIM_RAIDService,SystemNa
me=DCIM:ComputerSystem,Name=DCIM:RAIDService -h $IPADDRESS -V -v -c dummy.cert -P 443
-u $USERNAME -p $PASSWORD -J CreateTargetedConfigJob_RAID.xml
-j utf-8 -y basic
The input file CreateTargetedConfigJob_RAID.xml is shown below:
<p:CreateTargetedConfigJob_INPUT xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-
schema/2/root/dcim/DCIM_RAIDService">
<p:Target>RAID.Integrated.1-1</p:Target>
<p:RebootJobType>3</p:RebootJobType>
<p:ScheduledStartTime>TIME_NOW</p:ScheduledStartTime>
<p:UntilTime>20111111111111</p:UntilTime>
</p:CreateTargetedConfigJob_INPUT>
OUTPUT:
When this method is executed, a jobid or an error message is returned. The status of this jobid can be
checked within the job control provider in Section 10.
<n1:CreateTargetedConfigJob_OUTPUT>
<n1:Job>