Local Configuration Objects tab for a component template

The Local Configuration Objects tab lets you create and manage local configuration objects associated with a component template.

A local configuration object is a configuration file or extended object that only applies to the specific component template. When defining a local configuration object, you can specify a path to that object using local properties as parameters. Using properties in this way, you can create one definition of a configuration object that applies to multiple components on the same server.

For example, if you are setting up multiple instances of an Oracle database on the same server, you might want to know who has permission to log on to each database. This information can be found in the /network/admin/tnsnames.ora file for each database. Using a local configuration file, you can obtain the contents of the tnsnames.ora file for each database. To accomplish this you first create a local property called INSTALL_DIR. Then you define instances of that property, which provide the path to each occurrence of tnsnames.ora. Finally, you create a local configuration file that parses the contents of tnsnames.ora. In that local configuration file, the path to tnsnames.ora uses the INSTALL_DIR local property as a parameter, such as /??INSTALL_DIR??/tnsnames.ora. By creating a local configuration file in this way, you can discover multiple instances of the same component on a server, and each component can provide the contents of a different tnsnames.ora file.

For another example demonstrating how to ensure application compliance using local configuration objects and other component-related functionality, see Using component templates to ensure compliance for multiple instances of an application.

The Local Configuration Objects tab contains icons for adding, copying, and deleting local configuration files and extended objects on the left panel and editing local configuration files and extended objects on the right panel.

The procedures for creating or modifying a local configuration object or extended object are almost identical to procedures available from the Configuration Object Dictionary. See Identifying additional configuration files and Creating an extended object.


A local configuration object that you create must not conflict with any global configuration object defined in the Configuration Object Dictionary. If a configuration file with the same name and path or an extended object with the same name and operating system already exists in the Configuration Object Dictionary, you can not save your local configuration object.

Was this page helpful? Yes No Submitting... Thank you