Merge Compliant All Assigned operation
For enforced compliance, a configuration is enforced to comply to a standard. A standard is defined as a set of rules. Enforcement is requested to all assigned Rule Sets, a specific Rule Set, or a specific rule. Merge Compliant All Assigned operation enforces a configuration to comply to all assigned Rule Sets.
The following table describes the elements for the <items> XML element and adapter request for the Merge Compliant All Assigned operation.
Elements for the <items> XML element and adapter request for the Merge Compliant All Assigned operation
The following figure shows a sample <items> XML element for the Merge By Config Type operation.
<items> XML element for the Merge Compliant All Assigned operation
<item>
<parameters>
<job-params-dto>
<annotation>a</annotation>
<change-id>a</change-id>
<device-filter>
<dynamic-field-range>
<element>
<dynamic-field-key-string>a</dynamic-field-key-string>
<range>
<key>a</key>
</range>
</element>
<element>
<dynamic-field-key-string>b</dynamic-field-key-string>
<range>
<key>b</key>
</range>
</element>
</dynamic-field-range>
<dynamic-fields>
<element>
<name>a</name>
<value>a</value>
</element>
<element>
<name>b</name>
<value>b</value>
</element>
</dynamic-fields>
<key>a</key>
<access-mode>1</access-mode>
<address-match>a</address-match>
<created>
<key>a</key>
<end-date>1215099084593</end-date>
<start-date>1215099084593</start-date>
<time-period-type-id>1</time-period-type-id>
</created>
<device-agent-info-name>a</device-agent-info-name>
<device-security-profile-name>a</device-security-profile-name>
<device-type-id>1</device-type-id>
<group-name>a</group-name>
<ios-hw-filter>
<entity-descr-match>a</entity-descr-match>
<entity-name-match>a</entity-name-match>
<entity-pid-match>a</entity-pid-match>
<entity-sn-match>a</entity-sn-match>
<entity-vid-match>a</entity-vid-match>
<file-system-free-size>
<key>a</key>
<max>1</max>
<max-inclusive>true</max-inclusive>
<min>1</min>
<min-inclusive>true</min-inclusive>
<range-type-id>1</range-type-id>
</file-system-free-size>
<file-system-name-match>a</file-system-name-match>
<file-system-total-size>
<key>a</key>
<max>1</max>
<max-inclusive>true</max-inclusive>
<min>1</min>
<min-inclusive>true</min-inclusive>
<range-type-id>1</range-type-id>
</file-system-total-size>
<memory-name-match>a</memory-name-match>
<memory-size>
<key>a</key>
<max>1</max>
<max-inclusive>true</max-inclusive>
<min>1</min>
<min-inclusive>true</min-inclusive>
<range-type-id>1</range-type-id>
</memory-size>
</ios-hw-filter>
<last-span-action-days>1</last-span-action-days>
<last-span-action-days-action-type>1</last-span-action-days-action-type>
<last-span-action-days-flag>true</last-span-action-days-flag>
<last-span-action-error-match>a</last-span-action-error-match>
<last-span-action-status>1</last-span-action-status>
<last-span-action-status-action-type>1</last-span-action-status-action-type>
<last-span-action-status-flag>true</last-span-action-status-flag>
<last-span-action-success-date-action-type>1</last-span-action-success-date-action-type>
<last-span-action-success-date-flag>true</last-span-action-success-date-flag>
<last-span-action-success-days>1</last-span-action-success-days>
<last-span-action-success-days-action-type>1</last-span-action-success-days-action-type>
<last-span-action-success-days-flag>true</last-span-action-success-days-flag>
<last-span-action-success-time-period>
<key>a</key>
<end-date>1215099084593</end-date>
<start-date>1215099084593</start-date>
<time-period-type-id>1</time-period-type-id>
</last-span-action-success-time-period>
<model-match>a</model-match>
<name-match>a</name-match>
<no-discrepancies-flag>true</no-discrepancies-flag>
<no-discrepancies-include>true</no-discrepancies-include>
<no-violations-flag>true</no-violations-flag>
<no-violations-include>true</no-violations-include>
<online>1</online>
<os-image-discrepancy-flag>true</os-image-discrepancy-flag>
<os-image-discrepancy-include>true</os-image-discrepancy-include>
<os-image-match>a</os-image-match>
<realm-name>a</realm-name>
<running-startup-discrepancy-flag>true</running-startup-discrepancy- flag>
<running-startup-discrepancy-include>true</running-startup-discrepancy-include>
<running-trusted-discrepancy-flag>true</running-trusted-discrepancy-flag>
<running-trusted-discrepancy-include>true</running-trusted-discrepancy-include>
<running-violation-flag>true</running-violation-flag>
<running-violation-include>true</running-violation-include>
<startup-trusted-discrepancy-flag>true</startup-trusted-discrepancy-flag>
<startup-trusted-discrepancy-include>true</startup-trusted-discrepancy-include>
<startup-violation-flag>true</startup-violation-flag>
<startup-violation-include>true</startup-violation-include>
<transfer-mode>1</transfer-mode>
<vendor-id>1</vendor-id>
</device-filter>
<dynamic-fields>
<element>
<name>a</name>
<values>
<element>foo</element>
<element>bar</element>
</values>
</element>
<element>
<name>b</name>
<values>
<element>foo</element>
<element>bar</element>
</values>
</element>
</dynamic-fields>
<job-approval-type-key>a</job-approval-type-key>
<login-password>a</login-password>
<login-user-name>a</login-user-name>
<privileged-password>a</privileged-password>
<privileged-user-name>a</privileged-user-name>
<run-at-time>1215099084593</run-at-time>
<span-keys>
<element>a</element>
<element>b</element>
</span-keys>
<task-id>a</task-id>
</job-params-dto>
<wait-for-completion>true</wait-for-completion>
<smart-merge-mode>1</smart-merge-mode>
<syntax-scan>true</syntax-scan>
<make-trusted>true</make-trusted>
<commit>true</commit>
</parameters>
</item>
</items>
The following figure shows a sample adapter request for the Merge Compliant All Assigned operation.
Sample adapter request for the Merge Compliant All Assigned operation
<entity>span-action</entity>
<request>
<operation-name>do-merge-compliant-all-assigned</operation-name>
<parameters>
<job-params-dto>
<annotation>merge compliant all assigned</annotation>
<change-id>mcaa02</change-id>
<span-keys>
<element>714294386-41</element>
</span-keys>
</job-params-dto>
<wait-for-completion>false</wait-for-completion>
<smart-merge-mode>0</smart-merge-mode>
<syntax-scan>true</syntax-scan>
<make-trusted>true</make-trusted>
<commit>true</commit>
</parameters>
</request>
</bmc-configuration-automation-networks-request>
The following figure illustrates the adapter response for the sample Merge Compliant All Assigned operation.
Adapter response for the sample Merge Compliant All Assigned operation
<metadata>
<status>success</status>
</metadata>
<parameters>
<output>BCA000158</output>
</parameters>
</bmc-configuration-automation-networks-response>