Every deployment starts with directory services. LDAP and native Domino directories are supported. When planning your deployment, it is important to understand how users will authenticate. Sametime can be integrated into many other HCL products such as HCL iNotes, Verse, Connections and Digital Experience. It is recommended to use a common directory.

Review the LDAP Planning section for considerations in choosing a directory.

Small Internal Deployments

For small internal deployments, it is still recommended to install everything on separate servers in a multiple server configuration. If you do plan on installing everything on a single server, HCL recommends a minimum of 8GB of RAM.

An example of a small deployment includes a single Sametime Community Server, Sametime Proxy server (for mobile and web clients), MongoDB Server and the directory services (LDAP or native Domino).

To learn more about which clients are supported by each of the servers, see the topic Sametime Servers.

Figure 1 shows an example of a small internal deployment:

Small Deployments with Internet Access

There are many ways to extend access to your small deployment from the internet. Some examples include:

  • Place a network device in the DMZ to direct the traffic to the servers inside the internal zone.(see figure 2)
  • Place the Sametime Proxy and standalone Mux server directly in the DMZ and open the required ports in the firewall.

Medium and Large Deployments

In a medium or large deployment you can deploy a cluster of Community servers for redundancy and high capacity, all Community servers share a MongoDB server. See the topic on Clustering and High Availability for more information.

Sametime 11.5 Meetings Deployments