Converse agora com nosso suporte
Chat com o suporte

Integration for Notes 20.13 - User Guide - FreeBusy

Section 1. Introduction Section 2. Scope Section 3. Recommended Installer Prerequisites Section 4. Pre-installation Requirements Section 5. Configure the Domino environment Section 6. Configure Integration for Notes FreeBusy in Exchange or Office 365 Section 7. Install FreeBusy On the Domino Coex Server Section 8. Create and Configure the Domino Databases Section 9. Modify the Notes.ini File Section 10. Start FreeBusy on Domino Coex Server Section 11. Install FreeBusy for Windows Section 12. Verification Section 13. Ongoing Administration Appendix A. Adding a Root Trusted Signed Certificate to the FreeBusy Operating System(s) Appendix B. SetFBCred Utility Appendix C: Enable Modern Authentication Appendix D. Notes.ini File Parameters

Section 11. Install FreeBusy for Windows

9.2 How to update the Notes.ini file

To make changes to the Notes.ini file, follow these steps:

  1. Shutdown BTFreebusy by issuing the following command at the Domino Coex server console:

Domino Coex Server Console

tell btfreebusy quit

  1. Shut down the Domino Coex server by issuing the following command:

Domino Coex Server Console

quit

  1. When the Domino server has completed its shutdown:

    1. Open the INI file in a basic text editor (e.g. Notepad)

    2. Make the modifications and save the text file

 


If using 64-bit Domino and/or a language with double-byte characters, the text file must be saved as UTF-8 without a BOM.

  1. Restart the Domino Coex server

Section 10. Start FreeBusy on Domino Coex Server

After installing the FreeBusy software and updating the Notes.ini file, the Domino Coex server needs to be restarted.

Refer to the Ongoing Administration section for more information on FreeBusy Domino server commands.

If the Domino server was not shutdown when the Notes.ini was updated, restart FreeBusy. To do this, issue the following commands at the Domino Coex server console to start and stop the FreeBusy task:

Domino Coex Server Console

tell btfreebusy quit

load btfreebusy

 

The example below, shows a quit followed by a successful BTFreeBusy load.

 

cid:image001.png@01D4F115.95F2C6B0

Section 11. Install FreeBusy for Windows

To install Integration for Notes Free/Busy on the Windows Coex server, follow the instructions below:

  1. Run the Notes Integration FreeBusy.exe as Administrator

  2. On the installation wizard screen, click Next:

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

  2. On the Choose Destination Location screen, accept the default destination location or browse to the desired location; click Next:

  1. On the first screen, enter the Fully Qualified Domain Name (FDQN) of the Exchange CAS server hostname and click Next:

  2. Enter the DNS name of the Domino Server and click Next:

  1. On the third Free/Busy Install Configuration screen, enter the Domino SMTP domain name you want to expose Free/Busy information for and click Next:

  2. On the Additional setup is required screen, copy the command and run it in an Exchange Management Shell then click Next.

    This command sets the Availability Address Space in Exchange so Free/Busy requests are sent to Domino:

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

  4. When installation is complete, the Wizard Complete screen appears; click Finish to exit the wizard:

  5. Open a command prompt and run the following command: iisreset

Section 12. Verification

Proper verification of the FreeBusy installation, can prevent future issues from occurring during coexistence. Verify Autodiscover, BTAvailability and BTRouter and then complete the validation matrix at the end of this section.

Section 12. Verification

9.2 How to update the Notes.ini file

To make changes to the Notes.ini file, follow these steps:

  1. Shutdown BTFreebusy by issuing the following command at the Domino Coex server console:

Domino Coex Server Console

tell btfreebusy quit

  1. Shut down the Domino Coex server by issuing the following command:

Domino Coex Server Console

quit

  1. When the Domino server has completed its shutdown:

    1. Open the INI file in a basic text editor (e.g. Notepad)

    2. Make the modifications and save the text file

 


If using 64-bit Domino and/or a language with double-byte characters, the text file must be saved as UTF-8 without a BOM.

  1. Restart the Domino Coex server

Section 10. Start FreeBusy on Domino Coex Server

After installing the FreeBusy software and updating the Notes.ini file, the Domino Coex server needs to be restarted.

Refer to the Ongoing Administration section for more information on FreeBusy Domino server commands.

If the Domino server was not shutdown when the Notes.ini was updated, restart FreeBusy. To do this, issue the following commands at the Domino Coex server console to start and stop the FreeBusy task:

Domino Coex Server Console

tell btfreebusy quit

load btfreebusy

 

The example below, shows a quit followed by a successful BTFreeBusy load.

 

cid:image001.png@01D4F115.95F2C6B0

Section 11. Install FreeBusy for Windows

To install Integration for Notes Free/Busy on the Windows Coex server, follow the instructions below:

  1. Run the Notes Integration FreeBusy.exe as Administrator

  2. On the installation wizard screen, click Next:

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

  2. On the Choose Destination Location screen, accept the default destination location or browse to the desired location; click Next:

  1. On the first screen, enter the Fully Qualified Domain Name (FDQN) of the Exchange CAS server hostname and click Next:

  2. Enter the DNS name of the Domino Server and click Next:

  1. On the third Free/Busy Install Configuration screen, enter the Domino SMTP domain name you want to expose Free/Busy information for and click Next:

  2. On the Additional setup is required screen, copy the command and run it in an Exchange Management Shell then click Next.

    This command sets the Availability Address Space in Exchange so Free/Busy requests are sent to Domino:

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

  4. When installation is complete, the Wizard Complete screen appears; click Finish to exit the wizard:

  5. Open a command prompt and run the following command: iisreset

Section 12. Verification

Proper verification of the FreeBusy installation, can prevent future issues from occurring during coexistence. Verify Autodiscover, BTAvailability and BTRouter and then complete the validation matrix at the end of this section.

12.1 Verify Autodiscover, BTAvailability and BTRouter on the Windows Coex Server

All verification sequences in section 12.1 are run on the Windows Coex server.

12.1.1 Autodiscover

  1. Open a command prompt and navigate to the following path: %Program Files%\BinaryTree\CMT for Coexistence\Autodiscover


    If web.2010.config exists, rename it to web.config.

     

    1. Verify that web.config and connections.config are not set to Read-Only

  2. Open the IIS Administrator application

    1. Navigate to the Default Web Site

    2. Refresh IIS (press <F5>) and be sure that the Autodiscover virtual application has been added:

       

  3. In the left pane, select the Autodiscover application

    1. In the right pane, in the IIS section, double-click Authentication

      1. Be sure that Basic Authentication and Windows Authentication are enabled; if they are not, enable them:

         

      2. Click the Back button

  4. In the right pane, in the ASP.net section, double-click Connection Strings

    1. Verify that the EAD is: https://<Your Exchange CAS Server FQDN>/Autodiscover/Autodiscover.xml

      1. If the EAD (Exchange CAS Server) value is incorrect, modify it with the correct name:

      2. Click the Back button

  5. In the right pane, in the ASP.net section, double-click Application Settings

    1. Verify that ExchangeVersion is set to 2010 for all supported versions of Exchange

    2. If you require credentials to access the Active Directory environment and you do not see the following fields:

      AD-Username and AD-Password

      use the SetFBCred Utility to set the AD-Username and AD-Password (see Appendix B:  SetFBCred Utility)

    3. Be sure that Autodiscover is set to .\Autodiscover.xsl

    4. The following log settings are optional:

      1. LogAllRequests = False

      2. Log path = c:\log\autodiscover (must be an existing directory, create if needed)

  1. Close the IIS Manager

  2. If any changes were made in steps 1-5, open a command prompt and run iisreset

  1. Open Internet Explorer and navigate to the following virtual directory: https://autodiscover.domino.<contoso.com>/Autodiscover/Autodiscover.asmx

 


Be sure that you use the same name listed in the SAN SSL certificate applied to the system and that it matches the Autodiscover.<dominoSMTPdomain> specified above.

  1. The BT Autodiscovery Service for Exchange 2010 page should appear:

  2. Click BT_GetConfiguration

  3. On the page that loads, Click Invoke; an XML response with the correct endpoint for this machine should display in the browser:

  4. Return to the original AutoDiscovery screen

  5. Click BT_TestAutoDiscovery

  6. Enter the e-mail address of a valid Domino user; for example, user1@domino.contoso.com and click Invoke:

  7. A properly formatted Autodiscover XML document should appear showing the correct URL to the BTRouter application

     


    To successfully install the FreeBusy web services, the web server must accept connections via HTTP (Port 80) and can be later switched to HTTPS (Port 443).

     

12.1.2 BTAvailability

  1. Open a command prompt and navigate to the following path: %Program Files%\BinaryTree\CMT for Coexistence\AvailabilityService


    If web.2010.config exists, rename it to web.config.

     

    1. Verify that web.config and connections.config are not set to Read-Only

  2. Open the IIS Administrator application

    1. Navigate to the Default Web Site

    2. Refresh IIS (press <F5>) and be sure that the BTAvailability virtual application has been added:

  3. In the left pane, select the BTAvailability application in the left pane

    1. In the right pane, in the IIS section, double-click Authentication

      1. Be sure that Basic Authentication and Windows Authentication are enabled; if they are not, enable them:

      2. Click the Back button

  4. In the right pane, double-click Connection Strings

    1. Verify that the EWS is: https://<Exchange CAS Server FQDN>/EWS/Exchange.asmx

      1. If the EWS value is incorrect, modify it with the correct name:

      2. Click the Back button

  5. In the right pane, in the ASP.net section, double-click Application Settings

    1. Verify that ExchangeVersion is set to 2010 for all supported versions of Exchange


    2. If you require credentials to access the Active Directory environment and you do not see the following fields…

    3. If using these optional log settings, verify the following:

      1. LogAllRequests = False

      2. LogPath = c:\log\availability (must be an existing directory, create if needed)

  6. Close the IIS Manager

  7. If any changes were made in steps 1-5, open a command prompt and run iisreset

  8. Verify that the application is up and running

  9. Open Internet Explorer and navigate to the following virtual directory:

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

 


Be sure that you use the same name listed in the SAN SSL certificate applied to the system and that it matches the Autodiscover.<dominoSMTPdomain> specified above.

  1. The BT Availability Router for Exchange 2010 Web Services page should appear:

  2. Click BT_GetConfiguration

  3. On the page that loads, click Invoke; an XML response with the correct endpoint for this machine should display in the browser:

  4. Return to the original BT Availability Router screen

  5. Click BT_TestConnectivity

  6. Add two e-mail addresses of valid Exchange mailbox users (e.g. michael@contoso.com and david@contoso.com)

  7. Click Invoke:

  8. Two string representations of the Free/Busy stream should appear for each user for the current date

12.1.3 BTRouter

  1. Open a command prompt and navigate to the following path:

    %Program Files%\BinaryTree\CMT for Coexistence\AvailabilityRouter

  1.  


If web.2010.config exists, rename it to web.config.

 

  1. If Exchange.2010.asmx exists, rename it to Exchange.asmx

  2. Verify that web.config and connections.config are not set to Read-Only

  1. Open the IIS Administrator application

    1. Navigate to the Default Web Site

    2. Refresh IIS (press <F5>) and verify that the BTRouter virtual application has been added:

  2. In the left pane, select the BTRouter application

    1. In the right pane, in the IIS section, double-click Authentication

      1. Be sure that Basic Authentication and Windows Authentication are enabled; if they are not, enable them:

      1. Click the Back button

  3. In the right pane, in the ASP.net section, double-click Connection Strings

    1. Verify that the BTAS-NOTES URL is pointing to the BT Domino Availability Service URL (e.g. https://<FQDN of the Domino Web service>/BTAvailability)

    2. Verify that the EWS URL is: https://<Your Exchange CAS Server FQDN>/EWS/Exchange.asmx

    3. If the URLs in Connection Strings are incorrect, modify them with the correct values:

    4. Click the Back button

  4. In the right pane, in the ASP.net section, double-click Application Settings

    1. Verify that ExchangeVersion is set to 2010 for all supported versions of Exchange

    2. If you require credentials to access the Active Directory environment and you do not see the following fields…

  • BTAS-password

  • BTAS-username

    …use the SetFBCred Utility to set the BTAS-username and BTAS-password (see the  SetFBCred Utility appendix for more information).

    1. To ensure all requests that route through Domino, use the SMTP domain contoso.com rather than domino.contoso.com, map each of your Domino domains to the SMTP domain by creating one “map” entry per Domino domain as listed below:

    2. In the right-hand Actions pane, click Add

      1. In the Name field, enter:

        • MAP:@domino.<contoso.com>

      2. In the Value field, enter:

        • <contoso.com>

      1. Multiple FQDN’s can be supported by a single map entry using a wildcard (*) in the Name and Value fields as follows:

        • MAP:@domino.*

      2. A less common map entry is illustrated below and is not recommended to be installed without Binary Tree assistance; these settings are used in environments that wish to use Free/Busy lookups based on Domino shortname only:

 


Domino shortname-only lookups are also supported but for this type of installation it is recommended that you contact a Quest consultant.

  1. If using these optional log settings, verify the following:

    • LogAllRequests = False

    • Log path = c:\log\btrouter (must be an existing directory, create if needed)

  1. Close the IIS Manager

  2. If any changes were made in steps 1-5, open a command prompt and run iisreset

  3. Open Internet Explorer and navigate to the following virtual directory:

    https:// autodiscover.domino.contoso.com/BTRouter/Exchange.asmx

 


Ensure that the host name is listed as part of the SAN of the SSL certificate.

  1. The BT Availability Router for Exchange 2010 Web Services page should appear:

  2. Click BT_GetConfiguration

  3. On the page that loads, click Invoke; an XML response with the correct endpoint for this machine should display in the browser:

    1. If UNREACHABLE appears under the Domino endpoint URL, verify the Domino Availability Service endpoint. You should be able to reach the Domino service endpoint using the browser.

    2. Return to Application Settings in IIS and update the endpoint with the proper URL

  4. Return to the original BT Availability Router screen

  5. Click BT_TestConnectivity

  6. Enter email addresses for two valid Domino users (e.g. james@domino.contoso.com and daniel@contoso.com)

  7. Click Invoke; you should see a string representation the Free/Busy stream for each user for the current day

     

12.2 FreeBusy Client Validation Matrix

12.2     FreeBusy Client Validation Matrix

12.2.1 Create Test Accounts

Prior to performing the validation in the attached Excel spreadsheet, first create two Notes and two Outlook test accounts (or use existing accounts):

  • The Notes users should reflect a typical end user with a similar client, mail template and mail server

  • The Outlook client should match that of a typical end user

Section 13. Ongoing Administration

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação