Chat now with support
Chat mit Support

Coexistence Manager for Notes 3.9.2 - User Guide

About the CMN Documentation Suite Introduction CMN Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Starting and stopping the Directory Connector service
CMN Mail Connector
Mail Connector features overview Coexistence mail routing basics Deployment of CMN Mail Connector Installation Configuration Mail Connector Management Console
CMN Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C: CMN Logs

Editing configuration settings in a CMN configuration file

To edit any of the configuration settings in a CMN configuration file:

1
Use an XML editor to open the configuration file (filenames in the right-hand column in the charts above).
2
For the Mail Connector’s SMTP.log file (only): If you want to enable or disable SMTP logging altogether, find the section
<logger name="CMN. SmtpProtocol.logging" ...>, and then:
•
To enable SMTP logging:
•
Set the <level value="INFO" /> parameter value to INFO.
•
Uncomment the line:
<!-- <appender-ref ref="SmtpFileAppender" /> -->
•
To disable SMTP logging:
•
Set the <level value="OFF" /> parameter value to OFF.
•
Restore the comment enclosures to the line:
<appender-ref ref="SmtpFileAppender" />
3
For a Directory Connector or Mail Connector log (only): Find the corresponding section in the open file (section name also appears in the right-hand column above).
4
For any/all component log files: Make any desired changes. Values must be enclosed in double quotation marks and followed by a trailing space and slash character as shown in the field notes below.
The most commonly edited values in CMN configuration files are:
•
<file value="[PathAndFilename]" />: Location and name of the log file that log4net will generate. The path specification can be absolute (e.g., "C:\log4net\CMN.log") or relative to the installation directory (e.g., ".\log4net\CMN.log").
•
<threshhold value="INFO" />: Scope and level of detail to appear in the logs. A valid value is any of these single words:    OFF FATAL ERROR WARN INFO DEBUG ALL
The values as listed here are in ascending order of detail, left to right, and the log will contain items at and above (to the left of) the specified value. For example, <threshhold value="WARN" /> tells log4net to include WARN, ERROR and FATAL events in the log file. The level is set to INFO by default.
•
<rollingStyle value="Size" />: Determines what will trigger log4net’s closing of a current log file and opening of a new one: either a change in calendar date, or a log file reaching a particular size. Parameter value is set to "Size" by default, or change to "Date" for the alternative.
•
<maximumFileSize value="10MB" />: Maximum log file size—the size at which log4net will close the current log file and open a new one (applies only if <rollingStyle value="Size" />.
•
<maxSizeRollBackups value="25" />: Maximum number of log files to keep—after which log4net deletes the oldest log file to create a new one.
(Not all of these parameters apply to all CMN components.)
5
Close and Save the configuration file under the same filename.
* 
NOTE: Note: Any changes to the log42net.config file are immediately applied by the CMN service when the configuration file is saved.

For more detailed information about the log4net utility and how its log files can be configured, see the log4net Config Examples at the Apache.org web site.

Enable DEBUG logging for the CMN Directory Sync service

1
Stop the Coexistence Manager for Notes Directory Sync service.
2
Navigate to the log configuration file at
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Directory Connector\tools\log42net.config.
3
Open the file for editing.
* 
NOTE: If desired, you can make a backup copy of the file prior to editing.
4
There are two entries for <threshold value="INFO" />.
One under <root> and a second under <!-- Main log appender. -->.
Change both entries to <threshold value="DEBUG" />
See the example below.
5
Save and close the file.
6
Delete, rename, or move the current log file at
C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Directory Connector\Logs\Sync.log.
7
Start the Coexistence Manager for Notes Directory Sync service.
8
Once the troubleshooting is completed, change DEBUG back to INFO.
Example

<log42net>

<root>

<!-- Only log the INFO messages, change to DEBUG if you want more

details in the ERROR log. This will have a substantial impact on

the performance of CMN. -->

<level value="DEBUG" />

<!-- The main log. -->

<appender-ref ref="LogFileAppender" />

<!-- Broadcast via UDP. -->

<appender-ref ref="UdpAppender" />

<!-- Errors only log. -->

<appender-ref ref="ErrorLogFileAppender" />

<!-- Write to CONSOLE when running console application. -->

<appender-ref ref="ColorConsoleAppender" />

</root>

 

<!-- Main log appender. -->

<appender name="LogFileAppender" type="log42net.Appender.RollingFileAppender" >

<file value="..\Logs\Sync.wlog" displayName="Directory Sync Service Main Log" />

<!-- Change this to include more or less information in main log. -->

<threshold value="DEBUG" />

<appendToFile value="true" />

<datePattern value="yyyyMMdd&quot;.wlog&quot;" />

<rollingStyle value="Size" />

<!-- Change this setting to change the max log size. -->

<maximumFileSize value="10MB" />

<!-- Change this setting to change the max number of logs. -->

<maxSizeRollBackups value="25" />

<!-- Newest files have smaller numbers. -->

<layout type="log42net.Layout.PatternLayout">

<conversionPattern value="%date %-5level %logger [%t] - %message%newline" />

</layout>

<encoding value="utf-8" />

</appender>

 

 

Adding the UdpAppender to an existing log file

The Open Log File button in the Management Console’s Health screen is enabled only when at least one module has the UdpAppender defined in its log42net.config file. During a new installation, the Log Viewer installer installs a file with the required UdpAppender. During an upgrade, however, the installer does not overwrite the log42net.config file, so the UdpAppender is not present, and this makes the Open Log File button invisible.

For upgrades or installations prior to the current release, the log42net.config file must be modified in each module to enable live log viewing. In the <log4net> root in each module directory, add the following lines:

<root>
      <!-- Broadcast via UDP. -->
      <appender-ref ref="UdpAppender" />
</root>

<!-- UDP appender. -->
      <appender name="UdpAppender" type="log4net.Appender.UdpAppender">
      <threshold value="DEBUG" />
      <remoteAddress value="127.0.0.1" />
      <remotePort value="2500" />
      <layout type="log4net.Layout.PatternLayout">
      <conversionPattern value="%date{HH:mm:ss.fff}|%level|MC|%message" />
   </layout>
</appender>

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen