Space banner

   

TEST - please delete me.

Launching operational rules and software deployments through XML

The entire process of creating, distributing and executing operational rules/software deployments can be accomplished within the . Alternatively you can include a XML file which contains information about:

  • Assigned operational rules/packages
  • Assigned devices
  • Administrator with which assignment is created
  • Schedule

With this method you can modify operational rules/software deployments by editing the XML file without needing to have access rights to the .

  1. Create an XML file with the following format:
    • for operational rules:

      <?xml version="1.0" encoding="UTF-8"?>
      <RULEASSOCIATIONS>
          <!-- This section must contain the list of operational rules to assign -->
          <RULES>
              <RULE id="1001"/>             // The Rule ID/Name must be the exact value that 
              <RULE name="Test Rule"/>         the rule is known in the console.
          </RULES>
          <DEVICES>
              <!-- This section must contain the list of devices to which the rules are to
                      be assigned -->
              <DEVICE id="1000"/>             // The Device ID/name must be the exact value
              <DEVICE name="Device X"/>          that the device is known in the console.
          </DEVICES>
          <OPTIONS>
              <!-- When will the rule be activated (number of hours, minutes, and so on.
                      Set the hours="0" to immediately activate and execute) -->
              <ADMINISTRATOR name="admin"/>
              <SCHEDULE hour="16" minute="0" day="9" month="10" year="2011"/>
          	<!--Possible value for NETWORKINSTALL: "normal", "administrative"
      		and "network"-->
      	<NETWORKINSTALL mode="normal" /> 
      	</OPTIONS>
      </RULEASSOCIATIONS>                                
    • for software deployments:

      <?xml version="1.0" encoding="UTF-8"?>
      <PACKAGEASSOCIATIONS>
          <!-- This section must contain the list of packages to assign -->
          <PACKAGES>
              <PACKAGE id="1001"/>          // The Package ID must be the value that the package
          </PACKAGES>                            is known in the console.
          <DEVICES>
              <!-- This section must contain the list of devices to which the packages are
                      assigned to-->
              <DEVICE id="1000"/>           // The Device ID must be the value that the device is
              <DEVICE id="1002"/>               known in the console.
          </DEVICES>
          <OPTIONS>
              <!-- This section contains the optional parameters, such as the administratorunder 
                      which the packages are assigned and the schedule. -->
                      
              <ADMINISTRATOR name="admin"/>
              <SCHEDULE hour="16" minute="0" day="9" month="10" year="2011"/>
      	<!--Possible value for NETWORKINSTALL: "normal", "administrative"
      		and "network"-->
      	<NETWORKINSTALL mode="normal" />
          </OPTIONS>
      </PACKAGEASSOCIATIONS>
                                          
  2. Add the following step to a new or existing operational rule:
    • For operational rules: Master Steps > Operational Rule Assignment via XML File
    • For software deployments: Master Steps > Package Assignment via XML File
  3. In the Properties dialog enter the complete path to the storage location of the XML file, as well the administrator name in the respective text boxes. This is a default administrator that will only be used if no administrator is defined in the XML file.

You created an Operational Rule which launches Operational Rules/Software Deployments through an XML file. If you want to change schedule or modify included Operational Rules/Packages/Administrator you can do so directly in the XML file without having to launch the console.

Was this page helpful? Yes No Submitting... Thank you

Comments