Common Configuration File To Store Parameters to avoid system restarts
(Doc ID 1486644.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Communications ASAP - Version 7.0.0 and later
Information in this document applies to any platform.
Suppose there is a one Network Element cartridge which is Socket based. We would like to avoid hard coding of mml commands and would like to maintain one configuration file where we will have all the common parameters. Then, whenever we fire mml commands, we would like to get the parameter values from that common configuration file. Our requirement is to avoid ASAP server restarts whenever any parameter key or value changes are there (Decoupling mechanism).
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