Content format XML files overview
Content format files are structured hierarchically. At the top level, you can choose to include root nodes for the following entities:
Entity in content format | Description |
|---|---|
operators | A list of available operators used within rules or signatures. |
grammars | A list of grammar files used by configuration files and extended objects. |
packages | Definitions of the BLPackages available for compliance rule remediation. Each defined package in the content format file corresponds to a single BLPackage in the TrueSight Server Automation Console. |
types | Definitions for the following types of data used in TrueSight Server Automation (as accepted, for example, by rules, properties, or configuration objects):
|
data instances | Definitions of a property class instance. |
rule library | A library of compliance rules or discovery signatures. |
services | A group of definitions for a component template. Each defined service corresponds to a single component template. |
service instances | Each service instance corresponds to an instance of a local property set defined for a component template. |
policies | A group of compliance rules associated with a component template. Each policy contains all compliance rules defined for a single component template. |
The following example presents a block of XML code at its highest level within a content format file, with all subordinate nodes collapsed:
<content locale="en">
<operators>
<grammars>
<packages>
<types>
<data-instances>
<rule-library>
<services>
<service-instances>
<policies>
</content>