Questions Related To Changing The CM Log Level Dynamically And BRM Environment Variables (Doc ID 1539679.1)

Last updated on AUGUST 24, 2016

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.
*** Checked for relevance on 10-16-2015 ***

Goal

Q1)Dynamically changing the loglevel of CM without restarting the CM process

We want to change the CM loglevel dynamically.

a) If we use the PCM_OP_INFMGR_SET_LOGLEVEL opcode we can set 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.

Please confirm if (b) is standard behaviour of the BRM.

Q2) We would like to use environmental variables for some configuration parameters like cm_name etc
But as per the documentation only some specific system environmental variables can be used ? is it correct or any environmental variables defined
can be used


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

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

it is working fine

Please could you confirm what is the right behavior.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms