The RIMS Component in a Fresh NCC Installation Does Not Write Output to its Own Log File (Doc ID 1920741.1)

Last updated on JULY 21, 2017

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.0 to 6.0.0 [Release 4.4 to 6.0]
Information in this document applies to any platform.

Symptoms

The binaries shipped with Network Charging and Control (OCNCC/NCC) usually install with wrapper startup scripts.  This allows for such things as: the setting of specific component parameters, enabling/disabling debug options, and redirecting output to a specific log file. 

However, out of the box, the Routing Information for Mobile Services (RIMS) interface installs with no wrapper startup script, meaning that any output is logged, by default, to the SLEE.log file, defined in slee.sh startup script.

RIMS has been re-branded and is now known as: Messaging Manager Navigator

Changes

 

Cause

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