Installation
TANDBERG IBM Lotus Notes/Domino v 11.3 - Installation & getting started guide
Page 25 of 49
7. Enter the Domino service account in the
Service Account
field. (See Figure 16: The TMS admin
document).
Figure 16: The TMS admin document
8. Enter the IP or DNS name of the TMS Server in the
Host name
field.
9. Enter the username and password of the TMS Service Windows account (including the domain, if
applicable).
10. If you have completed the Enable secure communication (Optional) section, select
Yes
for field
HTTPS
. If not, select
No
.
11. If you are using V7.0 or V8.X of Lotus Notes, an additional option titled
Automatic Update
is
displayed. Because of a known issue with Lotus Notes, the Free/Busy information for booked
resources is not handled by the
Room and Resources Manager
. As a work around for this
release, you can automatically refresh the Free/Busy information after each booking event. This is
enabled by default, but if you are experiencing severe delays, consider turning off this option.
5
12. Click
Save and Close
to save your changes to the document.
Configuring the Domino Rooms for TMS Systems
Each system that will be bookable through Lotus Notes must be represented as a Room within
Domino. This step must be done by the userID who was added to the Reservation Database with the
role of
create resource
completed in the previous section.
1. You must know the system ID of each system in TMS that you wish to integrate with Lotus. In
TMS v9.6 or later, this can be found on the View Settings page for each system in the System
Navigator.
Note: For TMS versions 9.0 to 9.2, or if you wish to get a consolidated list of all systems, open a web
browser and enter the following URL. If you only have one Application Integration License, you must
perform this step from the Domino Server itself. Substitute TMSADDRESS with the IP or DNS name
of your TMS server.
http://TMSAddress/tms/external/booking/remotesetup/remotesetupservice.asmx?op-GetSystems
5
For an in depth description of this issue, please contact your local IBM representative. The issue is
reported to IBM Quality Engineering as SPR# MMQN6QWC6K
