This panel enables you to define the specifications of the Configuration Object. The settings on this panel depend on the type of Configuration Object that you are defining — whether a Server Object (Custom Configuration Object), Extended Object, or Configuration File.
Server Object field
Field or GUI element | Description |
---|---|
Implementation .zip file | The ZIP file that you want to use as your custom configuration object (or custom server object). |
Extended Object fields
Field or GUI element | Description |
---|---|
Name | A name for the extended object |
Description | An optional description for the extended object |
Operating Systems | The class of OS to which this extended object applies If you want to create an extended object that is associated with an object that does not have a BMC Server Automation RSCD agent installed, select None. If you select None, the Application Server must centrally execute the script or program associated with this extended object |
Icon | An icon to associate with this extended object. To populate this list with choices, you must create an icon library (see Defining custom icons). If you select Default from this list, the standard icon for extended objects is associated with the extended object you are defining. |
Command/Script | A command that the extended object should run. Enter your command or enter (or specify by browsing) a path to the program or script that contains this information for the extended object. When entering a path, you can include one or more parameters. You can enter a parameter manually, or you can click Select Property . Using parameters, you can enter a path such as /??TARGET.WINDIR??/system32/$$TARGET.SCRIPT_DIR??/script.bat. When the script runs, the system replaces the parameters with the value of the server properties Note If any of the characters shown below are included in a command, they could potentially be interpreted as delimiters within a compound shell command. To prevent this, if any of these characters appear without being escaped or enclosed within quotes, BMC Server Automation treats the entire entry as a single string, as if it was enclosed in quotation marks. For execution of the script or program, select one of the following options:
|
Character encoding | The mode of character encoding to use with the extended object, one of the following:
|
Grammar file | The type of grammar that can process output generated by the script you specified in the Command/Script field. For more information, see Grammar files supported by BMC Server Automation. |
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 extended object in the Configuration Object Dictionary if an extended object with the same name and operating system already exists in any component template. Similarly, you are not allowed to save your component template after creating a local extended object with the same name and operating system as any extended object that already exists in the Configuration Object Dictionary.
Configuration File fields
Field or GUI element | Description |
---|---|
Operating Systems | The class of OS to which this configuration file applies |
Add multiple files (wildcarded File path) from server | To add one or more new configuration files using wild cards in a file path, select this check box. Then, from the drop-down list to the right, select the server with the file path you are specifying. |
File path | To specify the file path for the configuration file, do one of the following:
|
File encoding | The mode of character encoding to use with the configuration file, one of the following:
|
Grammar file | The type of grammar used to parse the files that you are adding. For more information, see Grammar files supported by BMC Server Automation. |