Services node


A service entity in the content format file represents most of the definitions of a component template. Each defined service corresponds to a single component template in the TrueSight Server Automation Console.

Warning

Note

The definitions of the compliance rules associated with a component template are represented separately in the content format file as policy entities.

Under the services node, individual services are grouped under folders, which correspond to component template groups. The service ID is used internally in the file for associating other objects, such as entities, to services.

The following XML code shows the basic format of the services node.

<services>
 <folder name="Component Template Group">
   <service id="internal_service_id">
     <notes>notes for service</notes>
   </service>
 </folder>
</services>

For each service, you can choose to include the following nodes of service definitions:

Allowed-operations node

This node lists allowed operations for a component template, as defined on the General panel of a component template in the TrueSight Server Automation Console.

The following XML code lists allowed operations.

<allowed-operations>
 <operation id="Discover"/>
 <operation id="Snapshot"/>
 <operation id="Audit"/>
 <operation id="Deploy"/>
 <operation id="Compliance"/>
 <operation id="Allow_Remediation"/>
 <operation id="Allow_Auto_Remediation"/>
</allowed-operations>

Configuration-objects node

This node defines local configuration objects for a component template, as defined on the Local Configuration Objects panel of a component template in the TrueSight Server Automation Console. Configuration objects include extended objects, server objects, and configuration files.

<configuration-objects>
 <extended-objects>
    <extended-object id="Groups">
       <description></description>
       <grammar-data grammar-ref="ini.gm" os="Windows" encoding="Default"/>
       <command remote-execution="false">blquery $server:host$ -E "/C/Program Files/BMC Software/BladeLogic/8.0/share/sensors/ extended_objects/groups.blq"</command>
    </extended-object>
 </extended-objects>
 <server-objects>
    <class root="false" version="1" name="Extended Object" id="Extended Object" built-in="false">
       <properties>
          <property name="Path" id="Path" type="Primitive:String"/>
          <property name="Name" id="Name" type="Primitive:String"/>
       </properties>
    </class>
 </server-objects>
 <configuration-files>
    <configuration-file id="??TARGET.WINDIR??/desktop.ini">
       <grammar-data grammar-ref="ini.gm" os="Windows" encoding="Default"/>
       <path>??TARGET.WINDIR??/desktop.ini</path>
    </configuration-file>
 </configuration-files>
</configuration-objects>

Properties node

This node defines properties assigned to the component template, not including local properties. The following XML code defines one property.

<properties>
 <property id="AUTO_GENERATED">
    <value>true</value>
 </property>
</properties>

Local-properties node

This node defines local properties assigned to the component template, as defined on the Local Properties panel of a component template in the TrueSight Server Automation Console.

<local-properties>
 <property deprecated="false" editable="true" built-in="false" required="false" used-in-report="false" id="MY_INTEGER_ENUM" type="enumeration">
   <description></description>
   <enumeration type="Primitive:Integer">
      <value name="intvalue1" id="intvalue1">1</value>
      <value name="intvalue2" id="intvalue2">2</value>
   </enumeration>
   <default>
      <value>1</value>
   </default>
 </property>
 <property deprecated="false" editable="true" built-in="false" required="false" used-in-report="false" id="TEST_INTEGER" type="Primitive:Integer">
   <description></description>
   <default>
      <value>10</value>
   </default>
 </property>
</local-properties>

Parts node

This node defines the server objects that make up the component template, as defined on the Parts panel.

<parts>
  <part id="File:??EXTPROC_HOME??/extproc.exe">
     <notes>My part notes</notes>
     <item>
       <type>File</type>
       <path>??EXTPROC_HOME??/extproc.exe</path>
     </item>
     <allowed-operations>
       <operation id="Discover"/>
       <operation id="Snapshot"/>
       <operation id="Audit"/>
       <operation id="Compliance"/>
     </allowed-operations>
     <includes-excludes recurse-subfolders="true"/>
  </part>
  <part id="Windows Service:BladeLogic RSCD Agent">
     <notes></notes>
     <item>
       <type>Windows Service</type>
       <path>BladeLogic RSCD Agent</path>
     </item>
     <allowed-operations>
       <operation id="Browse"/>
       <operation id="Snapshot"/>
       <operation id="Audit"/>
       <operation id="Compliance"/>
     </allowed-operations>
     <includes-excludes recurse-subfolders="true"/>
  </part>
</parts>

Signature node

This node defines the component signature used in discovery, as defined on the Discovery panel. You can instead refer to a signature defined in the rule library.

The following XML code defines a signature.

<signature>
 <rule name="Template Signature" service="xml test service">
   <expression><![CDATA[??TARGET.OS?? is one of ["AIX", "Linux", "HP-UX", "Windows"]]]></expression>
 </rule>
</signature>

 

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

TrueSight Server Automation 21.02