Last updated on AUGUST 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.5.0]
Information in this document applies to any platform.
How to enable High Availability for Reat-Time Zoning pipeline? In the proposed BRM implementation, there are two servers (BRM1 and BRM2) that each runs a CM, a DM Oracle (DMO) and a real-time zoning pipeline (RTP) for real-time rating. For high-availability, the following two em_pointer entries were configured in the CM pin.conf on each server in order to be able to perform real-time usage on both servers if the real-time zoning pipeline is down on one server: - cm em_pointer zoning ip BRM1 20029 - cm em_pointer zoning ip BRM2 20029 The expectation is that if the first RTP is not available then the CM will automatically failover to the second RTP in order to process the real-time rating request. In testing however, if one of the servers (e.g. BRM2) is unavailable, the CM running on the other server tries to send real-time zoning requests to the server that is unavailable and does not failover to the server that is available. This causes real-time rating requests to fail even though one server is still available.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms