Adapter Software Configuration
Configuration for the Oracle Utilities Network Management System Switching Adapter comes from the following sources:
• CES_PARAMETERS database table
• Oracle Utilities Network Management System configuration rules
• JBot Commands
This section includes the following topics:
Support for Encrypted Configuration Parameters
Some configuration parameters that are stored in the CES_PARAMETERS database table contain sensitive information, such as authentication credentials, which should be protected. To protect this data, the VALUES column can be encrypted using Oracle WebLogic Server encrypt utility. This utility encrypts cleartext strings for use with Oracle WebLogic Server. Its output can then be used to populate values in CES_PARAMETERS database table.
For detailed information, see "encrypt" in the Oracle WebLogic Server Command Reference.
Configuration Parameters
Entries in the CES_PARAMETERS database table for the Oracle Utilities Network Management System Switching Adapter should have value 'SwmanInterface' in the APP column. Column ATTRIB should contain name of the configuration parameter and column VALUE its value.
The following table describes the general configuration parameters.
Project Extension Configuration
• The example extension inherits the product parameters shown above. Projects can reuse these parameters as-is or introduce project-specific attributes. The example includes an InterfaceProperties helper and wiring to read values from CES_PARAMETERS.
• Sensitive attributes (for example, passwords or tokens) must be encrypted using the Oracle WebLogic Server encrypt utility or stored in a keystore per Appendix A. Do not store cleartext secrets in the database.
• If additional REST-related configuration is introduced by a project (for example, OAuth settings or custom endpoints), define attributes under APP='SwmanInterface' (or a project-specific APP value) and access them via your extension classes. Refer to the example extension README.md.
• For additional information about how the sample uses build.properties, InterfaceProperties, CES_PARAMETERS, and REST-related settings together, see the README.md file packaged with the example extension.