Chat now with support
Chat mit Support

Coexistence Manager for Notes 3.8.4 - 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

View menu

•
Show Line Numbers (or Ctrl+L): Toggles the display of line numbers (within the open file) on and off.
•
Show Complete Log Entry (or F5): Opens a Log Detail window that shows the entire string for the selected item—useful when the item text overruns the Log Viewer’s maximum line length (maximum 259 characters), or if the line extends beyond the right edge of the viewer window without wrapping.
•
Enable Internet Access: Toggles the Internet connection on and off. Note these important disclosures:
 
* 
IMPORTANT: The full benefit of Quest's Log Viewer requires the application to transmit log event codes from the computer hosting the Log Viewer to a remote Quest database of Solutions (useful information about the events associated with the log codes). The Quest Solutions database then sends a corresponding Solution back to the Log Viewer for display to the user.

This feature is enabled by default, but can be disabled by deselecting this Enable Internet Access option (on the View menu). Note:

•
The Log Viewer sends event codes to Quest servers in the United States, as the codes appear in a log file that has been opened into the Log Viewer window.
•
The Log Viewer sends only event codes and source IP addresses to Quest's server. No personally identifying information other than IP addresses is collected or sent.
•
Quest's transmission of Solutions corresponding to received event codes is fully automated (no human intervention or observation). Quest tallies the frequencies of event codes received and Solutions sent in reply, but does not associate those tallies with IP addresses or any other personally identifying information, and no other information is logged.
•
Quest servers treat each received event code as a query. Quest uses an event code only to determine which Solution to send back to the source of the query, and uses an IP address only to transmit the Solution to the source of the query. Quest servers log querying IP addresses as a matter of course, but Quest does not use them for any other purpose and does not disclose them to any other entity.
•
You may opt out of this feature, to prevent the transmission of event codes and IP addresses to Quest, by unmarking the Enable Internet Access option on the View menu.
•
Goto Line Number: Prompts for a line number in the file to display.

Help menu

•
Online Help... (or F1): Opens Quest’s online Help file for the Log Viewer, which documents its features.
•
About...: Opens a window of information about the Log Viewer—identifying the current release, and asserting Quest’s intellectual property rights to the software.

How to ...

To open a specific log:
•
Drag and drop a wlog file name from Windows Explorer into the Log Viewer window.
— OR —
Click the Open Log File button (in the Toolbar) to view a list of log files that can be opened. In the File section of the screen, select a log file and click OK to open the log in the Quest Log File Viewer.
 
* 
NOTE: The Open Log File button in the Management Console’s Health screen is enabled only when the UdpAppender is defined in the log42net.config file of at least one module. During a new installation, the Log Viewer installer installs a file with the required Udp­Appender. 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. To correct this, see To Add the UdpAppender to an Existing Log File at the end of the Configuring CMN Logging Appendix.
To find a particular text string within an open file:
•
Edit menu | Find... (or Ctrl+F): Opens a Find dialog box that lets you specify a text string to search for within the open file. The Find feature highlights the entire line that contains the target string.
To re-open a recently viewed file:
•
File menu | Recent Files: Shows a list of recently opened files, from which you can select a file to re-open (to quickly re-open a file you have recently viewed and closed).
To save a copy of a file:
•
File menu | Save Copy Of Log File As... (appears only when a file is open): Opens a standard Windows Save As dialog box, from which you can specify the filename and location where you want the open file to be saved. (This feature does not permit any revisions to the open file. It simply lets you save the file in its original form to a new filename and/or a new location.)
To show or hide line numbers:
•
View menu | Show Line Numbers (or Ctrl+L): Toggles the display of line numbers (within the open file) on and off.
To jump to a particular line number in the file:
•
Edit menu | Go To Line Number: Opens a dialog box that lets you specify the destination line number. (Enter the number and click OK.)
To view an entire untruncated log entry:
•
View menu | Show Complete Log Entry (or F5): Opens a Log Detail window that shows the entire string for the selected item—useful when the item text overruns the Log Viewer’s maximum line length (maximum 259 characters), or if the line extends beyond the right edge of the viewer window without wrapping.
To turn internet access on or off:
•
View menu | Enable Internet Access: Toggles the Internet connection on and off.
To copy a selected line to the clipboard:
•
Edit menu | Copy (or Ctrl+C): Copies the selected line to the Windows clipboard.
To close the log viewer:
•
File menu | Exit: Closes the Log Viewer window, or click the Log Viewer Close box ([X]) to dismiss the window and return to the previous display.

Appendix A: Known limitations

The known limitations of any coexistence method are usually due to feature inconsistencies between the two environments. That is, features that are available in one environment may not have an equivalent function in an alternate environment. Other limitations are due to feature incompatibilities, where similar features are available in both environments, but their implementations are so different that remediation is impractical.

 
* 
NOTE: Many of the Known Limitations documented here are due to known or suspected problems with the connected systems, rather than any inherent limitation of the coexistence process with CMN. We list them here as a courtesy, with known solutions (upgrades and hotfixes) where they exist.

Many of the known limitations listed here are inherent to the process and, as such, may not be resolved. Issues that we do expect to resolve in upcoming releases are itemized in the CMN Release Notes, under Known Issues.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen