Grammar files supported by TrueSight Server Automation

TrueSight Server Automation supports a variety of grammar files capable of parsing data presented in a prescribed format. After it is parsed, that data can be generated in a format consistent with other information in TrueSight Server Automation so you can then browse, snapshot, audit, and deploy that information.

Although TrueSight Server Automation provides many grammar files, the following are the basic types:

• CSV — Parses files consisting of comma-separated entries
• HTTPD — Parses httpd.conf files
• name = value — Parses files with single name/value pairs connected by an equal sign (=)
• name space value — Parses files with name/value pairs connected by white space instead of an equal sign (=)
• XML — Parses XML files using the Xerces DOM parser to generate a DOM tree. Configuration files are then created by traversing the tree. Various schemes are used to generate a unique key for each record.
• Regular — Parses all other configuration files. The following table lists all the grammar files TrueSight Server Automation supports by default. These grammar files reside in <installDirectory>/scripts. For additional information about how an individual grammar file is used to parse configuration files, refer to information provided in each grammar file. For information about creating custom grammars, see Creating-custom-grammars.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.