Launching Operational Rules 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, and 0 for
                      immediate) -->
              <ADMINISTRATOR name="admin"/>
              <SCHEDULE hour="16" minute="0" day="9" month="10" year="2011"/>
          </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"/>
          </OPTIONS>
      </PACKAGEASSOCIATIONS>
                                          
  2. Add the following step to a new or existing operational rule:
    • For operational rules: ** *> *
    • For software deployments: ** *> *
  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 .

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Client Management 12.2