Converse agora com nosso suporte
Chat com o suporte

Integration for Notes 20.12.01 - User Guide - BTCal

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

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.

Unused Parameters

The following parameters are no longer required for the Integration for Notes (3.0 release or higher) of BTCal.

  • BTHOLDDOMAIN

  • BTDEBUGIDLEDELAY

Appendix G: Notes.ini Parameter Values

NOTES.INI Parameters

Accepted Value

Default Value

BTADDUSERDWASUPPORT

Y/N

 

BTALTEXCHANGEDOMAINS

<comma-separated domain names>

None

BTAPPTREROUTE

0/1

1

BTBCCSKIPADDRESS

<SMTP address>

None

BTBLOCKCANCELNOCACHE

Y/N

Y

BTBLOCKUPDATENOCACHE

Y/N

N

BTCACHEDB

<BTCache.nsf>

BTCAL.NCF

BTCALRESTARTTIMER

<number>

0 (no restart)

BTCALSTATSNDR

0/1

1

BTCALSTATSNOCHANGE

0/1

0

BTCALSTATSZAPP

0/1

1

BTCHECKINTERNALSMTP

0/1

0

BTCHECKRECIPIENTS

Y/N

N

BTCOEX_APPROVED_CALLERS

<list of IP addresses>

Required

BTCOEX_BYPASS_REQUESTOR

0/1

0

BTCOEX_CLIENT_LOG

6

6

BTCOEX_DEFAULT_FB_ACCESS_ACCOUNT

<SMTP address>

Required

BTCOEX_DOMINO_DOMAINS

<comma-separated domain names>

Required

BTCOEX_EXCHANGE_DOMAINS

<comma-separated domain names>

Required

BTCOEX_FOREIGN_WS_URL

https://autodiscover.%domino.contoso%.com/BTAvailability/Availability.asmx

Required

BTCOEX_LOG

0-8

0

BTCOEX_LOGDATA

1,2,4,8

???

BTCOEX_LOGFILE

Log file should be relative to the <Domino server>\Domino Data Directory

\IBM_TECHNICAL_SUPPORT\OUTPUT.LOG

BTCOEX_NSF

btws.nsf

btws.nsf

BTCOEX_RECYCLE_ENV_REQ_COUNT

<number>

2500

BTCOEX_SERVER_LOG

0-6

0

BTCOEX_SERVICE_TYPE

COEX

COEX

BTCOEX_WS_NAME

<Virtual directory used by the BTRouter on the Windows Coexistence server>

BTAvailability

BTCONVERTPNG

0/1

0

BTCONVERTPROPOSE

0/1

0

BTDELAY

<number>

60

BTDELEGATENDR

Y/N

Y

BTEXCHANGEDB

<mailbox name>

Required

BTEXCHANGEDOMAIN

<domain name>

Required

BTEXCHANGEROUTER

BTExchange.box

Required

BTEXCHANGESERVER

<SMTP address>

Required

BTEXPANDCALGROUPS

Y/N

N

BTEXPANDMAILGROUPS

Y/N

N

BTEXPANDGROUPS

Y/N

N

BTEXPANDGROUPSDOMAIN

<string>

None

BTFORCELOCATIONRESOLUTION

0/1

0

BTINATTOPT

0/1

0

BTINATTSKIPNAMES

<comma-separated filename patterns>

None

BTINTERNALSMTPDOMAIN

< SMTP domain,SMTP domain2>

None

BTKEEPPOSTED

Y/N

Y

BTLINKSOPTION

0/1

0

BTLOGCACHE

0/1

0

BTLOGCANCEL

0/1

0

BTLOGCONSOLE

Y/N

Y

BTLOGDIRECTORY

<Windows path name>

Windows temp directory

BTLOGLEVEL

0/1/2

0

BTLOGPNG

0/1

0

BTLOGRMB

0/1

0

BTLOGSTATS

0/1

0

BTLOGUIF

0/1

0

BTLOGWMBP

0/1

0

BTMULTISCHEDREPORTADDRESS

<SMTP address>

None

BTMULTISCHEDREPORTADDRESSTYPE

0 or 1 or 2

0

BTMULTISCHEDREPORTLEVEL

1 or 2 or 4

1

BTMULTISCHEDREPORTTEXTx

BTMULTISCHEDREPORTTEXTx

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%

BTNONDRONQUIT

0/1

0

BTNDRFROMADDRESS

<email address> or <common name>

None

BTNOTESDOMAINS

<comma-separated domain names>

Required

BTNOTIFYONDELEGATEORCOUNTER

0/1

0

BTONLINEMEETINGLABEL

<text>

None

BTORPHANDELAY

<number>

300

BTINMESSAGEMAX

0/<any number greater than 0>

100

BTPARTIALTEXT

<text>

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

BTPRESERVEATTACHMENTS

0/1

1

BTPROCESSDOMAIN

<SMTP domain>

Required

BTRECIPCONVERTFIELD

shortname/internetaddress-local/internetaddress-full

shortname

BTRECURRENCELIMIT

<number>

1200

BTRESOLVENDRRECIPIENTS

Y/N

N

BTRESOLVENDRRECIPIENTSDOMAIN

<string>

None

BTRETRYLIMIT

<number>

10

BTRETRYLIMITTEXTx

<text>

None

BTRETRYSENDNDR

0/1

0

BTSENDEXPANDED

Y/N

Y

BTSTATSDB

<database name>

BTCALSTA.NSF

BTSTOREDB

<database name>

BTSTORE.NSF

BTSTORETEXTx

<text of the custom e-mail to a recipient of a ZApp'ed e-mail>

None

BTSUBJECTPREFIXMARKER

<comma-separated list of markers>

None

BTSUPPORTMULTIPLEDOMINODOMAINS

0/1

0

BTTRUNCATESUBJECT

Y/N

N

BTWORKDIRECTORY

<Windows path name>

Windows temp directory

BTZAPPBYPASS

0/1

0

BTZAPPBYPASSDOCSWITHFIELDS

<comma-separated list of field names>

None

BTZAPPCHECKENCRYPT

0/1

1

BTZAPPCOMBINEENCRYPTEDCALENDAR

0/1

1

BTZAPPENCRYPTTEXT

0/1/2

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

BTZAPPFIELDSx

<comma separated list of field:value pairs>

None

BTZAPPIGNOREALLFORMS

0/1

0

BTZAPPIGNOREELEMENTS

<comma-separated list of element names>

None

BTZAPPIGNOREFORMS

allnonstandard/<comma separated list of form names>

None

BTZAPPIGNORESTOREDFORMS

0/1

0

BTZAPPINCLUDEFULLDISTRIBUTION

0/1

0

BTZAPPKEEPATTACHMENTS

0/1

0

BTZAPPORGS/BTZAPPORGSx

<comma-separated list of org units>

None

BTZAPPPDB

<database name>

BTZAPP.NSF

BTZAPPPROCESSFORMS

<comma-separated list of form names>

None

BTZAPPREADERS

<Domino address>

None

BTZAPPRENDERSTOREDFORMS

0/1

0

BTZAPPSENDORIGINAL

0/1/2/3

0

BTZAPPSUPPORT

0/1/2/3

0

BTZAPPTABLES

Y/N

N

BTZAPPTEMPLATE

<database template name>

Required if BTZAPPSUPPORT=2 or 3

BTZAPPUNIQUECOPY

Y/N

Y

BTZAPPUSERFORMS

<list of non-standard form names separated by commas>/All/None

None

EXTMGR_ADDINS

 

BTEx

MIMEFORCEATTACHMENTS

0/1

0

 

Appendix H: 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 routes mail to addresses, such as michael@contoso.com, and Exchange receives and routes mail to addresses, such as david@contoso.com, 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 james@contoso.com, but their target address would be james@domino.contoso.com. 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.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação