Abbreviations for BlackBerry Enterprise Server debug logs

Article ID: KB04777

Type: Support Content

Last Modified: 05-17-2012

 

Product(s) Affected:

  • BlackBerry Enterprise Server for Microsoft Exchange
  • BlackBerry Enterprise Server for IBM Domino
  • BlackBerry Enterprise Server for Novell GroupWise
CollapseEnvironment
  • BlackBerry® Enterprise Server 4.0 to 5.0
CollapseOverview

Abbreviation

Debug Log Name

ACNV

BlackBerry® Attachment Service attachment conversion

ALRT

BlackBerry Enterprise Server Alert Tool

APP

BlackBerry Monitoring Service Application Core

ASCL

BlackBerry Attachment Service client

ASMN

BlackBerry Attachment Service attachment monitor

ASRV

BlackBerry Attachment Service component

BAA

BlackBerry Administration API

BAS-AS

BlackBerry Administration Service Application Server

BBAS-NCC

BlackBerry Administration Service Native Code Container

BBIM

BlackBerry Instant Messaging

BBMS

BlackBerry Monitoring Service console

BBMS-APP

BlackBerry Monitoring Service Application Core

BBMS-DCS

BlackBerry Monitoring Service Data Collection Subsystem

BBMS-ENG

BlackBerry Monitoring Service Polling Engine

CALH

CalHelper

CEXC

Exchange Connector

CBCK

Backup Connector

CMNG

Management Connector

CONN

BlackBerry Synchronization Connector

CTRL

BlackBerry Controller

DBNS

BlackBerry database notification service

DCS

BlackBerry Monitoring Service Data Collection Subsystem

DISP

BlackBerry Dispatcher

EXTS

Extension Connector

HHCG

BlackBerry Configuration Panel

MAGT

BlackBerry Messaging Agent

MAST

BlackBerry Mail Store Service

MDAT

BlackBerry® Mobile Data System (BlackBerry MDS)Connection Service

MDSS

BlackBerry MDS Integration Service

MDSS-AC

BlackBerry MDS Integration Service Application Console

POLC

BlackBerry Policy Service

ROUT

BlackBerry Router

SYNC

BlackBerry Synchronization Service

TAT

BlackBerry Threshold Analysis Tool

Information

Log file names are generated in the following format:

<Server-Name_Abbreviation_Agent-Number_Date_Log-Iteration>.txt

where,

Server-Name is the name of the BlackBerry® Enterprise Server.

Abbreviation is the abbreviation for the log name (from the table above).

Agent-Number identifies the log created for each agent (01 to05).

Date is the date the log is created.

Log-Iteration is a number assigned to a log each time the BlackBerry Enterprise Server is started. When the BlackBerry Enterprise Server is restarted, a new log is created, and the Log-Iteration number increases (for example, 0001, 0002, and 0003).

For example, a third log file for the BlackBerry Messaging Agent #2 is created on January 5, 2006 after the BlackBerry Enterprise Server named BES01 is restarted twice. The log file name is BES01_MAGT_02_20060105_0003.txt.

OR

A BlackBerry Policy Service log file is created on December 31, 2005 for a BlackBerry Enterprise Server named RIMBES that has not been restarted. The log file name is RIMBES_POLC_01_20051231_0001.txt.

Debug Log Names for BlackBerry Enterprise Server for Novell® GroupWise®

The following table shows BlackBerry Enterprise Server debug log names and the specific versions and connection modes to which they pertain:

Abbreviation

Debug Log Name

Software Version and Connection Mode

ADLSYNC

Novell® GroupWise® system address book synchronization

BlackBerry Enterprise Server versions 4.0, 4.1.

GWCO

Novell GroupWise GWCO

GWSV

Novell GroupWise service

CWPA

Novell GroupWise personal address book connector

CWQM

Novell GroupWise CheckNew connector

GWSC

Novell GroupWise SOAP connector

BlackBerry Enterprise Server versions 4.1.2+, 5.0

CollapseAdditional Information

Log file names are generated in the following format:

<Server-Name_Abbreviation_Agent-Number_Date_Log-Iteration>.txt where Server-Name is the name of the BlackBerry Enterprise Server. Abbreviation is the abbreviation for the log name (from the table above). Agent-Number identifies the log created for each agent (01 to05). Date is the date the log is created. Log-Iteration is a number assigned to a log each time the BlackBerry Enterprise Server is started. When the BlackBerry Enterprise Server is restarted, a new log is created, and the Log-Iteration number increases (for example, 0001, 0002, and 0003).

For example, a third log file for the BlackBerry Messaging Agent #2 is created on January 5, 2006 after the BlackBerry Enterprise Server named BES01 is restarted twice. The log file name is BES01_MAGT_02_20060105_0003.txt.

OR

A BlackBerry Policy Service log file is created on December 31, 2005 for a BlackBerry Enterprise Server named RIMBES that has not been restarted. The log file name is RIMBES_POLC_01_20051231_0001.txt.

Debug Log Names for BlackBerry Enterprise Server for Novell® GroupWise®

The following table shows BlackBerry Enterprise Server debug log names and the specific versions and connection modes to which they pertain:

Abbreviation

Debug Log Name

Software Version and Connection Mode

ADLSYNC

Novell® GroupWise® system address book synchronization

BlackBerry Enterprise Server versions 4.0, 4.1.

GWCO

Novell GroupWise GWCO

GWSV

Novell GroupWise service

CWPA

Novell GroupWise personal address book connector

CWQM

Novell GroupWise CheckNew connector

GWSC

Novell GroupWise SOAP connector

BlackBerry Enterprise Server versions 4.1.2+ and 5.0

CNGW

Novell GroupWise connector

Disclaimer

By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.


Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.