How To Manage High Availability Of BRM System And Fail-Over Management?
(Doc ID 786305.1)
Last updated on SEPTEMBER 30, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.2.1.0.0 and laterInformation in this document applies to any platform.
Goal
1. How to set-up High Availability of a Billing and Revenue Management (BRM) System?
2. Will the performance of system be impacted, if using Connection Manager Master Process (CMMP) configuration?
3. Will CMMP automatically pick other Connection Manager (CM) if one of CM in list fails?
4. How to manage fail-over mechanism, if Primary CMMP is not available then direct to secondary CMMP?
5. Which option out of the two is advisable from Oracle BRM and from user's experience:
- Have multiple CM ptr entries in the application's Infranet.properties or pin.conf file? (having multiple CMs but applications pointing own CM)
OR
- Have multiple CMMP ptr entries in the applications Infranet.properties or pin.conf file?
6. If the application is a custom java application/MultiThreaded Application (MTA) application, and having multiple CM pointer
entries in the application's Infranet.properties or pin.conf file, then how the application automatically picks other CM if one of CM in the list fails?
As per documentation, it is stated that "The CMMP does not validate whether the CMs it points
to are running. If the CMMP sends a transaction to a nonfunctioning CM, the client can tell that the CM is offline, and tries to connect to a different CM or CMMP"
If that is case then will the following functions automatically handle that?
7. How to manage fail-over mechanism if Primary CMMP is not available then direct to secondary
CMMP? Any recommended software for managing clusters on HP-UNIX superdome machine.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |