Binary Tree BTCal 5.5 Notes Integration User Guide

Notes Integration | CMT

BTCal 5.5

User Guide

May 2017

Binary Tree Documentation

Table of Contents

Section 1: Introduction ............................................................................................. 6

1.1

Need for Coexistence ................................................................................................................. 6

1.2

Notes Integration | CMT: Product Overview ................................................................................ 6

1.3

Coexistence Environment ........................................................................................................... 7

Section 2: Features and Advantages ............................................................................. 9

2.1

Features .................................................................................................................................... 9

2.2

Functions ................................................................................................................................... 9

2.3

Advantages ................................................................................................................................ 9

Section 3: Installing Notes Integration | CMT ................................................................ 10

3.1

Downloading Instructions ......................................................................................................... 10

Section 4: Notes Integration | CMT on the Domino Coexistence Server ................................ 11

4.1

Installing Notes Integration | CMT BTCal ................................................................................... 11

4.2

Installing Notes Integration | CMT Free/Busy on the Domino Coexistence Server ........................ 16

4.3

Installing Notes Integration | CMT Free/Busy on the Windows Coexistence Server ...................... 20

Section 5: Verifying Notes Integration | CMT for Domino Installation................................... 25

5.1

Notes Integration | CMT ........................................................................................................... 25

5.2

Free/Busy ................................................................................................................................ 25

5.3

For All Components (Common Steps) ........................................................................................ 26

Section 6: Configuring the Domino Coexistence Server .................................................... 27

6.1

Signing the Newly Deployed Templates ..................................................................................... 27

6.2

Creating Mail Router Mailbox.................................................................................................... 27

6.3

Creating Databases using Templates.......................................................................................... 28

6.4

Copying the Access Control List (ACL) to the Newly Created Domino Databases ........................... 28

6.5

Assigning DSAPI Filter to Domino Server Document.................................................................... 29

6.6

Creating a Foreign Domain Document ....................................................................................... 29

6.7

Creating the Foreign SMTP Domain Document........................................................................... 30

6.8

Verifying the Server Configuration Document ............................................................................ 30

6.9

Creating and Editing a Root Trusted Signed Certificate ............................................................... 31

6.10

Configuring Domino Free/Busy Security ................................................................................... 33

6.11

Configuring Exchange Free/Busy Caching ................................................................................. 34

6.12

Configuring the BT Stats Database ........................................................................................... 34

6.13

Configuring Domain Settings ................................................................................................... 35

Section 7: Messaging and Calendaring Component ......................................................... 36

7.1

Invoking the Domino Server Task .............................................................................................. 36

7.2

Domino Mail Router Extension Manager Task (BTEx) .................................................................. 36

7.3

Invoking the Domino Mail Router Extension Manager Task ......................................................... 36

7.4

Notes Integration | CMT Domino Databases .............................................................................. 37

7.5

Adding Exchange Users to an Existing Notes Meeting ................................................................. 37

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

2

Binary Tree Documentation

7.5.1 Feature Description ................................................................................................................. 37

7.5.2 GRIP – Get Repeating Invitation Pattern System Definition ........................................................ 38

7.5.3 GRIP – Get Repeating Invitation Pattern System Workflow ........................................................ 38

7.5.4 GRIP – Get Repeating Invitation Pattern System Configuration .................................................. 39

7.5.5 GRIP – Get Repeating Invitation Pattern System Deployment Alternatives .................................. 39

7.5.6 Add User Notes.ini Parameters ................................................................................................ 40

7.5.7 New Cache Document Creation................................................................................................ 41

7.5.8

Data flow in the GRIP system ................................................................................................ 42

Section 8: Configuring Domino SMTP Routing................................................................ 43

8.1

Foreign SMTP Domain Document .............................................................................................. 43

8.2

Server Connection Document.................................................................................................... 43

8.3

Enable the SMTP Listener Task on a Domino Server.................................................................... 44

8.4

Create a Domino Server Configuration....................................................................................... 44

Section 9: Configuring NOTES.INI ............................................................................... 46

9.1

General Conventions ................................................................................................................ 46

9.2

Configuring Domino Directories ................................................................................................ 46

9.3

Configuring Domino Mail Routing to Exchange ........................................................................... 46

9.4

Handling Attachments between Domino and Exchange .............................................................. 57

9.5

Processing Meetings between Exchange and Domino................................................................. 58

9.6

Processing Repeating Meetings between Exchange and Domino ................................................. 59

9.7

Zero-Touch Application Remediation (ZApp) .............................................................................. 64

9.8

Logging .................................................................................................................................... 72

9.9

Delegation NDRs ...................................................................................................................... 75

9.10

Unused Parameters ................................................................................................................ 75

9.11

Sample NOTES.INI .................................................................................................................. 75

Section 10: Installing ZApp ....................................................................................... 79

10.1

Setting Security for BTStore Database for Notes Integration | CMT ........................................... 79

10.2

Configuring ZApp NOTES.INI Parameters.................................................................................. 82

10.3

ZApp Administration Functions ............................................................................................... 83

10.4

Testing ZApp .......................................................................................................................... 84

Section 11: Verifying Autodiscover, BTAvailability, and BTRouter ........................................ 85

11.1

Autodiscover.......................................................................................................................... 85

11.2

BTAvailability ......................................................................................................................... 86

11.3

BTRouter ............................................................................................................................... 87

Section 12: Troubleshooting Autodiscover, BTAvailability, and BTRouter............................... 90

12.1

Autodiscover.......................................................................................................................... 90

12.2

BTAvailability ......................................................................................................................... 90

12.3

BTRouter ............................................................................................................................... 90

Section 13: Configuring Exchange SMTP Connectivity ...................................................... 92

13.1

Configuring Accepted Domains ............................................................................................... 92

13.2

E-mail Address Policy .............................................................................................................. 92

13.3

Create a Send Connector ........................................................................................................ 93

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

3

Binary Tree Documentation

13.4

Create a Receive Connector .................................................................................................... 94

Section 14: Operations............................................................................................ 95

14.1

Background............................................................................................................................ 95

14.2

Basic Operational Information................................................................................................. 95

14.3

Data Flow through Notes Integration | CMT ............................................................................ 96

Appendix A: Detailed Description of Workflow Items ...................................................... 98

Availability Workflow ........................................................................................................................ 98

Messaging Workflow ........................................................................................................................ 98

Calendar Workflow ........................................................................................................................... 98

Application Workflow ....................................................................................................................... 98

Appendix B: All About Certificates ............................................................................. 99

Creating Autodiscover SSL Certificate on the Windows Coexistence Server .......................................... 99

Replacing Self-signed with CA Certificates in CAS Servers .................................................................... 99

Installing Active Directory CA Services.............................................................................................. 101

Install Enterprise Certificate Authority on a Windows 2008 Server..................................................... 102

Creating Domino SSL Certificate Request ......................................................................................... 103

Appendix C: Considerations for Domino SMTP Domain Exposure ..................................... 106

Appendix D: NOTES.INI Parameters.......................................................................... 107

Appendix E: Processing Repeating Meetings............................................................... 112

Overview ....................................................................................................................................... 112

Repeating Meetings from Lotus Notes ............................................................................................. 113

Recurring Meetings from Microsoft Outlook .................................................................................... 115

Handling Unsupported Events ......................................................................................................... 116

Important Differences in Repeating Meeting Functionality between Notes and Outlook ..................... 116

Handling of the Entire Series Reschedule in Microsoft Outlook.......................................................... 118

Summary ....................................................................................................................................... 118

Appendix F: Deployment Quick Reference ................................................................. 119

Lotus Domino Configuration............................................................................................................ 119

Appendix G: Customizable Non Delivery Report (NDR) Reason Codes ................................ 121

Appendix H: Cross Platform Delegation ..................................................................... 128

Notes Chairperson invites Notes User who delegates to an Outlook User .......................................... 128

Notes Chairperson invites Outlook User who delegates to a Notes User ............................................ 128

Notes Chairperson invites Outlook User who delegates to an Outlook User ....................................... 129

Outlook Chairperson invites Outlook User who delegates to a Notes User ......................................... 129

Outlook Chairperson invites Notes User who delegates to a Notes User ............................................ 129

Appendix I: BTCache Database Purging and Archiving ................................................... 130

Purge Settings ................................................................................................................................ 130

Setting $BTPurgeDate on documents ............................................................................................... 131

Appendix J: On the Fly Decryption and Encryption ....................................................... 132

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

4

Binary Tree Documentation

Prerequisites & Settings .................................................................................................................. 132

Decryption Option 1 (Recommended) ............................................................................................. 132

Decryption Option 2 ....................................................................................................................... 133

Encryption Options ......................................................................................................................... 134

Customizable NDR’s ........................................................................................................................ 135

Configuration of the Domino Database ............................................................................................ 135

Creating the ID Vault Database ...................................................................................................... 135

Setting up Security for the BTIDVaultDB Database........................................................................... 136

Configuring the Settings in the BTIDVault Database ........................................................................ 138

Mail-enabling BTIDVault Database................................................................................................. 139

Modifying the Inbound Processing Agent ........................................................................................ 140

Message Templates....................................................................................................................... 141

Types of Predefined Message Templates......................................................................................... 142

Importing Users ............................................................................................................................ 142

Sending User Notifications ............................................................................................................. 142

How it Works ................................................................................................................................. 143

Encrypting from Exchange to Domino ............................................................................................. 143

Decrypting from Domino to Exchange.............................................................................................. 144

Decryption Option 1 ...................................................................................................................... 144

Decryption Option 2 ...................................................................................................................... 144

Appendix K: BT Stats Database ............................................................................... 145

Appendix L: SetFBCred Utility ................................................................................. 146

AvailabilityService........................................................................................................................... 146

Autodiscover .................................................................................................................................. 147

AvailabilityRouter ........................................................................................................................... 148

About Binary Tree................................................................................................ 149

Binary Tree Social Media Resources ................................................................................................. 149

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

5

Binary Tree Documentation

Section 1: Introduction

Notes Integration | CMT BTCal features a new name and logo, but is the same, trusted product previously k nown as CMT for Coexistence.

1.1 Need for Coexistence

Coexistence is required when multiple messaging environments need to exist together over an extended period due to mergers, acquisitions, or during e-mail system migrations. During the coexistence period transparent, highly functional, and stable communication throughout the e-mail environment is mission-critical. Therefore, coexistence becomes much more than just a system that merely ensures that e-mail is delivered in a timely fashion.

Coexistence between Lotus Domino and Microsoft Exchange is successful, if the following criteria are met:

 Messages on the destination platform appear exactly the way they appear in the source platform including attachments, rich text, embedded images, and forms

 Cross platform calendaring including Free/Busy lookups is functional

 Synchronized e-mail directories using Directory Sync Pro to allow transparent access to addressing information

*See Directory Sync Pro for Domino and Active Directory documentation for details

1.2 Notes Integration | CMT: Product Overview

Notes Integration | CMT delivers the highest levels of functionality, stability, and scalability for connection between Microsoft Exchange and Lotus Domino. It provides high-fidelity exchange of mail and calendar data. It also intercepts mail and calendar data traveling between the environments, and if necessary, alters address and content portions of message header and body to make coexistence between environments more transparent, functional, and user-friendly.

Notes Integration | CMT establishes high-fidelity interoperability and preserves user workflow between Domino and Exchange Servers. Workflow can be described as flow of data or informatio n between users, applications, or a user and application. To understand the different types of workflow accomplished in a Coexistence environment, refer to the following illustration.

Here is a brief description of how each of the workflow component contributes to making Notes Integration | CMT a complete solution for coexistence.

Directory Workflow – Directory Sync Pro can be used to establish directory synchronization between the two platforms to make sure that user addressing is transparent and functional regardless of the migration status of the users. See the Directory Sync Pro User Guide for more information.

Availability Workflow - Provides for calendar free/busy lookups to ensure that users can obtain availability information for other users regardless of the system with which the users are associated.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

6

Binary Tree Documentation

Messaging Workflow - Enables the high-availability, high-performance, and high-fidelity exchange of data that preserves the workflow related to e-mail including document and database links.

Calendar Workflow - Ensures that calendars stay synchronized between Notes and Outlook users when creating, updating, rescheduling, and cancelling meetings regardless of a user’s migration status.

Application Workflow - Preserves the ability of a user to receive application-originated e-mails and to perform the actions required by these e-mails.

For a more detailed description of each of these workflow items, refer to Appendix A.

1.3 Coexistence Environment

A coexistence environment consists of three servers, which are specifically configured so that Notes Integration |

CMT can be utilized optimally. These servers are:

 Domino Coexistence Server

 Windows Coexistence Server

 SQL Coexistence Server (for Directory Sync Pro)

An optional component of Notes Integration | CMT is Zero-touch Application Remediation (ZApp), which enables

Microsoft Outlook users to view and act on e-mail-enabled Notes applications. This is configured on the Domino

Coexistence server.

In the illustration, one of the components is the Domino Coexistence Server, which is responsible for supporting coexistence server tasks at the Domino end of the environment. These server tasks include:

 Messaging/calendaring/application coexistence

 Free/Busy lookup

It also holds a Domino database for storing remediated items (BTStore).

The Windows Coexistence Server, on the other hand, is designed to support coexistence on the Exchange side with Free/Busy lookup.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

7

Binary Tree Documentation

The SQL Coexistence Server can be a dedicated or shared SQL Server (in the middle of the illustration) and contains a dedicated transitional SQL database, which is utilized for directory synchronization between Domino and Exchange.

Messaging

The coexistence environment is configured to enable mail flow between Domino and Exchange. It is also configured to determine how the e-mail addressing will be handled between the two platforms. Similarly, the system is configured such that there is transitional calendar workflow between Domino users and Exchange users to enable them to schedule/update/reschedule/cancel single occurrences and recurring meetings irrespec tive of their migration status.

For migrated items with Notes Migrator | CMT, this will not be true until a full post-migration workflow has been implemented. Refer to Appendix E for information regarding unsupported items.

Directory Synchronization Using Directory Sync Pro

Directory Synchronization is accomplished by reading data from source directories, Active Directory and the

Domino Directory, and writing it into an SQL database. In turn, information in SQL is written into target directories,

Active Directory and the Domino Directory. The SQL database allows for the customization of data from one directory to another directory. Some of the basic mapping is already completed; however, there are several changes that must be made to accommodate environments ranging from the small business to enterprise deployments. The Domino BTDirSync task handles all the interaction with SQL for reading and writing to Domino.

The Windows BTDirSync (full name BinaryTree.Coexistence.DirSync.Exchange.ex e) service handles the reading and writing to Active Directory. The Client UI component is used to configure the base settings for connectivity.

Free/Busy

The way a Domino environment implements its calendar Free/Busy queries is different from the way Exchange does. One environment cannot see the availability of users in the other environment. To make the two environments communicate with each other, Notes Integration | CMT configures the system such that one environment can determine the Free/Busy status of users within the other environment.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

8

Binary Tree Documentation

Section 2: Features and Advantages

2.1 Features

There are a number of improvements achieved by Notes Integration | CMT in the interchange of e-mail and calendar data between Domino and Exchange.

The following functions indicate the various improvements:

 Improvement in the display-name formatting for mail messages and calendar invites

 Calendar originator and invitee presentation

 Improvement in invitee tracking, attachments, room/resource reservation, repeating/recurring invitations/updates

 Improvement in alerting users when updates to recurring meetings cannot be processed correctly

 Database, view, and document links are displayed in Outlook the same way they are displayed in Notes

 Embedded forms, buttons and other Lotus Notes elements come across to Outlook users as actionable links; therefore, critical workflow processes are not disrupted

 Supports Notes UI email commands (as designed) even after the user moves to Outlook

 Supports redundancy and clustering of mail flow

2.2 Functions

Notes Integration | CMT is designed to:

 Achieve high-fidelity exchange of mail and calendar data by utilizing SMTP protocol with MIME and iCAL encoding of Rich Text data.

 Increase reliability with redundant mail flow paths for SMTP-based high-fidelity e-mail data exchange.

 Enable reliable Free/Busy schedule lookup between Microsoft Exchange and Lotus Domino users by providing the proper address resolution.

2.3 Advantages

Notes Integration | CMT :

 Improves the appearance of the From:, To:, and CC: addresses, replacing potentially unfriendly SMTP addresses with user-friendly display names, thereby improving the transparency and addressability of email replies

 Identifies and intercepts Exchange or Domino initiated invitations that the opposite system cannot support, and sends notifications to the meeting initiators

 Uses an auto-processing workflow to enable Outlook users to invite rooms and/or resources defined in the Lotus Domino Resource Reservati ons databases and apply those rooms or resources to Outlook calendars

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

9

Binary Tree Documentation

Section 3: Installing Notes Integration | CMT

To install Notes Integration | CMT, you need to perform the following two main installations:

 Notes Integration .exe installation package for BTCal and ZApp to be installed on the Domino Coexistence server

 Notes Integration FreeBusy.exe installation package for BTFree/Busy to be installed on the Domino

Coexistence server and Windows Coexistence server

Please refer to the Directory Sync Pro Installation Guide if you will be installing Directory Sync Pro.

The Windows Server 2008 R2 administrator needs to turn on the .Net 4.0 features prior to installing Notes Integration | CMT for Exchange on the Windows Coexistence server. Enable the feature by running the following command:

ServerManagerCMD -i RSAT-ADDS Net-Framework Web-Server Web-Metabase Web-ASP-NET

Web-ISAPI-Ext Net-HTTP-Activation Web-Basic-Auth Web-Digst-Auth Web-Windows-Auth

Web-Dyn-Compression Web-Net-Ext

3.1 Downloading Instructions

Binary Tree maintains the latest release of all the Install Kits on a secure FTP web site. The address to the FTP site is ftp://cftp.binarytree.com

. To download a copy, Binary Tree will provide a user name and password. Log on to the web site using the given credentials and download a copy of the Install Kit to your Windows Desktop.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

10

Binary Tree Documentation

Section 4: Notes Integration | CMT on the Domino

Coexistence Server

4.1 Installing Notes Integration | CMT BTCal

If partitioned, your Domino server(s) need to be stopped to install the Notes Integration |

CMT software.

The BTCal components are installed separately from the Free/Busy components.

1. Run the Notes Integration .exe as Administrator.

2. On the installation wizard screen, click Next.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

11

3. Review the Software License Agreement and then click Yes.

Binary Tree Documentation

4. On the Verify Domino Instance Data Directory Path screen, browse to the location of the Notes.ini file that will be modified for the Domino instance. Click Next.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

12

Binary Tree Documentation

5. On the Confirm Domino Directories screen, confirm the displayed directories contain the Domino

Program Directory where you want to install Notes Integration | CMT BTCal and the Domino Data

Directory. Click Next.

6. On the Ready to Install the Program screen, click Install to begin the installation.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

13

7. The progress of the installation will be displayed on the Setup Status screen.

Binary Tree Documentation

8. On the Edit notes.ini screen, select to modify the notes.ini file, save the required changes to a notes.ini alt file, or select to not make any changes to the notes.ini file. Click Next.

These changes must be made to the

Notes.ini for Notes Integration | CMT BTCal to run.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

14

Binary Tree Documentation

9. An informational message appears if you selected to modify the notes.ini file. Click OK. You must restart the Domino server for the changes to take effect.

10. When installation is completes, the wizard complete screen appears. Click Finish to close.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

15

Binary Tree Documentation

4.2 Installing Notes Integration | CMT Free/Busy on the Domino Coexistence Server

The Free/Busy components for the Domino Coexistence server is installed separately from the BTCal components.

1. Confirm the Domino server is not running on the box.

2. Run the Notes Integration FreeBusy.exe as Administrator.

3. On the installation wizard screen, click Next.

4. Review the Software License Agreement and if you agree click Yes to continue.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

16

Binary Tree Documentation

5. On the Verify notes.ini path for the FreeBusy Domino server screen, browse to the location of the

Notes.ini file that will be modified for the Domino instance. Click Next.

If you are installing on a partitioned server, the default value may not be correct. Verify that this is the Domino data directory for the Notes Integration | CMT server.

6. On the Confirm Domino Directories screen, confirm the Domino Program and Data directory paths for the

Domino Server instance where you want to install Free/Busy and the path to the Notes.ini. Click Next.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

17

Binary Tree Documentation

7. On the FreeBusy Install Configuration screen, enter the Domino SMTP domain name for which you would like to expose Free/Busy information. Click Next.

8. On the Ready to Install the Program screen, click Install to begin the installation .

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

18

Binary Tree Documentation

9. The progress of the installation will be displayed on the Setup Status screen.

10. On the Edit notes.ini screen, select one of the following options:

 Let Setup modify the notes.ini file – (Default) Recommended for first time installing Notes

Integration |CMT BTCal and Free/Busy.

 Save the required changes to a notes.ini alt file – May select if you want to manually update an existing notes.ini file from a previous installation. This is recommended if you are reinstalling or repairing Free/Busy, and wish to manua lly update the existing entries.

 Do not make any changes – Selecting this option is not recommended.

Click Next.

11. An informational message appears if you selected to modify the notes.ini file. Click OK. Changes to the notes.ini file will take effect when the Domino server is restarted.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

19

Binary Tree Documentation

12. When installation is complete, the Wizard Complete screen appears. Click Finish to close.

4.3 Installing Notes Integration | CMT Free/Busy on the Windows Coexistence Server

1. Run the Notes Integration FreeBusy.exe as Administrator .

2. On the installation wizard screen , click Next.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

20

3. Review the Software License Agreement and if you agree, click Yes to continue.

Binary Tree Documentation

4. On the Choose Destination Location screen, accept the default destination location or browse to the desired location. Click Next.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

21

Binary Tree Documentation

5. On the first Notes Integration CMT - FreeBusy Install Configuration screen, enter the FQDN of the

Exchange CAS server hostname. Click Next.

6. On the second Notes Integration CMT - FreeBusy Install Configuration screen, enter the DNS name of the

Domino Server. Click Next.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

22

Binary Tree Documentation

7. On the third Free/Busy Install Configuration screen, enter the Domino SMTP domain name for which you would like to expose Free/Busy information. Click Next

8. On the Additional setup is required screen, copy the command and run it in an Exchange Management

Shell. Then, click Next. This command will set the Availability Address Space in Exchange for the Domino user so Free/Busy requests are sent to Domino.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

23

9. On the Ready to Install the Program screen, click Install to begin the installation.

Binary Tree Documentation

10. The progress of the installation will be displayed on the Setup Status screen.

11. When installation is complete, the Wizard Complete screen appears . Click Finish to close.

12. Run an IIS Reset by typing “iisreset” from a command prompt.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

24

Binary Tree Documentation

Section 5: Verifying Notes Integration | CMT for Domino

Installation

5.1 Notes Integration | CMT

1. Once the installation completes, make certain that the following files exists in the

C:\Lotus\Domino

folder:

 nBTCal.exe

 nBTCal.sym

 nBTEx.dll

 nBTEx.sym

2. BTCal value is added to the ServerTasks parameter in the NOTES.INI file.

3. EXTMGR_ADDINS= BTEx is added to the NOTES.INI file.

5.2 Free/Busy

1. After installation completes, verify the following files exist in the Domino program directory:

 BinaryTree.Domino.CAPIWrapper.dll

 BinaryTree.Domino.CoexServiceLibrary.dll

 BinaryTree.Domino.Ex12ServiceLibrary.dll

 BinaryTree.Domino.Ex14ServiceLibrary.dll

 BinaryTree.FreeBusy.Domino.dll

 BTAvailabilityService.wsdl

 nBTDominoListener.dll

 nBTFreeBusy.exe

 nBTFreeBusy.exe.config

If any of these files are missing, confirm the security rights to the install directories and then rerun the install wizard.

2. Verify the following items have been added to the NOTES.INI file.

 ServerTasks=BTFreeBusy, HTTP

 BTCOEX_NSF=btws.nsf

 BTCOEX_WS_NAME=BTAvailability (should match the virtual directory used by the BTRouter on the

Windows Coexistence server; BTAvailability is the default value)

 BTCOEX_LOGFILE=\IBM_TECHNICAL_SUPPORT\OUTPUT.LOG (should be relative to the <Domino server>\Domino Data Directory)

 BTExchangedb=btexchange.box

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

25

Binary Tree Documentation

3. Verify the following databases exist in the Domino data directory (create if missing):

 BTWS.nsf file (Free/Busy Web Services database)

 BTExchange.box (mail router database based off a mailbox.ntf template)

The Domino Administrator should sign this database (and all databases installed by Notes

Integration | CMT) with the appropri ate ID.

5.3 For All Components (Common Steps)

Some verification steps are common to all components.

1. The Domino component of Notes Integration | CMT is comprised of an executable (BTCal) that runs as a

Domino server task, and a Domino Extention Manager dll(BTEX). These are copied into the Domino

Program Directory of the Domino Coexistence Server during the installation. If a previous version of the file exists, it should be backed up for future reference. When installing or upgrading this module, stop the

Domino Server.

2. The C:\Program Files\BinaryTree\CMT for Coexistence <version number> Domino folder is created by the install.

3. The NOTES.INI file is updated with the required and optional parameters .

4. Modify the NOTES.INI file to comment out the new BT tasks in the ServerTasks entry. You need to perform this step; otherwise, these tasks will launch automatically prior to configuration, which can lead to a server crash.

The best way to do this is to copy the servertasks line and paste it back underneath the original line. Then, comment out the first line and remove the BT server tasks from the new line.

5. Once the NOTES.INI file is modified, you may start up the Domino server.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

26

Binary Tree Documentation

Section 6: Configuring the Domino Coexistence Server

The installer deploys the following files in the Domino Data Directory on the target Domino Server if you selected the corresponding component to install:

 BTCacheV3.ntf - Application template for Notes Integration | CMT Calendar Cache BTCache.nsf

(Calendaring)

 BTStore.ntf - Application template for Notes Integration | CMT ZApp Storage BTStore.nsf (ZApp)

 BTCalStats.ntf – Application template for gathering statistical information on ZApped items, NDR’s, and calendaring processing

 BTws.nsf - The Free/Busy Web Services database (Free/Busy)

 BTGRIPLocalV2.ntf -

A single local database is deployed on the Domino Coexistence Server .

 BTGRIPRemote.ntf -

Any number of remote databases are deployed on any number of downstream

Domino Servers.

 BTIDCache.ntf - ID Vault database used for decrypting mail being sent from Domino to Exchange/O365 .

6.1 Signing the Newly Deployed Templates

1. Locate the following database and templates in the Domino server’s Data directory and sign them with either the server’s ID or an ECL signing ID:

 btws.nsf

 btcachev3.ntf

 btstore.ntf

 btcalstats.ntf

 BTIDCache.ntf

2. Set the ACL of btcachev3.ntf and btcalstats.ntf to the following. Include any other entries that may be required by company policy:

[-Default-] No Type No Access

[LocalDomainAdmins] Person Group Manager

[LocalDomainServers] Server Group Manager

3. Set the ACL of btstore.ntf to the following. Include any other entries that may be required by company policy:

[-Default-] No Type Editor

[BTZAppAdmins] Person Group Manager (Make sure this matches the group that was created)

[LocalDomainAdmins] Person Group Manager

[LocalDomainServers] Server Group Manager

4. The ACL setting for the BTIDVault Database are covered in Appendix J.

6.2 Creating Mail Router Mailbox

After the templates are in place and signed by the administrative Notes ID, create the mail router mailbox

(btexchange.box) on the server using the mail router Mail Router Mailbox mailbox.ntf template also from the server .

1. Launch Lotus Notes.

2. Click File -> Database -> New.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

27

Binary Tree Documentation

3. In the New Database dialog box, specify the server name in the Server field and title as BT Exchange

Mailbox for the database in the Title field.

4. The File name is specified automatically based on the title name. It is recommended that you do not change the name.

5. Click Show advanced templates.

6. Select the Mail Router Mailbox mailbox.ntf template to create a new mail router mailbox.

7. Click OK.

6.3 Creating Databases using Templates

1. Create a new database in the Data directory of the Domino Coexistence server based on the BT Calendar

Cache (btcachev3.ntf) template. Title the new database as “BT Calendar Cache” with a filename of btcache.nsf.

2. Create a new database in the Data directory of the Domino Coexistence server based on the BT Stats

(btcalstats.ntf) template. Title the new database as “BT Stats” with a filename of btcalsta.nsf.

3. Create a new database in the Data directory of the Domino Coexistenc e server based on the BTDocument

Store (btstore.ntf) template. Title the new database as “BT Document Store” with a filename of btstore.nsf.

4. Open the BTStore.nsf database, select Database Settings from the Navigator and enter the following settings;

General Settings

Enable ZAPP Logo; = Yes (Enables the ZApp logo in the Left hand corner)

Prevent Storage of emails generated by this database: =Yes (to prevent emails that are replied to or forwarded from being stored)

Hide BCC: = Yes (could generate email to us er with their name missing from the header)

Purge Settings

Status: = Enabled (will auto-purge based on settings)

BT Store Info

DB Owner: = Set to Admin or Agent ID

Production Date: = Date going into to Production

6.4 Copying the Access Control List (ACL) to the Newly Created Domino Databases

Use the Domino Administrator to copy the ACL from an existing mail router box on a Domino Server and paste it into the ACL of the newly created databases.

1. To do this, switch to Domino Administrator. Ensure that the cor rect server is open.

2. Open the Files tab.

3. Locate a mail router box on the server and right-click on it.

4. From the pop-up menu, select Access Control -> Copy.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

28

Binary Tree Documentation

5. Next, select BTCache.nsf, right-click on the databases and from the resulting pop-up menu select Access

Control -> Paste.

6. The Default ACL for the BTStore.nsf database should allow Editor with delete privileges for all Domino users.

7. To access the Default ACL for BTStore.nsf in Domino Administrator, select the database, right click on it, and select Access Control -> Manage from the pop-up menu.

8. Next, select the Default ACL, change the access to Editor in the Access field, check the Delete documents checkbox, and then click OK.

There should now be four new databases on the Domino server.

The BTIDVault database and Stats database will also appear if deployed

9. In addition to the above databases, the BTZAppREADERS group should also be assigned the Manager

Access with all privileges on each database.

6.5 Assigning DSAPI Filter to Domino Server Document

Specify the DSAPI filter to the Domino server document.

1. In Domino Administrator, click the Configuration tab.

2. Expand Server, and then select All Server Documents in the left pane.

3. Double-click on the Domino server document in the right pane to open the server document.

4. Click the Internet Protocols tab, and then the HTTP tab.

5. In the DSAPI Filter section, specify nBTDominoListener as the ONLY DSAPI filter entry, and then Save &

Close the document.

6.6 Creating a Foreign Domain Document

Create a Foreign Domain document. This document is used to route mail from Domino to the BTCal application so it can convert data from Domino that cannot be translated properly in Exchange.

1. In the Domino Administrator , go to the Configuration tab, and in the left pane, select Messaging ->

Domains. Choose Add Domain.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

29

Binary Tree Documentation

2. In the document that opens, set the following options:

Field Name

Domain type

Description

Choose Foreign Domain.

Foreign domain name

Typically, this will be BTExchange, but should match the Foreign Domain attribute on the

Directory Connector you create.

Gateway server name

Specify the canonical name of the Domino

Coexistence server and for the Gateway Mail File

Name use the value BTExchange.box.

Calendar server name

Specify the canonical name of the Domino

Coexistence server and for the Calendar System use the value BTExchange.box.

3. Click Save & Close. This new document will need to replicate to all other servers in the Domino domain.

For multiple domain installations, additional non-adjacent Domain documents must be created to allow Free/Busy requests from these downstream domains to Exchange users.

6.7 Creating the Foreign SMTP Domain Document

The Foreign SMTP Domain document describes specific routes to SMTP destinations for Domino servers in much the same way as SMTP Outbound Connectors do in Exchange server.

1. Specify the Internet Domain and the Domain name (as SMTPExchangeDirect).

2. Verify the Global Domain document to ensure that the alternate Internet domain alias of the specified IIS site (domino.contoso.com) is added.

6.8 Verifying the Server Configuration Document

1. Under Messaging in the Configurations tab, verify the Configuration document for the server.

2. Under the Mime -> Conversion Options -> General tab, Return receipts is Enabled.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

30

Binary Tree Documentation

3. Under Mime -> Conversion Options -> Outbound, verify that the Attachment encoding method is Base64 and the Message content is From Notes to HTML.

4. On the Router/SMTP tab in the Configuration document, under Basics, ensure that you set the Number

of mailboxes to 1 and SMTP used when sending messages outside of the local internet domain is

Enabled.

6.9 Creating and Editing a Root Trusted Signed Certificate

Free/Busy requests that are coming from Exchange go through Domino’s HTTP task, which fully supports SSL when properly configured. You can refer to the Domino Administrator help for configuration steps.

Free/Busy requests going to Exchange cannot be made using Domino’s HTTP task, so the BTFreeBusy task is used.

If you can access the IIS COEX server root site from Internet Explorer on the Domino COEX server without SSL error

BT FreeBusy is configured properly.

1. From the server, open Internet Explorer and browse to the Windows Coexistence Server via HTTPS protocol: (e.g.: https://autodiscover.domino.contoso.com/).

2. Click on the lock on the browser bar, and then select View certificates.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

31

Binary Tree Documentation

3. Next, click on the Certification Path tab, the root certificate signer, and then click View Certificate.

4. When the root certificate is open, click on the Details tab, and then click Copy to File.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

32

Binary Tree Documentation

It is assumed that the installer know how to install the SSL certificate on the Domino and

Windows Coexistence servers.

The Domino SSL certificate will need to be added to the Certificate Store on the Windows

Coexistence server.

6.10 Configuring Domino Free/Busy Security

User-Level Security

OrgWide FreeBusy (OrgWideFB)

Everyone in the Exchange organization has the same access rights, so there is no need to identify the person making the request. This is the default for Exchange.

BTCOEX_BYPASS_REQUESTOR

Accepted value = 0/1

Default = 0

This setting must be set to 1.

When set to 1, Exchange requests will use the credentials supplied by the

BTCOEX_DEFAULT_FB_ACCESS_ACCOUNT parameter (described below). This is useful when Exchange is not supplying the user ID because it is set to OrgWideFB.

BTCOEX_DEFAULT_FB_ACCESS_ACCOUNT=<SMTP address>

The account specified will provide the access, which the entire Exchange organization will have when querying into the Domino Availability Service. The SMTP address is that of an Exchange user in the Domino Foreign domain that has been Directory Synchronized to Domino.

This allows Domino to correctly recognize the domain of the mailbox; an Exchange OrgWideFB user, and if it finds a

Free/Busy request for a user in that same Foreign domain, it will not send it.

If BTFreeBusy detects an invitee in the same domain as the person checking FreeBusy time, it prints a message to the Domino console. The BTFreeBusy Server prints the message when the request is from an Outlook user, and

BTFreeBusy Client prints the message when the request is from a Notes user. The error mess age is in the following format:

05/11/2011 10:59:10 AM BTFreeBusy Server: Error servicing request for <the user name>.break.loop - caller and this user are in same domain: CMT.: schedule object doesn't exist

5/11/2011 10:59:10 AM BTFreeBusy Server: This request should not be going through BTFreeBusy Server.: schedule object doesn't exist

The administrator of the appropriate system will need to modify the indicated user's configuration.

BTCOEX_APPROVED_CALLERS=<IP addresses>

This comma separated list of IP addresses restricts the source of Free/Busy requests that will be processed by

Domino Free/Busy. Legitimate requests would only come from servers known to the BT Coexistence install, and trusted to have performed all necessary authentications prior to all owing OrgWideFB requests. (example,

127.0.0.1,192.168.0.1)

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

33

Binary Tree Documentation

Not providing a list of IP addresses for this setting is a potential security risk as the box would allow requests to come from any source.

6.11 Configuring Exchange Free/Busy Caching

Duplicate Free/Busy requests from Domino to Exchange are filtered to improve the performance. Duplicate requests are caused by incompatible behavior in the Lotus Notes client, as well as when the refresh button is clicked. The responses are cached for a default duration of 60 seconds. The caching duration can be modified by changing the following NOTES.INI settings:

BTCOEX_CACHE_EXCH_RESPONSE

Accepted value = <number of seconds to cache the response>

Default = 60

You can also set the Free/Busy caching on by using the following Domino console command: tell btfreebusy cache n, where n is the number of seconds to cache the response; 0 is also a valid value.

To turn the Exchange Free/Busy caching feature off, set the BTCOEX_CACHE_EXCH_RESPO NSE parameter to a value of zero.

You can also use the BTCOEX_DONT_CACHE_EXCH_RESPONSE parameter to turn the Exchange Free/Busy caching feature off. Specify 1 to indicate that the default value of 60 seconds should not be used.

6.12 Configuring the BT Stats Database

The BT Stats Database (btcalsta.nsf) is configured by default to capture all NDR and ZApp items and can be configured to log all successes of BTCal calendar processing as well.

The BT Stats Database can be configured by changing the following NOTES.INI settings:

BTSTATSDB

Default = btcalsta.nsf

By default btcalsta.nsf is the file name of the BT Stats database.

BTCALSTATSNDR

Accepted value = 0/1

Default = 1

Details of all NDR notifications appear in the view. This parameter is enabled (value set to “1”) by default.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

34

Binary Tree Documentation

BTCALSTATSZAPP

Accepted value = 0/1

Default = 1

Details of all ZApped items appear in the view. This parameter is enabled (value set to “1”) by default.

BTCALSTATSNOCHANGE

Accepted value = 0/1

Default = 0

This parameter can be enabled to log all successes of BTCAL calendar processing (messages not changed by ZApp or BTCal). This parameter is disabled (value set to “0”) by default.

6.13 Configuring Domain Settings

BTCOEX_ EXCHANGE _DOMAINS and BTCOEX_DOMINO _DOMAINS

Invitees in a Free/Busy request going to Exchange must be in a domain listed in the notes.ini

BTCOEX_EXCHANGE_DOMAINS variable. Invitees in a Free/Busy request going to Domino must be in a domain listed in the notes.ini BTCOEX_DOMINO_DOMAINS vari able. These two notes.ini variables are required (the below values are examples only).

BTCOEX_DOMINO_DOMAINS=BinaryTree,BTCMT,Domino

BTCOEX_EXCHANGE_DOMAINS=BinTreeEX,BTExchange,Exchange

The BTFreeBusy code checks requests coming from Exchange to make sure they are asking about users in the

BTCOEX_DOMINO_DOMAINS.

The BTFreeBusy code checks requests going to Exchange to make sure they are asking about users in the

BTCOEX_EXCHANGE_DOMAINS.

This is done to prevent an infinite loop of FreeBusy requests between the Exchange and Domino servers, which can happen when Exchange assumes that a particular SMTP address belongs to a Domino user, while Domino assumes that SMTP address belongs to an Exchange user.

If a list of domains is longer than 255 characters, the notes.ini variables are contained in a series by appending a sequence number to the end of the variable name.

For example, if the original variable BTCOEX_DOMINO_DOMAINS contains more than 255 characters, the variables

BTCOEX_DOMINO_DOMAINS1, BTCOEX_DOMINO_DOMAINS2, and so on, where each one provides up to a 255 character portion of the list of domains, will be used.

BTCOEX_SERVICE_TYPE

Accepted Value: COEX

Default Value: COEX

The BTCOEX_SERVICE_TYPE parameter specifies the Web Service format used by the Binary Tree IIS apps to translate to the correct version of the EWS format.

The BTCOEX_SERVICE_TYPE parameter is set to COEX by default and should not be changed.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

35

Binary Tree Documentation

Section 7: Messaging and Calendaring Component

The Notes Integration | CMT BTCal (also sometimes referred to as BTCal) primarily consists of:

 Two sets of software modules installed in the Domino Program Directory: o BTCal – Domino Server Task o BTEx – Domino Mail Router Extension Manager Task

 Two Domino Database Templates installed in the Domino Data Directory of a dedicated Domino server: o BTCacheV3.ntf o BTStore.ntf

 Two GRIP (

Get Repeating Invitation Pattern) templates: o BTGRIPLocalV2.ntf o BTGRIPRemote.ntf

You may have several Domino Coexistence Servers defined in a Lotus Domino Environment.

7.1 Invoking the Domino Server Task

Like any other Domino Server Task, BTCal, may be invoked manually by issuing the following command on the

Domino Coexistence Server Console.

Load btcal

The installation adds BTCal to the list of values of the ServerTasks parameter in the Domino Coexistence Server

NOTES.INI file to set it to invoke automatically at the start of the Coexistence Domino Server.

ServerTasks=Router,Replica,…,

BTCal

Do not rename nBTCal.exe, as it will result in the loss of functionality.

BTCal will now create a new logfile each time it starts up. The log filename will be in the format btlog_yyyy_mm_dd@hh_mm_ss.log.

7.2 Domino Mail Router Extension Manager Task (BTEx)

The following files are included for BTEx:

 nBTEx.dll

 nBTEx.sym

The Domino Mail Router Extension Manager Task module is copied into the Program Directory of the Domino

Coexistence Server during the installation. If a previous version of the file exists, it should be backed up for future reference. When installing the module, the Domino Coexistence Server must be shut down.

7.3 Invoking the Domino Mail Router Extension Manager Task

The installation adds BTEx to the list of values of the EXTMGR_ADDINS parameter in the Domino Coexistence

Server NOTES.INI file to set Mail Router Extension Manager Task to invoke automatically at the start of the Domino

Coexistence Server.

EXTMGR_ADDINS=BTEx

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

36

Binary Tree Documentation

Binary Tree strongly recommends that BTEx be the only Mail Router Extension Manager Task invoked on the Domino Coexistence Server. If this is not possible, please ensure that BTEx is the first value of the EXTMGR_ADDINS parameter.

7.4 Notes Integration | CMT Domino Databases

In addition to the program modules, Notes Integration | CMT requires four Domino databases and two GRIP databases:

 BTStore

 BTCache

 BTGRIPRemote

 BTGRIPLocal

These databases must be created from the templates provided as part of the Notes Integration | CMT installation package. These templates are copied into the Data Directory of the Domino Coexistence Server during the installation. To create the BTStore database, create a new Domino database based upon the BTStore.ntf template received as part of the Notes Integration | CMT Installation package. To create a new BTStore database from the

latest BTStore template, click here .

If previous versions of the templates exist, they should be backed up for future reference.

The ACL for all three templates should be modified with the following entries:

-Default-

Unspecified “No Access”

Anonymous

LocalDomainAdmins

LocalDomainServers

[-Default-]

Unspecified

Person Group

Server Group

Unspecified

“No Access”

"Manager"

"Manager"

“No Access”

[Anonymous]

Unspecified “No Access”

[LocalDomainAdmins]

[LocalDomainServers]

Person Group

Server Group

“Manager”

“Manager”

7.5 Adding Exchange Users to an Existing Notes Meeting

7.5.1 Feature Description

When one or more users are added to an existing Lotus 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 Lotus 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. 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).

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

37

Binary Tree Documentation

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.

7.5.2 GRIP – Get Repeating Invitation Pattern System Definition

When BTCal encounters an invitation representing the process of adding an Exchange user to an existing meeting,

BTCal cannot make a direct connection to a Mail File of a Domino meeting Chairperson; therefore, it employs th e

GRIP system consisting of multiple Mail -In databases and relies on Domino Mail Routing to transport the information between them. This system is referred to as GRIP – Get Repeating Invitation Pattern.

There are two types of databases in the GRIP system: Local and Remote. A single local database is deployed on the

Domino Coexistence Server. Any number of Remote databases may be deployed on any number of downstream

Domino Servers. Depending on the deployment decisions, a single GRIP Remote database ma y service multiple

Domino Servers; however, there should never be a need to put multiple Remote databases on any Domino Server.

The Local GRIP Database becomes a conduit between BTCal and the Remote GRIP Databases. Each GRIP database must be defined as a Mail-In database in a Domino directory.

The file name and file path of the Local and Remote GRIP Databases are immaterial. Recommended values are

BTGRIPLocal.nsf and BTGRIPRemote.nsf, respectively. The databases are based on the BTGRIPLocalV2.ntf and

BTGRIPRemote.ntf templates supplied by Binary Tree as part of the Notes Integration | CMT installation package.

The Mail-In name of the database is crucial and consists of a free-formatted prefix from the settings of the documents in the BTGRIP Local database followed by the lower case common name of the Domino Server on which it resides. It is required that a single space is placed between the prefix and the server name in the mail -in database document name. The GRIP system uses GRIP Mail-In database names to direct e-mails between them.

The recommended value for the prefix of the Local GRIP Database is ZZ BT GRIP Local and of the Remote GRIP

Database(s) is ZZ BT GRIP Remote (ZZ sequences the name down to the bottom of the alphab etically sorted list).

For example, a Remote GRIP database on the Domino Server DomNYHub/Servers/CompanyX would have the Mail -

In Database Name ZZ BT GRIP Remote domnyhub. Although the name of each GRIP database may be different, it is recommended to use the same value for the prefix of each Remote GRIP Database and simply distinguish Mail-In names by the common name of the Domino Server.

Processing of documents in each GRIP database is performed through a series of scheduled agents running on its

Domino Server. As part of the GRIP system deployment, these agents must be signed by the Domino Server on which each database resides and scheduled to run on a desired frequency. The Server-based Agent in each

Remote GRIP Database must be able to access Mail Files on Mail Servers that Database is configured to support.

Thus each Domino Server housing a Remote GRIP Database must be defined as a Trusted Server in the Server

Document for each Mail Server it supports. When setting the frequency for the scheduled agents, take into account the BTAddUserDelay and BTAddUserDelayMax parameters described in a later section to ensure that the maximum processing interval for BTCal is not exceeded due to the scheduling of agents.

7.5.3 GRIP – Get Repeating Invitation Pattern System Workflow

When BTCal encounters an invitation representing the process of adding an Exchange user to an existing Domino repeating meeting, it first checks whether its Calendar Cache (BTCache) already contains the original recurrence information from previously processed invitations. If the information is available, the GRIP system is not invoked.

If the information is not available, BTCal sets the invitation aside for future processing and creates a new document in the Local GRIP Database containing the invitation ApptUNID and Chair. A scheduled LotusScript

Agent (SendMeetingInquiry Sch) runs on a pre-defined schedule in the Local GRIP Database. The Agent processes such new documents, and from the available Domino Directories determines the Mail Server and the Mail File of the meeting Chair. It creates a mail item containing the invitation ApptUNID, Chair, Mail Server, and Mail F ile, and sends it to the Remote GRIP Mail -In Database configured for the Chair’s Mail Server.

When a new e-mail arrives in the Remote GRIP Database, it is queued for processing by a scheduled LotusScript

Agent (GetEntryInformation Sch) which runs on a pre-defined schedule in the Remote GRIP Database. The Agent processes new e-mail documents, opens the meeting Chair’s Mail File on the Mail Server, finds the original

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

38

Binary Tree Documentation invitation by ApptUNID, gathers all the information related to the original recurrence pattern, creates a mail item containing this information, and sends it to the Local GRIP Database.

When a new e-mail arrives in the Local GRIP Database, it is queued for processing by a scheduled LotusScript Agent

(CheckMeetingResponse Sch) which runs on a pre-defined schedule in the Local GRIP Database. The Agent processes new e-mail documents, finds the original document created in the Local GRIP Database by BTCal, copies all the recurrence information into it, and marks the information ready for BTCal.

BTCal periodically polls the Local GRIP Database to determine if a GRIP cycle has completed for any of the previously created documents, copies recurrence information into BTCache and processes a pending meeting invitation which adds Exchange users to a Domino repeating meeting. Any future Exchange users added to the same Domino meeting will no longer require a GRIP cycle.

7.5.4 GRIP – Get Repeating Invitation Pattern System Configuration

Configuration of the GRIP system is performed through a series of Settings documents in the Local GRIP Database.

A single settings document must be created to define the Local GRIP Database, a settings document must be defined for each Mail Server either explicitly by name or as a default one. If an explicitly defined setting s document is not found for a particular Mail Server, the default one will be used. If neither the explicit nor the default settings documents are present, an error message will occur. Settings documents are configured with the following parameters:

Mail Server Name:

The settings document for the Local GRIP Database must have the value “Local” in this field. The default settings document must have the value “Default” in this field. All other settings documents may have the full hierarchical name(s) of one or more Domino Mail Servers in this field; multiple values should be separated by commas or semi colons.

GRIP Database Server Name:

This field contains the Domino Server which houses the Remote GRIP database that services the Mail Server. The full hierarchical name of the GRIP Server must be entered; however, the field may also contain a reserved keyword, such as SameAsMailServer, which implies the same value as that of the Mail Server.

Mail-In DB Prefix:

This field contains the prefix of the Mail -In Database Name discussed above.

Server Domain:

This field contains the Mail Domain of the Mail Server. It must match the Mail Domain value defined in the Mail -In

DB document.

List of Domino Directories:

This field is only used in the “Local” settings document and contains the list of Domino Directories for all Domino

Domains in the environment. Each Domino Directory listed must have a replica on the Coexistence Domino Server and must be defined either as part of Directory Assistance or cascading directories on the Coexistence Domino

Server. For any settings document other than “Local”, this field may be left blank.

7.5.5 GRIP – Get Repeating Invitation Pattern System Deployment Alternatives

Depending on the topology of the Domino Environment, there may be multiple alternative approaches to deploying the GRIP system. The following scenarios outline possible GRIP system implementation approaches:

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

39

Binary Tree Documentation

1. Single Local and Remote GRIP databases.

This setup may be appropriate for a centralized Domino environment with a relatively small number of Domino

Servers located in the same data center. Both the Local and the Remote GRIP Databases reside on the Coexistence

Domino Server or the Remote GRIP Database resides on a designated Hub GRIP server. The Domino Server o n which the Remote GRIP Database resides must be defined in the list of Trusted Servers in the Security section of each Mail Server document.

2. Multiple Hub GRIP Servers.

This setup may be appropriate for a very large Domino environment with multiple Domino Server locations in different data centers. Each Remote GRIP database resides on a designated Hub GRIP server, which is defined in the list of Trusted Servers in the Security section of each Mail Server document it services. In this setup, a Setti ngs document exists for each Hub GRIP Server with the list of all Mail Servers in its scope defined as values in the Mail

Server field.

3. Each Mail Server is a GRIP Server.

This setup may be appropriate for a small to medium size distributed Domino enviro nment. Each Mail Server houses its own Remote GRIP database; thus, also becoming a GRIP Server. In this setup, only a Default settings document should exist with the value SameAsMailServer in the GRIP Server field.

Other scenarios are also possible, especially if the Domino environment consists of multiple Domino domains.

7.5.6 Add User Notes.ini Parameters

The following parameters need to be configured in the NOTES.INI file to implement the new feature in BTCal.

BTADDUSER

Accepted Value: Y/N

Default: N

This parameter accepts a value of Y or N. It specifies whether BTCal supports the ability for a Notes user to add an

Outlook user to an existing repeating meeting. This is the main switch for Add User processing. If this is set to N, and a request to add a user comes in, an NDR is returned.

BTADDUSERWITHEXCEPTIONS

Accepted Value: Y/N

Default: Y

This parameter accepts a value of Y or N. It specifies whether BTCal supports the ability for a Notes user to add an

Outlook user to an existing meeting that has exceptions (one or more occurrences in a series that have either been updated, rescheduled or canceled). If this is set to N and the meeting has exceptions, an NDR is returned.

BTADDUSEREXCEPTIONSMAX

Accepted Value: <number>

Default: 5

This parameter specifies the maximum number of exceptions allowed, and is only applicable if

BTADDUSERWITHEXCEPTIONS=Y. If the number of exceptions exceeds the value specified, an NDR is returned.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

40

Binary Tree Documentation

BTADDUSERDELAY

Accepted Value: <number>

Default: 0

This parameter specifies the number of seconds BTCal waits to receive all mail items pertaining to an add user request before processing the set of requests.

BTADDUSERDELAYMAX

Accepted Value: <number>

Default: 0

This parameter specifies the maximum number of seconds BTCal waits to receive the original invitation from the

GRIP database. If the invitation is not received before this is reached, an NDR is returned. A value of 0 is used to indicate there is no maximum.

BTADDUSERDB

Accepted Value: <database name>

Default: BTADDUSER.NSF

This parameter specifies the name of the Database that is used for processing requests for the original invitation. If

BTADDUSER = Y and this parameter is not specified in NOTES.INI, BTCal terminates.

7.5.7 New Cache Document Creation

When you add an Exchange user to a Notes meeting that is not already in the cache, a new cache document is created.

Additionally, when a single user is added, a new type of cache document is created called AddUserDoc. This document contains the ApptUNID|Address key, along with the original dates and current dates. In the Notes cache document, two new fields have been added:

 $BTAddUserSingle

 $BTAUList

$BTAddUserSingle is set to Yes if an Exchange user was added to a single occurrence of a repeating meeting.

$BTAddUserList contains a list of addresses for those users added to single occurrences.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

41

7.5.8 Data flow in the GRIP system

Receive Outbound Calendar Item from

Domino to Exchange

Is this the original invitation

No

No

Yes

Does

BTAddUser=Y?

Has

BTAddUserDelay timer expired?

Yes

Does event have exceptions?

No

No

Wait BTDelay number of seconds.

Yes

No

Does

BTAddUserWithExceptions=Y?

Yes

Do # of exceptions exceed

BTAddUserExceptionsMax

Yes

Send NDR

No

Yes

Yes

Is invitation in

BTCacheDB?

No

Create request document in

BTGRIPLocal DB

Yes

Response received from BTGRIPRemote

DB?

Yes

No

Wait BTDelay number of seconds

No Has

BTAddUserDelayMax

Timer expired?

Generate invitation

Generate Exceptions

Create AddUser documents in

BTCache DB

Create cache document in

BTCacheDB

Binary Tree Documentation

Put invitation in mail.box

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

42

Binary Tree Documentation

Section 8: Configuring Domino SMTP Routing

Depending on the namespace design chosen, there will be some differences in the configuration of Domino.

There are several documents to verify or configure on the Domino side:

 Foreign SMTP Domain Document

 Connection Document

 Server Documents

 Server Configuration Documents

As stated above, in a pure Exchange 2007, 2010, or 2013 environment, you no longer need

“domino.domain.com” for proper outbound routing from Exchange to Domino; therefore, it has been left out of this section. This is because the Exchange Send Connector looks internally first before sending to a smart host or utilizing an external DNS lookup.

8.1 Foreign SMTP Domain Document

Create a Foreign SMTP domain that will tell Domino that any mail addressed to a user @exch.contoso.com should route through this SMTP domain.

The Foreign SMTP Domain document describes specific routes to SMTP destinations domains in much the same way as SMTP Outbound Connectors do in Exchange server 2007 & 2010.

1. On the workstation, open the Lotus Administrator Client from the Start menu as illustrated below.

2. Connect to the server using the Admin client.

3. Select the Configuration tab in the Lotus Domino Administrator client. In this tab, expand Messaging setting in the left pane, and then select Domains as shown below. Click Add Domain.

4. The Foreign SMTP Domain document should show the following settings. o Domain type: Foreign SMTP Domain

5. Select the Routing tab. Fields should be filled in with the following information. o Internet Domain: exch.contoso.com (a subdomain should be listed here) as the Domino

Coexistence Server will be re-writing the outbound address for anyone in the foreign domain. o Routed to / Domain name: SMTPExchangeDirect. This is virtual domain used later in the connection documents for mail routing purposes .

6. Select Save & Close to create the Foreign SMTP Domain.

You should now see a new Foreign SMTP Domain document that will be used to route SMTP mail to the connection document that you will create in the next step.

8.2 Server Connection Document

Create a Domino connection document to route mail sent to SMTP domain created in the previous section.

Connection documents define message routing paths and methods, as well as replication topology. Since replication is not required, this option will be disabled.

1. In the Lotus Domino Administrator client, select the Configuration tab. Expand Messaging in the left pane, then select Connections. Click Add Connection.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

43

Binary Tree Documentation

2. The Connection document should show the following settings. o Connection type: SMTP o Source Server: The Domino Coexistence Server name. o If multiple Coexistence servers are desired for redundancy, Connection documents should be created for each of them. o SMTP MTA relay host: To avoid making changes when the IP address of the relay host changes, it is recommended that you enter the FQDN for the SMTP MTA relay host. In this case, specify the

Exchange Server name.

3. In the Replication/Routing tab, change Replication task to Disabled and Routing task to SMTP Mail

Routing as shown below.

4. In the Schedule tab, you need to enable a schedule, it is preferred that a longer time range is specified in the Connect at times field, such as 12:00 AM – 11:59 PM. If you use anything other than 12:00 AM –

11:59 PM, it will restrict mail transfer to less than 24 hours/day. Specify the repeat interval as 60.

5. Click Save & Close to save the document.

You have successfully created an SMTP routing path to Exchange.

8.3 Enable the SMTP Listener Task on a Domino Server

Enable the SMTP listener tasks to allow Exchange Bridgehead servers to connect to Domino for receiving mail.

Server documents contain significant information and configuration details (but not all configuration details) about a particular server. The document for incoming bridgeheads for mail from the Exchange server(s) must be updated to ensure that the server listens on SMTP.

1. Edit the Server document for the Domino Coexistence Server from the Lotus Administrator Client as outlined below. Click Edit Server.

2. Click the Routing tasks drop-down arrow.

3. On the prompt, select SMTP Mail Routing, and then click OK.

4. Click Save & Close.

You have made a change to the Domino Coexistence Server to listen for incoming SMTP requests and connections on port 25.

8.4 Create a Domino Server Configuration

Next, outline the steps needed to set up a Server Configuration document to handle SMTP traffic and secure connections.

Not all server configuration information is contained in server documents. A Server Configuration document contains additional parameters for a server or group of servers that outline how to handle SMTP messages and can help secure SMTP connections from anonymous relaying.

1. From the Lotus Domino Administrator Client, click the Configuration tab. Expand Server in the left pane, and select Configurations. o To verify an existing Server Configuration document, select the button in the middle pane called

Edit Configuration. o To create a new Server Configuration document if one does not exist, click Add Configuration.

2. Select the Server Configuration document, and then click Edit Configuration.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

44

Binary Tree Documentation

3. In the Basics tab, the configuration should take the defaults as shown below.

4. Select the Router/SMTP tab and then Basics. Make the following changes to the fields. This will ensure the SMTP is the standard protocol to and from the Domino Coexistence Server. o Number of mailboxes: 1 o SMTP Used when sending messages outside of the local internet domain: Enabled o SMTP allowed within the local internet domain: Disabled o Servers within the local Notes domain are reachable via SMTP over TCP/IP: Always o Address lookup: Full name then Local Part o Exhaustive lookup: Enabled

Multiple mailboxes are supported and should be based on internal Domino standards.

5. On the MIME tab, select Conversion Options and navigate to General and change Return receipts to

Enabled as shown below.

6. Finally, on the MIME tab, select Conversion Options -> Outbound. Next, navigate to the Outbound

Conversions Options section and change the message content to, From Notes to HTML.

7. Click Save & Close in the Configuration document to save your changes to the Server Configuration document.

8. Replicate servers’ address books from Domino console:

Replicate names.nsf

9. Restart the Domino Coexistence Server by typing Restart Server on the console.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

45

Binary Tree Documentation

Section 9: Configuring NOTES.INI

For all the configurable parameters that accept True/False, it is acceptable to specify 1 or Y for

True and 0 or N for False.

9.1 General Conventions

Notes Integration | CMT configuration is performed via Domino and Exchange configuration parameters as well as via the Coexistence Domino Server’s NOTES.INI file. The NOTES.INI file can be updated either by editing it manually or by issuing an appropriate set config command on the Domino Server’s Console. NOTES.INI file parameters are defined as pairs of the type Keyword=Value, where the total length of Keyword=Value string cannot exceed 256 characters.

9.2 Configuring Domino Directories

BTCal performs name resolution against the traditional Domino Server Directory Structure. If such structure consists of more than one directory, they must be defined via either Directory Cascading or Directory Assistance.

Cascaded Domino Directories are defined by names= parameter in Domino Coexistence Server NOTES.INI.

NAMES=names.nsf,morename.nsf,exchangenames.nsf

If Directory Assistance is used to represent multiple directories, refer to the Domino Server configuration documentation to configure Directory Assistance.

9.3 Configuring Domino Mail Routing to Exchange

BTEXCHANGEDOMAIN

Accepted Value: <domain name>

Default: Required

This parameter specifies the Foreign Domain associated with BTCal. It must match the Domain value in the Foreign

Domain Document set up in Domino Directory. This parameter must be specified; if it is not found, BTCal will terminate.

Using the example above, NOTES.INI would be configured as follows:

BTEXCHANGEDOMAIN=Exchange

The value of this parameter should be similar to the value of the Notes Domain to enhance the transparency of transitioning users from Domino to Exchange.

BTALTEXCHANGEDOMAINS

Accepted Value: <comma-separated domain names>

Default: None

This parameter specifies additional (alternate) Foreign Domains associated with BTCal. This parameter is option al, and if specified, the value(s) must match the Domain value in the Foreign Domain Document(s) set up in Domino

Directory.

Using the example above, NOTES.INI would be configured as follows:

BTALTEXCHANGEDOMAINs=Exchange-1

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

46

Binary Tree Documentation

If the recipient address does not contain a domain specified by either BTEXCHANGEDOMAIN or BTALTEXCHANGEDOMAINS, then a Non-Delivery Report (NDR) is returned to the originator.

BTEXCHANGEDB

Accepted Value: <mailbox name>

Default: Required

This parameter specifies the Foreign Domain mailbox associated with BTCal. It must match the Gateway Mail File

Name on the Mail Information tab and Calendar System on the Calendar Information tab in the Foreign Domain

Document set up in Domino Directory. This parameter must be specified; if it is not found, BTCal will terminate.

The BTEXCHANGEDB database must be created on the Domino Coexistence Server using the Mail Router template.

The Domino Server must have Manager Access to this database; it is recommended that the Default access be set as Manager.

Using the example above, NOTES.INI would be configured as follows:

BTEXCHANGEDB=otherexchange.box

BTEXCHANGEROUTER

Accepted Value: BTExchange.box

Default: Required

This parameter is intended for Exchange 2003 Lotus Domino connectors. Foreign Domai n mailbox associated with

Notes Connector; must match the Connector mailbox set up in the General tab of the Notes Connector configuration.

The parameter value should be specified as ‘BTExchange.box’.

BTRECIPCONVERTFIELD

Accepted Value: shortname/internetaddress-local/internetaddress-full

Default: shortname

This parameter defines which Domino Directory field is used for generating SMTP address for recipients of mail items from Domino to Exchange. Based on the value of the field, the SMTP address for eac h recipient is generated as follows:

Each Recipient value is matched against all Domino Directories defined by Directory Cascading or Directory

Assistance. If a unique match is not found, an NDR is generated and sent to the originator.

If the value of the BTRECIPCONVERTFIELD parameter is shortname or the field is not present in NOTES.INI, the first value of the ShortName field of the matched Domino Directory Entry is used. If the value represents a valid SMTP address, then it will be used as the new recipient value; otherwise, the value will be appended with "@" +

<BTEXCHANGESERVER> (see below).

If the value of the BTRECIPCONVERTFIELD parameter is internetaddress -local, the value of the InternetAddress field of the matched Domino Directory Entry is used. The string to the left of the “@” sign will be appended with

"@" + <BTEXCHANGESERVER>.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

47

Binary Tree Documentation

If the value of the BTRECIPCONVERTFIELD parameter is internetaddress -full, the value of the InternetAddress field of the matched Domino Directory Entry is used as the new recipient value.

If the value of the field is internetaddress -full or internetaddress-local and InternetAddress is blank, it is treated as an invalid recipient address.

The internet address-full option must be used very carefully due to possible looping dangers.

This option is only practical when the SMTP domain(s) of the Domino environment are different from that of the Exchange environment.

BTEXCHANGESERVER

Accepted Value: <SMTP address>

Default: Required

This parameter specifies the value in the Foreign SMTP Domain document and Connection Document defined in the Domino Directory.

The first token in the route cannot match the Foreign Domain value defined above.

Using the example above, NOTES.INI would be configured as follows:

BTEXCHANGESERVER=exchange1.binarytree.com

BTPROCESSDOMAIN

Accepted Value: <SMTP address1, SMTP address2,……,SMTP address15>

Default: Required

OR

BTPROCESSDOMAIN1

Accepted Value: <SMTP address1, SMTP address2,……,SMTP address15>

BTPROCESSDOMAIN2

Accepted Value: <SMTP address1, SMTP address2,……,SMTP address15>

This parameter contains a list of SMTP domains representing true Internet addresses of Exchange users as well as direct SMTP routes from Exchange to Domino and from Domino to Exchange. This is the only parameter used by

BTEx module to determine whether to translate the From:, To:, Cc:, or Bcc: values from SMTP to Lotus Notes format for e-mails from Exchange to Domino. It is important to ask the customer about all the domain na mes being used in their environment and ensure that those names are listed in this field. Issues with names not being properly converted from SMTP format are most likely due to a domain not being listed in this parameter.

 BTPROCESSDOMAIN, without a trailing number, can be used for a single line of domains. o Only 15 domains are supported using this method o Each line in the NOTES.INI file is limited to 216 characters.

 Multiple BTPROCESSDOMAINx lines can be defined (i.e. BTPROCESSDOMAIN1=…

BTPROCESSDOMAIN2=…): o If more than 15 domains are required or; o If all 15 domains cannot fit on a single 216 character line. o The trailing numbers must be sequential.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

48

o Each line, except for the last, must end in a comma. o The * character can be used to start a domain (example: *.contoso.com)

BTNOTESDOMAINS

Accepted Value: <comma separated domain names>

Binary Tree Documentation

Default: Required

This parameter can only be used when configuring BTCal against the Microsoft Exchange 2003 Notes Connector and represents the list of Notes Domains whose mail must be routed via Microsoft Exchange 2003 Notes

Connector. This type of routing is a highly specific requirement and is normally not used. This is a multi -valued field with values separated by commas. When not used, the value must be set to _ (underscore).

BTLINKSOPTION

Accepted Value: 0/1

Default: 0

This parameter can only be used when configuring BTCal against the Microsoft Exchange 2003 Notes Connector and determines whether e-mails from Domino to Exchange containing document links will be processed by BTCal or the Microsoft Exchange 2003 Notes Connector. A value of 0 specifies the processing will be done by BTCal; a value of 1 specifies the processing will be done by the Microsoft Exchange 2003 Notes Connector. Routing of links via the Microsoft Exchange 2003 Notes Connector is a highly specific requirement and is normally not used. The recommended value is 0.

BTAPPTREROUTE

Accepted Value: 0/1

Default: 1

This parameter can only be used when configuring BTCal against the Microsoft Exchange 2003 Notes Connector and determines whether calendar entries from Domino to Exchange containing non -text attachments will be processed by BTCal or the Microsoft Exchange 2003 Notes Connector. A value of 0 specifies the processing will be done by the Microsoft Exchange 2003 Notes Connector; a value of 1 specifies the processing will be done by BTCal.

Routing of calendar items via the Microsoft Exchange 2003 Notes Connector is a highly specific requirement and is normally not used. The recommended value is 1.

BTDELAY

Accepted Value: <number>

Default: 60

This parameter specifies the interval in seconds for processing Domino to Exchange messages. The recommended value is 15. The value can be set higher than 30, but any value lower than 10 will be interpreted as 10.

BTORPHANDELAY

Accepted Value: <number>

Default: 300

This parameter specifies the interval in seconds for processing orphaned messages (i.e., Exchange to Domino messages marked dead by BTEx) but not processed immediately by BTCal (for a number of possible reasons). The recommended value is 120. If the provided value is less than 60, it will be reset to 60.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

49

Binary Tree Documentation

BTCALRESTARTTIMER

Accepted Value: <number>

Default: 0 (no restart)

This parameter indicates that the BTCal server task should restart itself every <number> minutes. Task restart may be useful to ensure that all memory segments used by a task are properly released. Recommended values for the restart interval are between 60 and 720, representing a task restart between every hour and twice a day. There is no performance impact on BTCal due to a periodic restart.

For this Restart Timer to work correctly, the name of the file associated with BTCal must be nBTCal.exe. If you rename it to anything else, the Restart Timer will cycle every 5 seconds attempting to restart the task.

BTRETRYLIMIT

Accepted Value: <number>

Default: 10

This parameter is used when inbound and outbound mail items need to be processed. When processing inbound and outbound mail items, this parameter prevents a bad message from continuously crashing BTCAL or clogging the mail flow by specifying the maximum number of times BTCAL can process the same message.

BTRETRYSENDNDR

Accepted Value: 0/1

Default: 0

If BTCal has exceeded the retry limit while processing a specific mail item, this parameter specifies whether or not an NDR will be sent to the originator of the mail item. If the parameter is set to 1, an NDR is sent, and if it is set to

0, an NDR is not sent.

BTRETRYLIMITTEXTx

Accepted Value: <text>

Default: None

This parameter defines the text of the retry limit notification. There can be any number of lines of text; however, the lines must be sequentially numbered starting with 1 and the text of each line cannot exceed 216 characters.

When the notice text is created, the contents of lines are scanned as a s ingle string with no implied line ends. Line ends are defined by the string \n in the text of any line. The string “\t” defines a tab.

Because NOTES.INI parameters cannot have leading or trailing spaces, each

BTRETRYLIMITTEXTx line must begin and end with a non-blank character.

For example:

 BTRETRYLIMITTEXT1=Dear User\n\n\tYour message or calendar entry cannot be delivered to its intended recipient

 BTRETRYLIMITTEXT 2=s.\n\nPlease contact your e-mail administrator for further assistance.

Translates as follows:

Dear User

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

50

Binary Tree Documentation

Your message or calendar entry cannot be delivered to its intended recipients.

Please contact your e-mail administrator for further assistance.

BTBCCSKIPADDRESS

Accepted Value: <SMTP address>

Default: None

This parameter allows BTCal to coexist with an archiving solution – Ascentor – implemented using a similar approach and architecture in message processing as BTCal.

Ascentor marks every message with fields $Processed and $ProcessedID to indicate that it h as already processed the message and adds a Bcc SMTP recipient to force a copy of a message to be directed to a specific mailbox via the SMTP address. Without this parameter, BTCal will stop processing an item if it encounters fields $Processed and $ProcessedID. With this parameter defined, BTCal will check if an item with fields $Processed and

$ProcessedID has a Bcc recipient whose address matches the value specified in the configuration. If such a recipient is found, BTCal will continue processing the item assuming that it has the fields $Processed and

$ProcessedID because of prior processing by Ascentor. If such a recipient is not found, BTCal will stop processing the item assuming that it has the fields $Processed and $ProcessedID because of prior proces sing by BTCal.

BTSUPPORTMULTIPLEDOMINODOMAINS

Accepted Value: 0/1

Default: 0

When processing a mail item from Domino to Exchange, BTCal typically removes the FromDomain field from the mail item. If there are multiple Domino Domains, this can cause problems processing replies from Exchange to

Notes originally sent from downstream Domains. This parameter specifies whether BTCal should process the

FromDomain field to avoid this issue. If BTSUPPORTMULTIPLEDOMINODOMAINS is set to 1, BTCal will examine the

FromDomain and determine if the value contains "@" signs. If it does, the FromDomain value is replaced with the value to the left of the first @ sign. If it does not, the FromDomain field is left alone.

BTWORKDIRECTORY

Accepted Value: <Windows path name>

Default: Windows temp directory

This parameter defines the directory to which temporary work files used by BTCal will be written. It expects a properly formatted windows path name (e.g., c:\CMTc\work). If the specified directory does not exist, BTCal will attempt to create the directory. If this directory cannot be found or created, or if this parameter is not specified, work files will be written to the Windows temp directory.

BTTRUNCATESUBJECT

Accepted Value: Y/N

Default: N

The parameter accepts a value of Y and N. When set to Y, BTCal truncates the subjects of all messages sent from

Notes to Exchange at 255 characters if the subject length is greater than 255 characters. There are times when

Outlook will not correctly handle messages whose Subject is grea ter than 2K, so this parameter can be used to avoid these issues.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

51

Binary Tree Documentation

BTEXPANDCALGROUPS

Accepted Value: Y/N

Default: N

This parameter accepts a value of Y or N. If BTEPANDCALGROUPS is set to Y, the recipient list on inbound calendar mail items will be checked and expanded if it contains a Domino group name; otherwise, the group name will be passed in untouched.

If you have Domino group names that contain Exchange users, BTEXPANDCALGROUPS should be set to Y. This will ensure that inbound calendar mail items a re correctly processed by BTCal for any Exchange recipients. If you do not have Domino groups, or your Domino groups do not contain any Exchange users, you should set this parameter to N.

BTEXPANDMAILGROUPS

Accepted Value: Y/N

Default: N

This parameter accepts a value of Y or N. If BTEXPANDMAILGROUPS is set to Y, the recipient list on inbound non calendar mail items will be checked and expanded if it contains a Domino group name; otherwise, the group name will be passed in untouched. There is no recommended setting for this parameter.

BTEXPANDGROUPS

Accepted Value: Y/N

Default: N

This parameter accepts a value of Y or N. If an Outlook user sends an invitation to a group defined in Domino that contains Exchange users, the group name must be expanded by BTCal for calendar processing to work correctly. If you are using Domino groups that contain Exchange users, you should set this parameter to Y; otherwise, this parameter will be ignored.

 Notes Integration | CMT now expands nested groups.

 If there is an error in expanding groups (e.g., the expanded group would exceed 64K), an

NDR is returned to the Outlook user.

 There is a 64k limit on expanded Distribution Lists (nested groups) imposed by Domino.

 BTEXPANDGROUPS has been deprecated in Release 3.1 and is superseded by the two new parameters: BTEXPANDCALGRO UPS and BTEXPANDMAILGROUPS. The settings of these new parameters override the setting of BTEXPANDGROUPS if it is found in your

NOTES.INI file. We recommended that you delete BTEXPANDGROUPS from your

NOTES.INI file if it was previously configured.

BTEXPANDGROUPSDOMAIN

Accepted Value: <string>

Default: None

There are times when the domain name defined for Domino groups in Exchange may be different from the domain name defined for associated groups in Domino. For example, the SMTP address in Exchange may be

[email protected], but the Internet address in the NAB could be [email protected].

BTEXPANDGROUPSDOMAIN takes a string-value, and is configured with the domain name that wil l be used for matching the groups. For example, set BTEXPANDGROUPSDOMAIN to notes.com in the above scenario.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

52

Binary Tree Documentation

BTCal will first try to find a match using [email protected]. If it is not found, and

BTEXPANDGROUPSDOMAIN is defined, BTCal would replace the domain name and try to match it with

[email protected] and will succeed.

BTEXPANDGROUPSDOMAIN only supports one domain.

BTFORCELOCATIONRESOLUTION

Accepted Value: 0/1

Default: 0

When enabled (parameter set to 1), BTCal will look at each attendee in the Exchange ICAL stream and attempt to resolve it to a Domino room/resource. If the attendee is found to be a Domino room/resource, the display name will be added to the LOCATION value in the ICAL. This allows BTCAL and Domino to recognize the room/res ource properly so that cancellations and updates are properly applied. This should be enabled for Exchange 2013 or higher. Exchange 2007 and 2010 handle this correctly already.

BTSENDEXPANDED

Accepted Value: Y/N

Default: Y

This parameter accepts a value of Y or N, and is only used if BTEXPANDCALGROUPS=Y. When set to Y, BTCal will send reschedule/cancellation notices to Exchange users after expanding the group. If the messages are sent, this will result in duplicate e-mails for Exchange users. If the messages are not sent, you run the risk of Exchange users not receiving reschedule/cancellation notices if they have not yet accepted the original invitation. Note that the original invitation is always sent to Exchange users, regardless of the setting of this pa rameter.

The setting of BTEXPANDMAILGROUPS has no effect on this parameter.

BTCHECKINTERNALSMTP

Accepted Value: 0/1

Default: 0 and

BTINTERNALSMTPDOMAIN

Accepted Value: <SMTP domain1,SMTP domain2>

Default: none

This parameter allows an Office 365 customer, who is gradually transitioning users from Domino to Office 365, to process all inbound external mail originating from Office 365, while letting other externally originated mail flow through untouched.

BTCHECKINTERNALSMTP accepts a value of 0/1, with the default being 0. To enable Office 365 compatibility, you should set BTCheckInternalSMTP=1.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

53

Binary Tree Documentation

BTInternalSMTPDomain accepts a comma separated list of SMTP domains, with no default. If Office 365 compatibility is enabled (i.e., BTCheckInternalSMTP=1), BTEx will compare the originator address of all inbound mail items against the list of configured internal SMTP domains. If a match is not found, the mail item is passed through unchanged. This also means that no address translation is done.

BTCONVERTPNG

Accepted Value: 0/1

Default: 0

BTCONVERTPNG accepts a value of 0/1, with the default being 0. When the parameter is set to 0, inline PNG images are not looked for and the BTPNG field is not set for BTCal if PNG images are found. When it is set to 1, PNG images are looked for and BTPNG fi eld is set if images are found.

BTCONVERTPROPOSE

Accepted Value: 0/1

Default: 0

For on-prem installations only. Not for use for hybrid or O365 deployments.

The BTCONVERTPROPOSE parameter can be used to prevent the message, which is sent by a Notes user to propose a new time for a meeting that originated in Outlook, from always converting to a text message. The parameter allows BTCal to either convert the message to a text message or let i t flow through as a counter proposal.

BTCONVERTPROPOSE accepts a value of 0/1, with the default being 0. When the parameter is set to 0, proposals for SINGLE meetings will be sent to Outlook as calendar counter proposals. When it is set to 1, proposals wil l be converted to text messages.

 Proposals for entire series are ALWAYS converted to text messages, regardless of the setting of BTCONVERTPROPOSE. In addition, regardless of the setting of

BTCONVERTPROPOSE, BTCal will insert text in the mail item that wi ll be displayed by

Outlook to the Outlook user. This text will specify the original date/time of the meeting, and the proposed date/time.

 When an Outlook invitee declines a meeting request that originated in Notes and proposes a new date/time for the meeti ng, then message received by the Notes user comes as a counter proposal. If the Notes user declines it, the Notes message is changed to a Meeting Confirmation (NoticeType=N) and the subject is prefixed with Counter

Proposal Declined and sent to the Outlook user.

 Counter proposals from Notes users to O365 chairs are not supported.

BTOUTMESSAGEMAX

Accepted Value: 0/<any number greater than 0>

Default: 100

And

BTINMESSAGEMAX

Accepted Value: 0/<any number greater than 0>

Default: 100

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

54

Binary Tree Documentation

BTOUTMESSAGEMAX and BTINMESSAGEMAX allow you to specify the maximum number of messages that you want BTCal to process in a mailbox before i t switches to the next mailbox.

 The BTOUTMESSAGEMAX parameter defines the maximum number of messages that should be processed from the mailboxes defined in BTEXCHANGEDB for Outbound SMTP traffic to Exchange.

 The BTINMESSAGEMAX parameter defines the maximum number of messages that should be processed from the mail.boxes (mail1.box, mail2.box, etc.) for Inbound SMTP traffic to Notes/Domino.

The default for both parameters is 100, and when you specify zero (0) for either of the parameters, this indicates to BTCal that there is no maximum limit specified and it should process all of the messages in the mailbox before switching to another mailbox.

BTONLINEMEETINGLABEL

Accepted Value: <text>

Default: None

If an online meeting invitation is being sent from Notes to Outlook, and it contains an APPTUNIDURL, the

BTOnlineMeetingLabel parameter can be configured to add the specified label and URL in fro nt of the body of the notice.

It can be used as BTOnlineMeetingLabel1 and BTOnlineMeetingLabel2 and has a maximum size of 8K characters.

BTNOTIFYONDELEGATEORCOUNTER

Accepted Value: 0/1

Default: 0

When enabled (parameter set to 1), BTCal will send the fol lowing NDR’s when the Prevent Delegation or the

Prevent Counter-Proposals is enabled:

 Prevent Delegation enabled - BTNDR43 =”This meeting has “Prevent delegating” enabled. This functionality is not supported for Outlook participants.”

 Prevent Counter-Proposals enabled - BTNDR44=”This meeting has “Prevent counter-proposing” enabled.

This functionality is not supported for Outlook participants.”

 Prevent Delegation enabled and Prevent Counter-Proposals enabled - BTNDR45=”This meeting has

“Prevent delegating” and “Prevent counter-proposing” enabled. This functionality is not supported for

Outlook participants.”

 Default text for the notify body - BTNDR46="Dear User,\r\n\r\nWhile this invitation will be delivered, it contains functionality not supported between Notes and Outlook:\r\n\r\n\t%REASON%\r\n\r\n***Your invitation information:\r\n\tSubject: %SUBJECT%\r\n\tLocation: %LOCATION%\r\n\tDate:

%DATE%\r\n\r\nThe affected recipient(s):\r\n%RECIPIENTS%"

Please refer to Appendix H: Cross Platform Delegation to determine which option is appropriate for your environment and user community.

BTSUBJECTPREFIXMARKER

Accepted Value: markers separated by a comma.

Default: none (disabled by default)

When Notes sends meeting-related messages to Outlook, it prepends various strings to the meeting title, making the actual meeting title difficult to view on mobile device calendar views. This parameter allows for prepended text such as "Updated: " and "Rescheduled: " to be removed by looking for the pattern at the end of the prepended text (the marker). Removing the prepended text allows users to more easily see meeting titles on mobile device calendar views. When a meeting title with prepended text contains one of the markers from the list,

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

55

Binary Tree Documentation all the text preceding the marker and the marker itself will be removed from the meeting title.

 Use a trailing comma to avoid Notes stripping trailing spaces from the marker. For example,

BTSubjectPrefixMarker=: , means BTCal will look for the string ": " in the meeting title.

 Commas as part of a marker can be escaped with a backslash (\,).

 Backslashes as part of a marker can be doubled (\\).

 Characters with diacritics (é, ü, etc.) are supported, but NOTES.INI must be in UTF-8 format (as it is by default)

BTSUBJECTPREFIXEXCL USION

Accepted Value: prefixes separated by a comma.

Default: none (disabled by default)

Note, this parameter modifies the behavior of BTSUBJECTPREFIXMARKER and is only valid if

BTSUBJECTPREFIXMARKER is set.

This parameter allows certain prefixes to be retained in meeting titles for messages sent from Notes and received by Outlook. When a meeting title with prepended text starts with one of the prefixes from the list, the full meeting title is left intact.

 Use a trailing comma to avoid Notes stripping trailing spaces from the marker. For example,

BTSubjectPrefixExclusion=Résiliation: , means BTCal will look for the prefix "Résiliation: " in the meeting title.

 Commas as part of a prefix can be escaped with a backslash (\,).

 Backslashes as part of a prefix can be doubled (\\).

 Characters with diacritics (é, ü, etc.) are supported, but NOTES.INI must be in UTF-8 format (as it is by default).

The BTSUBJECTPREFIXEXCLUSION parameter supports multiple lines. If the total list of prefixes is larger than 255 characters, it can be separated across multiple BTSUBJECTPREFIXEXCLUSIONx variables. Any number of sequentially numbered BTSUBJECTPREFIXEXCLUSIONx prefixes can be defined, starting with

BTSUBJECTPREFIXEXCLUSION1.

The following example illustrates two alternatives of defining prefixes:

BTSUBJECTPREFIXEXCLUSION=Cancelled: ,Cancelado: ,Résiliation: ,Suspender: ,

Or

BTSUBJECTPREFIXEXCLUSION1=Cancelled: ,Cancelado: ,

BTSUBJECTPREFIXEXCLUSION2=Résiliation: ,Suspender: ,

BTSUBJECTPREFIXFILTERING

Accepted Value: Y/N.

Default: N (disabled by default)

With filtering disabled (BTSUBJECTPREFIXFILTERING=N), all messages from Notes to Outlook are processed if

BTSUBJECTPREFIXMARKER is set. With filtering on (BTSUBJECTPREFIXFILTERI NG=Y), only meeting notices from

Lotus Notes to Outlook that are initiated by the chairperson or someone representing the chairperson are processed if BTSUBJECTPREFIXMARKER is set.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

56

Binary Tree Documentation

9.4 Handling Attachments between Domino and Exchange

Due to certain differences in processing MIME-encoded attachments by Domino and Exchange, the following

Domino Server configuration variable is required:

MIMEFORCEATTACHMENTS=1

Although not specifically used by BTCal, this parameter must be set for the Domino Server to process outbound mail items with attachments properly.

BTINATTOPT

Accepted Value: 0/1

Default: 0

When Domino SMTP translates e-mails sent from Exchange to Domino into Notes documents, MIME-encoded attachments and embedded objects are represented by $FILE items. Due to certain limitations of Lotus Notes

Clients prior to versions 6.x, some attachments are not properly displayed for the eventual recipients of e-mails. To ensure that $FILE items are properly displayed, BTCal detaches and re-attaches each $FILE object and, if necessary, performs additional processing of these items. This parameter specifies whether and what type of additional processing is performed by BTCal.

When BTINATTOPT is set to 0, BTCal performs no additional processing. This value should always be used for environments where all Notes Client versions are 6.x or higher.

When BTINATTOPT is set to 1, BTCal performs name-based and host-based processing of $FILE items. A value of 1 should only be used for environments where some Notes Client versions are 5.x or lower. Additional processing of

$FILE item is performed according to the following rules:

If the HOST value of the original $FILE item is not STREAM (2304), the HOST value of the re-attached $FILE object will be left unchanged.

If the HOST value of the original $FILE item is STREAM and the File Name of the $FILE item matches a pattern defined by the BTINATTSKIPNAMES parameter, the HOST value of the re-attached $FILE object will be left unchanged.

If the HOST value of the original $FILE item is STREAM and the File Name of the $FILE item does not match a pattern defined by the BTINATTSKIPNAMES parameter, the HOST value of the re-attached $FILE object will be replaced with value of UNKNOWN. This results in $FILE element always being displayed as an attachment (even if the $FILE element represents an embedded image).

BTINATTSKIPNAMES

Accepted Value: <comma separated filename patterns>

Default: None

This parameter specifies a multi -valued field with values separated by commas that represent various fil e name patterns, against which File Name values of $FILE items may be compared (see rules defined above). The following syntax rules should be used when constructing values for this parameter:

(asterisk) represents string of any length or value.

# (number sign) represents a single digit.

*<string> matches a file name of any length ending in <string> (case and extension insensitive). For example, file name test document.doc matches value *document.

<string>* matches a file name of any length starting with <string> (case and extension insensitive). For example,

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

57

Binary Tree Documentation file name test document.doc matches value test*.

<string>### matches a file name starting with <string> followed by 3 digits (case and extensi on insensitive). For example, file name image123.bmp matches value image###; however, file names image1x3.bmp or image12.jpg do not match value image###.

The recommended value is image###, since embedded images in Outlook are given “virtual file names of imageNNN.<extension>. For example, image001.bmp, image002.jpg, image003.tif.

BTBLOCKCANCELNOCACHE

Accepted Value: Y/N

Default: Y

This parameter determines what happens when a meeting chaired in Notes and sent to an Outlook user is cancelled and there is no cache document which results in no NDR and no cancellation notice by default. If the

BTBlockCancelNoCache parameter is set to "Y", "Cancel Single Occurrence" will not be delivered. If the

BTBlockCancelNoCache parameter is set to "N", the cancel will be delivered. "Cancel All Occurrences" is needed for the chair to cancel and recreate the meeting and will be delivered regardless of the BTBlockCancelNoCache parameter setting.

BTPRESERVEATTACHMENTS

Accepted Value: 0/1

Default: 1

This parameter preserves the attachments added during an update of a Notes repeating meeting sent to Outlook attendees. When enabled (parameter set to 1), BTCal will not remove the attachments added during an update to a repeating meeting in Notes and sent to Outlook attendees. This pa rameter resolved a defect that was incorrectly removing attachments during meeting updates, and should always be enabled. It is Binary Tree's practice to use ini parameters to correct this type of issue to protect the previous behavior in the event an exis ting deployment is dependant on it.

9.5 Processing Meetings between Exchange and Domino

BTKEEPPOSTED

Accepted Value: Y/N

Default: Y

If BTKEEPPOSTED is set to Y or if it is not present in the NOTES.INI file, BTCal inserts the KeepPosted text field in the meeting response. If the KeepPosted text field is present in the decline response you sent to a meeting, and the meeting is updated, Domino will send you the update even though you declined the original invitation. This may be useful in the case where an Exchange user could not attend the meeting at its originally scheduled time but can attend at the rescheduled time. Also, if the meeting is canceled, the cancellation notice is sent to the Exchange user if KeepPosted is set.

If BTKEEPPOSTED=N, this text field is not added to the meeting response.

BTCHECKRECIPIEN TS

Accepted Value: Y/N

Default: N

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

58

Binary Tree Documentation

If BTCHECKRECIPIENTS is set to Y, BTCal searches the recipient list of all inbound calendar mail items for any

Exchange users. If Exchange users are found, the original mail item is copied to a new mail item. The Exchange users are copied to the new mail item and then removed from the original mail item.

If BTCHECKRECIPIENTS = N, the recipient list is not searched for Exchange recipients.

This process can be time consuming, depending on the size of the recipient list. Therefore, this parameter should only be enabled if BTCal is receiving inbound mail items that contain

Exchange addresses.

9.6 Processing Repeating Meetings between Exchange and Domino

Due to significant differences in handling repeating/recurring meetings from invitations to reschedules and updates and to cancellations by Exchange and Domino, BTCal examines such items and determines whether the opposite environment can properly handle them. If a scheduling or a rescheduling action is improperly handled, an appropriate notification is issued based on parameter values defined further in the document.

For the detailed documentation on handling various types and functions of rep eating/recurring meetings by BTCal, please refer to Appendix E.

BTCACHEDB

Accepted Value: <database name>

Default: btcache.nsf

This parameter defines the database that will be used to store data required for proper processing of repeating/recurring meetings by BTCal. The database must be stored in the Domino Coexistence Server Data

Directory and built from the default database received as part of the Notes Integration | CMT Installation package.

BTRECURRENCELIMIT

Accepted Value: <number>

Default: 1200

With the limit being around 1200, there is an issue with the actual number of recurrence dates that Notes will accept. To avoid issues in Notes after a calendar invitation from Exchange is delivered to Domino,

BTRECURRENCELIMIT should be us ed to specify the maximum number of recurrence dates that should process be processed. If this number is exceeded, an NDR is sent to the originator.

BTMULTISCHEDREPORTLEVEL

Accepted Value: 1/2/4

Default: 1

This parameter determines whether the notice of a n inappropriate action is sent by BTCal.

1 – an error report is sent back just to the originator of the meeting

2 – an error report is sent back to the originator and specified administrator address, which can be a group

4 – checking the validity of invitations or reschedules is disabled. (not recommended)

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

59

Binary Tree Documentation

BTMULTISCHEDREPORTADDRESS

Accepted Value: <SMTP address>

Default: None

This parameter defines the value of an additional address to which notification of an inappropriate recurring meeting action is sent. The SMTP address [email protected] is an example of the value that can be assigned to the parameter. This address can also be a group.

This parameter is only needed if BTMULTISCHEDREPORTLEVEL is set to 2.

BTMULTISCHEDREPORTADDRESSTYPE

Accepted Value: 0/1/2

Default: 0

This parameter allows the user to specify whether the configured BTMULTISCHEDREPORTADDRESS should be placed in the To, CC, or BCC field when sending a mail notification. Acceptable values are 0 (To), 1 (CC) and 2 (BCC), with the default being 0. If the parameter is not included in the NOTES.INI file or contains an unacceptable value then the address will appear in the To field a s that is the default behavior.

BTMULTISCHEDREPORTTEXTx

Accepted Value: <text>

Default: Dear User,

The calendar pattern used in the invitation you sent is not supported at this time for the following reason:

%REASON%

Please reschedule using another pattern!

Original invitation information:

Subject: %SUBJECT%

Date: %DATE%

Notes Integration | CMT allows the user to customize the NDR returned for invalid calendar items. The

BTMULTISCHEDREPORTTEXTx parameter defines the text of the notice of the inappropriate action. Customization is based on the text configured for this parameter. There can be a ny number of lines of text; however, the lines must be sequentially numbered starting with 1 and the text of each line cannot exceed 216 characters. When the notice text is created, the contents of the lines are scanned as a single string with no implied l ine ends. Line ends are defined by the string “\n” in the text of any line. The string “\t” defines a tab.

Because NOTES.INI parameters cannot have leading or trailing spaces, each

BTMULTISCHEDREPORTTEXTx line must begin and end with a non-blank character.

For example, you can specify the BTMULTISCHEDREPORTTEXTx parameter as follows to create a customized message for the NDR when a calendar pattern is rejected.

BTMULTISCHEDREPORTTEXT1 =Dear User\n\nThe calendar pattern used in invitation you sent is not supported at this time\n

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

60

Binary Tree Documentation

BTMULTISCHEDREPORTTEXT2 =for the following reason:\n%REASON%\n

BTMULTISCHEDREPORTTEXT3 =Please reschedule using another pattern!\n\n

BTMULTISCHEDREPORTTEXT4 =***Your invitation information:\n

BTMULTISCHEDREPORTTEXT5 =Subject: %SUBJECT%\n

BTMULTISCHEDREPORTTEXT6 =Location: %LOCATION%\n

BTMULTISCHEDREPORTTEXT7 =Time: %DATE%\n

BTMULTISCHEDREPORTTEXT8 =Chair: %CHAIRPERSON%\n

BTMULTISCHEDREPORTTEXT9 =The invitation was not sent to the following user(s):\n%RECIPIENTS%

It will translate as:

The calendar pattern used in invitation you sent is not supported at this time for the following reason:

<Reason>

Please reschedule using another pattern!

***Your invitation information:

Subject: <SUBJECT>

Location: <LOCATION>

Time: <DATE>

Chair: <CHAIRPERSON>

The invitation was not sent to the following user(s):<RECIPIENTS>

3.

4.

5.

6.

There are six keywords that can be placed anywhere in the configured text to supply additional information specific to the non-delivery report. Note that the keywords are not case-sensitive, but they MUST be enclosed in percent signs.

1.

2.

%REASON% - Displays a textual reason why Notes Integration | CMT is rejecting the calendar event and returning a non-delivery notification. See Appendix G for a complete list of the r easons for a failure as well as the cause of the failure.

%DATE% - Displays the start date of the meeting notice in the long form, such as Monday, March 8, 2010.

%SUBJECT% - Subject specified in calendar event.

%LOCATION% - Location specified in the calendar event.

%CHAIRPERSON% - Chairperson specified in the calendar event.

%RECIPIENTS% - Comma-separated list of foreign recipients of the calendar event. For messages originating in Outlook, this keyword would refer to Notes users. For messages originating in Notes, this keyword would refer to Outlook users.

The rejection notices for unsupported meeting patterns originating in Notes display the

Chairperson and Foreign Recipient addresses in full canonical format.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

61

Binary Tree Documentation

If the BTMULTISCHEDREPORTTEXTx parameter is not set in the NOTES.INI file, then the default message that appears when a calendar pattern is rejected is:

Dear User,

The calendar pattern used in the invitation you sent is not supported at this time for the following reason:

%REASON%

Please reschedule using another pattern!

Original invitation information:

Subject: %SUBJECT%

Date: %DATE%

BTNDRFROMADDRESS

Accepted Value: <email address> or <common name>

Default: None

When an email address is provided for this parameter, the From field of all NDR’s will be set to the email address.

This parameter will accept an SMTP name or a common name. If there is no value, the NDR will app ear to come from the recipient.

BTNONDRONQUIT

Accepted Value: 0/1

Default: 0

This parameter specifies whether or not BTCal wil l send an NDR if it is in the middle of processing a mail item when the QUIT command is issued from the console. If BTNONDRONQUIT is set to 0, an NDR will not be sent; otherwise, an NDR will be generated and sent to the originator.

BTPARTIALTEXT

Accepted Value: <text>

Default: Room/Resource is already booked for the following date(s). You must use another time or find another

resource.

When an Exchange user attempts to schedule a recurring meeting with a Notes Room/Resource and the

Room/Resource is not available for one, multiple, or all instances of the meeting, a complete Decline is generated.

This parameter allows you to customize the notification text for the Decline message. For example:

BTPartialText1=Room/Resource is not available.

BTPartialText2=You must use another time or find another resource.

There is a maximum of 1024 characters for this parameter.

BTBLOCKUPDATENOCACHE

Accepted Value: Y/N

Default: N

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

62

Binary Tree Documentation

The default behavior of BTCal is to assume all calendar updates coming from an Exchange chair to a Domino participant where there is no information of the meeting in the BTCache database are valid and are delivered to the Domino participant. This includes reschedules, updates, and adding a Domino participant. When this parameter is set to Y (Yes), BTCal is blocks any calendar update coming from an Exchange chair to a Domino participant where there is no information of the meeting in the BTCache database.

Updates (Exchange to Domino)

When a calendar update arrives from Exchange, BTCal first looks for the UID in the cache database. If the UID does not exist:

 If BTBlockUpdateNoCache = N

The document is processed by BTCal and passed through to Domino. It will not be blocked based on the missing cache document.

 If BTBlockUpdateNoCache = Y

We determine if it is a repeating meeting by looking in the iCal stream for either an RRULE: or a

RECURRENCE-ID:

If the SEQUENCE: is 0, the document is processed by BTCal and passed through to Domino. It will not be blocked based on the missing cache document.

If the SEQUENCE: is greater than 0 but the iCal stream contains neither an RRULE: or a

RECURRENCE-ID: it is a single occurrence meeting update and passed through to Domino. It will not be blocked based on the missing cache document.

If the SEQUENCE: is greater than 0 and the iCal stream contains either an RRULE: or a

RECURRENCE-ID: it is a recurring meeting update and will be stopped by BTCal. It will be blocked based on the missing cache document. This can be either an update to a single occurrence, all occurrences, or an add user.

Cancels (Domino to Exchange)

When a calendar cancel arrives from Exchange, BTCal first looks for the UID in the cache database. If the UID does not exist:

 "Cancel All Occurrences" will be delivered regardless of the BTBlockCancelNoCache INI setting. Without this, the chair cannot cancel and recreate the meeting.

 "Cancel Single Occurrence" will not be delivered by default. If the INI parameter BTBlockCancelNoCache is set to "N", the cancel will be delivered.

BTRESOLVENDRRECIPIENTS

Accepted Value: Y/N

Default: N

When enabled (parameter set to Y), the recipients list in a calendar NDR is resolved from the Exchange-based

SMTP addresses into a Notes name. For example, [email protected] becomes John Smith/Contoso.

BTRESOLVENDRRECIPIENTSDOMAIN

Accepted Value: <string>

Default: None

This parameter allows you to specify the SMTP domain to search if the first search fails. When

BTResolveNDRRecipientsDomain=localpart, the local part of the address is used to perform look ups. If the local

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

63

Binary Tree Documentation part is not unique across all address books, the first matching entry found will be used. When local part is used for name resolution, no secondary domain lookups are supported. If possible, the incoming SMTP address is converted to the abbreviated Notes name.

BTADDUSERDWASUPPORT

Accepted Value: Y/N

This parameter accepts a value of Y or N. It specifies whether BTCal supports the ability for a user to add an

Outlook user to an existing repeating meeting via Domino Web Access (DWA). If this parameter is set to N (or not present in the NOTES.INI file), and a request to add a user comes in, an NDR is returned.

9.7 Zero-Touch Application Remediation (ZApp)

ZApp is an optional (separately purchased) feature of BTCal designed to perform on -the-fly transformation of mail items sent from Domino to Exchange, which contain elements that can only be processed by a Lotus Notes Client.

Such elements include Custom e-Mail Forms, Hot Spot Button, Action Pop-up, and Mouse-over Action. When these items are encountered, they require remediation. To ensure that the Notes -specific elements of these mail items are not lost in transmission from Domino to Exchange, a remediated mail item that contains custom text (defined by the BTSTORETEXT parameter) is sent to the Exchange user. The original mail item is stored in a Domino database on the Domino Coexistence Server (referred to as BTStore) and/or in a Domino database attached to the remediated message. If the original mail item is stored on the Coexistence Server, when the Exchange user receives the resulting mail item in Outlook or Outlook Web Access, the user can click on the link and access the original Lotus Notes mail item in BTStore. If the original mail item is stored in a database attached to the remediated mail item, the Exchange user can open the attached database. In either case, it is assumed the

Exchange user's workstation has the Lotus Notes Client and the original Lotus Notes ID File.

Since the mail item transformation requires no action beyond original configuration, the process is referred to as

Zero Touch Application Remediation. ZApp actions are defined by the following parameters:

BTZAPPSUPPORT

Accepted Value: 0/1

Default: 0

This parameter defines whether ZApp functionality is enabled and which Domino database should be used to store the original mail item.

 If BTZAPPSUPPORT is set to 0, ZApp is disabled and all subsequent ZApp parameters are ignored.

 If BTZAPPSUPPORT is set to 1, the original mail item is stored in a Domino database on the Domino

Coexistence Server (defined by the BTSTOREDB parameter). If the Domino database cannot be found,

BTCal will terminate.

 If BTZAPPSUPPORT is set to 2, the original mail item is stored in a Domino database that is attached to the remediated mail item. The Domino database is created based on the Domino template defined by the

BTZAPPTEMPLATE parameter. If the Domino template cannot be found, BTCal will terminate.

 If BTZAPPSUPPORT is set to 3, the original mail item is stored in the BTSTOREDB on the Domino

Coexistence Server as well as in a Domino database that is attached to the remediated mail item. If either the BTSTOREDB database or the BTZAPPTEMPLATE cannot be found, BTCal will terminate.

BTZAPPTEMPLATE

Accepted Value: <database name>

Default: Required if BTZAPPSUPPORT=2 or BTZAPPSUPPORT=3

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

64

Binary Tree Documentation

This parameter defines the Domino Database template used to create the ZApp Database that is attached to the remediation messages if BTZAPPSUPPORT is set to 2 or 3. If BTZAPPSUPPORT is set to 2 or 3, and this parameter is not specified, BTCal will terminate. If BTZAPPSUPPORT is set to 2 or 3 and this BTCal cannot open the configured template, BTCal will terminate.

This template should be created by the Administrator and Binary Tree recommends using a standard mail template.

When the mail item is received in Outlook, if the Exchange user is running Exchange 2010, the user must set the message to Edit mode by clicking Actions -> Edit message before attempting to open the attached ZApp Database.

BTZAPPDB

Accepted Value: <database name>

Default: BTZAPP.NSF

This parameter defines the name of the Domino Database that is attached to the remediation message if

BTZAPPSUPPORT is set to 2 or 3.

When the %DATETIME% keyword is included in the INI parameter BTZAPPDB, the keyword is replaced with the date and time on the CMTc server in the following format: dd-mm-yyyy_hhmm. For example, if the parameter is BTZAPPDB=%DATETIME%_EncryptedContent.nsf, the database would receive a name like 13-02-2014_12-12_EncryptedContent.nsf.

BTSTOREDB

Accepted Value: <database template name>

Default: BTSTORE.NSF

This parameter defines the ZApp BTStore Lotus Domino database. The database must be stored in the Domino

Coexistence Server data directory and is built from the btstore*.ntf Template received as part of the Notes

Integration | CMT Installation package. The database can be treated as any other standard Domino database, including creation of replicas, agents to manage document aging, r eporting, and other activiti es.

BTZAPPUNIQUECOPY

Accepted Value: N/Y

Default: Y

This parameter defines how the original mail item that contains the ZApp-able items will be handled.

 If BTZAPPUNIQUECOPY is set to Y, a separate document is stored in the BTStore database for each recipient (if BTZAPPSUPPORT is 1 or 3) and a separate ZApp database is created and sent to each recipient

(if BTZAPPSUPPORT is 2 or 3).

 If BTZAPPUNIQUECOPY is set to N, one document is stored in the BTStore database for all recipients (if

BTZAPPSUPPORT is 1 or 3) and the same ZApp Database is sent to all recipients (if BTZAPPSUPPORT is 2 or

3).

This parameter can be used to control the size of the BTStore databa se effectively. Setting BTZAPPUNIQUECOPY to

N significantly reduces the database; however, users can inadvertently delete common documents in the BTStore database. To avoid this, BT recommends that the ACL of the BTStore database be set up to prevent users from deleting documents. Additionally, if any documents in the BTStore database contain buttons that update fields to prevent multiple executions, their functionality can be adversely affected by this setting. Size versus functionality considerations should be carefully considered when implementing this feature.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

65

Binary Tree Documentation

If only one copy of the documents is stored in the BTStore database, and the same ZApp

Database is sent to all recipients, then all recipients will have access to the same document.

Therefore, if the original mail item contained BCC addresses, these addresses will be present for all recipients to view.

BTZAPPCHECKENCRYPT

Accepted Value: 0/1/2

Default: 1

This parameter defines whether encrypted e-mails sent from Domino to Exchange will be remedia ted by BTCal.

If BTZAPPCHECKENCRYPT is set to 0, for all encrypted items (e-mail or calendar entries), the user receives a message (not the calendar entry) with a notice in the body that contents are missing due to being encrypted.

If BTZAPPCHECKENCRYPT is set to 1 and the e-mail is encrypted, it will be treated as an e-mail containing Notesspecific items and will be saved in the BTStore.nsf database and a custom e-mail with a link to the saved document will be sent to the target user. If the encrypted i tem is a calendar entry, it is ZApped and the message is sent along with the link to the original entry, which cannot be acted upon.

If BTZAPPCHECKENCRYPT is set to 2, and the encrypted item is a calendar entry, the unremediated calendar notice is stored in the Btstore.nsf database, a message (similar to BTZAPPCHECKENCRYPT=1) is delivered to the Outlook user, and a calendar notification is delivered to the Outlook user.

Messages are processed by the On the Fly Decryption and Encryption feature before being processed by the ZApp feature. See Appendix J for more information about the On the Fly

Decryption and Encryption feature.

BTZAPPCOMBINEENCRYPTEDCAL ENDAR

Accepted Value: 0/1

Default: 1

This parameter defines whether the ZApp notice is placed in the body of the meeting notice.

If BTZAPPCOMBINEENCRYPTEDCALENDAR is set to 0 the ZApp notice is not placed in the bocy of the meeting.

If BTZAPPCOMBINEENCRYPTEDCALENDAR is set to 1 the ZApp noti ce is placed in the body of the meeting notice.

The standard ZApp text is used in place of the encrypted text.

BTZAPPENCRYPTTEXT

Accepted Value: <text>

Default: Contents of this document are encrypted with a Notes certificate and cannot be read.

This parameter provides the message text for when encrypted e-mails sent from Domino to Exchange are remediated by BTCal. This parameter can be specified as just BTZAPPENCRYPTTEXT or as a multi -line value

(BTZAPPENCRYPTTEXT1, BTZAPPENCRYPTTEXT2).

The maximum number of characters that can be specified in the parameter is 255. If BTZAPPENCRYPTTEXT is not configured, then the following default text is used:

Contents of this document are encrypted with a Notes certificate and cannot be read.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

66

Binary Tree Documentation

BTZAPPBYPASS

Accepted Value: 0/1

Default: 0

This parameter defines whether the presence of a $BTZAppBypass field in an e-mail will cause BTCal to not examine the e-mail for the purposes of remediation regardless of its contents. Encrypted e-mails sent from

Domino to Exchange will be remediated by BTCal. If BTZAPPBYPASS is set to 1 and the e-mail contains a field

$BTZAppBypass that equals to 1, the e-mail will be ignored by the remediation process; otherwise, the presence of a $BTZAppBypass field will not be checked.

BTZAPPBYPASSDOCSWITHFIELDS

Accepted Value: <comma separated list of field names>

Default: None

This parameter defines a list of fields, the presence of which in any mail item will force document remediation to be skipped. This is a multi -valued case-insensitive parameter.

BTZAPPIGNORESTOREDFORMS

Accepted Value: 0/1

Default: 0

This parameter defines whether the presence of a stored form in a mail item will force or skip remediation regardless of its contents. If (mail item’s Form is blank or no form is present) and (mail item has fields

$Body_StoredForm or $Fields_StoredForm or $TITLE_StoredForm or $Info_StoredForm) it is considered to have a stored form.

 BTZAPPIGNORESTOREDFORMS=1 will cause remediation to be skipped while,

 BTZAPPIGNORESTOREDFORMS=0 will cause remediation to be performed.

BTZAPPINCLUDEFULLDISTRIBUTION

Accepted Value: 0/1

Default: 0

This parameter defines whether to maintain the email’s original SendTo, CopyTo, and BlindCopyTo values. If the original SendTo, CopyTo, and BlindCopyTo values are maintained, Outlook recipients of Zapped items will only see other Outlook recipients in the TO and CC fields, not the Notes recipients.

If BTZAPPINCLUDEFULLDISTRIBUTION is set to 0 the email’s original SendTo, CopyTo, and BlindCopyTo values will not be maintained.

If BTZAPPINCLUDEFULLDISTRIBUTION is set to 1 the BTCal will maintain the email’s original SendTo, CopyTo, and

BlindCopyTo values.

BTZAPPPROCESSFORMS

Accepted Value: <comma separated list of form names>

Default: None

This parameter defines a list of non-standard mail item forms whose remediation will be performed. This is a multi-valued case-insensitive parameter.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

67

Binary Tree Documentation

A value of “None” represents the condition of the form being blank or absent from the document. The following values for this parameter are invalid a nd will be ignored:

 Memo

 Reply

 Reply with history.

BTZAPPIGNOREFORMS

Accepted Value: allnonstandard/<comma separated list of form names>

Default: None

This parameter defines a list of non-standard mail item forms whose remediation will be skipped. This is a multi valued case-insensitive parameter.

A value of “none” represents the condition of the form being blank or absent from the document. If the firs t value of this parameter is set to is "allnonstandard", all other values are ignored and forms except for “memo”, “reply”,

“reply with history”, “appointment”, “notice”, “task”, “delivery report”, “nondelivery report”, “return receipt”,

“trace report”, “phone message” will cause BTCal to skip remediation.

BTZAPPIGNOREALLFORMS

Accepted Value: 0/1

Default: 0

This parameter specifies whether remediation will be skipped for a mail item that contains a non -standard form.

If a value of 1 is specified for this parameter, all forms except for “memo”, “reply”, “reply with history”,

“appointment”, “notice”, “task”, “delivery report”, “nondelivery report”, “return receipt”, “trace report”, “phone message” will cause BTCal to skip remediation. Specifying BTZAPPIGNOREALLFORMS=1 has the same effect as specifying BTZAPPIGNOREFORMS=allnonstandard.

BTZAPPORGS/BTZAPPORGSx

Accepted Value: <comma separated list of org units>

Default: None

This parameter defines a multi -valued list of legacy Lotus Domino Organizations used for determination of document security in the BTStore Database. For each recipient of a remediated document, a corresponding entry in the Domino Directory is located and each value of the full name is examined to locate the value that matches user’s name in Lotus Notes ID file. Each hierarchical entry will be compared against the list of organizations specified by this parameter and the first hierarchical value matching one of the values in the list will be used for securing the copy of the mail item in the BTStore Database using a Readers field called $BTReaders.

If no full name value contains an organization matching one of the values in the list, the document will be unsecured when placed into the BTStore Database.

If the total list of organizations is larger than 240 characters, it can be separated across multiple BTZAPPORGSx variables. Any number of sequentially numbered BTZAPPORGSx variables can be defin ed, starting with

BTZAPPORGS1.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

68

Binary Tree Documentation

The following example illustrates 2 alternatives of defining valid Lotus Domino Organizations:

 BTZAPPORGS=BinaryTree,BinTree,BT,BTree

Or

 BTZAPPORGS1=BinaryTree,BinTree,

 BTZAPPORGS2=BT,BTree

 In the second alternative, every BTZAPPORGSx line, except for the last one, must end with a comma.

 If BTZAPPORGS and BTZAPPORGS1 – BTZAPPORGSn approaches are used, the

BTZAPPORGS value will be ignored.

BTZAPPREADERS

Accepted Value: <Domino address>

Default: None

This parameter defines an additional value for the $BTReaders field described in the BTZAPPORGS section. Usually, this value represents a group containing the LocalDomainServers group and other administrative group(s).

BTZAPPRENDERSTOREDFORMS

Accepted Value: 0/1

Default: 0

This parameter specifies whether BTCal will process a memo containing a stored form. If

BTZAPPRENDERSTOREDFORMS is set to 0, the stored form will be ignored and only the remediation notice will be sent; otherwise, the stored form will be processed by BTCal.

This parameter can be used for custom mail database designs and will only work if the value of the

BTZAPPSENDORIGINAL parameter is anything but a zero (BTZAPPSENDORIGINAL accepts 0, 1, 2, and 3).

BTZAPPSENDORIGINAL

Accepted Value: 0/1/2/3

Default: 0

This parameter defines whether an unremediated copy of the mail item is sent to the Exchange user. It sho uld be understood that this mail item will be missing specific Notes -only elements and functionality, but the text will be there. The action taken for each value is as follows:

 0 - the feature is disabled.

 1 - the original mail item is sent in addition to the ZApp notification. In this case, two mail messages are received by each recipient.

 2 - the ZApp notification is inserted into the original mail item at the top. In this case one mail message is received by each recipient.

 3 - the ZApp notification is inserted into the original mail item at the bottom. In this case one mail message is received by each recipient.

This parameter does not affect the process of storing the mail item in the BTStore database.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

69

Binary Tree Documentation

BTZAPPFIELDSx

Accepted Value: <comma separated list of field:value pairs>

Default: None

This parameter contains a list of field:value pairs, separated by a comma. If configured, BTCal will check each message for the configured field, and if found, will compare the value of that field with the configured value. If they are equal, BTCal will remediate the mail item. Note that only fields of TYPE_TEXT and TYPE_NUMBER are supported.

If the total list of field:value pairs is larger than 240 characters, it can be separated across multiple BTZAPPFIELD Sx variables. Any number of sequentially numbered BTZAPPFIELDSx variables can be defined, starting with

BTZAPPFIELDS1.

The following example illustrates 2 alternatives of defining valid field:value pairs:

BTZAPPFIELDS=MailFormat:E,Z:1

Or

BTZAPPFIELDS1=MailFormat:E,

BTZAPPFIELDS2=Z:1

 In the second alternative, every BTZAPPFIELDSx line, except for the last one, must end with a comma.

 If BTZAPPFIELDS and BTZAPPFIELDS1 – BTZAPPFIELDSn approaches are used, the

BTZAPPFIELDS value will be ignored.

BTSTORETEXTx

Accepted Value: <text>

Default: The original custom form that was mailed to you can be found using the following link:\n\n".

This parameter defines the text of the custom e-mail sent to a recipient of a “ZApp’ed” e-mail. There can be any number of lines of text; however, the lines must be sequentially numbered starting with 1 and the text of each line cannot exceed 216 characters. When the e-mail text is created, the content of lines is scanned as a single string with no implied line ends. Line ends are defined by the string \n in the text of any line. The string “\t” defines a tab.

Because NOTES.INI parameters cannot have leading or trailing spaces, each BTSTORETEXTx line must begin and end with a non-blank character.

For example:

BTSTORETEXT1=Dear User\n\n\tAn e-mail was sent to you from Lotus Domino containing special object

BTSTORETEXT2=s accessible only via Lotus Notes Client.\n\n

BTSTORETEXT3=To access this e-mail please click this link ----->\t

Translates as follows:

Dear User

An e-mail was sent to you from Lotus Domino containing special objects accessible only via Lotus Notes

Client.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

70

Binary Tree Documentation

To access this e-mail please click this link----->.

If BTSTORETEXT is not configured, the default text is as follows:

The original custom form that was mailed to you can be found using the following link:\n\n".

BTZAPPUSERFORMS

Accepted Value: <list of non-standard form names separated by commas>/All/None

Default: None

This parameter defines a list of non-standard mail item forms. The BODY of these non-standard mail item forms should be checked for remediation. This is a multi -valued case-insensitive parameter. A value of “None” represents the condition of the form being blank or absent from the document. A value of “All” indicates that all messages containing a non-standard form in the FORM field will be checked for remediation. It is valid to specify both All and

None. When checking for ZAppable items, the only field checked is the BODY field.

BTZAPPTABLES

Accepted Value: Y/N

Default: N

This parameter accepts a value of Y or N. It is used to specify whether BTCal should remediate mail messages that contain non-basic tables.

BTZAPPIGNOREELEMEN TS

Accepted Value: All, Button, Mouseover, Popup, Hotregion

Default: None

BTZAppIgnoreElements accepts the following as comma-separated values:

 All

 Button

 MouseOver

 PopUp

 HotRegion

Please note that these values are not case sensitive. Each value represents a valid ZAppable element, with ALL representing the combination of the remaining values. If this parameter is configured, and ZApp is enabled, BTCal will examine the mail item to see if the ZAppable element should be ignored. For example, if you have specified

“BTZAPPIGNOREELEMENTS=Mouseover,Popup”, and the mail item contains a Mouseover, BTCal will not ZApp the mail item. Also note that if you have “BTZAPPIGNOREELEMENTS=Mouseover”, and the mail item contains both a

Mouseover and Button, the mail item will still be ZApped since you did not configure the Button to be ignored. The mail item will NOT be ZApped if it contains only the specified element.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

71

Binary Tree Documentation

BTZAPPKEEPATTACHMEN TS

Accepted Value: 0/1

Default: 0

This parameter specifies whether attachments will be retained on ZApped messages. By default (parameter set to the default value of 0), attachments are deleted from ZApped messages. When enabled (parameter set to 1), attachments to ZApped messages are retained. This does not alter the attachment as it appears in the

BTStopre.nsf.

The BTZAPPSENDORIGINAL parameter does not affect this parameter, When

BTZAPPKEEPATTACHMENTS is enabled, attachements will be retained on ZApped messages regardless of the BTZAPPSENDORIGINAL parameter setting.

9.8 Logging

There may come a time when it is necessary to gather more information than what is simply written to the Domino console log. There are several logging parameters built into the product that are used to accomplish this. Note that enabling any type of logging will affect performance. Therefore, it is recommended that these parameters only be enabled when instructed to do so by a Binary Tree representative.

 Logging can be enabled or disabled on the fly (i.e., you do not need to restart BTCal).

 When writing messages to the log file(s), the messages are appended to the end of the file. To capture a clean log, the previous log file must be deleted before logging of the current session is enabled.

 A new type of log file is generated on the Windows Coexistence server when there is a

SOAP: Fault message returned by the Exchange Web Services. The new log files are named *.error.log. The log folder can be specified using IIS manager to set it in the

Application properties.

If the SOAP: Fault message indicates the CAS throttling policy has been exceeded, the following EMC commands could be used on the CAS server to cr eate a new throttling policy that has no limits, and assign it to the IIS box:

New-ThrottlingPolicy BTFreeBusy

Set-ThrottlingPolicy BTFreeBusy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null

-RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency

$null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -

EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -

EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null -CPAMaxConcurrency

$null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null -

CPUStartPercent $null

Set-ThrottlingPolicyAssociation [your iis machine name] -ThrottlingPolicy BTFreeBusy

BTLOGDIRECTORY

Accepted Value: <Windows path name>

Default: Windows temp directory

This parameter defines the directory to which log files will be written. It expects a properly formatted windows path name (e.g., c:\CMTc\log). If the specified directory does not exist, BTCal will attempt to create the directory. If this directory cannot be found or created, or if this parameter is not specified, log files will be written to the

Windows temp directory.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

72

Binary Tree Documentation

BTLOGCACHE

Accepted Value: 0/1

Default: 0

A cache database is used to store data required for proper processing of repeating/recurring meetings by BTCal.

This parameter defines whether messages relating to processing of the cache database will be logged. If

BTLOGCACHE is set to 0, logging is disabled; otherwise, log messages are wr itten to the file BTCACHE.LOG.

BTLOGICAL

Accepted Value: 0/1

Default: 0

Calendar information received from Exchange contains information stored in iCal format. This parameter defines whether messages relating to processing of this iCal information will be logged. If BTLOGICAL is set to 0, logging is disabled; otherwise, log messages are wri tten to the file BTICAL.LOG.

BTLOGRMB

Accepted Value: 0/1

Default: 0

During the processing of calendar invitations received from Exchange, MIME body parts are converted to an .ICS file attachment for delivery to Notes. This parameter defines whether messa ges relating to this conversion will be logged. If BTLOGRMB is set to 0, logging is disabled; otherwise, log messages are written to the file BTRMB.LOG.

BTLOGUIF

Accepted Value: 0/1

Default: 0

During the processing of calendar invitations received from Exchange, certain fields within the .ICS file are updated before being delivered to Notes. This parameter defines whether messages relating to the updating of .ICS files will be logged. If BTLOGUIF is set to 0, logging is disabled; otherwise, log messages are written to the file BTUIF.LOG.

BTLOGWMBP

Accepted Value: 0/1

Default: 0

During the processing of calendar invitation received from Exchange, if the .ICS file has been updated, the MIME body part may need to be re-written. This parameter defines whether messages relating to re-writing of the MIME body part will be logged. If BTLOGWMBP is set to 0, logging is disabled; otherwise, log messages are written to the file BTWMBP.LOG.

BTLOGCONSOLE

Accepted Value: Y/N

Default: Y

Notes Integration | CMT has been enhanced to allow the user to determine whether log messages should be written to the Domino console.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

73

Binary Tree Documentation

BTLOGCONSOLE accepts a value of Y(es) or N(o), with the default being Y. Note that Error messages are always written to the console, regardless of the setting of this parameter. Also, note that log messages are always written to the General BTCal log regardless of the setting of this parameter.

BTLOGLEVEL

Accepted Value: 0/1/2

Default: 0

A log file named [email protected] G resides in the Logging Directory configured for Notes

Integration | CMT. All log messages are written to this file, based upon the setting of the BTLOGLEVEL parameter, and optionally to the Domino console (depending on the setting of BTLOGCONSOLE).

BTLOGLEVEL accepts a value of 0 (minimal), 1 (light), or 2 (full), with the default being 0. A log level of 1 corresponds to the debug messages written using the old BTCalL.exe. A log level of 2 corresponds to the debug messages written using the old BTCalF.exe.

BTLOGPNG

Accepted Value: 0/1

Default: 0

If a message from Outlook contains embedded .PNG graphic files, the images are converted to .GIF files and displayed properly when viewed within Notes.

BTLOGPNG accepts a value of 0/1, with the default being 0. When set to 1, Notes Integration | CMT logs all messages relating to PNG processing to a file called BTPNG.LOG, which resides in the Logging directory configured for Notes Integration | CMT.

The BTEx DLL version contained within the current release must be used for full support of embedded PNG conversion.

BTLOGCANCEL

Accepted Value: 0/1

Default: 0

When BTLOGCANCEL is set to 1, BTCal turns on full debugging (equivalent of BTCalF) if it detects that it is processing an inbound cancellation message. When processing of that message is complete, logging returns to the value specified in BTLogLevel.

This parameter does not have any effect if you are running BTCalF as it is already at full logging.

BTANONYMIZELOGGING

Accepted Value: 0/1

Default: 0

When BTANONYMIZELOGGING is set to 1, subject and originator are anonymized (appear as asterisks) when logging.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

74

Binary Tree Documentation

9.9 Delegation NDRs

BTCal can be configured to trap meetings that have been forwarded from an Outlook user to a Notes user. The

Outlook user will receive a Non-Delivery Report (NDR) with customizable text stating that this is an unsupported action. Please refer to Appendix H for details regarding cross -platform delegation.

This feature will only work with Exchange 2010 or higher.

Two parameters support this functionality:

BTDelegateNDR=

Accepted Value: Y/N

Default: Y

This parameter accepts a value of Y or N. It specifies whether BTCal will return an NDR when it detects an inbound

(from Outlook) meeting delegation request. If this is set to Yes, an NDR will be returned. If this is set to No, the

$REF field will be deleted from the inbound message and it will be passed through to the recipient.

9.10 Unused Parameters

The following parameters are no longer required for the Notes Integration | CMT (3.0 release or higher) of BTCal.

 BTHOLDDOMAIN

 BTDEBUGIDLEDELAY

9.11 Sample NOTES.INI

A sample of the NOTES.INI file is displayed below. Depending on your requirement, add, delete, or update the existing Notes Integration | CMT entries.

;************************************************BT START**************************

[email protected]

BTCOEX_BYPASS_REQUESTO R=1

BTEXCHANGEDOMAIN=Exchange

BTEXCHANGEROUTER=BTExchange.box

BTALTEXCHANGEDOMAINS=EXCHANGE-1, EXCHANGE-2

BTEXCHANGEDB=otherexchange.box

BTEXCHANGESERVER=exchange1.binarytree.com

BTNOTESDOMAINS=_

BTLINKSOPTION=0

BTAPPTREROUTE=1

BTDELAY=15

BTORPHANDELAY=300

BTCALRESTARTTIMER=0

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

75

Binary Tree Documentation

BTRETRYLIMIT=5

BTRETRYSENDNDR=0

BTRETRYLIMITTEXT1=Dear User\n\n\tYour message or calendar entry cannot be delivered to its intended recipient

BTRETRYLIMITTEXT 2=s.\\Please contact your e-mail administrator for further assistance.

BTBCCSKIPADDRESS=user@host

BTTRUNCATESUBJECT=N

BTEXPANDGROUPS=N

BTSENDEXPANDED=Y

BTSUPPORTMULTIPLEDOMINODOMAINS=0

BTWORKDIRECTORY=E:\Program Files\Lotus\Domino\data\BTWorks

MIMEFORCEATTACHMENTS=1

BTINATTOPT=0

BTINATTSKIPNAMES=none

BTCACHEDB=BTCache.nsf

BTRECURRENCELIMIT=1200

BTMULTISCHEDREPORTLEVEL=1

BTMULTISCHEDREPORTTEXT1 =Dear User\n\nThe calendar pattern used in invitation you sent is not supported at this time\n

BTMULTISCHEDREPORTTEXT2 =for the following reason:\n%REASON%\n

BTMULTISCHEDREPORTTEXT3 =Please reschedule using another pattern!\n\n

BTMULTISCHEDREPORTTEXT4 =***Your invitation information:\n

BTMULTISCHEDREPORTTEXT5 =Subject: %SUBJECT%\n

BTMULTISCHEDREPORTTEXT6 =Location: %LOCATION%\n

BTMULTISCHEDREPORTTEXT7 =Time: %DATE%\n

BTMULTISCHEDREPORTTEXT8 =Chair: %CHAIRPERSON%\n

BTMULTISCHEDREPORTTEXT9 =The invitation was not sent to the following user(s):\n%RECIPIENTS%

BTMULTISCHEDREPORTADDRESS=none

BTNONDRONQUIT=0

BTZAPPSUPPORT=1

BTSTOREDB=BTStore.nsf

BTZAPPUNIQUECOPY=Y

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

76

Binary Tree Documentation

BTZAPPCHECKENCRYPT=1

BTZAPPBYPASS=0

BTZAPPBYPASSDOCSWITHFIELDS=none

BTZAPPIGNORESTOREDFORMS=0

BTZAPPPROCESSFORMS=none

BTZAPPIGNOREFORMS=allnonstandard,none

BTZAPPORGS=BinaryTree,BinTree,BT,BTree

BTZAPPREADERS=None

BTZAPPRENDERSTOREDFORMS=0

BTZAPPSENDORIGINAL=0

BTZAPPFIELDS=None

BTZAPPUSERFORMS=None

BTZAPPTABLES=N

BTSTORETEXT1=Dear User\n\n\tAn e-mail was sent to you from Lotus Domino containing special object

BTSTORETEXT2=s accessible only via Lotus Notes Client.\n\n

BTSTORETEXT3=To access this e-mail please click this link ----->\t

BTSTORETEXT4=[<a>href="notes://<servername>/8525772900501000">Click Here</a>]\n

BTLOGDIRECTORY=E:\Program Files\Lotus\Domino\Data\BTLogs

BTLOGCACHE=0

BTLOGICAL=0

BTLOGRMB=0

BTLOGUIF=0

BTLOGWMBP=0

BTLOGSTATS=1

DOMINO_FONTSIZE_CUTOFF_1=8

DOMINO_FONTSIZE_CUTOFF_2=10

DOMINO_FONTSIZE_CUTOFF_3=12

DOMINO_FONTSIZE_CUTOFF_4=14

DOMINO_FONTSIZE_CUTOFF_5=18

DOMINO_FONTSIZE_CUTOFF_6=24

BTPROCESSDOMAIN1=exchange1.binarytree.com,Exchange-1.local,Exchange-2.local

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

77

Binary Tree Documentation

BTPROCESSDOMAIN2=exch1.btex2010.local

BTCOEX_NSF=btws.nsf

BTCOEX_FOREIGN_WS_URL=https://autodiscover.BTdomino.btex2010.local/BTAvailability/Availability.asmx

BTCOEX_LOGFILE=\IBM_TECHNICAL_SUPPORT\O UTPUT.LOG

BTCOEX_WS_NAME=BTAvailability

EXTMGR_ADDINS=BTEx

BTCOEX_LOG=6

;***********************************************BT END*****************************

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

78

Binary Tree Documentation

Section 10: Installing ZApp

Installing ZApp is a simple process of adding the template and creating a new BTStore database for the configuration.

1. After the installation of Notes Integration | CMT you will see BTStore.ntf template in the Domino Data

Directory.

2. If you do not see the template in your data directory – reinstall Notes Integration | CMT and verify the

ZAPP module is selected.

3. The Coexistence server may need a restart to use the new databases created from the copied template files.

10.1 Setting Security for BTStore Database for Notes Integration | CMT

Notes Integration | CMT uses a mail-in storage database to store all mail -enabled application messages in a single store repository that provides document level security and allows Exchange/Outlook users to access any applications during the coexistence period.

1. From the Coexistence server, open Domino Administration Client.

2. From the Domino Administrator, open the server, and then navigate to the Files tab as shown below, select Databases only from the Show Me: drop-down box.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

79

3. Right-click BTStore.nsf.

4. Select Access Control -> Manage to set up the ACL as shown below.

Binary Tree Documentation

5. Because the database is new and not signed or secured, if you receive a prompt to cross -certify the signature as seen below, select Yes.

6. The ACL displays. Add the Domino Administrators for the domain or LocalDomainAdmin as shown below and click Add. From the Add User dialog box, select LocalDomainAdmin, and then click OK.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

80

Binary Tree Documentation

7. Change the user types to Person group for LocalDomainAdmins as shown below. Additionally, grant your

LocalDomainAdmins [Manager] role to view additional configuration options in the BTStore database.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

81

Binary Tree Documentation

8. Demote the Default group by giving it only Author without delete access. This database has document security and its own set of purging options, as you do not want users deleting documents even by mistake.

10.2 Configuring ZApp NOTES.INI Parameters

The ZApp NOTES.INI parameters are defined in the Zero-Touch Application Remediation (ZApp) section.

Copy the following parameters to your Notes.ini file if they are not currently present at the end of the Binary Tree

Customizations.

;Begin ZAPP ini settings

BTSTOREDB=BTStore.nsf

BTSTORETEXT1=e-Mail sent to you from Lotus Notes contains specific elements requiring Lotus Notes

Client\n\nPlease press link below to access it\n\n

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

82

Binary Tree Documentation

BTSTORETEXT2=This is BTStoreText2.\n

BTSTORETEXT3=This is BTStoreText3.\n

BTSTORETEXT4=Click here for Server Access [<a href="notes://<servername>/86257316:0041FCE6">Click

Here</a>]\n

BTZAPPBYPASS=1

BTZAPPCHECKENCRYPT=1 (Not needed if using On the Fly Decryption and Encryption)

BTZAPPENCRYPTTEXT1 =Dear User\n\n\tYou cannot access the contents of this document because they are encrypted with a Notes certificate.

BTZAPPENCRYPTTEXT2 =\n\nThese cannot be read.

BTZAPPORGS=CMTU

BTZAPPREADERS=LOCALDOMAINADMINS

BTZAPPSENDORIGINAL=0

BTZAPPSUPPORT=1

BTZAPPIGNORESTOREDFORMS=0

BTZAPPUNIQUECOPY=Y

BTZAPPTABLES=Y

;End ZAPP ini settings

10.3 ZApp Administration Functions

Now that you have created the BTStore database on the Coexistence server, you can configure the Administration settings for the database.

1. Open the server document from the Domino Administrator Client and navigate to the Files tab as outlined below.

2. Before you can open the new database, you must sign it by the server to avoid and ECL prompts. Rightclick the database and select Sign.

3. Double-click on the BTStore.nsf database to open it and set the Administration properties as shown below.

General Settings

 Enable ZAPP Logo – will display BTZapp icon in the top left corner of messages if setting is YES (OR refer to the database Help)

 Prevent storage of e-mails generated in this database – if set to No it will prevent the storage of messages replied to or sent from within BTStore database

 Hide BCC – if BTZAPPUNIQUECOPY configuration parameter is set to NO – this will prevent the viewing of

BCC recipients in a shared message. Note – If set to Yes – user can receive links to messages missing their name in the header fields.

Purge Settings:

 Status – You can enable auto purge agent for documents stored in the database by clicking the Enable button

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

83

Binary Tree Documentation o Days – Indicate the # of days to keep documents in BTStore database o Server to run – Indicate the Domino server to run the purge agent (if multiple servers host replicas of the BTStore database)

10.4 Testing ZApp

Restart the BTCal process to test the ZApp process. Then create a test e-mail that is remediated for having a hotspot button.

1. From the console of the coexistence server, enter the command Tell BTCal Quit, and then when it terminates, enter the command Load BTCal.

2. From Migration Administration e-mail file, create a new memo to an Exchange and add a hotspot button as shown below.

3. Create a simple button with a message box.

4. Send the e-mail to the Exchange User, and then open the ZApp Database to see if it was remediated.

5. This is what the Exchange/Outlook user will see if ZApp is working correctly.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

84

Binary Tree Documentation

Section 11: Verifying Autodiscover, BTAvailability, and

BTRouter

11.1 Autodiscover

1. From the Command Prompt window on the Windows Coexistence server, navigate to %Program

Files%\BinaryTree\CMT for Coexistence <version>Exchange\ and ensure that the following files are installed o Autodiscover, AvailabilityService, and AvailabilityRouter folders are created in the C:\Program

Files\BinaryTree\CMT for Coexistence <version> folder. o Connections.config exists in the Autodiscover, AvailabilityService, and AvailabilityRouter folders exist under C:\Program Files\BinaryTree\CMT for Coexistence <version>.

If web.2010.config exists, rename it to web.config. Unless you are running Exchange

2007, then rename web.2007 to web.config.

2. Verify that web.config and connections.config are writable (not Read-Only).

3. Open the IIS Administrator.

4. Navigate to the Default Web Site.

5. Refresh IIS (press <F5>) and verify that Autodiscover virtual application has been added.

6. Next, select the Autodiscover application in the left pane.

7. Double-click Authentication in the right pane. o Verify that Basic Authentication and Windows Authentication are enabled. o If not, enable them. o Click the Back button.

8. Double-click Connection Strings in the right pane. o Verify that the URL of the EAD value is: https://<Exchange CAS Server

FQDN>/Autodiscover/Autodiscover.xml o Correct the machine name if incorrect. o Click the Back button.

9. Double-click Application Settings. o Verify that ExchangeVersion is set to 2010 for all versions of Exchange except 2007 o If you require credentials to access the Active Directory environment see Appendix L: SetFBCred

Utility. o Verify that Autodiscover is set to .\Autodiscover.xsl.

10. Create a map entry for the Domino SMTP domain name for which you would like to expose Free/Bu sy information. The entry should look like: o MAP:@domino.contoso.com = contoso.com. o This ensures that all requests that go through to Domino use the SMTP domain contoso.com rather than domino.contoso.com. o Multiple map entries, such as the foll owing are also perfectly valid. In this case, both SMTP domains would be mapped to contoso.com. o MAP:@domino.contoso.com = contoso.com

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

85

Binary Tree Documentation o MAP:@domino.spintoptoys.com = contoso.com

11. Optional log settings: o LogAllRequests = False o Log path = c:\log\autodiscover (must be an existing directory, create if needed)

12. If any of the above resulted in changes to the application, run the iisreset command in the Command

Prompt window.

13. Verify that the application is up and running.

14. Open IE and navigate to the following virtual directory:

https://autodiscover.domino.contoso.co m/Autodiscover/Au todiscover.asmx

(Ensure that you are using the same machine name as the SSL certificate issued to the property, and that it matches the Autodiscover.<dominoSMTPdomain> specified above).

15. A web page with a blue header that reads BT Autodiscovery Service for Exchange 2010 Web Services should appear.

16. Click BT_GetConfiguration.

17. Click Invoke.

18. An XML response with the correct endpoint for this machine should display in the browser.

19. Click Back.

20. Click BT_TestAutoDiscovery.

21. Enter the e-mail address of a Domino user with the same domain as previously entered (for example,

[email protected]).

22. Click Invoke.

23. A properly formatted Autodiscover XML document should appear, showing the correct URL to the

BTRouter application.

11.2 BTAvailability

1. From the Command Prompt window, navigate to %Program Files%\BinaryTree\CMT for Coexistence

<version> Exchange\ AvailabilityService.

Verify that the folders and files mentioned above are present.

If web.2010.config exists, rename it to web.config. Unless you are running Exchange

2007, then rename web.2007 to web.config.

2. Verify that web.config and connections.config are writable (not Read-Only).

3. Open the IIS Administrator.

4. Navigate to the Default Web Site.

5. Refresh IIS (press <F5>) and verify that the BTAvailability virtual application has been added.

6. Next, select the BTAvailability application in the left pane.

7. Double-click Authentication in the right pane.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

86

Binary Tree Documentation o Verify that Basic Authentication and Windows Authentication are enabled. o If not, enable them. o Click the Back button.

8. Double-click Connection Strings in the right pane. o Verify that the URL of the EWS value is https://<Exchange CAS Server

FQDN>/EWS/Exchange.asmx. o If the machine name is incorrect, correct it. o Click the Back button.

9. Double-click Application Settings. o Verify that Exchange Version is set to 2010 for all versions of Exchange except 2007 o If you require credentials to access the exchange environment see Appendix L: SetFBCred Utility.

10. Optional log settings: o LogAllRequests = False o Log path = c:\log\availability (must be an existing directory, create if needed)

11. If any of the above resulted in changes to the application, run the iisreset command in the Command

Prompt window.

12. Verify that the application is up and running.

13. Open IE and navigate to the following virtual directory: https:// autodiscover.domino.contoso.com/BTAvailability/Availability.asmx

(Ensure that you are using the same hostname as the SSL certificate issued to the property, and that it matches the Autodiscover.<dominoSMTPdomain> specified above).

You should see a webpage with a blue header that reads BT Availability Service for Exchange Web

Services.

14. Click GetConfiguration.

15. Click Invoke.

16. An XML response with the correct endpoint for this machine should display in the browser.

17. Click Back.

18. Click BT_TestConnectivity.

19. Add two e-mail addresses of valid Exchange mailbox users (for example, [email protected],

[email protected]).

20. Click Invoke.

21. You should see two string representations of the Free/Busy stream for each user for the current date.

11.3 BTRouter

1. From the Command Prompt window, navigate to %Program Files%\BinaryTree\CMT for Coexistence

<version> Exchange\AvailabilityRouter.

2. Verify that the files mentioned above are present.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

87

Binary Tree Documentation

If web.2010.config exists, rename it to web.config. Unless you are running Exchange

2007, then rename web.2007 to web.config. If Exchange.2010.asmx exists, rename it to Exchange.asmx.

3. Verify that web.config and connections.config are writable (not Read-Only).

4. Open IIS Administrator.

5. Navigate to the Default Web Site.

6. Refresh IIS (press <F5>) and verify that the BTRouter virtual application has been added.

7. Select the BTRouter application in the left pane.

8. Double-click Authentication. o Verify that Basic Authentication and Windows Authentication are enabled. o If not, enable them. o Click the Back button.

9. Double-click Connection Strings. o Verify that the URL of the EWS value is https://<Exchange CAS Server

FQDN>/EWS/Exchange.asmx. o Verify that the URL of the BTAS-NOTES value is pointing to the BT Domino Availability Service URL

