ConfigFile policy General tab

When a SPI is installed, one or more so-called ConfigFile varieties are also installed. ConfigFile varieties consist of the application, subgroup, and file name attributes. These three attributes determine the path and file name of the configuration file that is associated with the policy.

When a policy is newly created, the fields in the General tab can be changed. When an existing policy is edited, the fields cannot be changed.

• Application: Specifies the name of the managed application. This usually equals the name of the SPI itself, for example dbspi or sapspi.
• Sub-Group: Additional grouping mechanism that helps the SPI to manage configuration files by grouping them according to custom categories. For example, sapspi uses the subgroup attribute to differentiate between global and local scope of the configuration. dbspi has one subgroup for every supported database vendor.
• File name: Specifies the file name of the configuration file. For example, sapspi's monitor instrumentation configuration files have r3monxxx.cfg names, where xxx is the abbreviation of the particular monitor.

NOTE:
Some SPIs may allow you to specify your own configuration file in the File name field. If this is the case, make sure to use alpha-numeric characters only in the file name. Special characters are not allowed.

Related Topics:

• ConfigFile policy Data tab
• ConfigFile policy type
• Instrumentation
• Policy deployment
• opcdeploy

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.