Enabling or Disabling Third-party NF Data Processing

10 Enabling or Disabling Third-party NF Data Processing

This section lists the prerequisites and the procedure for enabling and disabling non-Oracle NF data processing through the Ingress Adapter.

Note:

Georedundancy is currently not supported for the Ingress Adapter.

Certificates for the Ingress Adapter and Non-Oracle Aggregation Service must be created.
The topic NON_ORACLE should be created before enabling third-party NF data processing. If the topic is not created, please see "Creating Topics for OCNADD".
The Non-Oracle Aggregation Service must be enabled from Helm charts and should be in a running state. To enable the Non-Oracle Aggregation Service, perform the following steps:
- Go to the release folder and edit the ocnadd-custom-values-worker-group.yaml created for worker group installation.
- Change the following line:
```
global.ocnaddnonracleaggregation.enabled: false         ## Change this to true
```
- Run Helm upgrade for the worker group namespace:
```
helm upgrade <worker-release-name> -f ocnadd-custom-values-<worker-group>.yaml --namespace <release-namespace> <helm_chart>
```
For example:
```
helm upgrade ocnadd-wg -f ocnadd-custom-values-worker-group.yaml --namespace ocnadd-deploy ocnadd_wg
```

Note:

It is recommended to use mTLS while enabling data processing between Non-Oracle Network Functions and the Ingress Adapter component of Data Director.