Services that were not tested

---

Sametime 3.0 requires Domino 5.0.11 (future Sametime releases will support higher Domino releases). The Sametime components that use Domino were disabled for the tests, so Domino was never actually running. The disabled components were

Directory Browsing Services. It is not reasonable to expect a high-volume Web site to provide directory browsing services, and if so they will not be related to the Sametime services.

Storage Services. Sametime Links clients do not use any storage services from Sametime and therefore this service is redundant in this scenario.

Privacy Services. Sametime Links do enforce but do not provide the user the ability to have privacy features of Sametime (Who can see me) and therefore this service is redundant in this scenario. We ran the Privacy Services in dummy mode.

Authentication services. The tests used a dummy interface to accept all users logging on to Sametime. This is an adequate simulation of having an LDAP authentication service remote from the Sametime server because the Sametime server still performs all CPU intensive operations needed for authentication, such as encryption, before calling the authentication interface.

The test environment and the robots do not simulate the resources for handling the request for and download of the small applet (~20K) used by the Sametime Links client. In the scale of the numbers discussed in this chapter, a high volume Web site should take that into consideration.

---