Ericsson | EMCLI | Debug Logging Description V.1.
EMCLI Javalogging
Contents
1 Introduction...................................................................................................2
1.1 Purpose.......................................................................................................... 2
2 Location of [Link] file..................................................................2
3 EMCLI Logging for Windows (lax file)............................................................2
4 EMCLI Logging for OSS................................................................................3
5 Configuring Specific Log Level in Your [Link] File......................3
6 Example of [Link] file..................................................................3
1|P a g e
Ericsson | EMCLI | Debug Logging Description V.1.0
1 Introduction
This document is an instruction to the EMCLI user to generate java logging for EMCLI by
using [Link] file.
1.1 Purpose
The purpose is to give a detailed guideline for the end user to create java logging for EMCLI
with different logging level for trouble shooting and other maintenance activities to the EMCLI
tool.
2 Location of [Link] file
Copy the [Link] file from chapter 6 Example of [Link] to a desire
area with writing permissions e.g.
Windows users:
C:\\Users\\userid\\[Link]
Save the [Link]
3 EMCLI Logging for Windows (lax file)
On windows platform, a lax file needs to be modified to include the [Link] file path.
• Open the lax file to get traces for Element manager Main window. It is located
under your “C:\Users\<user>\Ericsson\EM\Element [Link]” and has the
suffix .lax.
• In the already open lax file add a new parameter “[Link]”
under title “[Link]” and append the following
with it.:
-[Link]= <path to [Link]>
e.g.
[Link]=-[Link]="C:\\Users\\<user>\\[Link]"
Save the lax file
The log file output will be located at the user’s home directory and called Java(x).log where x
is a digit number.
2|P a g e
Ericsson | EMCLI | Debug Logging Description V.1.0
4 EMCLI Logging for OSS
When running from OSS-RC, Follow the steps in CPI document “Connectivity Packet
Platform Element Manager (CPPEM) System Administrator Guide (1543-APR 901 0242)”
for logging.
5 Configuring Specific Log Level in Your [Link] File
To specify a specific log level in the [Link] file you can change the following
loggers under title “facility specific properties” to your desire level:
• A level ALL that can be used to enable logging of all messages.
[Link] = ALL
• You can filter the messages by their log level, meaning you can configure
a logging level from ALL to your desire level to not log and not propagate
messages below a certain level.
[Link] = SEVERE
[Link] = WARNING
[Link] = INFO
[Link] = CONFIG
[Link] = FINE
[Link] = FINER
[Link] = FINEST
In addition there is a level OFF that can be used to turn off logging.
Warning: User must turn off the logging after saving the logs otherwise it may affect the
performance of EMCLI tool.
6 Example of [Link] file
############################################################
# Default Logging Configuration File
#
# You can use a different file by specifying a filename
# with the [Link] system property.
# For example java -[Link]=myfile
############################################################
############################################################
# Global properties
############################################################
# "handlers" specifies a comma separated list of log Handler
# classes. These handlers will be installed during VM startup.
3|P a g e
Ericsson | EMCLI | Debug Logging Description V.1.0
# Note that these classes must be on the system classpath.
# By default we only configure a ConsoleHandler, which will only
# show messages at the INFO and above levels.
#handlers= [Link]
# To also add the FileHandler, use the following line instead.
handlers= [Link],
[Link]
# Default global logging level.
# This specifies which kinds of events are logged across
# all loggers. For any given facility this global level
# can be overriden by a facility specific level
# Note that the ConsoleHandler also has a separate level
# setting to limit messages printed to the console.
.level= ALL
############################################################
# Handler specific properties.
# Describes specific configuration info for Handlers.
############################################################
# default file output is in user's home directory.
[Link] = %h/java%[Link]
[Link] = 500000
[Link] = 1
[Link] = ALL
[Link] =
[Link]
# Limit the message that are printed on the console to INFO and
above.
[Link] = INFO
[Link] =
[Link]
############################################################
# Facility specific properties.
# Provides extra control for each logger.
############################################################
# For example, set the [Link] logger to only log SEVERE
# messages:
[Link] = ALL
[Link] = SEVERE
[Link]= SEVERE
[Link] = SEVERE
[Link] = SEVERE
[Link] = SEVERE
4|P a g e
