2 Known Problems

Learn about known problems in Oracle Communications Offline Mediation Controller and the appropriate workarounds.

Topics in this document:

Test Node Chain Fails with “TestId is Invalid” and No Output Records in the UI

When you start a test node chain from the Offline Mediation Controller UI, the subsequent request to fetch test events can fail with HTTP 404 and the following error:

{"code":"404","reason":"TestId is Invalid"}

In the UI, you might also see:

Connection error - Failed to establish connection

This occurs when the ECE DC node’s success and duplicate directories are not present in the Node Manager pod. These directories are not created automatically.

Workaround: Manually create the success and duplicate directories under the Elastic Charging Engine (ECE) Distribution Cartridge (DC) node’s configured output path in the Node Manager Pod and ensure they have appropriate read and write permissions. In the Offline Mediation Controller UI, enable Log success records in the ECE DC node’s Advanced Settings tab so output records appear in the UI. Restart the test node chain and reload the input file.

For more information on how to enable Log success records, see Offline Mediation Controller Web UI Help.