Space banner

   

TEST - please delete me.

Assigning application management policies through XML

The entire process of creating, distributing and assigning Application Management Policies can be accomplished within the Console . Alternatively you can include an XML file which contains information about:

  • assigned application management policies
  • assigned devices
  • administrator with which assignment is created
  • schedule

With this method you can modify Application Management Policies by editing the XML file without needing to have access rights to the Console .

  1. Create an XML file with the following format:

    <?xml version="1.0" encoding="UTF-8"?>
    <OBJECTASSOCIATIONS><!-- This section must contain the list of application rules to assign -->
        <OBJECTS>
            <!-- type can be OperationalRule, Package, PatchGroup or ApplicationList -->
            <!-- the object can be referenced with its database ID with attribute "id" -->
            <!-- or through its name with attribute "name" -->
            <OBJECT type="ApplicationList" id="1001"/>
        </OBJECTS>
        <DEVICES>
            <!-- This section contains the list of devices to which the objects are to be assigned -->
            <!-- Devices can be referenced with database ID (attribute "id") -->
            <!-- or name (attribute "name") -->
        
            <DEVICE id="1000"/>
            <DEVICE name="Device X"/>
        </DEVICES>
        <DEVICEGROUPS>
            <!-- This section contains the list of device groups to which the objects are to be assigned -->
            <!-- Groups can be referenced with database ID (attribute "id") -->
            <!-- or name (attribute "name") -->
        
            <DEVICEGROUP id="1000"/>
            <DEVICEGROUP name="My Group"/>
         </DEVICEGROUPS>
        <OPTIONS>
            <!-- Which administrator profile will be used for the assignment -->
            
            <ADMINISTRATOR name="admin"/>
            
            <!-- When will the object assignment be sent to devices (number of hours, minutes, and so on, and 0 for immediate) -->
            <!-- This only applies to OperationalRule, Package, PatchGroup object types -->
            
            <SCHEDULE hour="16" minute="0" day="9" month="10" year="2011"/>
            
            <!-- Add if type is OperationalRule and only advertizemnt is needed -->
            
            <ADVERTIZE/>
        </OPTIONS>
    </OBJECTASSOCIATIONS>
                            

    You can mix object types in this file (for example,include application lists, devices and/or groups.

  2. Add the following step to a new or existing operational rule: Master Steps > Assignment Management 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 administrator is a default administrator that will only be used if no administrator is defined in the XML file.
  4. Enter the directories into which the xml files are to be copied in case of success or error.

    If an error occurred during the assignment process you can find a explanation on what happened in the OperationalRules.log file

    You can list device and/or device groups in this file, depending on the targets of the specified objects. If, for example, the objects are only to be assigned to device groups, the <DEVICES> section is not needed.

  5. If you want the assignments directly activated, that is, to become operative right away, check the Activate Created Assignment box. If this box is left unchecked the assignments will remain paused.
  6. If the newly defined assignment is to overrule any possibly already existing assignment, that is, if the object is to be reassigned with the new information, check the Reassign if Assignment Already Exists box. If you do not check this box and such an object assignment already exists, the original assignment will still be valid.

You created an object assignment which launches the management of application lists through an XML file. If you want to change the schedule or modify the included patch groups/application policies/administrator you can do so directly in the XML file without having to launch the console.

Unassigning application list

This step also allows you to unassign application list assignments. To execute such an operation the same information is required as for the assignment process. The only difference lies in the contents of the XML file: the opening and closing tag of the file use the expression <OBJECTUNASSIGN> instead of <OBJECTASSOCIATIONS>. Example:

        <![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<OBJECTUNASSIGN>
    <OBJECTS>
        <OBJECT type="ApplicationList" name="Prohibiting Pinball"/>
    </OBJECTS>
    <DEVICEGROUPS>
        <DEVICEGROUP id="1000"/>
        <DEVICEGROUP name="My Group"/>
    </DEVICEGROUPS>
</OBJECTUNASSIGN>
Was this page helpful? Yes No Submitting... Thank you

Comments