b+s Logs

Logging

Logs from b+s Connects for Siebel are written by default to the following directory: C:\ProgramData\BucherSuter\logfiles\MCAforSiebel

The output files are simple ASCII text and can be opened with a conventional text editor, such as Notepad. However, it is more comfortable to open them with b+s EventLogView. Please contact b+s Customer Services for more information about the usage of this tool.

Logger Settings

All components share the same logging concept. All logging related configurations are part of the respective configuration-file (.ini - except the Communication Toolbar Adapter. Its logging configuration resides in the Siebel definition file). If the values are <empty> or do not exist at all, the following default values will be set:

restart service

The size of log files can be defined in kilobytes (KB) or megabytes (MB).
These logger settings are not dynamic, i.e. the Windows services must be restarted for the adjusted settings to take effect.

Communication Toolbar Adapter

Key	ini-Default	Range	Description
Logfile	C:\ProgramData\BucherSuter\logfiles\MCAforSiebel\	-	Path to log file
MaxLogFileSize	100MB	-	Max. log file size
MaxLogFileRollBackups	10	1-50	Number of log files

starting a new instance of the Communication Toolbar

When a new instance of the Communication Toolbar Adapter is started, it searches for the next free port starting at the RemoteConsoleBasePort. The difference between the located port and the RemoteConsoleBasePort defines the instance number, which is used for the LogFile suffix, as the offset for the RemoteConsolePort.

ConnectMCAL

Key	ini-Default	Range	Description
Path	C:\ProgramData\BucherSuter\logfiles\MCAforSiebel\ConnectMCAL_Siebel.log	-	Path to log file
FileSize	100MB	-	Max. log file size
MaxBackupIndex	10	1-50	Number of log files

configuration keys renaming

The keys BsLoggerFile, BsLoggerFileSize, and BsLoggerMaxBackupIndex have been renamed to Path, FileSize, and MaxBackupIndex, respectively

Media Manager

Key	ini-Default	Range	Description
PATH	C:\ProgramData\BucherSuter\logfiles\MCAforSiebel\	-	Path to log file
FILE_SIZE	100MB	-	Max. log file size
MAX_BACKUP_INDEX	10	1-50	Number of log files

Data Store

Key	ini-Default	Range	Description
Path	C:\ProgramData\BucherSuter\logfiles\MCAforSiebel\DataStore_Siebel.log	-	Path to log file
FileSize	100MB	-	Max. log file size
MaxBackupIndex	10	1-50	Number of log files

configuration keys renaming

The keys BsLoggerFile, BsLoggerFileSize, and BsLoggerMaxBackupIndex have been renamed to Path, FileSize, and MaxBackupIndex, respectively

Routing Adapter

Key	ini-Default	Range	Description
LogFile	C:\ProgramData\BucherSuter\logfiles\MCAforSiebel\SiebelRoutingAdapter_Siebel.log	-	Path to log file
MaxLogFileSize	100000KB	-	Max. log file size
MaxLogFileCount	10	1-50	Number of log files

Chat Connector

Key	ini-Default	Range	Description
Logfile	C:\ProgramData\BucherSuter\logfiles\MCAforSiebelCC\McilChat.log	-	Path to log file
MaxLogFileSize	100MB	-	Max. log file size
MaxLogFileRollBackups	10	1-50	Number of log files

Log Mask and Collected Log Mask

Tracing of the b+s Connects for Siebel components is controlled by the LogMask- and CollectedLogMask- settings in the configuration .ini-file.

Log Mask

The LogMask-setting is a bit mask that controls which tracing information is switched on or off. This setting is dynamic, i.e. Chat Connector does not have to be restarted for the adjusted collected trace mask to take effect.

[Dynamic]
...
TraceMask=0xXXXXXXXX
...

You can find detailed information about the TraceMask-Settings in the Trace bits-Chapter.

Collected Trace Mask

The collected bit of the trace mask is set by the most significant byte (MSB) of the TraceMask-setting and is used to write collected trace messages. Change this single digit by adding the COLLECTED (0x80000000) message to enable the collected trace messages. If the collected message pool contains one or more messages with the same or a lower trace level than the trace level of the TraceMask-setting, the collected message pool gets written into the log file. Collected tracing activates additional logging mechanisms that allow the inspection of complete transactions bundled in a collection of trace messages.