(for example, https://<FQDN of the Domino Web service>/BTAvailability). o Click the Back button.

10. Double-click Application Settings. o Verify that ExchangeVersion is set to 2010 for all versions of Exchange except 2007 o If you require credentials to access the domino environment see Appendix L: SetFBCred Utility.

11. Optional log settings: o LogAllRequests = False o Log path = c:\log\btrouter (must be an existing directory, create if needed)

12. If any of the above resulted in changes to the application, type the iisreset command in the Command

Prompt window.

13. Verify that the application is up and running.

14. Open IE and navigate to the following virtual directory: https:// autodiscover.domino.contoso.com

/BTRouter/Exchange.asmx

Ensure that you are using the same hostname as specified in the SSL certificate Issued To property. You should see a webpage with a blue header that reads BT Availability Router for Exchange Web Services

2010.

15. Click BT_GetConfiguration.

16. Click Invoke.

17. You should get an XML response with the correct endpoint for this machine. o If UNREACHABLE appears under the Domino endpoint URL, verify the Domino Availability Service endpoint. You shoul d be able to reach the Domino service endpoint using the browser. o Return to Application Settings in IIS and update the endpoint with the proper URL.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

88

Binary Tree Documentation

18. Click Back.

19. Click BT_TestConnectivity.

20. Enter two e-mail addresses for valid Domino users (for example, [email protected] and [email protected]).

21. Click Invoke. You should see a string representation the Free/Busy stream for each user for the current day.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

89

Binary Tree Documentation

Section 12: Troubleshooting Autodiscover, BTAvailability, and BTRouter

If you receive a Problem with this website's security certificate message, click to continue to this website. This certificate issue must be resolved before Free/Busy will work completely.

12.1 Autodiscover

 If the header is still red with the certificate error, click the certificate error button, and then select View

Certificates.

 When the certificate dialog comes up, look at the name to the right of the Issued To line.

 Verify that the Issued To name is the same as hostname used above in the URL. o If not, reopen the browser using the correct hostname in the URL. o If the hostname matches, click Install Certificate. o Click Next. o Select Place all certificates in the following store. o Click Browse. o Select Trusted Root Certification Authorities. o Click Next, Finish, Yes, OK until all the dialog boxes are closed. o Close the browser and reopen using the URL above. Now, there should be no certificate warnings.

 A webpage with a blue header that reads BT Availability Service for Exchange Web Services should appear.

12.2 BTAvailability

 If the header is still red with the certificate error, click the certificate error button, then select View

Certificates.

 When the certificate dialog comes up, look at the name to the right of the Issued To line.

 Verify that the Issued To name is the same as hostname used above in the URL. o If not, reopen the browser using the correct hostname in the URL. o If the hostname matches, click Install Certificate. o Click Next. o Select Place all certificates in the following store. o Click Browse. o Select Trusted Root Certification Authorities. o Click Next, Finish, Yes, OK until all the dialog boxes are closed. o Close the browser and reopen using the URL above. Now, there should be no certificate warnings.

 You should see a webpage with a blue header that reads BT Availability Service for Exchange Web

Services.

12.3 BTRouter

 If the header is still red with the certificate error, click the certificate error button, then click View

Certificates.

 When the certificate dialog comes up, look at the name to the right of the Issued To line.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

90

Binary Tree Documentation

 Verify that the Issued To name is the same as the hostname used above in the URL. o If not, reopen the browser using the correct hostname in the URL.

 If the machine name matches, click Install Certificate.

 Click Next.

 Select Place all certificates in the following store.

 Click Browse.

 Select Trusted Root Certification Authorities.

 Click Next, Finish, Yes, OK until all the dialog boxes are closed.

 Close the browser and reopen using the URL above. Now, there should be no certificate warnings.

 You should see a webpage with a blue header that reads BT Availability Router for Exchange Web

Services 2010.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

91

Binary Tree Documentation

Section 13: Configuring Exchange SMTP Connectivity

13.1 Configuring Accepted Domains

Depending on the namespace or address book design you use, SMTP connectivity is configured differently, and has slightly different prerequisites. This section will focus strictly on Binary Tree’s best practices and most common scenarios for clients. In the real world, there may be slight differences to this confi guration. This section will cover namespace design, shared namespace, and configuring SMTP connectors in Exchange.

It is advised to create a new remote domain, apart from the default "*", to allow for specific mail format parameters with domino SMTP while not disturbing internet mail formatting.

1. Log into the Windows Coexistence Server. Open the Exchange Management Console from the Start menu as illustrated below.

2. In the Exchange Management Console, in the left pane, click Organization Configuration/Hub Transport, and then click the Accepted Domains tab.

3. If the exch.contoso.com domain does not exist, In the right pane, click the New Accepted Domain option.

4. If it does not exist, specify the following details in the new window. o Name: Typically, enter the other domain name here, with a comment that this represents

Domino Users. For example: Exchange Sub-Domain (Inbound from Domino) o Accepted Domain: Specify the domain name. For example: exch.contoso.com

You should now see a new accepted domain for incoming traffic from Domino that will be delivered to the new Exchange users. This accepted domain was set up to be authoritative for the domain. This domain will accept e-mail addressed to the exch.contoso.com domain and deliver to Exchange users with a matching Proxy Address.

13.2 E-mail Address Policy

If using the Shared/Sub-domain namespace design, mailboxes in Exchange Server need to have an e-mail address added in the exchange domain. Rather than manually updating each user, an E-mail Address Policy can be created to perform this task.

1. Open the Exchange Management Console from the Start menu.

2. Open the E-mail Address Policy tab.

3. In the right pane, click the New E-mail Address Policy option.

4. Specify the details as listed below: o Name: Typically, enter something easy to recognize, for example Exchange Users. o Select the Include these recipient types option, and then select the following check boxes. o Users with Exchange mailboxes o Resource mailboxes o Mail-enabled groups

5. Click Next twice to move to the alias screen.

6. Click Add.

7. When adding the e-mail address policies, you will need to add all aliases that domino uses for the new exchange domain. Click SMTP Address.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

92

Binary Tree Documentation

8. Select the Browse button to select the appropriate accepted domain that was created in the previous step. Alternatively, you can also specify the fully qualified domain name.

9. Repeat the last step for all aliases (e-mail address local parts) you choose to use, such as short name, first name, and last name.

Please note that you may need to create e-mail addresses with both accepted domains for e-mail addresses. o contoso.com o Exchange1.contoso.com o exch.contoso.com

10. The next step is to set the reply to the address default policy. The selected custom address will be set as the reply to address and will make the e-mail address type the primary address. This should be set to whatever the Domino internet address. Click Next.

11. Choose immediately, and then click Next.

12. Click New.

After applying immediately, you will see a summary of the address policies you are about to create. A green check mark displays when completed successfully.

13. Click Finish.

You have successfully created the default address policies that will get stamped on each exchange user as they are provisioned and will ensure that proper namespace and aliases are created in Exchange for mail routing purposes.

13.3 Create a Send Connector

Create and configure a send connector from Exchange to Domino. This connector defines the path to route mail that exchange does not a have a mail box for, which will be your domino contacts.

This is one area in the coexistence process that can vary from customer to customer depending on what other type of routing they will be doing from Exchange, such as to internet or to other domains.

1. Open the Exchange Management Console.

2. Navigate to the Send Connectors, and then select New Send Connector.

3. The first page requires just two configuration items.

Name: Typically, enter the “other” domain name here with a comment that this represents a connection to Domino users. For example: Outbound to Domino

Intended use: Leave it as Custom.

Click Next.

4. Click the Add button, and then select SMTP Address Space.

5. In the SMTP Address Space box, specify the address space, and select the Include all sub-domains check box. This will ensure that all domains and sub-domains can send mail to Domino. Click OK.

6. Select the Next button.

7. Select the Route mail through the following smart hosts radio button, and then click Add.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

93

Binary Tree Documentation

8. If DNS is working properly in your environment, in other words, if you can ping your server’s FQDN, specify the server name for connection in the FQDN field. Click OK.

9. Click Next.

10. Configure the authentication settings. Specify None for this server, and then select Next.

11. Next, fill in your source server, which is the Exchange server you are setting up. This should be pre-filled.

12. Click Next.

13. Click New and Finish buttons to create your new SMTP send connector.

You have successfully created the SMTP Send Connector, which will configure the Exchange server to connec t to the Domino Coexistence server for mail addresses to any contact in Exchange without a mailbox.

13.4 Create a Receive Connector

Create and configure the Receive Connector in the Exchange Management Console. A Receive Connector must be configured to allow messages from Domino to enter the Exchange Server 2007 environment.

1. Start the Exchange Management Console for Lotus Domino from the Start menu as illustrated below.

2. Select Hub Transport from Server Configuration in the left pane, and then click New Receive Connector.

3. Similar to the Send Connector configuration, there are two configuration items. o Name: Typically, enter hub server name, and add a comment that this is a connection to Domino users. For example: Receive from Domino. o Intended use: Leave it as Custom.

4. Accept the defaults. This will allow the Exchange server to listen on all IP addresses assigned to it.

5. Specify the IP address of the Domino Coexistence Server, but first delete the range and add your address as seen in the images below.

Please ensure that you check the IP address of the Domino Coexistence Server before specifying it.

6. Click Next to receive a summary of your receive connector setup.

7. Click next again.

8. Click New to create the connector.

9. Click Finish.

10. The next step will be to configure the security and permissions for using this connector. So, right-click on the Receive from Domino connector you just created, and select Properties.

11. Select the Authentication tab. Deselect Transport Layer Security (TLS) and select Externally Secured.

12. Select the Permission Groups tab and select the following permission groups. These will be set for

Domino connections.

13. Select Apply.

14. Click OK to save your receive connector security settings and this will complete your connector.

This concludes all the settings required for routing SMTP mail to and from the Exchange server environment to the

Domino Coexistence server. The next step in the process is to setup the Domino SMTP settings.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

94

Binary Tree Documentation

Section 14: Operations

14.1 Background

 Notes Integration | CMT delivers the highest levels of functionality, stability and scalability for connection between Microsoft Exchange and Lotus Domino.

 Notes Integration | CMT software is deployed on a single or multiple Coexistence Domino Server(s).

 Notes Integration | CMT software consists of modules deployed in the Domino Server program directory: o nBTCal.exe represents BTCal Server Task. o nBTEx.dll represents BTEx Mail Router Extension Manager Add-In Task.

 Notes Integration | CMT is configured via a number of parameters in the NOTES.INI file of the Coexistence

Server.

14.2 Basic Operational Information

Notes Integration | CMT consists of two main components:

 Server Task – BTCal

BTCal Server Task is invoked by a simple load command or by its inclusion into the list of the ServerTasks parameter values in the Coexistence Domino Server’s NOTES.INI file.

An example of invoking the Server Task manually is by using the following command:

Load btcal

To determine if the BTCal Server Task is running, examine the list of Server Tasks for BT iCal Process.

BTCal Server Task accepts the following Domino Console Commands: tell BTCal quit

Quits the BTCal task tell BTCal restart

Restarts the BTCal task tell BTCal run tell BTCal show

Forces immediate processing of all pending messages

Shows version information tell BTCal flushstats

Writes stats records in the queue to the BT

Statistics database

 Mail Router Extension Manager Add-In Task – BTEx

The Domino Mail Router Extension Manager add-in task is activated at the Domino Coexistence Server startup and is defined as the value of the EXTMGR_ADDINS parameter in the Coexistence Domino Server’s

NOTES.INI file.

 BTEx should be the only Mail Router Extension Manager add-in task loaded on the Coexistence Domino Server.

 When upgrading nBTEx.dll to a new version, the existing module may not be over-written while the Domino Coexistence Server is active. The module must be replaced when the Server is down and will take effect when the Server restarts.

BTCal and BTEx record their activity in the standard Domino Log database as well as display it on the Domino

Console. By checking the Domino Server Log, one can determine whether BTCal and/or BTEx are perfor ming their expected tasks.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

95

Binary Tree Documentation

Notes Integration | CMT interfaces with the Mail Router mailboxes and the Foreign Domain mailbox.

 Foreign Domain mailbox path is defined by the NOTES.INI parameter BTEXCHANGEDB.

 Mail Router mailboxes are usually named mail.box or mail1.box, mail2.box….mailN.box depending on the number of mailboxes that are defined for the Coexistence Domino Server.

14.3 Data Flow through Notes Integration | CMT

Domino to Exchange

 Exchange users are defined in the Domino Directory as users at a specific Foreign Domain (defined by

Notes Integration | CMT Server NOTES.INI parameter BTExchangeDomain).

 Domino Mail Router delivers data destined for Exchange users to the Foreign Domain Mailbox on the

Domino Coexistence Server (defined by Notes Integration | CMT Server NOTES.INI parameter

BTEXCHANGEDB).

 Based on the pre-defined schedule (defined by Notes Integration | CMT Server NOTES.INI parameter

BTDELAY) BTCal periodically examines the system view “Mail” in the Foreign Domain Mailbox.

 Any item with field RoutingState equal to “Dead” and field DeadFailureReason equal to “Pending Removal by BTCal” is deleted from the Foreign Doma in Mailbox.

 Any other item is processed as follows: o Each value of the Recipients field is matched against the Domino Directory.



If the value does not have a unique match in the Domino Directory, a NDR is generated to the originator.



If the value has a unique match in the Domino Directory, the value is replaced with the

SMTP address constructed from the first value of the ShortName field of the Domino

Directory document and the pre-defined Exchange SMTP domain (defined by Notes

Integration | CMT Server NOTES.INI parameter BTEXCHANGESERVER). o If any valid recipients are found, BTCal performs further processing of the item contents, if applicable, and copies the completed item to the Domino Mail Router mailbox (mail.box or mail1.box depending on the number of Mail Router mailboxes on the Notes Integration | CMT

Server) for delivery to Exchange via SMTP. o Field RoutingState is set to “Dead” and field DeadFailureReason is set to “Pending Removal by

BTCal”.

 Domino Mail Router combined with Domino SMTP Gateway converts the item into the MIME format and delivers it to Exchange.

Exchange to Domino

 Domino users are defined in Active Directory as Contacts with the target address pointing them to

Domino.

 Exchange SMTP Connector delivers data destined for Domino users to the Coexistence Domino Server.

 Domino SMTP receives data from Exchange and places received items into a Domino Mail Router mailbox.

 BTEx examines the From field of each received item to determine whether it is received from an eligible

SMTP domain (defined by Notes Integration | CMT Server NOTES.INI parameter BTPROCESSDOMAIN).

 BTEx stops any mail item that contains an attachment for remediation.

 If value of From field is not an address representing an eligible SMTP domain, item is routed by Domino

Mail Router without further processing.

 If value of From field is an address representing an eligible SMTP domain, the received item is processed as follows: o Each value of From, SendTo, CopyTo, and BlindCopyTo fields representing an eligible SMTP domain is matched against the Domino Directory.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

96

Binary Tree Documentation o If the value does not have a unique match in the Domino Directory, it remains unchanged as an

SMTP address. o If the value has a unique match in the Domino Directory, the value is replaced with the first value of the FullName field of the Domino Directory document. o If it contains an embedded PNG object.

 If received item contains iCal or has one or more attachments, field RoutingState is set to “Dead” and field

DeadFailureReason is set to “Pending Processing by BTCal”.

 If BTCal is active, BTCal is invoked with reference to the current item.

 If BTCal is not active or is busy, the current item will become an “orphan” and will be processed later during the BTCal orphaned items processing cycle.

 BTCal performs further processing of the item contents, if applicable, and releases it for further mail routing by clearing fields RoutingState and DeadFailureReason.

 Domino Mail Router delivers the item to destination Domino mailbox.

 Based on the pre-defined schedule (defined by Notes Integration | CMT Server NOTES.INI parameter

BTORPHANDELAY) BTCal periodically examines the system view “Mail” in the Mail Router Mailbox(es) for

“orphaned” items, where Field RoutingState is equal to Dead and DeadFailureReason is equal to “Pending

Processing by BTCal”.

 BTCal performs further processing of the item contents, if applicable, and releases it for further mail routing by clearing fields RoutingState and DeadFailureReason.

 Domino Mail Router delivers the item to destination Domino mailbox.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

97

Binary Tree Documentation

Appendix A: Detailed Description of Workflow Items

Availability Workflow

 Ensuring the ability to obtain Free/Busy information for a user regardless of the system or the migration status

Messaging Workflow

 Ensuring that the flow of any message thread stays intact o Sending an email o Replying to an email o Replying to a reply

 Enables Outlook users to see items with their corresponding graphic icons just like they appear to Notes users o Database links o View links o Document links

Calendar Workflow

 Ensuring that any invitee's calendar is properly updated regardless of the migration status o Creating a meeting o Updating a meeting o Rescheduling a meeting o Cancelling a meeting

 Removes the duplicate entry of the meeting chairperson from calendar invitations sent by Outlook users to their Notes invitees

 Removes duplicate and incorrect attendee status entries of Outlook users from the views of Notes users who send calendar invitations to Outlook users

 Ensures that attachments to calendar invitations sent by Notes users arrive to their Outlook invitees and vice versa

 Enables Outlook users to reserve rooms and resources defined in the Domino-based resource reservation database

 Ensures that updates and reschedules to recurring meetings made by either Outlook or Notes users are properly updated for their invitees

Application Workflow

 Preserving the ability of a user to receive application originated e-mails and perform actions required by these e-mails

 Enables Outlook users to view and act on email -embedded Lotus forms and buttons via ZApp (Zero-touch

Application Remediation)

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

98

Binary Tree Documentation

Appendix B: All About Certificates

Creating Autodiscover SSL Certificate on the Windows Coexistence Server

Next, create an Autodiscover SSL certificate request for IIS on the Windows Coexistence Server. Submit the request to a Certificate Authority (CA), and then create the SSL certificate.

1. Log into the Windows Coexistence Server and launch the IIS Manager.

2. Select the root IIS Home.

3. Double-click Server Certificates to open.

4. On the right side, click Create Certificate Request.

5. Complete the Distinguished Name Properties form. o Common name: Specify the name to which the certificate will be issued. For example, autodiscover.domino.contoso.com. o Organization: Specify the name of the company, such as Contoso. o Organizational unit: Specify an organization within the company, such as IT. o City: Specify a city name. o State: Specify a state name. o Country: Specify a country name.

6. When done, click Next.

7. Accept the default values in the Cryptographic Service Provider Properties screen, and click Next.

8. Specify the path and filename for the location of the certificate request file. For example,

C:\swsetup\autodiscover.txt, and then click Finish.

9. Open the Request Certificate text file using Notepad and copy the contents to the clipboard.

10. Go to a CA website, such as Verisign or a free site at https://secure.instantssl.com, and complete the certificate request from the Request Certificate text file.

11. Once you receive the new server certificate, save it to a location accessible by the Windows Coexistence

Server.

12. Launch the IIS Manager again, sel ect the root server, and then click Server Certificates.

13. On the right, click Complete Certificate Request.

14. Enter the path to the server certificate that you specified in step 11. Select a friendly name for the certificate, such as autodiscover.domino.yourcompanyname.com, and click OK.

15. You can now see an additional certificate in the server certificates list.

Replacing Self-signed with CA Certificates in CAS Servers

Exchange Server Certificates

Microsoft Exchange CAS servers, by default, have self-signed certificates installed. These are adequate for intranet access, but have limited usage. Many Exchange functions by default do not allow self-signed certificates to be

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

99

Binary Tree Documentation used, and require special override, which may affect security. It is highly recommended that you replace these with actual Certificate Authority recognized certificates. If you have a Certificate Authority server installed on your network, you can generate them from that authority. You can also purchase certificates, which are SSL-capable from a third-party vendor, such as Verisign. These certificates need to be capable of at least 1024 -bit SSL - Server

Authentication.

Here are some online instructions on how to use Windows Certificate services to issue your own certificates using

Microsoft Certificate Server: http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html

Each CAS server must have an SSL certificate with the server name as the subject of the certifi cate. It is also recommended that you include some subject alternative names so that URLs with those hostnames can also be resolved to this certificate. For Example:

Server Name: CASHUB

Domain: ABC.LOCAL

FQDN: CASHUB.ABC.LOCAL

You may also want AltSubjectName entries for other hostnames to which you expose this CAS server. If this server hosts an external mail name, such as mail.abc.com, that name could also be included in the subject alternative

names.

DNS entries would need to be added for these entries as well, but having the names in the certificate ensures that

URLs are of the following forms:

 https://cashub/xxxx

 https://cashub.abc.local/xxxx

 https://mail.abc.com/xxxx

All these hostnames can then be properly secured on the same CAS server and b e associated with the same virtual directories in IIS.

Domino Domain Certificates

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

100

Binary Tree Documentation

For each Domino SMTP Domain that you will be exposing via Free/Busy - you will need an autodiscover certificate.

For example:

Domino SMTP Domain: contoso.com

Autodiscover hostname : autodiscover.contoso.com

Alternatively, you can generate a certificate with a subject name that is more widely applicable using the * notation:

This certificate must be installed on the server where the autodiscover service will be run, and where Exchange

Coexistence Free/Busy binaries are installed.

Certificates may be generated or purchased for multiple domains, or you can use a separate certificate for each domain.

Installing Active Directory CA Services

Certain versions of Windows Server 2008 only allow certain Active Directory CA Services components to be installed. The following table can be used as a general reference point.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

101

Binary Tree Documentation

 CA (Certification Authority) – Issues certificates to users, computers, and services while managing their validity; comes in root and subordinate.

 Network Device Enrollment Service – Allows network devices, such as routers, to request and receive certificates based on Simple Certificate Enrollment Protocol (SCEP).

 Online Responder Service – Implements Online Certificate Status Protocol (OCSP) by evaluating certificate status, decoding revocation status requests, and sending back signed responses containing certificate status information.

Install Enterprise Certificate Authority on a Windows 2008 Server

There are two varieties of root CAs:

 Enterprise

 Standalone

Each has their advantages and configuration.

To install the Enterprise root CA server in the AD domain on a Windows Server 2008 Enterprise version, you must first ensure that the server is a member of the domain, and is a domain controller.

1. Open Server Manager.

2. Select Roles, and then click Add Roles in the center pane.

3. The Before You Begin page may show up if you have not turned it off already. If it appears, click Next.

4. In the Select Server Roles window, select Active Directory Certificate Services, and then click Next.

5. Now, an Introduction to Active Directory Certificate Services page appears where you can read about the good things you can do with AD CS.

Name and Domain settings of a computer cannot be changed after a CA has been installed. If you want to change the computer name, join a domain, or promote this server to a domain controller before the install.

6. Click Next.

7. Next, the Select Role Services page appears, which can include any of the following depending on what version of Windows Server 2008 you are installing it on — refer to the table above for specifics.

8. Select Certification Authority.

9. Click Next.

10. In Specify Setup Type, select the Enterprise radio button, and then click Next.

11. For the Specify CA Type page, choose the Root CA radio button, and then click Next.

12. In Set Up Private Key, select Create a new private key radio button, and then select Next.

13. In the Configure Cryptography for CA screen, select the following options. o CSP - RSA#Microsoft Software Key Storage Provider

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

102

o Key Character length - 4096 o Hash algorithm - md5

14. Click Next.

Binary Tree Documentation

15. In Configure CA Name, overwrite the default common name for this CA with Test-Enterprise-CA and the

Distinguished name suffix, and then click Next.

16. Next, specify Set Validity Period for the CA certificate.

Please note that a root CA issues itself a certificate. The default is for 5 Years. You can change this based on any need you might have in your environment. Click Next.

17. Configure Certificate Database will let you specify where you want to put the database and log files for the CA. Retain the default settings. Click Next.

18. On the Confirm Installation Selections screen, you can review the selections you made, and a warning will again be displayed that you cannot change the computer name or domain settings for this server after installing the CA.

19. Click Install.

20. After a few minutes, you wil l see the Installation Results, and the Installation succeeded message.

21. Click Close.

22. Click on Certification Authority in Administrative Tools (if you get a UAC pop up, just click OK).

23. Now you can see the CA named Test-Enterprise-CA in the left pane with a bunch of folders for certificates.

24. You can also click the Certificate Templates folder to see that there are a few default templates, which are already set up and ready to go.

25. You successfully installed the Active Directory Certificate Services on Windows Server 2008. To request a certificate and configure it, you need to browse to localhost\certsrv or %servername%\certsrv.

It is preferred to obtain a certificate from a third-party CA or create internal CA within your network. Most third-party CA’s trusted root certificates are already present in both the client and server key rings so no administrative overhead would be required to get a trusted root certificate installed in all servers and clients. Follow the given procedure to create a Domino

CA.

Creating Domino SSL Certificate Request

Notes Integration | CMT uses SSL Certificates as the method for securing communication between the coexistence servers. An SSL Certificate is therefore required on the Domino and Windows Coexistence servers. Exchange requires non self-signed certificates.

It is preferred to obtain a certificate from a third-party CA or create internal CA within your network.

Most third-party CA’s trusted root certificates are already present in both the client and server key rings so no administrative overhead would be required to get a trusted root certificate installed in all servers and clients. Follow the given procedure to create a Domino CA.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

103

Binary Tree Documentation

1. Launch Lotus Notes client on your workstation.

2. Select the ID and password.

3. Click File -> Database -> New.

4. In the New Database dialog box, select the server name from the Server drop-down list.

5. Specify a title, such as Domino Certificate Authority and a name, such as DominoCA.nsf.

6. After checking Show Advanced templates, select the Domino Certificate Authority template and click OK.

7. Close the About Domino Certificate Authority tab for this database.

8. Click Create Certificate Authority Key Ring & Certificate.

9. Specify the following field values in the Key Ring Information and Key Size sections. o Key Ring File Name: Specify the path and file name for the location of the key ring (this is relative to the workstation making the request, not the server). o Key Ring Password and Confirm Password: Specify the password you wish to use to protect the key ring, and confirm the password. o Key Size: Change the key size from 512 to 1024 (this provides better security).

10. In the Distinguished Name section, specify the following values. o Common Name: Specify a common name. This is the FQDN for the server that people would access through a browser. o Organization: Specify the organizational name. o Organizational Unit: Specify the OU. o City or Locality: Specify a city. o State or Province: Specify the full name of the state. Abbreviations are not accepted. o Country: Specify a country. Only two characters are allowed.

11. Next, click the Create Certificate Authority Key Ring button.

12. Verify the information, and then click OK.

13. Next, click the Configure Certificate Authority Profile.

14. Verify the location of the key ring file in the CA Key File field.

15. Enter the Domino Mail Server FQDN in the Certificate Server DNS Name field.

16. Select the defaults for the remaining fields.

17. Click the Create Certificate Request button.

18. Next Select the Create Server Key Ring & Certificate option.

19. Verify the location of the key ring file in the CA Key File field.

20. Enter the key ring password and confirm.

21. Select 1024 for the Key Size.

22. Next, enter CAKeyPair for the CA Certificate Label.

23. Fill in the Distinguished Name as you did in the earlier step only including the FQDN of the host server the

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

104

Binary Tree Documentation key is being created for.

24. Click the Create Server Key Ring button.

25. When prompted, enter the password you set for the key ring file.

26. A confirmation screen will appear for the location of the new Server Key Ring.

27. Perform the same steps above for domino server.

28. To setup SSL on your domino servers, you will need to copy each of the key ring files named

win23dmbx74.kyr and win23dmbx74.sth onto the respective servers Lotus \Domino partitioned data directory. You can find these files on the workstation that you used to create them.

29. If necessary, connect to the appropriate folder on the server prior to moving them into their server’s data directory.

30. From the Domino server, copy the respective file pairs into the Domino Partition.

31. From the Domino Administrator Client, select open server and select the %servername%/CMTU server to administer.

32. Select the Configuration tab, and then click Current Server Document -> Ports -> Internet Ports.

33. Edit the Server and replace the Keyfile.kyr with your server key ring file. An example of the server key king is win23dmbx74.kyr.

34. Open the Server document for this server. Go to the Ports -> Internet Ports.

35. If necessary, change the entry in the SSL key file name field to reflect the name of the server key ring file.

36. Make sure that SSL port status is set to enabled. Optionally, to force SSL to be used for all connections, change TCP/IP Port Status to Redirect to SSL.

37. Save and close the Server document.

38. From the Domino consoles, issue the Restart Server command to each server to initiate the new SSL

Certificates.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

105

Binary Tree Documentation

Appendix C: Considerations for Domino SMTP Domain

Exposure

If Exchange and Domino do not share a common SMTP domain, you can expose the Domino domain directly.

If Exchange and Domino share a common SMTP domain, you will need to create a unique domain by which

Domino users can be uniquely identified by Exchange. For instance, if Domino receives and ro utes mail to addresses, such as [email protected], and Exchange receives and routes mail to addresses, such as [email protected], this would indicate a shared SMTP domain namespace. A new SMTP domain must be created to allow Exchange to route Free/Busy calls properly to Domino, such as domino.contoso.com. When one of these contacts is viewed, their primary SMTP address would be [email protected], but their target address would be

[email protected]. In this case, the SMTP domain that you want to expose from Domino is in fact

domino.contoso.com. The domain name you choose will also determine the Autodiscover hostname used in DNS for the IIS box.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

106

Binary Tree Documentation

Appendix D: NOTES.INI Parameters

NOTES.INI Parameters

BTADDUSERDWASUPPORT

BTALTEXCHANGEDOMAINS

BTAPPTREROUTE

Accepted Value

Y/N

<comma-separated domain names>

0/1

Default Value

1

None

BTBCCSKIPADDRESS

BTBLOCKCANCELNOCACHE

BTBLOCKUPDATENOCACHE

BTCACHEDB

<SMTP address>

Y/N

Y/N

<BTCache.nsf>

None

Y

N

BTCAL.NCF

BTCALRESTARTTIMER

BTCALSTATSNDR

BTCALSTATSNOCHANGE

BTCALSTATSZAPP

BTCHECKINTERNALSMTP

BTCHECKRECIPIENTS

0/1

0/1

0/1

Y/N

BTCOEX_APPROVED_CALLERS

BTCOEX_BYPASS_REQUESTO R

<list of IP addresses>

0/1

BTCOEX_CLIENT_LOG ??

BTCOEX_DEFAULT_FB_ACCESS_ACCOUNT <SMTP address>

BTCOEX_DOMINO_DOMAINS <comma-separated domain names>

BTCOEX_EXCHANGE_DOMAINS

BTCOEX_FOREIGN_WS_URL

BTCOEX_LOG

<number>

0/1

0 (no restart)

1

<comma-separated domain names> Required https://autodiscover.%domino.contoso%.

com/BTAvailability/Availability.asmx

0-8

Required

???

0

N

0

1

Required

0

??

Required

Required

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

107

NOTES.INI Parameters

BTCOEX_LOGDATA

BTCOEX_LOGFILE

BTCOEX_NSF

BTCOEX_RECYCLE_ENV_REQ_COUNT

BTCOEX_SERVER_LOG

BTCOEX_SERVICE_TYPE

BTCOEX_WS_NAME

BTCONVERTPNG

BTCONVERTPROPOSE

BTDELAY

BTDELEGATENDR

BTEXCHANGEDB

BTEXCHANGEDOMAIN

BTEXCHANGEROUTER

BTEXCHANGESERVER

BTEXPANDCALGROUPS

BTEXPANDMAILGROUPS

BTEXPANDGROUPS

BTEXPANDGROUPSDOMAIN

BTFORCELOCATIONRESOLUTION

BTINATTOPT

BTINATTSKIPNAMES

BTINTERNALSMTPDOMAIN

BTKEEPPOSTED

Binary Tree Documentation

Accepted Value

1,2,4,8

Default Value

???

Log file should be relative to the <Domino server>\Domino Data Directory btws.nsf

\IBM_TECHNICAL_SUPPOR

T\OUTPUT.LOG btws.nsf

<number>

??

COEX

2500

??

COEX

<Virtual directory used by the BTRouter on the Windows Coexistence server>

0/1

BTAvailability

0

0 0/1

<number> 60

Y Y/N

<mailbox name> Required

Required <domain name>

BTExchange.box Required

Required <SMTP address>

Y/N N

N Y/N

Y/N

<string>

N

None

0/1

0/1

<comma-separated filename patterns>

< SMTP domain,SMTP domain2>

Y/N

0

0

None

None

Y

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

108

NOTES.INI Parameters

BTLINKSOPTION

BTLOGCACHE

BTLOGCANCEL

BTLOGCONSOLE

BTLOGDIRECTORY

BTLOGICAL

BTLOGLEVEL

BTLOGPNG

BTLOGRMB

BTLOGSTATS

BTLOGUIF

BTLOGWMBP

BTMULTISCHEDREPORTADDRESS

BTMULTISCHEDREPORTADDRESSTYPE

BTMULTISCHEDREPORTLEVEL

BTMULTISCHEDREPORTTEXTx

BTNONDRONQUIT

BTNDRFROMADDRESS

BTNOTESDOMAINS

Accepted Value

0/1

0/1

0/1

Y/N

<Windows path name>

0/1

0/1/2

0/1

0/1

0/1

0/1

0/1

<SMTP address>

0 or 1 or 2

1 or 2 or 4

BTMULTISCHEDREPORTTEXTx

0/1

<email address> or <common name>

<comma-separated domain names>

Binary Tree Documentation

Default Value

0

0

0

Y

0

0

0

Windows temp directory

0

0

0

0

None

0

1

Dear User,

The calendar pattern used in the invitation you sent is not supported at this time for the following reason:

%REASON%

Please reschedule using another pattern!

Original invitation information:

Subject: %SUBJECT%

Date: %DATE%

0

None

Required

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

109

Binary Tree Documentation

NOTES.INI Parameters

BTNOTIFYONDELEGATEORCO UNTER

BTONLINEMEETINGLABEL

Accepted Value

0/1

<text>

Default Value

0

None

BTORPHANDELAY

BTINMESSAGEMAX

BTPARTIALTEXT

BTPRESERVEATTACHMENTS

BTPROCESSDOMAIN

BTRECIPCONVERTFIELD

BTRECURRENCELIMIT

BTRESOLVENDRRECIPIENTS

BTRESOLVENDRRECIPIENTSDOMAIN

BTRETRYLIMIT

<number>

0/<any number greater than 0>

<text>

0/1

<SMTP domain> shortname/internetaddress local/internetaddress-full

<number>

Y/N

<string>

<number>

300

100

Room/Resource is already booked for the following date(s). You must use another time or find another resource.

1

Required shortname

1200

N

None

10

BTRETRYLIMITTEXTx

BTRETRYSENDNDR

BTSENDEXPANDED

BTSTATSDB

<text>

0/1

Y/N

<database name>

None

0

Y

BTCALSTA.NSF

BTSTOREDB <database name> BTSTORE.NSF

BTSTORETEXTx <text of the custom e-mail to a recipient of a ZApp'ed e-mail>

<comma-separated list of markers>

None

None BTSUBJECTPREFIXMARKER

BTSUPPORTMULTIPLEDOMINODOMAINS 0/1 0

BTTRUNCATESUBJECT

BTWORKDIRECTORY

BTZAPPBYPASS

Y/N

<Windows path name>

0/1

N

Windows temp directory

0

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

110

Binary Tree Documentation

NOTES.INI Parameters

BTZAPPBYPASSDOCSWITHFIELDS

BTZAPPCHECKENCRYPT

Accepted Value

<comma-separated list of field names>

0/1

Default Value

None

1

BTZAPPCOMBINEENCRYPTEDCALENDAR

BTZAPPENCRYPTTEXT

BTZAPPFIELDSx

BTZAPPIGNOREALLFORMS

BTZAPPIGNOREELEMENTS

BTZAPPIGNOREFORMS

BTZAPPIGNORESTOREDFORMS

BTZAPPINCLUDEFULLDISTRIBUTION

0/1

0/1/2

<comma separated list of field:value pairs>

0/1 0

<comma-separated list of element names> allnonstandard/<comma separated list of form names>

0/1

None

None

0

0/1 0

1

Contents of this document are encrypted with a

Notes certificate and cannot be read.

None

BTZAPPKEEPATTACHMENTS

BTZAPPORGS/BTZAPPORGSx

BTZAPPPDB

BTZAPPPROCESSFORMS

0/1

<comma-separated list of org units>

<database name>

<comma-separated list of form names>

0

None

BTZAPP.NSF

None

BTZAPPREADERS

BTZAPPRENDERSTOREDFORMS

BTZAPPSENDORIGINAL

<Domino address>

0/1

0/1/2/3

None

0

0

BTZAPPSUPPORT

BTZAPPTABLES

BTZAPPTEMPLATE

BTZAPPUNIQUECOPY

BTZAPPUSERFORMS

EXTMGR_ADDINS

0/1/2/3

Y/N

<database template name>

Y/N

<list of non-standard form names separated by commas>/All/None

0

N

Required if

BTZAPPSUPPORT=2 or 3

Y

None

BTEx

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

111

NOTES.INI Parameters

MIMEFORCEATTACHMENTS

Accepted Value

??

Binary Tree Documentation

Default Value

??

Appendix E: Processing Repeating Meetings

Overview

Lotus Notes / Domino and Microsoft Outlook / Exchange provide to end-users an extensive list of features and functions in the area of repeating/recurring calendar events, specifically, meetings. While the overall concept and interface are fairly similar in both environments, the technical implementation of the functionality is dramatically different between the two. From a simple difference in terminology (Exchange uses the term recurring while

Domino uses the term repeating, when referring to multi -instance calendar events) to the radically different approach of managing recurrence patterns, changes to individual or multiple occurrences, the disparity makes it sometimes impossible to transparently represent repeating/recurring meeting workflow in a mixed messagin g environment.

When traditional SMTP transport is used to exchange repeating/recurring meeting invitations, updates, cancellations and responses between Lotus Notes and Microsoft Outlook users, a number of common functions do not work. Notes Integration | CMT enhances the interchange of calendar functionality to ensure the highest level of fidelity in workflow of single instance and repeating/recurring meetings in a cross -platform environment.

The following table provides a high-level illustration of functionality enhancement delivered by Notes Integration |

CMT as compared to pure SMTP:

In spite of Notes Integration | CMT advanced functionality, a smal l subset of one system’s functionality simply cannot be transparently supported by another. The limitation is not caused by Notes Integration | CMT , but by mismatch in functionality between Microsoft Outlook and Lotus Notes calendars.

The negative impact may be either visual or functional; the former results in user inconvenience, the latter causes loss of functionality or even calendar data. In these rare cases, Notes Integration | CMT is able to recognize the conditions that may create a negative impact on users and stop them from reaching their intended destination while sending a customizable report to the originator and/or an administrator informing them of the problem and suggesting corrective action.

The remainder of this document provides details of how Notes Integration | CMT handles repeating/recurring meetings in a mixed messaging environment.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

112

Binary Tree Documentation

Repeating Meetings from Lotus Notes

Supported Invitations

The Vast majority of patterns used in Lotus Notes to schedule repeating meetings are supported in a mixed environment. Supported repeating patterns include:

 Daily – every N days;

 Weekly – single or multiple days per week every N weeks;

 Monthly by Date – specific date of a month every N months;

 Monthly by Day – specific weekday of a month every N months;

 Yearly – specific date of a year every N years;

Meeting invitations with supported repeating patterns originating in Lotus Notes will be correctly delivered and applied to Microsoft Outlook calendars depending on whether Microsoft Outlook users accept, tentatively accept or decline these invitations.

Unsupported Invitations

A few Lotus Notes repeating patterns cannot be supported by Microsoft Outlook:

 Custom pattern – arbitrary collection of dates.

 All patterns (except for daily) that specify that meeting instances falling on a weekend should be moved or deleted (e.g. Move to Monday or Move to Nearest Weekday). The Lotus Notes Daily repeating meeting pattern will appear in Outlook as a Weekly repea ting meeting occurring on each day.

 Monthly by date with multiple dates of the month (e.g. 4th, 6th and 10th).

 Monthly by day with multiple days of the month (e.g. 1st Mon, 2nd Tue and 3rd Thu).

Supported Reschedules

Reschedules of a single instance of a repeating meeting as well as all instances of a repeating meeting are properly supported. Such reschedules will be correctly delivered and applied to Microsoft Outlook calendars depending on whether Microsoft Outlook users accept, tentatively accept or decl ine these reschedules.

Unsupported Reschedules

Updating or rescheduling all instances of a repeat meeting originating from Notes using the Monthly by Day pattern is not supported.

Reschedules of a subset of instances of a repeating meeting cannot be suppor ted by Microsoft Outlook. Such subsets are represented by “This instance and all previous instances” and “This instance and all future instances” options.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

113

Binary Tree Documentation

Confirming the entire series after confirming an instance from the series is not supported.

Supported Confirmations

Confirmations of a single instance of a repeating meeting as well as all instances of a repeating meeting are properly supported. Such confirmations will be delivered as reschedules and applied to Microsoft Outlook calendars depending on whether Microsoft Outlook users accept, tentatively accept, or decline them.

Unsupported Confirmations

Confirmations of a subset of instances of a repeating meeting cannot be supported by Microsoft Outlook. Such subsets are represented by “This instance and all previous instances” and “This instance and all future instances” options.

A confirmation of all instances is handled the same way as a reschedule of all instances.

Confirming the entire series after confirming an instance from the series is not supported.

Supported Updates

Updates to a single instance of a repeating meeting as well as all instances of a repeating meeting are properly supported. Such updates will be correctly delivered and applied to Microsoft Outlook calendars.

Unsupported Updates

Updates to a subset of instances of a repeating meeting cannot be supported by Microsoft Outlook. Such subsets are represented by “This instance and all previous instances” and “This instance and all future instances” options.

Supported Cancellations

Cancellations of a single instance of a repeating meeting as well as all instances of a repeating meeting are properly supported. Such reschedules will be correctly delivered and applied to Microsoft Outlook calendars.

Unsupported Cancellations

Cancellations of a subset of instances of a repeating meeting cannot be supported by Microsoft Outlook. Such subsets are represented by This instance and all previous instances and This instance and all future instances options.

Unsupported Room or Resource specified in the Room/Resource: field in a Meeting

When scheduling a meeting from Notes that contains both an Exchange Room/Resource and an Outlook user, if the Room or Resource is specified in the Room/Resource: field in the invitation, the Notes user will receive an

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

114

Binary Tree Documentation

NDR. This is because Outlook cannot support invitations containing a Room/Resource that are specified this way.

To include an Exchange Room/Resource successfully, it must be specified in the To: field instead.

Supported Removing Invitees from Repeat Meetings

Removing an Outlook invitee from one or all occurrences of a repeat meeting originated in Notes is supported.

Supported Actions by Outlook Users

Outlook users can propose a new time on a single instance of a repeating meeting that had previously been rescheduled.

Outlook users can decline a single instance of a repeating meeting that had previously been rescheduled.

Recurring Meetings from Microsoft Outlook

Supported Invitations

All patterns used in Microsoft Outlook to schedule repeating meetings for a defined date range or occurrences count are supported in the mixed environment. Supported repeating patterns include:

 Daily – every N days;

 Weekly – single or multiple days per week every N weeks;

 Monthly by Date – specific date of a month every N months;

 Monthly by Day – specific weekday of a month every N months (with End by);

 Yearly – specific date of a year every N years;

 Yearly – specific day of a month every N years;

Meeting invitations with supported repeating patterns originating in Microsoft Outlook will be correctly delivered and applied to Lotus Notes calendars depending on whether Lotus Notes users accept, tentatively accept, or decline these invitations.

Unsupported Invitations

Any recurrence pattern listed above with “No End Date” cannot be supported by Lotus Notes, since Lotus Notes does not have a corresponding feature.

Supported Reschedules

Reschedules of a single instance of a repeating meeting as well as all instances of a repeating meeting are properly supported. Such reschedules will be correctly delivered and applied to Lotus Notes calendars depending on whether Lotus Notes users accept, tentatively accept or decline these reschedules.

Reschedules will typically contain “Rescheduled” in the Subject line. Reschedules to single occurences that also include other changes, such as a location change, will include the other change in the Subject instead of

“Rescheduled”.

Unsupported Reschedules

Any change to the duration of the recurrence pattern, by increasing or decreasing the n umber of occurrences, or extending or curtailing the end date cannot be supported by Lotus Notes. Additionally, any change to the recurrence pattern itself. For example, changing from daily to weekly recurrence cannot be supported by Lotus

Notes.

Rescheduling the entire series after rescheduling an instance from the series is not supported.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

115

Binary Tree Documentation

The default behavior of BTCal is to assume all calendar updates coming from an Exchange chair to a

Domino participant where there is no information of the meeting in the BTCache database are valid and are delivered to the Domino participant. Note that this default behavior can bechanged by changing the

BTBLOCKUPDATENOCACHE parameter in the NOTES.INI file.

Supported Updates

Updates for a single instance of a repeating meeting as well as all instances of a repeating meeting are properly supported. Such updates will be correctly delivered and applied to Lotus Notes calendars when Lotus Notes users choose to update calendars.

Updates to the attachments will be noted as a description change in the Subject line. Location changes will be noted as a location change in the Subject line.

Supported Cancellations

Cancellations of a single instance of a repeating meeting as well as all instances of a repeating meeting are properly supported. Such reschedules will be correctly delivered and can be applied to Lotus Notes calendars.

Unsupported Cancellations

If an Outlook user schedules a recurring meeting that contains both a Notes Room/Resource and a Notes user, cancels a single occurrence of that recurring meeting, and then subsequently attempts to cancel the entire series,

BTCal will return an NDR to the Outlook user. This functionality is not supported.

Supported Adding/Removing Invitees

Adding Lotus Notes invitees to or removing Lotus Notes invitees from a Microsoft Outlook meeting is supported.

Handling Unsupported Events

Notes Integration | CMT can be configured either to look for problematic repeating/recurring meeting activities or to ignore them. In the case of the latter, all events will be allowed to proceed to their destinations untouched.

However, these unsupported events cause unexpected and unwanted calendar workflow behavior. Calendars are often not updated correctly without any indiction to the chairperson or invitees. In the case of the former, Notes

Integration | CMT will stop the problematic activity and send a fa ilure notification to the activity originator.

Optionally, Notes Integration | CMT can be configured to send a failure notification to a designated administrator or multiple administrators. The text of this delivery failure is also customizable using the

BTMULTISCHEDREPORTTEXTx NOTES.INI variable.

For example:

Dear User

You are performing an operation on a repeating/recurring meeting, which is not supported in a mixed environment. Unsupported functionality includes:

Scheduling or rescheduling one or more occurrence(s) of a meeting using an unsupported (complex) recurrence pattern.

Adding one or more invitees to a meeting, who reside in a different environment than yours.

Please cancel the original meeting and schedule a new one using a supported pattern.

Important Differences in Repeating Meeting Functionality between Notes and Outlook

There are several options in the Lotus Notes implementation of repeating meetings, which are not available in

Microsoft Outlook. Likewise, there are several options in the Microsoft Outlook implementation of repeating meetings, which are not available in Lotus Notes. When these options are used in scheduling or modifying a

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

116

Binary Tree Documentation repeating meeting, they will be intercepted and handled based on the configuration op tions described earlier in this document.

Unsupported Recurrence Pattern Originating in Lotus Notes

Yearly repeating meetings on the last day of the month, generated from Lotus Notes to Outlook, causes an unsupported meeting pattern message to be received in Outlook.

Modifying Meeting Subset in Lotus Notes

As stated earlier in the document, Lotus Notes supports rescheduling, update, confirmation and cancellation of a subset of repeating meeting instances defined as “This instance and all previous instances” and “This instance and all future instances”. Since these options do not have an equivalent in Microsoft Outlook, they cannot be supported as part of a cross -platform calendar workflow.

Extending or Altering Recurrence Pattern in Microsoft Outlook

As stated earlier in the document, Microsoft Outlook supports modification or extension of a recurrence pattern.

This functionality does not have an equivalent in Lotus Notes, therefore cannot be supported as part of a cross platform calendar workflow.

Recurrence Pattern with No End Date in Microsoft Outlook

As stated earlier in the document, Microsoft Outlook supports recurrence patterns without a defined end date.

This functionality does not have an equivalent in Lotus Notes, therefore cannot be supported as pa rt of a crossplatform calendar workflow.

Handling of the Entire Series Reschedule in Lotus Notes

Lotus Notes treats the rescheduling of the entire repeating meeting series as relative to any reschedules which have been previously made to any individual instance of the meeting. This functionality is described in the following example:

Original meeting:

 Repeating meeting was scheduled to start on Monday and repeat every day for 5 days from 9 A.M. to 9:15

A.M.

Subsequent individual modification events followed by reschedule of the entire series:

 Tuesday’s occurrence was rescheduled to take place from 10 A.M. to 10:15 A.M.

 Wednesday’s occurrence was rescheduled to take place from 8 A.M. to 8:30 A.M.

 Thursday’s occurrence was cancelled

 Then the entire meeting was rescheduled to take place from 1 P.M. to 1:15 P.M.

Resulting meeting dates/times:

Monday: 1 P.M. to 1:15 P.M.

Tuesday:

Wednesday:

Thursday:

Friday:

2 P.M. to 2:15 P.M.

12 noon to 12:30 P.M. no meeting

1 P.M. to 1:15 P.M.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

117

Binary Tree Documentation

Handling of the Entire Series Reschedule in Microsoft Outlook

Microsoft Outlook treats rescheduling of the entire repeating meeting series as an absolute event, ignoring any previously made changes to individual occurrences. This functionality is described in the following example:

Original meeting:

 Repeating meeting was scheduled to start on Monday and repeat every day for 5 days from 9 A.M. to 9:15

A.M.

Subsequent individual modification events followed by reschedule of the entire series:

 Tuesday’s occurrence was rescheduled to take place from 10 A.M. to 10:15 A.M.;

 Wednesday’s occurrence was rescheduled to take place from 8 A.M. to 8:30 A.M.;

 Thursday’s occurrence was cancelled;

 Then the entire meeting was rescheduled to take place from 1 P.M. to 1:15 P.M.

Resulting meeting dates/times:

Monday:

Tuesday:

Wednesday:

1 P.M. to 1:15 P.M.

1 P.M. to 1:15 P.M.

1 P.M. to 1:15 P.M.

Thursday: 1 P.M. to 1:15 P.M.

Friday: 1 P.M. to 1:15 P.M.

In another example of rescheduling repeating meetings, consider the following and its outcome.

Original meeting:

 An Outlook user schedules a repeating meeting to start on Monday and repeat every day for 5 days from

9 A.M. for an hour.

Subsequent individual modification events followed by reschedule of the entire series:

 Wednesday’s occurrence was rescheduled to take place from 1.00 P.M.

 Then the entire meeting was rescheduled to take place from 10.00 A.M. for an hour.

If the Outlook user used the Outlook client, then the Notes user will receive a message that the individual occurrence (Wednesday) has been canceled; and if the Outlook user used Outlook Web Access (OWA), then the

Notes user will receive a message that the Wednesdays’ meeting has been rescheduled to 1.00 P.M.

In both cases, an NDR will be returned to the Outlook originator stating that reschedul ing a series when an individual occurrence has already been rescheduled is not supported, and that the entire meeting should be canceled and rescheduled.

Summary

Although Notes Integration | CMT successfully remediates repeating/recurri ng meeting workflow for the vast majority of cross-platform calendar events, there are still examples of functionality that cannot be supported. The most important success factor of any coexistence infrastructure implementation is the proper setting of expectations among end-users. Considering that limitations for the infrastructure are minimal, properly informing end-users about such limitations will avoid negative perception and attitude toward the coexistence solution.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

118

Binary Tree Documentation

Appendix F: Deployment Quick Reference

Lotus Domino Configuration

Files Deployment

Ensure that nBTCal.exe, nBTCalL.exe, nBTCalF.exe, nbtex.dll files are copied to Lotus Domino directory.

NOTES.INI Parameters

See Appendix G.

Domino Routing Configuration Modifications

1. Foreign Domain Document

i.e. Exchange

Mail Information

Gateway server name: BTEXCHCONN/ACME

Gateway mail file name: btexchange.box

Calendar Information

Calendar server name: BTEXCHCONN/ACME

Calendar system:

2. Foreign SMTP Domain

btexchange.box i.e. exchange*.binarytree.com Domain name: ExchangeDirect

3. Server Configuration Document

SMTP used when sending messages outside of the local internet domain = Enabled

SMTP allowed within local internet domain = Disabled

Servers within the local Notes domain are reachable via SMTP over TCPIP = Always

MIME Tab

On the MIME tab navigate to the Conversion tab and then select the Outbound sub -tab. Enter the following information.

Return receipts: Enabled

Message content = from Notes to HTML

4. Server Connection

1. Connection type = SMTP

2. Source server = BTMail01/BinaryTree

3. Connect via = Direct Connection

4. Destination server = CMTC Mail

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

119

5. Destination domain = ExchangeSMTPDirect

6. SMTP MTA relay host = 167.105.2.155 “

7. Replication task = Disabled

8. Routing task = SMTP Mail Routing

9. Route at once if = 1 messages pending

10. Routing cost = 1

11. Connection = enabled

12. Connect at times = 12:00 AM to 11:59 PM

13. Repeat interval of = 60 minutes

Binary Tree Documentation

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

120

Binary Tree Documentation

Appendix G: Customizable Non Delivery Report (NDR)

Reason Codes

Notes Integration | CMT includes customizable reason codes displayed for Non Delivery Reports (NDR’s) sent by

BTCal. The default reason codes in the table below will be displayed as part of the message defined in the

BTMULTISCHEDREPORTTEXTx Notes.ini parameter by %reason%. The only exception is BTNDR22, which completely replaces the BTMULTISCHEDREPORTTEXTx.

The table below includes the default customizable reason codes in the Notes.ini file and valid keywords that can be used in the error message.

Default Reason Code Explanation

BTNDR1="Converting a single instance meeting to a recurring meeting cannot be supported between Exchange and Domino.

Please cancel the meeting and recreate it as a recurring meeting."

The Outlook user scheduled a single occurrence meeting and is now trying to convert it to a recurring meeting.

BTNDR2=" Rescheduling an entire series of a recurring meeting that contains a Domino

Room or Resource cannot be supported between Exchange and Domino. Please cancel and recreate the meeting."

The Outlook user attempted to reschedule the entire series of a meeting that contains a Domino

Room or Resource.

BTNDR3="Canceling an entire series of a recurring meeting that contains a Domino

Room or Resource after a single occurrence has been cancelled cannot be supported between Exchange and Domino. Please notify all participants that they should delete the meeting from their calendars.

The Room or Resource reservation must also be manually deleted from the

Resource Reservations database.”

The Outlook user attempted to cancel the series that contains a

Domino Room or Resource but had previously canceled a single occurrence of the series.

The Outlook User scheduled a recurring meeting to occur on the zero day of each month. This appears to have been a bug in one or more versions of Outlook 2007.

BTNDR4="You have specified that this recurring meeting should occur on the “0”

(zero) day of each month, which cannot be supported by Domino. Please cancel and recreate the meeting using a value between 1-28 (the 29th, 30th and 31st days of each month are also not supported as not every month contains more than 28 days).”

BTNDR5="You have specified that this recurring meeting should occur on the

29th, 30th or 31st day of each month, which cannot be supported by Domino, because not every month contains more than 28 days. Please cancel and recreate the meeting using a value between 1-28”

The Outlook User scheduled a recurring meeting to occur on either the 29th, 30th or 31st day of each month. This is not supported by Notes.

Valid Keywords

%RULE%

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

121

Binary Tree Documentation

Default Reason Code Explanation

BTNDR6="You have specified that this recurring meeting should occur on the

29th, 30th or 31st day of each month, which cannot be supported by Domino, because not every month contains more than 28 days. Please cancel and recreate the meeting using a value between 1-28.”

BTNDR7="Creating a recurring meeting with no end date cannot be supported by

Domino. Please cancel and recreate the meeting specifying an end date or number of occurrences.”

BTNDR8="Creating a recurring meeting that is scheduled to continue past 2037 cannot be supported by Domino. Please cancel and recreate the meeting so the series ends before the year 2037."

The Outlook User scheduled a recurring meeting to occur on either the 29th, 30th or 31st day of each month. This is not supported by Notes.

The Outlook user scheduled a recurring meeting with no end date, which cannot be supported by all versions of Domino and

Notes.

The Outlook user tried to schedule a recurring meeting that will go past year 2037.

BTNDR9="Creating a recurring meeting with over 1200 instances cannot be supported by Domino. Please cancel and recreate the meeting with fewer than 1200 instances."

The Outlook user specified a recurring meeting that contains too many dates. By default, Notes

Integration | CMT will only support

1200 meetings for a recurring meeting. This is configurable via the BTRecurrenceLimit parameter.

If the expanded list of individual meetings exceeds this limit, this error will be returned.

BTNDR10="Rescheduling the entire series of a meeting after one or more occurrences have been rescheduled cannot be supported between Exchange and

Domino. Please cancel and recreate the entire meeting series.”

The Outlook user rescheduled a single occurrence of a recurring meeting, and is now trying to reschedule the entire series.

BTNDR11="The recurring meeting contains a larger number of instances than can be supported between Exchange and Domino.

Please cancel and recreate the meeting with fewer instances.”

The Outlook user specified a recurring meeting that contains too many dates. For recurring meetings, the RRULE from the ICS file is expanded into a list of individual date/times for the meeting. These are stored in a 32K buffer. Too many dates and will overflow this buffer and this error will be returned.

BTNDR12="Creating a recurring meeting with a date in the “Until” field that is before the first meeting date cannot be supported by Domino. Please cancel and recreate the meeting with valid dates.”

The Outlook user specified an

“UNTIL” date/time that preceded the first date/time of the meeting.

This appears to have been a bug in one or more versions of Outlook

2007.

Valid Keywords

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

122

Binary Tree Documentation

Default Reason Code Explanation

BTNDR13="There was an internal processing issue that should be reported to

IT Support as an invalid cache document.

Please cancel and recreate the meeting.”

There were problems with the cache document for the meeting, such as it could not be opened or a specific field could not be found.

BTNDR14="Your meeting update could not be processed due to an uncorrectable error. Please cancel the entire meeting and recreate it.”

This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce, or determine the root cause.

BTNDR15="Your meeting update could not be processed due to an uncorrectable error. Please cancel the entire meeting and recreate it.”

This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce, or determine the root cause.

BTNDR16="Your meeting update could not be processed due to an uncorrectable error. Please cancel the entire meeting and recreate it.”

This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce. Notes

Integration | CMT expands the

RRULE for a recurring meeting into a series of RDATES, with each

RDATE representing a single instance of the recurring meeting.

While trying to do this, one of the parameters taken from the ICS file is invalid.

BTNDR17="Your meeting update could not be processed due to an uncorrectable error. Please cancel the entire meeting and recreate it.”

This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce, or determine the root cause.

BTNDR18="Changing the recurrence pattern of the meeting cannot be supported by Domino. Please cancel and recreate the entire series.”

BTNDR19="Changing the entire series of a recurring meeting after one or more instances of that meeting have been changed cannot be supported between

Exchange and Domino. Please cancel and recreate the meeting.”

You cannot change the original definition of the meeting occurrences. For example, you cannot schedule a recurring meeting in Outlook for Monday-

Friday, and then change the recurrence pattern to start on

Wednesday and continue for 3 days.

For recurring meetings between

Exchange and Domino, you cannot change the entire series after an instance of the meeting has been changed.

Valid Keywords

%RULE%

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

123

Binary Tree Documentation

Default Reason Code Explanation

BTNDR20="The number of updates made to this meeting exceeds the limit supported between Domino and Exchange. Please cancel the meeting and recreate it.”

In the ICS file, a VEVENT is used to define a calendar event. Notes

Integration | CMT does not support more than one VEVENT in a single ICS file.

BTNDR21="Your meeting update could not be processed due to an uncorrectable error. Please cancel the (entire) meeting and recreate it.”

The ICS file is encoded in MIME as

Quoted Printable Text. This is not a supported type. This is defensive code for a scenario found in a customer's production environment. Although we had the offensive ICS file, we were not able to reproduce, or determine the root cause.

BTNDR22="Dear User,\r\n\r\nThe delegation (forwarding) of your invitation is not currently supported.\r\nPlease request that the chairperson invite the intended delegate.\r\n\r\nOriginal invitation information:\r\n\r\n\tSubject:

%SUBJECT%\r\n\tDate: %DATE%\r\n”

An Exchange user is invited to a meeting and delegates (forwards) that meeting to a Domino user.

Meeting delegation functions differently between Domino and

Exchange and cannot be supported.

BTNDR23="Creating a recurring meeting with the option to move it if it occurs on a non-workday can only be supported if the meeting is a daily meeting. Please cancel and recreate the meeting specifying Don’t

Move if the meeting occurs on a nonworkday.”

The Notes user specified to move the meeting if it occurs on weekend for a non-daily recurring meeting. The Notes user can only choose “Don’t move”.

BTNDR24="Adding an Exchange user to an existing meeting cannot be supported between Domino and Exchange. Please cancel and recreate the meeting with the appropriate invitees.”

BTNDR25="Creating a meeting that occurs monthly by date, and selecting more than one date per month cannot be supported by Exchange. Please cancel and recreate the meeting using one date per month, or use an alternative recurring pattern.”

The Domino user added an

Exchange user(s) to an existing meeting. This can only be supported if GRIP is configured in the coexistent environment.

The Notes user specified more than one date when choosing the

Monthly by Date option. The

Notes user can only choose one date.

BTNDR26="Creating a meeting that occurs monthly by day, and selecting more than one day per month cannot be supported by

Exchange. Please cancel and recreate the meeting using one day per month, or use an alternative recurrence pattern.”

The Notes user specified more than one day when choosing the

Monthly by Date option. The

Notes user can only choose one day.

BTNDR27="Rescheduling an instance of a meeting to occur after another scheduled instance of the series cannot be supported between Domino and Exchange. Please cancel and recreate the meeting series.”

The Domino user tried to reschedule an instance of a recurring meeting after another scheduled occurrence.

Valid Keywords

%SUBJECT%, %DATE%

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

124

Binary Tree Documentation

Default Reason Code Explanation

BTNDR28="Rescheduling an instance of a meeting to occur before another scheduled instance of the series cannot be supported between Domino and Exchange. Please cancel and recreate the meeting series.”

The Notes user tried to reschedule an instance of a recurring meeting before another scheduled occurrence.

BTNDR29="Exchange Rooms and Resource must be placed in the “To:” fiel d to ensure proper functionality.”

BTNDR30="Exchange Rooms and Resource must be placed in the “To:” field to ensure proper functionality.”

The Domino user tried to schedule a meeting and specified an

Exchange resource in the Resource field. Exchange resources must be added in the “To:” field.

The Domino user tried to schedule a meeting and specified an

Exchange room in the Room field.

Exchange resources must be added in the “To:” field.

BTNDR31="Rescheduling a recurring meeting and specifying that the reschedule applies to “This instance and all previous instances” or “This instance and all future instances” cannot be supported between

Domino and Exchange. Please cancel and recreate the meeting.”

The Domino user specified either

“This instance and all previous instances” or “This instance and all future instances” when rescheduling a meeting. This is not supported. The Notes user can only reschedule the entire series or just a single occurrence.

BTNDR32="Creating a recurring meeting using a custom recurrence pattern cannot be supported by Exchange. Please cancel and recreate the meeting using a noncustom recurrence pattern.”

The Notes user specified a recurring meeting using custom dates.

BTNDR33="This email cannot be processed by the system that manages coexistence between Domino and Exchange, because the domain (@domain.com) is not configured. Please report this to your technical support organization.”

The Domino user attempted to send a mail item to a Foreign

Domain that is not configured for

BTExchangeDomain or

BTAltExchangeDomains.

BTNDR34="Rescheduling the entire series of a meeting after one or more occurrences have been rescheduled cannot be supported between Domino and

Exchange. Please cancel and recreate the entire series.”

The Domino user rescheduled one or more individual occurrences of a recurring meeting, and is now trying to reschedule the entire series.

BTNDR35="Rescheduling a recurring meeting using the Monthly by Day recurrence pattern cannot be supported between Domino and Exchange. Please cancel and recreate the meeting using an alternative recurrence pattern.”

The Domino user attempted to reschedule a meeting using the

Month by Day option.

Valid Keywords

%RESOURCENAME%

%ROOMNAME%

%DOMAINNAME%

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

125

Binary Tree Documentation

Default Reason Code Explanation

BTNDR36="Adding an Exchange user to this meeting cannot be supported, because there have been too many changes to the meeting. Please cancel and recreate the meeting.”

The Domino user attempted to add Exchange users to an existing meeting and the number of exceptions exceeds

BTAddUserExceptionsMax. This required GRIP to be configured.

BTNDR37="Your attempt to add an

Exchange user to this meeting could not be processed at this time. Please cancel and create the meeting with the appropriate invitees.”

The Domino user attempted to add Exchange users to an existing meeting and BTCal could not get the original invitation information before BTAddUserDelayMax has expired. This could be due to network or server issues. This required GRIP to be configured.

BTNDR38="Adding an Exchange user to this meeting cannot be supported, because there have been too many changes to the meeting. Please cancel and recreate the meeting.”

The Domino user attempted to add Exchange users to an existing meeting that had exceptions and exceptions are not allowed. This requires GRIP to be configured.

BTNDR39="This meeting reschedule cannot be properly processed between Domino and Exchange. Please cancel and recreate the meeting.”

The Domino user attempted to reschedule a meeting, and BTCal could not find the meeting in the cache database. Cache.nsf may be corrupt, or the document may not be in the expected cache folder.

This is the same as BTNDR41, but in a different place in the code.

BTNDR40="This meeting reschedule cannot be properly processed between Domino and Exchange. Please cancel and recreate the meeting.”

The Domino user attempted to reschedule a meeting, and BTCal could not open the meeting in the cache database. Cache.nsf may be corrupt.

BTNDR41="This meeting reschedule cannot be properly processed between Domino and Exchange. Please cancel and recreate the meeting.”

The Domino user attempted to reschedule a meeting, and BTCal could not find the meeting in the cache database. Cache.nsf may be corrupt, or the document may not be in the expected cache folder.

This is the same as BTNDR39, but in a different place in the code.

BTNDR47=" This meeting change cannot be supported between Outlook and Lotus

Notes. Please cancel and recreate the meeting to ensure that the Lotus Notes invitees are properly updated."

The meeting between Outlook and

Lotus Notes cannot be opened in

BTCache.

BTNDR49= "An encrypted copy of the message could not be delivered to the following Domino Group(s):

%GROUPLIST%.\r\nPlease re - send the message using individual recipients."

An encrypted copy of the message could not be delivered to the listed

Domino Groups.

Valid Keywords

%EXCEPTIONCOUNT%

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

126

Binary Tree Documentation

Default Reason Code Explanation

BTNDR50= "An encrypted copy of the message could not be created for the following Notes recipient(s):

%RECIPIENTS%.\r\nPlease contact the

HelpDesk."

BTNDR51= "An encrypted copy of the message could not be delivered to the following Notes recipient(s) :

%RECIPIENTS%.\r\nPlease contact the

HelpDesk."

BTNDR52= "This meeting contains more text than BTCal can process for Domino users.\r\nPlease recreate it using less than

25K of text."

An encrypted copy of the message could not be created for the listed

Notes recipients because there was not a Public Key in their

Person Document.

An encrypted copy of the message could not be delivered to the listed

Notes recipients because the

Public Key was not valid.

The meeting contains more than

25K of text.

Valid Keywords

To customize the text of a reason code add BTNDR##= to the Notes.ini followed by your custom text

Examples:

 BTNDR30=This is a custom reason code, using the keyword for a room %ROOMNAME%

 For reason codes requiring more than one line of text, append “.#” to the notes.ini parameter. As with

BTMULTISCHEDREPORTTEXTx, \n and \t must be used to insert the end on the line of text and a tab

(respectively). For example:

BTNDR29.1=first line of the reason code text\n

BTNDR29.2=the second line of the reason code text\n

BTNDR29.3=the third line of the reason code text\n

BTNDR29.4=the fourth line of the reason code text\n

There is no limit on the number of lines a message may span; however, there is a 64K size limit for all lines of text combined.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

127

Binary Tree Documentation

Appendix H: Cross Platform Delegation

This section describes how calendar delegation behaves between Domino and Exchange, as well as what remediation options are available in CMTC.

There are two types of delegation; delegating a meeting to another person, and delegating calendar privileges to another person.

In Domino, you may delegate a meeting to another person by selecting Delegate under the Participant Actions dropdown menu. Although there is an option to be kept informed of updates, the act of delegating in this scenario general means that the original invitee is no longer invited to the meeting.

In Exchange, a similar result is achieved by forwarding a meeting to another person. In this scena rio, the original invitee continues to be a full participant of the meeting.

Despite the similarities of these actions, the internal processing is quite different and it is not possible to achieve fully transparent functionality across platforms. The below table outlines the expected behavior of delegating/forwarding meetings in a Coexistent environment.

There are six different general scenarios for cross -platform delegation:

1. Notes Chairperson invites Notes User who delegates to an Outlook User

2. Notes Chairperson invites Outlook User who delegates to a Notes User

3. Notes Chairperson invites Outlook User who delegates to an Outlook User

4. Outlook Chairperson invites Outlook User who delegates to a Notes User

5. Outlook Chairperson invites Notes User who delegates to an Outlook User

6. Outlook Chairperson invites Notes User who delegates to a Notes User

For purposes of this document, the following terms will be used:

 Delegator - the person who delegates a meeting to another user

 Delegate - the person to whom the meeting is delegated

Notes Integration | CMT can be configured to detect forwarded invitations from Exchange to Domino, and to return an NDR when found. This is the recommended behavior. This feature is enabled via the BTDelegateNDR parameter. The parameter accepts a value of Y or N, with Y being the default. Therefore, by default, this feature is enabled.

Notes Chairperson invites Notes User who delegates to an Outlook User

In this scenario, delegation functions as expected. The chairperson is notified, and the Outlook delegate is an invitee of the meeting. There is no action taken by Notes Integration | CMT.

Notes Chairperson invites Outlook User who delegates to a Notes User

In this scenario, when the Outlook User forwards the meeting to a Notes User, an NDR will be returned to the

Outlook User. The NDR instructs the user to notify the Chairperson that the attempted delegate should be added to the meeting. Once the delegate is added to the meeting, workflow functions as expected for an invitee.

Note: If BTDelegateNDR=N, the Domino delegate will receive the forwarded meeting, and can accept the meeting.

However; any updates to the meeting will appear as a new meeting and workflow will not function properly.

Depending on the meeting type and the changes made, the results can be duplicate calendar entries, deleted calendar entries, missing meeting updates and un-actionable meeting updates.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

128

Binary Tree Documentation

Notes Chairperson invites Outlook User who delegates to an Outlook User

When the Outlook delegate acts on the invitation (accept/decline), he becomes an unknown invitee of the meeting. The Notes Chairperson’s calendar will not be updated, and no subsequent workflow is ever sent to him.

Subsequent workflow (reschedules/cancels) is only sent to the delegator. For the delegate to receive any subsequent workflow, the delegator must continue to forward any meeting notifications.

Since the forwarding action is restricted to the Exchange system, Notes Integration | CMT cannot take any action to remediate the result.

Note: If the Outlook recipient has configured the second Outlook User as a delegate to their calendar, forwarding will work as expected.

Outlook Chairperson invites Outlook User who delegates to a Notes User

In this scenario, when the Outlook User forwards the meeting to a Notes User, an NDR will be returned to the

Outlook User. The NDR instructs the user to notify the Chairperson that the attempted delegate should be added to the meeting. Once the delegate is added to the meeting, workflow functions as expected for an invitee.

Note: If BTDelegateNDR=N, the Notes delegate can accept the forwarded meeting invitation. The Outlook chairperson is correctly notifi ed, and the Notes delegate is added as an optional attendee. Although this scenario functions as expected, Binary Tree still recommends that BTDelegateNDR be set to Y to prevent Outlook users from forwarding invitations chaired by Notes users. There is no identifying information in forwarded calendar items from Exchange to Domino that can discern the mail system of the chairperson.

Outlook Chairperson invites Notes User who delegates to an Outlook User

In this scenario, the following issues will occur:

 When the Outlook delegate accepts the invitation, he becomes an optional invitee of the meeting.

 The Outlook Chairperson receives the delegation notice, which is interpreted it as a tentative acceptance from the Notes delegator. The Notes delegator is still seen as a required invitee.

 Subsequent workflow (reschedules/cancels) will be sent to both the delegator and the delegate.

 When the Notes delegator receives the subsequent workflow, he cannot act on them (since it was delegated to another user).

Note: There is no identifying information in the delegated item sent from Domino to Exchange that would enable

Notes Integration | CMT to take remediation action.

Outlook Chairperson invites Notes User who delegates to a Notes User

In this scenario, the following issues will occur:

 When the Notes delegate accepts the invitation, he becomes an optional invitee of the meeting.

 The Outlook Chairperson receives the delegation notice, which interpreted as a tentative acceptance from the Notes delegator. The Notes delegator is still seen as a required invitee.

 Subsequent workflow (reschedules/cancels) will be sent to both the delegator and the delegate.

However, the Notes delegator cannot act on them (since it was delegated to another user).

 When the Notes delegate receives subsequent workflow (e.g., reschedule), it is treated as a new meeting.

Therefore, both the original meeting and the rescheduled meeting appear on the delegate’s calendar.

Since the forwarding action is restricted to the Domino system, Notes Integration | CMT cannot take any action to remediate the result.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

129

Binary Tree Documentation

Appendix I: BTCache Database Purging and Archiving

BTCache supports the ability to purge or archive calendar documents that are no longer needed. Automatic purging and archiving of cache documents are based on the $BTPurgeDate field, which is automatically set to the last occurrence of a repeating meeting

To allow database purging or archiving of the cache.nsf, purge dates (BTPurgeDate) are added to the cache meeting documents originating from both Notes and Outlook. The BTPurgeDate is set to the end date/time of the last occurrence in an invitation. For rescheduled repeating meetings, the last occurrence date/time is compared with the BTPurgeDate in the cache and the BTPurgeDate is updated if the new date/time is greater. For a rescheduled single occurrence meeting, BTPurgeDate is updated to the end date/time of the reschedule.

There are two methods for setting the BTPurgeDate:

 A scheduled agent runs daily at 1AM to automatically set the value

 A manual agent can be run from the actions menu

Purge Settings

Click on Settings at the top of the navigator.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

130

Binary Tree Documentation

Configure the following settings to purge documents:

 Status – Enabled/Disabled. Click the Enable button to enable the agent.

 Number of Days - The number of days after $BTPurgeDate to delete the document(s).

 Purge Options – Select Delete to have the documents deleted from the cache database, or archive to have the documents archived to another Notes database. If you will select Archive, you must also populate the following fields: o Archive DB Path – The Cache Archive database path where the documents will be copied. Click the Select DB button to choose a DB.

Note: The archive database must use the btcache template o Archive Server – The Domino Server where Cache Archive will reside.

Setting $BTPurgeDate on documents

The following two agents are available in the cache database to set $BTPurgeDate on documents that do not have the field.

 From the menu, Actions\Binary Tree\Set Purge Dates - Where ever possible, this agent will create

$BTPurgeDate based on the date arrays in the cache document.

 From the navigator view click Missing Purge Date, and then Manually Set Purge Date on Selected - This agent prompts for a date and then sets $BTPurgeDate on the selected documents to the date entered.

This should be used with care since you cannot verify the end date of the meetings selected.

Note the following limitations:

 Meeting cancellations do not update BTPurgeDate.

 Response cache documents (those with Lotus_Notes_Generated on the end of the

UID) will not have a purge date set. The cleanup agent will have to find these documents based on the UID in the Notes to Exchange cache document.

 BTPurgeDate for repeating meetings will never be smaller than the original end date/time.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

131

Binary Tree Documentation

Appendix J: On the Fly Decryption and Encryption

On the Fly Decryption and Encryption is an advanced feature in Notes Integration | CMT that will automatically decrypt messages sent from Domino to Exchange, and encrypt messages sent from Exchange to Domino, usi ng standard Domino encryption.

For Decrypting mail there are two deployment options:

The first option is to use the Notes Integration | CMT database BTIDCache.nsf, where the system can be configured in several scenarios, from using the IBM IDVault to using the ID and pass word 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 fi eld of that item. Notes Integration | CMT 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.

Notes Integration | CMT 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.

Prerequisites & Settings

Decryption Option 1 (Recommended)

 Creation of the BTIDCache Database in the Notes Integration | CMT Domino Data Directory using the installed template.

 Configure the database. See the Configuration of the Domino Database section below for more information.

 Preferred configuration is to use the IBM IDVault database.

 The following Notes.ini values must be configured on all Domino Coexistence servers: o BTEncryptDecrypt=1



0 - disabled (default)



1 - encrypt and decrypt



2 - decrypt only



3 - encrypt only o BTIDVault=1



0 - disabled (default)



1 – Enabled

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

132

Binary Tree Documentation o BTIDFileLocation= BTIDVaultDB



BTIDVaultDB (default) – Uses the BTIDVault database which will store the users ID and password.



FileSystem – Uses a central file share repository that holds all backup copy of the user’s

ID files. The password will be stored in the BTIDVaultDB.



PersonDoc – Backup copy of the ID files will be stored in the person docs with in the

Domino Directory. Password for the ID files will be stored in the BTIDVaultDB.



DominoIDV – Backup copy of the ID Files will be stored in the I BM IDVault Database, with the corresponding passwords in the BTIDVaultDB.



DominoIDV2 – The users ID in the Domino IDVault Database, and the corresponding password will be provided Automatically by the Domino API. For this configuration option, the “Check Password setting in the senders person doc must be set to “don’t check password”.



PerUser – This option allows the configuration to be done at the user level individually selecting the first five options. o BTIDVaultDB= This variable sets the file name for the BTIDVault Notes Database o BTIDsDir= This variable sets the path information of the Senders notes ID when the

BTIDFileLocation=FileSystem o If using any options but DominoIDV2 in the INI setting “BTIDFileLocation”, user information will need to be gathered for each user. The following explains how this will be accomplished with the databse defined in the BTIDVaultDB INI setting.

Decryption Option 2

 The mail file template for all Domino users must be modified so that any time a message is marked for encryption, the Domino user account used for On the Fly Decryption and Encryption is added to the BCC field. This account should be an administrative account with a valid ID, password and certificate.

 The Domino user account used for On the Fly Decryption and Encryption must a valid Notes Certificate in their Person Document in the Domino Directory, but it does not need a mail file associated to it.

 The Domino user account ID file used for On the Fly Decryption and Encryption must be on all Domino

Coexistence servers. The password for this ID may be stored in the Notes.ini or in a text file the Domino

Coexistence server(s).

 All Exchange Recipients must also have a valid Notes Certificate in their Person Document in the Domino

Directory.

 The following Notes.ini values must be configured on all Domino Coexistence servers: o BTEncryptDecrypt=1



0 - disabled (default)



1 - encrypt and decrypt



2 - decrypt only



3 - encrypt only

Note: the last two values do not have a use at present and are broken out in case they are needed for future use cases o BTDecryptID=<ID file name, full pathname if not in the Data folder>

This is the ID file that is associated with the user account that i s added to the BCC field of encrypted messages (from Domino to Exchange) o BTDecryptEmail=<Notes distinguished name for the account used for on-the-fly encryption/decryption> o BTDecryptPasswordFile=<full path and file name>

Use this ini parameter if you wi ll be storing the password for the BTDecrypt ID in a text file. This

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

133

Binary Tree Documentation must be a plain text file that contains nothing but the password for the BTDecrypt ID file. OS security can be enabled on this file, as long as done with windows server account used by th e

Domino server. o BTDecryptPassword=<password for the account used for on-the-fly encryption/decryption>

Use this option is you will be storing the password for the BTDecrypt ID in the Notes.ini file.

Encryption Options

 BTEncryptDecrypt=1 o 0 - disabled (default) o 1 - encrypt and decrypt o 2 - decrypt only o 3 - encrypt only

Note: the last two values do not have a use at present and are broken out in case they are needed for future use cases

This setting must be set even if the BTIDVaultDB is being used.

 BTDominoEncryptDomains= This is a multivalue, comma separated parameter that should contains a list of Domino domains to be included is processing On the Fly Decryption and Encryption.

 BTCalTargetAddressPrefix=domino.

This is the value that is prepended to the SMTP address when creating the TargetAddress. The above value is a typical example (domino.). Note the value ends with a period, since that too is prefixed to the base smtp address for Domino users - as happens when the AD SMTP address of

"[email protected]" is stored in the AD targetAddress as a value of

"[email protected]" )

 BTLeaveKeepPrivate=0/1 (default=0) o When set to 0, Notes Integration | CMT will delete the $KeepPrivate item, which allows the

