My Oracle Support Banner

Configuration of Lifecycle From Jmx Console Level (Doc ID 2528995.1)

Last updated on APRIL 22, 2019

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.3.0.3.0 version, External notification (JMS)

ACTUAL BEHAVIOR
---------------
Configuration of lifecycle from jmx console level

It is not possible to gain the same result configuring lifecycle from jmx console (ECE Configuration -> charging.lifecycleConfiguration) as configuring it directly in configuration file ECE_HOME/oceceserver/config/management/charging-settings.xml. As a result each change in configuration (xml file) requires ECE restart instead of rolling upgrade (possible after configuration change from jmx console level).

EXPECTED BEHAVIOR
-----------------------
The expectation is to be able to configure the lifecycleConfiguration from jconsole. The requested configuration is in the attached charing-settings.xml file.
The problem is that some of the characters are substituted by the jconsole so they are not able to get the desired configuration using jconsole.

Changes

 

Cause

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
Symptoms
Changes
Cause
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.