When Diameter Gateway is configured to bypass rating during a planned maintenance activity or in an unplanned downtime of ECE, Diameter Gateway receives CCRs and persists them to the Oracle NoSQL Database. Later, when the ECE nodes are restarted, you stop the bypass rating extension and replay the persisted messages to the ECE charging servers for rating and updating balance impacts.

Managing the persistence of diameter requests involves starting and stopping the persistence of the requests. Before persisting the incoming diameter requests, ensure that the ocsBypassExtension charging extension is enabled. See "Configuring Diameter Gateway to Bypass Rating During ECE Downtime" for information on configuring Diameter Gateway to bypass rating.

For planned maintenance activities, you start the persistence of usage requests before the ECE nodes become unavailable. During an outage, the persistence of diameter requests starts only if the ocsBypassExtension charging extension is enabled. If only the extension is enabled and bypass rating is not started, the usage requests do not flow to the ECE Charging Server nodes. In such a scenario, Diameter Gateway returns Error 5012 for the requests.

To persist incoming diameter requests:

1. Access the ECE configuration MBeans in a JMX editor, such as JConsole. See "Accessing ECE Configuration MBeans".

2. Expand the DiameterGateway node.

3. Expand BFTTask.

4. Expand Operations.

5. Click startByPass.

   The Diameter Gateway starts persisting the incoming requests.

In planned maintenance activities or in unplanned downtime, once the ECE nodes become available and start running, you must stop the persistence of the requests. Otherwise, messages are persisted even after the ECE nodes are up and running, which results in a large volume of requests that need to be replayed.

To stop persisting the requests, click stopByPass. Before doing this, you can check if the persistence of requests is running by clicking BFTRunning. If bypassing rating is enabled, this field shows True. Otherwise, it shows False.

When you configure Diameter Gateway to bypass rating during planned maintenance or unplanned downtime of ECE, Diameter Gateway persists the incoming CCRs in the Oracle NoSQL Database. Later, during a non-peak period, you replay the persisted CCRs to the ECE charging server when the ECE server is restored and is ready to process real-time requests. When you replay the persisted CCRs, the requests are passed to the ECE charging server, which then rates the CCRs and updates the balance impacts. You can plan when to start replaying the persisted messages, considering that replaying them can have performance impacts while real-time requests are also being processed. Before replaying the persisted requests, ensure that bypass rating extension is disabled and the ECE nodes are up and running. To check if bypass rating is stopped, click BFTRunning in ECE MBeans.

To replay the persisted requests into ECE:

1. Access the ECE configuration MBeans in a JMX editor, such as JConsole. See "Accessing ECE Configuration MBeans".

2. Expand the DiameterGateway node.

3. Expand BFTTask.

4. Expand Operations.

5. Click persistedMessageCount to view the number of requests that have been persisted and are ready for replay.

6. Click startBFTReplayer.

   The replayer starts replaying the persisted messages to the ECE charging servers. As messages are replayed to the servers, the number of persistedMessageCount keeps decreasing until it becomes 0.

   The replayedMessageCount field shows the number of requests that are being replayed. As requests are replayed, the number of replayedMessageCount keeps increasing until it matches the initial count of persistedMessageCount.

You stop replaying the messages once all the persisted messages are replayed into the ECE charging servers.

To stop replaying the persisted messages:

1. Check the status of the replayer by clicking BFTReplayerRunning. Ensure that this field shows Running.

2. Check the status of the replayedMessageCount field. Ensure that this field shows 0, which indicates that all the persisted messages are replayed into the ECE charging servers.

   • replayedMessageCount indicates the number of Diameter messages that are replayed to the ECE charging server by the current instance of Diameter Replayer.

   • persistedMessageCount indicates the number of Diameter messages that have been persisted to the Oracle NoSQL database, but are yet to be replayed.

3. Click stopBFTReplayer.

   Replaying of messages is stopped.