Page tree
Skip to end of metadata
Go to start of metadata

You can identify additional configuration files that should appear under the Configuration object of a server in the Servers folder.

Before you begin

When performing this procedure, you must choose the grammar file used to parse information that is displayed as a configuration file. BMC Server Automation supports many types of grammars that can parse files and output file contents in a format consistent with other information you view when browsing server objects or viewing the results of snapshots or audits. For a description of the available grammar files, see Grammar files supported by BMC Server Automation. The following procedure also explains how to add local configuration objects to a component template.

Note

  • BMC Server Automation does not support configuration files that include binary data.
  • You can set a limit to the number of records that a server can provide an Application Server for a single configuration file. To accomplish this, you must use the Application Server Administration console (that is, the blasadmin utility) to set a value for the MaxConfigRecords option. By default this value is set to 50,000. For more information, see Restricting the size of configuration and extended objects.

To identify additional configuration files for a server

  1. Do one of the following:
    • Select Configuration > Config Object Dictionary. The Config Object Dictionary opens.
    • When editing a component template, click Local Configuration Objects on the shortcut bar to display the Local Configuration Objects panel. It provides the same options as the Configuration Object Dictionary.
  2. Do one of the following:
    • To add a new configuration file, click Add Configuration Object . The New Configuration Object wizard opens. On the General panel, select Configuration File, if it is not already selected, and click Next. The Configuration File panel of the wizard appears.
    • To modify an existing configuration file, select the file and click Edit Configuration Object . The Edit Configuration Object: Configuration File window appears. It provides the same options as the Configuration File panel of the Configuration Object wizard. When using the Configuration Object Dictionary, you can filter the list of configuration objects displayed using the drop-down lists at the top of the window to select the category of configuration objects, the relevant operating system, or both. These filters are not available when creating local configuration objects.

      If you select Server Objects in the drop-down list at the top, two additional types of filtering are possible. A drop-down list lets you select All or Root. Selecting All displays all types of server objects, including all built-in server objects and all custom configuration objects. Selecting Root displays only root objects (both built-in and custom configuration objects). You can also filter on server object names by entering text in the text box and pressing Enter. The system shows all server objects with names that include the text you entered.
    • To copy an existing configuration file, select that file and click Copy Configuration Object .

      This option functions the same as the Add Configuration Object icon except that all fields are automatically completed using information from the configuration file you are copying.
    • To delete one or more configuration files, select those files and click Delete Configuration Object . A message prompts you to confirm your action. Click Yesto confirm.

      Note

      A global configuration object defined in the Configuration Object Dictionary must not conflict with a local configuration object created within any component template. You are not allowed to save your configuration file in the Configuration Object Dictionary if a configuration file with the same name and path already exists in any component template. Similarly, you are not allowed to save your component template after adding a local configuration file with the same name and path as any configuration file that already exists in the Configuration Object Dictionary.

  3. From Operating Systems, select the class of OS to which this configuration file applies.
  4. To add one or more new configuration files using wildcards in a file path, check Add multiple files (wildcarded File path) from server. Then, from the drop-down list to the right, select the server with the file path you are specifying.
  5. For File path, do one of the following:
    • If you are adding a single file, enter the path to the file or use Browse to navigate to the file.
    • If you are using the wildcard approach, enter the path to a directory or use Browse to navigate to the directory containing configuration files. Then use a wildcard to identify multiple files in that directory. When entering a path, you can include one or more parameters. For example, you can enter $$TARGET.PATH??/??TARGET.CONFIG_DIR??/.xml* to add all the XML files at a location identified by the combination of the TARGET.PATH and the TARGET.CONFIG_DIR properties. You can enter a parameter manually, or you can click Select Property .

      If you are defining a local configuration object for a component template, use the local properties of the component template to make the path applicable to multiple instances of the same component on a server.
  6. From File encoding, do one of the following:
    • Select Uses default character encoding to use your system's default character encoding when displaying the configuration file.
    • Select Uses encoding and then select the type of character encoding that is used when displaying the configuration file. For example, you might select UTF8 or UTF16.
  7. From Grammar file, select the type of grammar used to parse the files you are adding.

    BMC Server Automation supports a variety of grammar files. For more information, see Grammar files supported by BMC Server Automation.
  8. Do one of the following:
    • If you are copying or editing an existing configuration file, click OK. The procedure is complete.
    • If you are creating a local configuration file for a component template, click Finish. The procedure is complete.
    • If you are creating new configuration files, click Next. The Permissions panel appears.

      The Permissions panel is an access control list (ACL) granting roles access to these configuration files. Access to all objects, including the sharing of objects between roles, is controlled through ACLs.
  9. On the Permissions panel, define an ACL for the configuration files. For more information, see Defining permissions for a system object.
  10. Click Finish to close the wizard and save the new configuration files.