My Oracle Support Banner

Questions Related to Changing the CM Log Level Dynamically and BRM Environment Variables (Doc ID 1539679.1)

Last updated on SEPTEMBER 04, 2020

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.5.0.0.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.

Goal

Q1) Please advise two approaches below on how to dynamically changing the loglevel of Connection Manager (CM) without restarting the CM process:
     a) When using the PCM_OP_INFMGR_SET_LOGLEVEL opcode, it sets for the current process but this will not change globally.
     b) Without restart if we update the CM pin.conf log level the next new processes is considering the new updated log level,

       Eg: we started all the process cm log level was set to 1 and after some time changed the log level to 3 in CM pin.conf spawned a new CM process just by connecting testnap then this new process taken CM log level 3 and printed the debug information.

Q2) How to use environmental variables for some configuration parameters like cm_name, etc ...?
Per the documentation only some specific system environmental variables can be used.  Is it correct or any environmental variables defined can be used?


Eg: defined hostname as environmental variable and used it CM pin.conf it is working fine
$echo $HOSTNAME
<HOSTNAME>

defined in CM pin.conf as
- cm cm_name ${HOSTNAME}

Please confirm what is the right behavior.
 

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
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.