Static configuration (application.yaml)

The file ./config/application.yaml is read by the application at startup. It contains configuration for the following:

• server; configuration for the WEB server
  • used port for HTTP/HTTPS, this is however not the port numbers visible outside the container
  • SSL parameters for setting up using of key store and trust store databases.
• webclient; configuration parameters for a web client used by the component
  
  • SSL parameters for setting up using of key store and trust store databases.
  • Usage of HTTP Proxy; if configured, the proxy will be used for accessing the NearRT-RICs
• logging; setting of of which information that is logged.
• filepath; the local path to a file used for dynamic configuration (if used). See next chapter.

For details about the parameters in this file, see documentation in the file.

Dynamic configuration

The component has configuration that can be updated in runtime. This configuration can either be loaded from a file (accessible from the container) or from a Consul database (Cloudify). The configuration is re-read and refreshed at regular intervals.

The includes:

• Controller configuration, which includes information on how to access the a1-adapter
• One entry for each NearRT-RIC, which includes:
  • The base URL of the NearRT RIC
  • A list of O1 identifiers that the NearRT RIC is controlling. An application can query this service which NearRT RIC should be adressed for controlling (for instance) a given Cell.
  • A reference to the controller to use, or excluded if the NearRT-RIC can be accessed directly from this component.
• Configuration for using of DMAAP. There is