The TraceMaskCollectMsg-setting is a bit mask that controls which collected tracing information is switched on or off. This setting is dynamic, i.e. ConnectMCAL does not have to be restarted for the adjusted collected trace mask to take effect.

Traces for Troubleshooting

In this list we provide some recommendations about trace mask settings.

Communication Toolbar Adapter

Level	TraceMask	TraceMaskCollectMsg
Minimum trace	Required:Driver:LogTraceMask=0x80000004	Required:Driver:LogTraceCollectMask=0x00000004
Troubleshooting	Required:Driver:LogTraceMask=0xfffffff8	Required:Driver:LogTraceCollectMask=0xfffffff8

ConnectMCAL

Level	TraceMask	TraceMaskCollectMsg
Minimum trace	TraceMask=0x00000004	TraceMaskCollectMsg=0x00000000
Medium trace	TraceMask=0x00004018	TraceMaskCollectMsg=0x00000000
Troubleshooting	TraceMask=0x830fe038	TraceMaskCollectMsg=0xfffffff8

Media Manager

Level	TraceMask	TraceMaskCollectMsg
Minimum trace	TraceMask=0x00000004	TraceMaskCollectMsg=0x00000000
Medium trace	TraceMask=0x00044018	TraceMaskCollectMsg=0x00000000
Troubleshooting	TraceMask=0x842fc3f8	TraceMaskCollectMsg=0xfffffff8

DataStore

Level	TraceMask	TraceMaskCollectMsg
Minimum trace	TraceMask=0x00000004	TraceMaskCollectMsg=0x00000000
Medium trace	TraceMask=0x0007a018	TraceMaskCollectMsg=0x00000000
Troubleshooting	TraceMask=0x800fe018	TraceMaskCollectMsg=0xfffffff8

Routing Adapter

Level	TraceMask	TraceMaskCollectMsg
Minimum trace	Required:Driver:LogTraceMask=0x80000003	Required:Driver:LogTraceCollectMask=0x80000003
Troubleshooting	Required:Driver:LogTraceMask=0xfffffff8	Required:Driver:LogTraceCollectMask=0xfffffff8

Chat Connector

Level	TraceMask	TraceMaskCollectMsg
Minimum trace	Required:Driver:LogTraceMask=0x80000003	Required:Driver:LogTraceCollectMask=0x00000003
Troubleshooting	Required:Driver:LogTraceMask=0xfffffff8	Required:Driver:LogTraceCollectMask=0xfffffff8

Version, Status and Product Activation Key Information

The b+s Connects for Siebel components write periodical status information into the logfile:

Component	Periodical Message
ConnectMCAL	SysInfo:CTI+,:MCIL+,:Cl.1,:Agts0,:E0,:W3;
Data Store	012.20.23134 VEXE:2.1.0(52621);VDS:2.1.0.52591;AS:4;EC:1;WC:45;MTC:15
Media Manager	SysInfo: CTI + (2), MRI + (3) Routing +, MCIL-CL 3, RT-CL 3, Agts 0, PJ-RH 0, PJ-ARM 0

Item	Description
AS:	Application Status (1= Idle, 2=Connecting, 3=Reconnecting, 4=Connected)
Agts:	Number of Agents
ARM:	ARM Interface Status (1=Online, 0=Offline)
CTI:	Shows status of CTI connections (+=connected, -=not connected)
EC or E:	Errors Count
MAC:	Monitors Agent Count
MCIL:	Shows status of MRI connections (+=connected, -=not connected)
MCIL-CL:	Number of MCIL clients connected
MRI:	MRI Interface Status (1=Online, 0=Offline, +=enabled)
MTC:	Monitors Transactions Count
PAK:	Product Activation Key entered during the installation of the CRMConnectorSAP
PJ-ARM:	Pending Jobs towards CTI Server
PJ-RH:	Internal pending jobs
Routing:	Checks if Routing session is available (+=available, -=not available)
RT-CL:	Number of Routing Clients
VDS:	Version of theIcmDsServiceDll.dl
VEXE:	Version of the DataStore.exe
WC or W:	Warnings Count