DOM Processor
The DOM Processor microservice handles adding, updating, and deleting devices in the inventory that were discovered by the Discovery Service microservice.
This microservice is part of the Discovery microservice pipeline. See Understanding the Discovery Pipeline in Unified Assurance Concepts for conceptual information.
DOM Processor Prerequisites
Before deploying the microservice, confirm that the following prerequisites are met:
-
A microservice cluster is set up. See Microservice Cluster Setup.
-
The following microservices are deployed:
Deploying DOM Processor
To deploy the microservice, run the following commands:
su - assure1
export NAMESPACE=<namespace>
export WEBFQDN=<WebFQDN>
a1helm install <microservice-release-name> assure1/dom-processor -n $NAMESPACE --set global.imageRegistry=$WEBFQDN
In the commands:
-
<namespace> is the namespace where you are deploying the microservice. The default namespace is a1-zone1-pri, but you can change the zone number and, when deploying to a redundant cluster, change pri to sec.
-
<WebFQDN> is the fully-qualified domain name of the primary presentation server for the cluster.
-
<microservice-release-name> is the name to use for the microservice instance. Oracle recommends using the microservice name (dom-processor) unless you are deploying multiple instances of the microservice to the same cluster.
You can also use the Unified Assurance UI to deploy microservices. See Deploying a Microservice by Using the UI for more information.
Changing DOM Processor Configuration Parameters
When running the install command, you can optionally change default configuration parameter values by including them in the command with additional --set arguments. You can add as many additional --set arguments as you need.
For example, set a parameter described in Default DOM Processor Configuration by adding --set configData.<parameter_name>=<parameter_value>. For example, --set configData.LOG_LEVEL=DEBUG.
Default DOM Processor Configuration
The following table describes the default configuration parameters found in the Helm chart under configData for the microservice.
Name | Default Value | Possible Values | Notes |
---|---|---|---|
LOG_LEVEL | INFO | FATAL, ERROR, WARN, INFO, DEBUG | The logging level used by the DOM Processor. |
PULSAR_DOM_PROCESSOR_OVERRIDE | "" | persistent://assure1/discovery/dom-processor-zoneX | Overrides the Pulsar topic from which the DOM Processor receives requests. This is the topic where the discovery service sends requests. For example, example- dom-processor-zone1. |
PULSAR_DOM_FEEDBACK_OVERRIDE | "" | persistent://assure1/discovery/dom-feedback-zoneX | Overrides the Pulsar topic to which the DOM Processor sends errors. For example: dom-feedback-zone1 |
DB_CONNECTION_TIMEOUT | 60 | Integer | The number of seconds to wait for the database connection timeout. |
DB_FAILOVER_CONNECTION_TIMEOUT | 10 | Integer | The number of seconds to wait for failover database connection timeout. |
DB_HEALTH_CHECK_DELAY | 30 | Integer | The number of seconds to wait, before verifying the database connectivity. |
DB_FAILOVER_ENABLED | "true" | true, false | Whether database failover is enabled (true) or not (false). |