Notes user to reply with history or forward to the encrypted memo, as well as respond to calendar items. (Recommended) o When this is set to 1, $KeepPrivate will remain in place, which result in not being able to reply with history, forward or res pond to calendar items. o This setting will override SMTP_NO_MAP_PERSONAL, SMTP_NO_MAP_PRIVATE and

SMTP_NO_MAP_COMPCONF. Please refer to this IBM technote for more information on these settings: http://www-01.ibm.com/support/docview.wss?uid=swg21417429 o If this is set to 1, the chairperson will receive an NDR from any Domino rooms or resources in the invitation.

 BTScanSubjectForEncryptFlag=1 o If set to 1, Notes Integration | CMT will encrypt any item that has the value of BTScanSubjectFlag in the subject of the message. This allows Exchange users to encrypt items from mobile devices. o If set to 0, Notes Integration | CMT will not encrypt any items based on the subject content.

 BTScanSubjectFlag=<text> o This value is used to allow Exchange mobile users to put a keyword in the subject of an email to have that message encrypted. This should be unique text that will not be used accidentally. This value is case insensitive.

 BTEXPANDCALGROUPS=N

 BTEXPANDMAILGROUPS=N

 BTEXPANDGROUPS=N o The three existing INI parameters defined when mail group membership is expanded during the routing process.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

