Software Configuration
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 the 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 the CES_PARAMETERS database table.
Note: For detailed information, see "encrypt" in the Oracle WebLogic Server Command Reference documentation.
 
Sensitive configuration parameters can also be stored in a keystore. Keystore alias should be the string 'nhubinterface.' followed by the configuration parameter name (for example, nhubinterface.config.auth.pwd). See Appendix A for details of using keystore to store sensitive configuration parameters.
Configuration Parameters
Configuration parameters for the application will be stored in the CES_PARAMETERS database table. The APP field will have value 'NHubInterface' for the records related to this application. The column ATTRIB should contain the name of the configuration parameter and the column VALUE should contain its value.
Parameter
Description
config.enabled
Enable/disable the application.
Default: true (enabled)
config.auth.url
URL of OAuth server.
If provided, then the credentials specified by the config.auth.user and config.auth.pwd parameters will be used to contact the OAuth server and the obtain token for accessing Notifications Hub when publishing outage information.
If not provided, then the configured credentials are used directly when publishing outage information using the basic HTTP authentication mechanism.
config.auth.scope
The scope value used when requesting OAuth token.
config.auth.user
OAuth client id or username for Basic HTTP authentication.
config.auth.pwd
OAuth client secret or password for Basic HTTP authentication.
Value of this parameter should be encrypted, or it should be stored in keystore instead of the database (see Appendix A).
config.publish.url
URL of the Notifications Hub web service.
config.ws.timeout
Timeout in seconds for web service operations.
Default: 30 seconds
config.publish.period
Period for publishing outage notifications in seconds.
Cannot be set lower than 15 seconds.
Default: 60 seconds
config.publish.timeout
Amount of time in minutes after which notifications pending delivery are deleted from the database table (MYC_CSS_PARAM_VIO_TEXT).
Purpose of this configuration option is to avoid old notifications being sent out when Notifications Hub integration is restarted after it has been down for some time.
Setting the parameter to 0 disables this functionality.
Default: 240 minutes
config.publish.nfy_limit
Maximum number of notifications per message (per single web service call).
Default: 100
config.publish.size_limit
Maximum size of a single message in bytes.
Valid range [100000, 50000000].
Note: if a single notification is larger than the message size limit such notification will not be published.
Default: 1000000
config.publish.delete_sent
Delete notifications from the database table (MYC_CSS_PARAM_VIO_TEXT) once they are successfully published. Otherwise, records are marked as sent but not deleted which can be useful for debugging purposes.
Default: true
config.nms.instance
NMS instance identifier.
If multiple NMS instances send notifications to a single Notifications Hub instance, then each adapter instance should have unique identifier.
Default: NMS