Adding template parts
When you specify template parts, you can insert parameters into their paths.
This allows you to add a level of abstraction to the template part definition so it can apply to multiple configurations. For example, a parameter like
??TARGET.WINDIR?? lets you choose a template part that applies to /c/winnt on some Windows servers and /c/windows on others.
The Parts list lets you select any version of a custom configuration object, even though that version of the object may not be included in your Configuration Object Dictionary.
When you use component template parts as the basis for compliance rules, consider system performance when choosing those parts. Often, you can improve performance by selecting a collection of server objects rather than many individual server objects.
For example, you can select the Applications list rather than individual applications. Or, you can select a configuration file rather than many individual settings in that configuration file. Every time the system processes a component template part, it must contact an agent for information about that part. If compliance rules reference ten separate template parts, the system must contact the agent ten times. If compliance rules reference ten parts that are all part of the same collection, the system only contacts the agent to retrieve the collection.
To add a template part to a component template
- On the Parts list, click Add to open the Add Parts window.
- Using the tree on the left, navigate to the server objects that you want to include in the component template. Click the right arrow to move your selections to the right panel.
- If you are editing an existing component template, you can also expand Local Config Files, Local Server Objects, or Local Extended Objects and select an object to include in the component template (for information about these objects, see Local Configuration Objects tab for a component template).
- If you are creating a new component template, no local objects are available because you have not yet had the opportunity to define any.
- If you want to select hierarchical server objects, (that is, file system, Windows registry, COM+/MTS, Metabase, or configuration file information), you must expand the tree and select the directories or individual items that you want.
As an alternative, to add a server object without searching through the tree on the left, follow these steps:
Click Add Newto display the New Component Template Part dialog box.
From Type, select the server object type that you want to add.
Note: The Command type is not applicable for the Browse, Snapshot, and Audit operations even if you have selected them as the allowed operations while defining the component template.
For Name/path, click Browseto select a server object or enter the name of a server object and its path. To insert a parameter in the path, use Select Property .
Finally, click OK.
The path and server object that you specify appears in the Selected Parts list on the right.
To remove a server object from the list on the right, select it and click the left arrow. To remove all server objects from the list on the right, click the double left arrow.
- Click OK to close the Add Parts window.
The template parts you defined appear in the Parts list.
- To include an entire hierarchy when adding a hierarchical server object (such as a directory):
- Select the top level server object in the Parts list.
Check Recurse subfolders at the bottom of the Includes/Excludes list.
This option includes all folders subordinate to the selected server object.
On target IBM AIX servers of version 5.3 with certain Technology Levels (TL) and Service Packs (SP), do not recurse the /proc directory. For more information, refer to IBM documentation for APAR IZ45882 and APAR IZ45883.
On target Windows servers, if a drive is not specified for a part, the Windows RSCD agent supplies a default drive, which is the value in the SystemDrive environment variable.