134

Binary Tree Documentation o If these are set to N (no), On the Fly Decryption and Encryption requires that groups be synched, or represented as member-populated groups in the target directories. If groups are represented as Contacts (Exchange), or as Person documents (Domino), sending encrypted message to the group will result in an DNR (see NDR49) o If these are set to Y (yes), groups will be expanded prior to the decryption/encryption process, so they will be decrypted or encrypted as expected. o It is strongly recommended that you investigate how these setting will impact your messaging environment before you make any changes.

Customizable NDR’s

 As with other Notes Integration | CMT NDR messages, there is a single customizable message, and 4 customizable encrypt NDR’s reasons. The default text is listed below. These are customized in the same manner as any BTNDR text.

BTENCRYPTFAILTEXT - multiline, supplies the generic NDR email text.

Example:

BTENCRYPTFAILTEXT1=There was a problem delivering your message to a Lotus Notes user, group, or mailbox.\n\n

BTENCRYPTFAILTEXT2=%REASON%\n\n

BTENCRYPTFAILTEXT3=Thank you for giving this matter your prompt attention.\n

If not supplied in Notes.ini, it defaults to the values used in the first 2 lines above.

 BTNDR49: "An encrypted copy of the message could not be delivered to the following Domino Group(s):

%GROUPLIST%.\r\nPlease re - send the message using individual recipients."

 BTNDR50: "An encrypted copy of the message could not be created for the following Notes recipient(s):

%RECIPIENTS%.\r\nPlease contact the HelpDesk."

 BTNDR51: "An encrypted copy of the message could not be delivered to the following Notes recipient(s) :

%RECIPIENTS%.\r\nPlease contact the HelpDesk."

 BTNDR52: "This meeting contains more text than BTCal can process for Domino users.\r\nPlease recreate it using less than 25K of text."

Configuration of the Domino Database

With the recommended option 1 of not using a customized mail template, the configuration will require the corresponding BTIDVaultDB to be deployed to all Notes Integration | CMT servers in a replicated model with the exception that the customer is using IBM Domino IDVault Database and it has been configured to allow applications to have access to the ID files. The following will cover how to deploy the database for all other scenarios:

Installing the BTIDVaultDB is a simple process of adding the template and creating a new BTIDVaul tDB.nsf in the

Domino Data directory.

Creating the ID Vault Database

1. After the installation of Notes Integration | CMT, you will see BTIDCache.ntf template in the Domino Data

Directory.

2. If you do not see the template in your data directory, reinstall Notes Integration | CMT.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

135

Binary Tree Documentation

3. The Coexistence server may need a restart to use the new databases created from the copied template files.

4. Create the BTIDVault.nsf from this template noting the file name as it will need to be added the INI parameter BTIDVaultDB and proceed with configuration.

Setting up Security for the BTIDVaultDB Database

Notes Integration | CMT uses a mail-in storage database to store all mail -enabled application messages in a single store repository that provides document level security and allows Exchange/Outlook users to access any applications during the coexistence period.

1. From the Coexistence server, open Domino Administration Client.

2. From the Domino Administrator, open the server, and then navigate to the Files tab as shown below, select Databases only from the Show Me: drop-down box.

3. Right-click BTIDVault.nsf.

4. Select Access Control > Manage to set up the ACL as shown below.

5. Because the database is new and not signed or secured, if you receive a prompt to cross -certify the signature as seen below, select Yes.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

136

Binary Tree Documentation

6. The ACL displays. Add the Domino Administrators for the domain or LocalDomainAdmin as shown below and click Add. From the Add User dialog box, select LocalDomainAdmin, and then click OK.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

137

Binary Tree Documentation

7. Change the user types to Person group for LocalDomainAdmins as shown below. Additionally, grant your

LocalDomainAdmins [Admin] role to view additional configuration options in the BTStore database.

8. Demote the Default group by giving it only Author without delete access. This database has document security and its own set of purging options, as you do not want users deleting documents even by mistake.

Configuring the Settings in the BTIDVault Database

Confirm the INI setting defined in the section Prerequisites & Settings/Decryption Option 1 (Recommended) and proceed with this database for all options in the INI parameter BTIDFileLocation except “DominoIDV2”.

Once in the database is opened expand in the left navigator the section Configuration and select Settings.

Configure the database as follows:

1. On the General Setting tab set the following values:

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

138

Binary Tree Documentation a. Coex Server Name – This is the Domino server that the users will be populated from. b. Domino Directory File Name – Domino Directory that the user record will be created from. c. Server Mailbox – Populate this with the Router mailbox tnat will be used to send messages from. d. Domino INI Setting Option - This should be set to the option set on the Domino COEXT server for the INI value BTIDFileLocation.

The options on the rest of the configuration and how the databse will interact with the user is depended on this setting.

e. Default Network Path - Enter the network path where the backup copy of the ID files are stored.

This can only be a single value entry is used if the INI settting is set to “File System” f. Default Password - Value set to Domino ID file on creation. g. Delete Process Messages - Since the database has the ability to send request for users to collect

ID and Password this option allow the cleanup of the responses if environment policy do not dictate that all electronic communication be saved. h. Web Host Name - The database has the ability to collect user information via email or a website.

The website can also be used to maintain the account information for the users. This is the URL for the database.

HTTP services will need to be configure on the Domino COEX server, and a DNS name registered in the customer’s environment if not using the Domino server name in the

URL.

i. Success Message - Message that will display when the user Successful perform an action via the website.

Mail-enabling BTIDVault Database

A Mail-in Database Document is required for mail to be delivered to the newly created BTIDVault database. The procedure copies the database to the server and creates a Mail -In database document for the Notes Migrator |

CMT database.

1. Create a mail-in database for BTIDVault database. Click on the Server Db Copy and Mail-In Db Doc button to create a copy of the BTIDVault database on the Domino server and configure the Mail in Database document

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

139

2. The Does BT IDVault already exist? dialog box opens. Click Yes (and skip to step 5).

Binary Tree Documentation

3. If you are working with a local copy of the BTIDVault database, then click No. The Create a db copy? dialog box opens.

4. Click Yes to create a copy of the local BTIDVault database on the server.

5. If you clicked Yes in the Does IDVaultDB already exist? dialog box, the Choose Application dialog box opens. Locate the Notes Migrator | CMT database in the CMT folder on the server, and then click Open.

6. The Fullname for the mail-in db doc dialog box confirms that the mail -in database for the selected serverbased BTIDVault database does not exist, and prompts you to specify a name for the mail -in database.

After specifying the name, click OK.

7. In the Open the new mail-in doc? dialog box, click Yes to open the mail-in database. a. The mail-in database document for BTIDVaultDB opens.

8. To verify the creation of the mail -in database, you can also launch Domino Administrator, open the

Domino server, and access the Mail-In Databases and Resources folder under the People & Groups tab.

9. Double-click the document to open and review.

10. Once the mail-in database is successfully created, the Open Mail-In Db Doc button replaces the Server Db

Copy and Mail-In Db Doc button. Clicking it opens the database document for a review. Clicking the button with the X sign on it will remove all pointers to the location of the mail -in database.

11. It is recommended that after copying the database to the server, you delete the database from the local client folder. To remove it, right-click on BTIDVaultDB on Local. Select Database, and then Delete. The

Lotus Notes client prompts that the database and related documents will be permanently deleted. Click

Yes to delete the local database.

Modifying the Inbound Processing Agent

Once you have mail -enabled the database, you need to modify the Inbound Processing agent to view the updates.

Perform the following steps to run the agent.

1. With Domino Designer open the BTIDVault database in Domino Designer.

2. Expand Shared Code and select Agents.

3. Select the InboundProcessing agent as shown below.

4. Double-click InboundProcessing to open the InboundProcessing Agent Properties.

5. Click the Security tab.

6. The Administrator should be listed in the Run on behalf of section.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

140

Binary Tree Documentation

7. In the Set Runtime security level: field, select Allow Restricted Operations with full administration

rights.

8. Once you've edited the agent, close the Properties box.

9. Close the Inbound Processing – Agent tab.

10. Save the changes.

11. Click Sign.

Message Templates

Message Templates can be used for communication with the end users via Notes mail messages. These messages can be used for informational purposes only or they may contain action buttons with associated code designed to perform specific tasks. These messages are created using the Message Templates.

1. Click Message Templates in the Navigation Pane. The Data Pane displays a list of predefined message templates.

Each predefined Message template has a specific purpose. If you wished to create a custom template based on a predefined template, you need to select the predefined template before clicking the New Template button.

2. Select a predefined template, and click the New Template button in the Data Pane.

3. A new tab opens and displays a form where you can specify the detail s of the new Message Template.

Notice that the tab clearly specifies that the new template is based on the predefined template. However, when you save this template with a new name, the tab will reflect its new name.

4. Customize the new template. Refer to the table below for details on settings.

5. Once all the details have been specified, click Spell Check to ensure there are no spelling errors in the message.

6. A message box appears to confirm that no misspellings were found. Click OK to close the message box.

Next, save the new template. Click Save & Close.

The following table describes the values for each setting.

Settings

Template Name

Template Type

Return Notification

From

Subject

User Action Required

Description

Specify a name for the template that best describes the purpose of the new message template.

Specify the type of the new message template, such as Email Only or ID

Retrieval.

Specify if you want a return notice from the end user when the message is received and the required action is performed.

Specify the name of the entity sending this migration message to end users

(for example, Migration Coordinator).

Specify a brief description of the purpose of the new template.

Check this box if migration for this user cannot proceed until the user performs the embedded action within the message.

This check box also indicates that the user will remain in the Pending

Reponses view until they perform the end user action in a particular message template.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

141

Binary Tree Documentation

Message Body Specify a customized message.

The new template is saved and it appears in the list of existing templates.

Types of Predefined Message Templates

The database comes with predefined Message Templates which are designed to perform specific migration tasks.

The information contained within these predefined templates can be modified to tailor them to a client’s needs.

Predefined Message Templates can be of the following types depending on the actions they perform:

 Gather ID and Password Info

 Notification Only Email

Gather ID and Password Info

This message is used to gather User ID and password information.

Notification Email Only

As the name implies, Notification Email Only is designed for informational purposes only and does not include any action buttons. Notification Email Only templates can be used to keep the end users informed.

Importing Users

Users from the Domino Directory must be imported into the database.

Ongoing maintenance of users as they are added, deleted, or renamed must be maintained in this database. Also, if Password Poli cies exist in the environment, management of this must be considered for this database.

With the database open, expand in the left navigator the section Configuration and select Import Users. Import users as follows:

1. Click on the Import Users button and select either All Users or Select Users to Import (to select specific users).

2. If Select Users to Import is selected, choose users you want to import in the People view in BinaryTree’s

Address Book and click OK.

3. On the confirmation screen, click OK.

Sending User Notifications

Notification will be sent to the end users. These may be for relaying information, delivering end user driven action buttons for actions such as gathering ID and password information or both.

Send End User Notifications

To send a notification:

1. Expand User Notifications and click Send in the Navigation Pane.

2. Select all the user documents in the Data Pane to whom you want to send the notification.

3. Click the Send Notifications button in the Data Pane.

4. In the Message Templates dialog box, a list of available predefined templates is displayed. If you have created custom templates, these will also be listed. Select the template you wish to send and click OK.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

142

Binary Tree Documentation

5. The progression message box displays. After a few seconds of processing, another message box displays confirming that notifications have been sent to selected users. Click OK.

6. After you have sent the first notification to the users, the users remain in the Notify step under the

Pending Responses view so that you can send all the notifications that you wish to send to the users.

Pending Responses

Notifications where users are required to click an embedded button in the email are processed differently. If us ers don’t click the buttons, their response is considered pending and is listed in the Pending Responses view. To check if there are any pending responses from the notifications you sent, click Pending Responses.

For example, if John Smith has not performed the required action. The Data Pane will show that two notifications have been sent, one requires user action, and no response has been received.In a situation like this, you may want to send another notification prompting users to respond to migration notifications.

Responses Received

Responses can also be seen in the Responses view. Click Responses Received in the Navigation Pane.

Errors

If you need to check if there were any errors during the sending of the notifications. Click Errors.

Incoming Email Responses

The Incoming Email Responses view allows you to view user responses sent in via email.

How it Works

Encrypting from Exchange to Domino

 Exchange generated email sent to Domino users that is marked private, or has the property ICCategory=4 will be encrypted. Before submitting an item for encryption, Notes Integration | CMT will validate that all users in the recipient list have a Publi c Key in the Domino Directory. If any recipients do not have a Public

Key, an NDR will be sent to the originator.

 These items will marked as Private in the recipients’ inbox.

 If BTScanSubjectForEncryptFlag=1 and the subject contains the text value in BTSc anSubjectFlag the messages sent from Exchange to Domino users will be encrypted. This is to allow mobile users to encrypt messages sent from smart phones.

 In order to allow Domino users to reply with history and respond to calendar items, “Prevent Copy”

(Notes feature) is NOT set on encrypted items from Exchange.

 If any users do not have a valid Public Key, Notes Integration | CMT will send an NDR to the originator.

 When Calendar invitations are encrypted, they will appear as a memo with a meeting.ic s attachment in the Domino user’s inbox. When the item is opened it will be converted to a typical invitation.

Notes:

 Exchange generated email with external recipients should not be routed through the Domino Notes

Integration | CMT servers, therefore not encrypted.

 Encrypted calendar invitations from Exchange to Domino will initially arrive as an email with a meeting.ics attached, not an invitation.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

143

 Once the email is opened, it is properly displayed as an invitation.

Binary Tree Documentation

 There will also be an additional email version of the item in the inbox. If the Notes preferences are set to not to remove items from the inbox after you process them, you will see two items for each invitation.

Decrypting from Domino to Exchange

Decryption Option 1

 When any encrypted item is sent from a Domino user to an Exchange user, BTCal will stop the message and start the decrypting process if the INI setting BTIDVault is set to 1. BTCal will perform the following steps: o BT Will look at the INI variable BTIDFileLocation to determine location of the user’s ID file and if needed the password. o Depending on the configuration for the location of the ID and password, the process will open the ID to allow access to the message content. o After the message is opened the encryption will be removed.

 Once the message is decrypted, BTCal will update the header of the message and pass it to Domino to deliver the message to the Exchange/O365 environment.

Decryption Option 2

 When any encrypted item is sent from a Domino user to an Exchange user, it will be decrypted using the

BTDecryptID specified in the Notes.ini file of the Domino Coexistence server.

 The user account associated with this ID must be in the BCC field when the item is sent. If is not listed on the email (therefore it’s not possible to decrypt), then Notes Integration | CMT will automatically fallback to whatever process is specified for BTZAPPCHECKENCRYPT in the Notes.ini.

 Invites with Rooms and Resources – The BCC account is hidden. However, if there is a room, it goes to the router before BTCal, so resource reservation will show BCC. Note: Users can see BCC in properties (not the

BCC field in UI).

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

144

Binary Tree Documentation

Appendix K: BT Stats Database

The BT Stats database provides a way to view all NDR and ZApp items in a single view. The database can also be configured to display all successes of BTCal calendar processing

The database view includes the following columns:

 Notification Type – NDR or ZApp

 Sent To – User Name

 Messaging System – Domino/Exchange of recipient

 Date/Time – Date/time sent to user

 Affected Particpants (for NDR’s) – List of all meeting invitees

 NDR or ZApp Reason – User friendly reason

The BT Stats database can be configured by changing the following NOTES.INI settings:

BTSTATSDB

Default = btcalsta.nsf

By default btcalsta.nsf is the file name of the BT Stats database.

BTCALSTATSNDR

Accepted value = 0/1

Default = 1

Details of all NDR notifications appear in the view. This parameter is enabled (value set to “1”) by default.

BTCALSTATSZAPP

Accepted value = 0/1

Default = 1

Details of all ZApped items appear in the view. This parameter is enabled (value set to “1”) by d efault.

BTCALSTATSNOCHANGE

Accepted value = 0/1

Default = 0

This parameter can be enabled to log all successes of BTCAL calendar processing (messages not changed by ZApp or BTCal). This parameter is disabled (value set to “0”) by default.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

145

Appendix L: SetFBCred Utility

The SetFBCred utility is used to configure the credentials for the three Free/Busy IIS components:

AvailabilityService, Autodi scover, and AvailabilityRouter.

The SetFBCred utility should be run from the C:\Program Files\BinaryTree\CMT for

Coexistence\Exchange\AvailabilityService\bin directory.

Binary Tree Documentation

AvailabilityService

If Exchange Web Services are set to require a username/password to access Free/Busy information, the

AvailabilityService must supply those credentials on each request. Select the entry under AvailabilityService in the tree on the left to populate the BTAvailability tab.

After making changes, click Update. The config files will only be updated when you click Save.

The user name is the user's AD login (not an SMTP address) as seen below:

The pre-Windows 2000 format may also work, but the user@domain format is reccomended.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

146

Binary Tree Documentation

If you need to confirm that you have the right password, startup a new instance of Internet Explorer on the IIS box and point it to the EWS URL in the Availabi lityService connection settings. This will produce a login challenge where you can try out the password.

Autodiscover

If the domain controller requires a username/password for the LDAP queries to retrieve the AD TargetAddress attribute, Autodiscover must s upply those credentials on each request. Select the entry under Autodiscover in the tree on the left to populate the Autodiscover tab.

Changes to the configuration options on the Autodiscover tab should not be made without guidance from Binary Tree.

It is also possible to supply a list of AD sites, which are searched sequentially for a user record. Given the performance impact, this is strongly discouraged.

The default AD query (values coming from screen below): GC://{gc -contoso.contoso.local}/DC=contoso,DC=local

(&(objectCategory=person)(objectClass=user)(mail={usersSMTP})(!userAccountControl:1.2.840.113556.1.4.803:=2)

)

Disabled AD objects are no longer included in the search results, and the ObjectClass is 'user' instead of 'person' by default.

You can override the default with the AD URL and/or the AD Filter options.

The AD URL will be used in place of the AD Host Name/IP value. It allows you to specify the protocol (LDAP or GC) as well as starting location for the search. For example: LDAP://gc -contoso.local/OU=Users,DC=contoso,DC=local

The AD Filter can be used either with the AD Host Name/IP and Domain Components, or with the AD URL. It supplies the query values to be used in place of the defaults. To allow searching of disabled AD objects, for example: (objectCategory=person)(objectClass=user)

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

147

Binary Tree Documentation

The code will automatically add the (mail=userSMTP). Care must be used with parenthesis - do not include an outer '(&' and ' )'.

The 'Timeout in ms' applies when supplying multiple AD sites. A value of 0 indicates the system default will be used for AD queries (generally 120 seconds). Both Outlook and Notes have a timeout value for their Free/Busy requests in the 30 to 60 second range, so if searching many AD directories, it becomes critical to get a timely response. However, a Free/Busy request for one invitee can afford a longer AD lookup than a Free/Busy request for 10 invitees - so the risk with a low timeout value is that small groups will be timed out, when they would otherwise have been found i f a longer timeout was used.

AvailabilityRouter

If the Domino requires a username/password for Free/Busy queries, the AvailabilityRouter must supply those credentials on each request. Select the entry under AvailabilityRouter in the tree on the left to populate the

BTRouter tab.

The Username must belong to a Notes user who is listed in the ACLs of the btws.nsf.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

148

Binary Tree Documentation

About Binary Tree

At Binary Tree, we power enterprise transformations. Our award-winning software and services help Enterprise businesses modernize their Microsoft email, directories and applications by moving and integrating them to the cloud. Binary Tree mitigates the ris k of delays, downtime, and budget overruns for complex transformation projects for large organizations. We understand Enterprise migration requirements that go well beyond the needs of small companies. Since 1993, we’ve transformed more than 7,000 global clients and 40 million users, including

6 million to Office 365. Our business first approach helps plan, move and manage the transformation process from end-to-end. So, clients stay focused on their core business while our experts deliver a low-risk, successful IT transformation.

Binary Tree is a Microsoft Gold Partner and a globally preferred vendor for Offices 365. Our headquarters are located outside of New York City with global offices in the United Kingdom, France, Germany, Sweden and

Singapore. For more, visit us at www.binarytree.com

.

Binary Tree Social Media Resources

© Copyright 2017, Binary Tree, Inc. All rights reserved.

Binary Tree, the Binary Tree logo, and any references to Binary Tree’s products and services, are trademarks of Binary Tree, Inc. All other trademarks are the trademarks or registered trademarks of their respective rights holders.

Notes Integration | CMT BTCal 5.5 User Guide

BTCal 5.5

149