BCM 7.0 How to change server and client loglevels

BCM 7.0 How to change server and client loglevels

CLIENT LOGS

Increase first the loglevel for CDT. Then repeat the problem and collect the client logs.

Client logfiles are:
- CDT_YYYYMMDD.log
- BCMUI_<workstationname>_logs_<date>.<nbr>.txt
- BCM_

How to increase the loglevel for one CDT:

- Close all open IE windows
- Open Internet Explorer
- Type http:// <SERVER NAME OR IP ADDRESS>/cdt/?arg=loglevel=5
- Login to CDT with your usual account

How to increase the loglevel for all CDTs:

- Open System Configurator
- Go to User and Role Management
- Go to User Settings Template
- Go to CDT Personalization
- Change loglevel from "Log Level" parameters
- Save and Close

How to find the client logs from users PC:

- In Windows select Start / Run and type %temp% and copy the client logfiles CDT, BCMUI and BCM logs from time the problem happened.




SERVER LOGS

Increase first the loglevel for problematic component. Then repeat the problem and collect the logs.


The default path: D:\SAP\BCM\LOGS\<virtual unit name>\ log file

Log name convention: <componentNAME>_<serverName>_<virtualunitName>YYYYMMDD_HH.log

Increasing the logleveles for SAP BCM 7.0 happens via editing registery, loglevel is set individualy per component. The registery keys can be found from:
WIN 32-bit:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wicom\Virtual unit\component
WIN 64-bit:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wicom\<virtual unit>\component


CEM:
1. Set
LogLevel "debug"

In case where you need more detailed information ex. call GUIDs or Precense, Queues and etc. you have to enable following debugging option:
1. Disable the secured logs by creating REG_DWORD  "DebugSecure". Give the value 0 for this parameter. Please note that enabling this will print sensitive information to the log file.
DebugSecure "0"

2. Raise the Debug from value 7 to 9.
Debug "9"


Call Dispatcher :
1. Set
LogLevel "warning"
LogModule.BcmApi.Level "inherited"
LogModule.CallDispacher.Level "trace"
LogModule. #. "inherited"


OII
1. Disable the secured logs by creating STRING "UseSecureLogging" under integrations virtual unit (not under OII). Give the value 'no' for this parameter
2. Set
LOG_LEVEL under OII to 3


HAC
1. Set
LogLevel "Trace"
This can be found from
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wicom\ <HAC Node name> \ HAC


Other Components:
Set
LogLevel "trace"
All the LogModule.* "inherited"


Infrastucture Administrator > Settings > Local Logging Parameters >
Set from the Infrastucture Administrator
Log Detail Level "Include debug Messages"


!NOTE!
Side effects when increasing log level:

  Take into account the following:

  a) Extensive logs give you all the information you need
  b) For extensive logs you have to reserve enough disk space
  c) extensive log writing might affect to the server performance
  d) Change to log values are always affecting to a) and b) and c)
  e) Do not forget to set the loglevels and trace back to the normal level

    • Related Articles

    • Error installing BCM7 Web Server in IA

      During Web Server Virtual Unit installation you may get an IA default error message: Failed to run method 'postinstall' in 'I:\SAP\BCM\Install\7.0.3.100\Web Server\method' : Method returned an error : Exit code=1=0x1 ... not saying almost anything :) ...

    • Low volume on BCM call

      Could be that your workstation volume settings were changed. You can check this in CDT settings: Change Audio settings if call voice is too low (or high) If client claim that he or she cannot hear you - raise a Mictophone level or make it lower if ...

    • How to Enable QoS for SAP Contact Center Servers and Communication Desktop (CDT)

      How to Enable QoS for SAP Contact Center Communication Desktop (CDT) QoS or Quality of Service describes the way in which packets are tagged to ensure that network devices apply the correct prioritization, allowing the best possible experience when ...

    • Recording Format for SAP Contact Center (BCM) Prompts

      The prompt files must be saved in PCM format in order for SAP CCtr to play them. Specifically, save as .WAV file: Required audio recording format: Bit Rate: 128kbps Audio sample size: 16 bit Channels: 1 (mono) Audio sample rate: 8kHz Audio format: ...

    • How to configure a workstation to start using BCM

      Prerequisites BCM client workstation need to have the Microsoft Internet Explorer software installed. Procedure of enabling a client workstation to start using BCM To enable using the software in the Internet Explorer, configure workstations in the ...