立即与支持人员聊天
与支持团队交流

Integration for Notes 20.13 - User Guide - BTCal

Section 1: Introduction Section 2: Features and Advantages Section 3: Scope Section 4: Recommended Installer Prerequisites Section 5: Pre-installation Requirements Section 6: Configure the Domino Environment Section 7: Configure Integration for Notes BTCal in Exchange or Office 365 Section 8: Licenses Section 9: Installing Integration for Notes Section 10: Create and Configure Domino Databases Section 11: Modify the Notes.ini File Section 12: Re-start BTCal Domino server to bring it online Section 13: Verification Section 14: On-going Administration Appendix A: ZApp Appendix B: Configure GRIP Appendix C: On the Fly Encryption and Decryption Appendix D: Disable Encrypted Message Routing Appendix E: High Availability/Redundancy Mail and Calendar Routing for Foreign Domains Appendix F: Notes.ini Parameter Descriptions Appendix G: Notes.ini Parameter Values Appendix H: Considerations for Domino SMTP Domain Exposure Appendix I: Processing Repeating Meetings Appendix J: Deployment Quick Reference Appendix K: Customizable Non Delivery Report (NDR) Reason Codes Appendix L: Cross Platform Delegation Appendix M: BT Stats Database

Feature Description

When one or more users are added to an existing Notes repeating meeting, the new users receive an invitation in which the meeting is represented as a series of dates rather than by the original recurrence pattern.  While a Notes Client is able to process a repeating meeting without a well-defined recurrence pattern, a Microsoft Outlook Client is unable to process such a meeting. 

Additionally, if the original meeting had any changes to any of the occurrences, the new users receive a number of exceptions: updates, reschedules, or cancellations depending on the type of changes.  While a Notes client has the ability to automatically process all exceptions (options to ignore them or process them one at a time are also available), an Outlook Client must process exceptions one at a time. Thus, to support the ability to add Exchange Users to existing Domino repeating meetings, the information about the original recurrence pattern must be obtained and used by BTCal when constructing the invitation to Exchange users. 

The process of gathering information about the original meeting from the Domino Chairperson’s calendar is referred to as GRIP (Get Repeating Invitation Pattern).

How GRIP Relates to BTCal

When BTCal encounters an invitation from a Notes user, adding an Exchange user to an existing Notes meeting, it uses GRIP, a process that involves multiple mail-in databases, to manage the addition.   

Installation and Configuration of the GRIP Subsystem

For step-by-step instructions on installing and configuring GRIP, please refer to the Integration for Notes Installation and Configuration of the GRIP Subsystem guide.

 

 

Appendix C: On the Fly Encryption and Decryption

On the Fly Encryption and Decryption (OTFe) is an advanced feature in BTCal that uses standard Domino encryption to automatically decrypt messages sent from Domino to Exchange, and encrypt messages sent from Exchange to Domino.

For Decrypting mail there are two deployment options:

The first option is to use the BTCal database BTIDCache.nsf, where the system can be configured in several scenarios, from using the IBM IDVault to using the ID and password stored in the BTIDVault database.

The other deployment model requires a modification to the Mail file template for all Domino mail users, so that whenever a message (or calendar item) is encrypted, a specific user is automatically added to the BCC field of that item. Integration for Notes will use that ID to decrypt the message before it is routed to Exchange.

Encrypting items from Exchange to Domino requires that the message (or calendar item) be marked as Private.

Integration for Notes will utilize the Public Keys in the Domino Directory to encrypt the messages for each Domino recipient.


In Notes 8 and newer, encrypted messages are broken up into multiple messages if the recipient list is larger than 400 bytes. In these cases, if using the BCC field, only one message would include the BCC recipient. Therefore, Decryption Option 1 (below) is recommended if the BCC field is used.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级