1. SHOW201
Installation and Setup of
IBM Lotus Sametime 8.5
”From Zero to Hero” in Just Two Hours
Frank Altenburg | Senior Field Support Engineer
Volker Jürgensen | Software IT Architect
2. 2
Agenda
● Components of IBM Lotus Sametime 8.5
● Requirements for a IBM Lotus Sametime 8.5 Deployment
● Architecture of a IBM Lotus Sametime 8.5 pilot deployment
● The 21 steps to a IBM Lotus Sametime 8.5 pilot deployment
3. 3
The IBM® Lotus® Sametime® 8.5 Components
we will cover today
● Sametime System Console
● Sametime Community Server
● Sametime Proxy Server
● Sametime Meeting Server
● Sametime Media Manager
4. IBM Lotus Sametime System Level Architecture
Sametime
Gateway
Community
Server
Media
Manager
Unified
Telephony
Advanced
Server
Meeting
Server
Sametime
Proxy
Sametime Clients
External IM
Communities
Enterprise Phone
System
Embedded Applications, including
Web Client, Portal, and Mobile
Partner
A/V Bridges
SIP, RTP SIP, RTP
VP
VP VP
VP VP
VP VP
HTTP HTTP
HTTP
SIP, XMPP
SIP, TCSPI
SIP
Logical servers shown – may be
combined physically depending on
user workload
5. IBM Lotus Sametime System Console
Sametime
Presence/IM
Sametime
Classic
Meetings
Sametime
New Meetings
Sametime
Media
Server
Sametime
Gateway
DominoWebSphere
DB2
LDAP
Sametime
Proxy
SametimeSystemConsole
● Manage prerequisites.
– System console manages all needed info for prerequisite
components
– No install/reinstall of IBM DB2® (for example) for each
separate offering
● Centralize configuration.
– Setup & testing of things like LDAP centralized in a single
location, instead of various wizards in different installers
● Facilitate deployment planning.
– Mechanism to plan the Sametime server deployment
– Installation of server nodes is simpler, as the shared
configuration already exists. Server installers are
“headless”, and need no input from user
● Single point of action for administrative
tasks
– Example: Policies are managed from a single place for all
components
6. 6
IBM Lotus Sametime Community Server
The Lotus Sametime Community Server runs on IBM Lotus Domino®. It
supports presence (also called awareness) and instant messaging in a
Lotus Sametime community. Any Lotus Sametime client that contains
a presence list must connect to the Sametime Community server.
Basic functionality supported by the server includes:
● Handling client login requests
● Handling connections from rich clients that access the Sametime
server through a direct TCP/IP connection, or through HTTP, HTTPS,
or SOCKS proxy servers
● Providing directory access for user name search and display purposes
● Providing directory access to compile lists of all Sametime servers and
users in the community
7. 7
IBM Lotus Sametime Community Server
● Dissemination of presence and chat data to all users connected to
Community Services
● Maintenance and storage of privacy information, user preference
settings, and presence lists for online users
● Handling connections from the Community Services on other
Sametime servers when Using multiple non-clustered Lotus Sametime
Community Servers. Server-to-server connections for the Lotus
Sametime Community Server occur on default TCP/IP port 1516
● Logging of server events to the General log settings (stlog.nsf)
● Enabling a name entry prompt to appear when the ACL settings of a
Domino® database enabled with IBM Lotus instant messaging
technology allows anonymous access. This name entry prompt
ensures that the presence list in the Sametime database can display a
name for the user
8. 8
IBM Lotus Sametime Proxy Server
The Lotus Sametime Proxy Server runs on IBM WebSphere® Application
Server. It requires a Sametime Community Server.
The Lotus Sametime Proxy Server communicates direct with the Lotus
Sametime Community Server and indirect with the Lotus Sametime
Meeting server, Lotus Sametime Business Card Server, and Lotus
Sametime Telephony Conferencing Server.
The Proxy Server is responsible for the following activities:
● It hosts the Sametime client for browsers
● It provides livenames awareness for Sametime meetings, Business
Cards, and custom applications
● It replaces the Sametime Java Connect or Sametime Connect for
Browsers client
● It can also replace the Sametime Links Toolkit
9. 9
IBM Lotus Sametime Meeting Server
The Lotus Sametime Meeting Server runs on WebSphere Application
Server. It requires a LDAP Server and a IBM DB2 Database Server.
The Lotus Sametime Meeting Server provides the new Meeting
functionality that can be accessed by the Sametime Connect Client or
directly with a browser.
The Meeting Server is responsible for the following activities:
● Create and manage Meeting Rooms
● Interface for Browser and Sametime Plug-In access
● Routing connections to the right meeting rooms
● Storing information from the library
10. 10
IBM Lotus Sametime Media Manager
The IBM Lotus Sametime Media Manager runs on WebSphere
Application Server to provide audio visual services for chats and
meetings. It requires a Lotus Sametime Community Server.
The Lotus Sametime Media Manager uses the Session Initiation Protocol
(SIP) to provide support for point-to-point and multipoint calls. It is
designed to support standard audio and video codecs so that it can
inter operate with equipment of other audio and video vendors.
The Lotus Sametime Media Manager uses three components. In a pilot
environment, the Lotus Sametime Media Manager components can all
be installed on one server, but in a production environment, you should
install each of the components on its own server.
11. 11
IBM Lotus Sametime Media Manager
Conference server
● The Conference server manages all conferences, including point-to-
point and multipoint. It works with the client to establish the SIP
session for the call. It hosts the internal TCSPI adapter and optionally
an external TCSPI adapter.
● The Conference server requires access to LDAP, Meetings (optional),
and Proxy/Registrar (including transport protocol: UDP, TCP). The
Conference server will handle workload management for conference
sessions among the switchers.
12. 12
IBM Lotus Sametime Media Manager
Proxy and Registrar
● The Proxy and Registrar is responsible for location service and
forwarding SIP messages to a destination. It requires access to LDAP.
You may also install and configure a database to be used with it.
13. 13
IBM Lotus Sametime Media Manager
Packet switcher
● The Packet switcher is responsible for receiving and sending media
streams from endpoints to other endpoints in a conference. The
Switcher works on audio streams to determine the active video stream
to send to the participants, a process known as Voice-Activated
Switching (VAS).
● The Packet switcher requires access to LDAP, Conference server, and
media ports (1 or a range of ports for audio, and 1 or a range of ports
for video). If the switchers are installed on the same machine, ensure
that are no port conflicts.
14. 14
Agenda
● Components of IBM Lotus Sametime 8.5
● Requirements for a IBM Lotus Sametime 8.5 Deployment
● Architecture of a IBM Lotus Sametime 8.5 pilot deployment
● The 21 steps to a IBM Lotus Sametime 8.5 pilot deployment
15. IBM Lotus Sametime 8.5 Prerequisites
● IBM Lotus Sametime 8.5 System Console Server requires
● IBM WebSphere Application Server 7.0.0.3 (provided automatically via Install)
● IBM DB2 9.5 (provided automatically via Install)
● LDAP directory server (Supported IBM® Lotus® Domino® Directory LDAP, Microsoft® Active
Directory, IBM Tivoli® Directory Server, SunOne® iPlanet®, Novell® eDirectory®)
● IBM Lotus Sametime 8.5 Sametime Community Server requires
● IBM Lotus Domino 8.0.x or 8.5 (32 Bit Version only)
● LDAP directory server
● IBM Lotus Sametime 8.5 Proxy Server requires
● IBM WebSphere Application Server 7.0.0.3 (provided automatically via Install)
● IBM Lotus Sametime 8.5 Community Server
● IBM Lotus Sametime 8.5 Meeting Server requires
● IBM WebSphere Application Server 7.0.0.3 (provided automatically via Install)
● IBM DB2 9.5 (provided automatically via Install)
● LDAP directory server
● IBM Lotus Sametime 8.5 Media Server requires
● IBM WebSphere Application Server 7.0.0.3 (provided automatically via Install)
● IBM Lotus Sametime 8.5 Community Server
● LDAP directory server
16. IBM Lotus Sametime 8.5 Prerequisites, continued
● Hardware required (for a pilot deployment)
● 1 server for the IBM DB2 Server, IBM Lotus Sametime 8.5 System Console, IBM Lotus Sametime
8.5 Proxy Server, IBM Lotus Sametime 8.5 Meeting Server and IBM Lotus Sametime 8.5 Media
Manager
● Dual CPU, 6GB RAM or more, 50GB disk space or more
● 1 server for Sametime 8.5 Community Server
● 2GB RAM or more, 2GB disk space or more
● Various client endpoints
17. ● Software requirements
● Client
● Windows XP (SP2) and Vista – 32 and 64 bit (Sametime Connect 8.5 or Notes 8.5.1 upgrade)
● Server
● Windows Server 2003/2008 - 32 and 64 bit
● Linux (RHEL, SLES) - 32 and 64 bit
● AIX 5.3/6.1
● i5/OS 5.4, 6.1
● Solaris 10
● Browsers
● Microsoft® Internet Explorer 6.x, 7.x, 8.0 (Windows)
● Firefox 2.x and 3.0.x (Windows, Mac, Linux)
● Safari 3.2 and 4.0.x (Mac)
● Other
● Domino 8.0 /8.5 for Community/'Classic' meetings
● Websphere Application Server 7 for new servers and gateway (included)
● DB2 9.5 for new servers and gateway (included)
IBM Lotus Sametime 8.5 Prerequisites, continued
18. Other requirements:
● Make sure that all servers you want to use can be resolved in DNS.
● If DNS is not available then list all full qualified server names and IP
addresses from all servers in the hosts. File and publish this file to all
servers.
19. Required files for a deployment on Windows:
For a Windows installation you need to download these files from Passport
Advantage:
CZB8DML.zip DB2 Enterprise Server for Sametime
CZA6HML.zip Sametime System Console
CZA62ML.zip Sametime Community Server Standard
CZA6AML.zip Sametime Proxy Server
CZA65ML.zip Sametime Meeting Server
CZA6FML.zip Sametime Media Manager
CZA6MML.zip Sametime Connect Client Standard
Create a directory, for example “C:Install”, on the servers where you want to
install. Then unpack the downloaded files into this directory. Just unpack the
files required for your deployment architecture on the particular server.
20. 20
Agenda
● Components of IBM Lotus Sametime 8.5
● Requirements for a IBM Lotus Sametime 8.5 Deployment
● Architecture of a IBM Lotus Sametime 8.5 pilot deployment
● The 21 steps to a IBM Lotus Sametime 8.5 pilot deployment
21. 21
Different ways to a pilot deployment
● The Install Guide (“recommended small pilot deployment”) describes to
distribute the Domino and non Domino based services on different
servers.
● You can also install all components on separate servers. This is more
for production environments or bigger pilots.
● You can use any mix between these two previous methods.
In this session we will install on 3 servers:
▬ Server1: LDAP Server (we do not install this server, we use an already existing one)
▬ Server2: DB2 Server, System Console, Community Server, Proxy Server, Meeting Server
▬ Server3: Media Manager
Our reason for this scenario:
● There is no real reason for that.
● We just want to show that it is possible to go other ways.
● This script works well for all ways.
22. IBM Lotus Sametime 8.5 – our deployment
Same
tim
e
M
edia
Ma
nag
er
L
otus
Do
mino
L
DAP
Ser
v
e
r
D
B
2
9
.5
Ser
v
e
r
S
a
me
ti
m
e
Sy
stem
C
onso
le
S
a
me
ti
m
e
Com
mu
nity
Ser
v
e
r
Sam
etime
P
roxySer
v
e
r
Sam
etime
Me
eting
Serve
r
IPA
d
dr
ess
T
ab
le
:
1
92
.16
8
.0
.1
00
ld
ap
.re
no
v
a
ti
o
ns
.co
m
19
2
.168
.0
.1
0
stc
.reno
v
a
tions
.com
1
92
.16
8
.0
.1
2
stp
.ren
ovation
s.com
19
2
.1
68
.0
.1
4
stm
.reno
vations
.com
19
2
.1
68
.0
.1
6
stav
.reno
v
a
ti
o
ns
.c
o
m
ld
ap
.ren
ovation
s
.com
s
ta
v
.reno
v
a
ti
o
ns
.c
o
m
stc
.re
novation
s.com
stc
.re
novation
s.com
stc
.re
novation
s.com
stp
.reno
va
tions
.co
m
s
tm
.re
novatio
ns
.com
23. 23
Agenda
● Components of IBM Lotus Sametime 8.5
● Requirements for a IBM Lotus Sametime 8.5 Deployment
● Architecture of a IBM Lotus Sametime 8.5 pilot deployment
● The 21 steps to a IBM Lotus Sametime 8.5 pilot deployment
24. The 21 steps to deploy a complete
Sametime 8.5 environment
1.Set up or use an existing LDAP server
2.Install the IBM DB2 Server
3.Create the IBM Lotus Sametime System Console database
4.Install the IBM Lotus Sametime System Console
5.Log in to the IBM Lotus Sametime System Console
6.Run the guided activity to configure the LDAP server connection
7.Run the guided activity to configure the IBM Lotus Sametime Community
Server installation
8.Install the IBM Lotus Sametime Community Server
25. The 21 steps to implement a complete
Sametime 8.5 environment (continued)
9. Enable trust between the IBM Lotus Sametime Community Server and the
IBM Lotus Sametime Proxy Server
10.Run the guided activity to configure the IBM Lotus Sametime Proxy Server
installation
11.Install the IBM Lotus Sametime Proxy Server
12.Create the IBM Lotus Sametime Meeting Server database
13.Run the guided activity to configure the DB2 Meeting server database
connection
14.Run the guided activity to configure the IBM Lotus Sametime Meeting Server
installation
15.Install the IBM Lotus Sametime Meeting Server
26. The 21 steps to implement a complete
Sametime 8.5 environment (continued)
16.Enable trust between the IBM Lotus Sametime Community Server and the
IBM Lotus Sametime Media Manager
17.Run the guided activity to prepare the IBM Lotus Sametime Media Manager
installation
18.Install the IBM Lotus Sametime Media Manager
19.Install a IBM Lotus Sametime Connect client
20.Configure the Meeting Plug-In on the IBM Lotus Sametime Connect client
21.Configure the Sametime Meeting Room in the IBM Lotus Sametime
Connect Client Meeting Plug-In to use Audio and Video
28. The LDAP Server
In most environments a LDAP server is already present. If you use Domino
it is simple to just enable LDAP on one of the Domino Directory Servers. If
you use an existing LDAP Server other then Domino, it is important to use a
V3 compliant LDAP.
Make sure you have all relevant data from the LDAP system. (use
ldapsearch Apache LDAP studio or another LDAP browser to get the
relevant LDAP information -an LDIF extract of a user and a group)
A security related recommendation is to have a Bind DN. This means a
User in the LDAP that can be used for authenticated access to the user
data in the LDAP server.
Make sure that your LDAP can be accessed without SSL encryption first.
SSL can be enabled later.
29. In this session we use an existing Lotus Domino LDAP server.
If you plan to use other LDAP servers then step 6 can be different,
dependent on the used LDAP directory.
See the Sametime InfoCenter for more details.
37. Remove “Program Files” and click “Next” to continue
U
s
in
g
th
e
W
in
d
o
w
s
s
ta
n
d
a
rd
p
a
th
c
a
n
c
a
u
se
p
ro
b
le
m
s
d
u
ri
n
g
in
st
a
lla
tio
n
a
n
d
d
e
p
lo
y
me
n
t.
R
e
a
so
n
is
th
e
b
la
n
k
ch
a
ra
ct
e
r
in
s
o
me
d
ire
ct
o
ry
n
a
m
e
s
like
in
„P
ro
g
ra
m
F
ile
s“.
Bl
a
n
k
s
a
n
d
sp
e
ci
a
l
ch
a
ra
ct
e
rs
a
re
n
o
t
su
p
p
o
rt
e
d
fo
r
th
e
in
s
ta
lla
tio
n
o
f
W
e
b
Sp
h
e
re
A
p
p
lica
tio
n
S
e
rv
e
r
a
n
d
th
e
S
a
m
e
tim
e
co
m
p
o
n
e
n
ts
!
A
lso
lo
n
g
p
a
th
n
a
m
e
s
sh
o
u
ld
b
e
a
v
o
id
e
d
a
s
th
e
re
a
re
u
su
a
lly
limi
ta
tio
n
s
o
f
2
5
6
ch
a
ra
ct
e
rs
fo
r
th
e
p
a
th
+
file
n
a
m
e
.
42. The Installer installs the IBM DB2 Server now. This step takes approximately 10 to 15 minutes.
43. Important to know
Your DB2 Database Server is a high sensitive component in your
Sametime Environment.
It stores all the predefined configuration data and holds the information
how to communicate with your servers for administration and
maintenance.
We highly recommend to make regulary backup of your DB2 database
using a DB2 aware backup software, or export data and backup the
exported data.
It is possible to cluster your DB2 Server for high availability and load
balancing using DB2 methods.
For more information check into the DB2 InfoCenter.
61. Important to know...
If you plan to use the IBM Lotus Sametime System Console, you have to
install this part first. In the actual release it is not possible to add an already
installed Sametime Server to the System Console for managing and
administration.
Be sure to make a backup of all related data and files (DB2 and WebSphere)
because this data can not be reverted if a failure occurs.
You will see that it is worth to learn about the Sametime System Console
and use it very soon!
70. Fill the fields in this form with your relevant data. We use:
Check the “Authenticated Access” checkbox (see recommendation ahead)
Deployment Name: “Renovations LDAP”
Hostname: “ldap.renovations.com”
The host name of your LDAP server
Bind Distinguished name: “cn=LDAP Admin,o=renovations”
The Bind DN name (full qualified)
Password: “********”
The Bind DN password.
Then click the “Next” button.
98. Important to know:
The Sametime Community Server Deployment Plan Guided Activity
checks the existence of the Domino Administrator user ID and that this
user can authenticate with its HTTP password.
Therefore it is required to install the Domino Server before the Sametime
Community Server Deployment Plan is created.
Later it is possible to change this credentials if the Domino Administrator
user changes. This can be done in the Sametime System Console.
99. Important to know:
The Sametime 8.5 Community server reads the Policy Configuration from
the Sametime System console during startup and then every hour.
(This can be configured)
If the Sametime Community Server can not read the Policy data,
(because of the SSC is not up) then no user is able to log in to the
Sametime Server.
A work around is possible by reconfiguring the policy parameters in the
sametime.ini file.
129. Important to know:
The Sametime Proxy Server:
● does not need a Database
● does not need a LDAP connection
● is just a Web Interface for browser access to the Sametime Community
Services – Web based Sametime Connect Client
● supplies the new Web API for Web based application integration
● can be implemented with or without the SSC
● can be connected to existing older Sametime Servers (R 7.5.1+)
● can be connected to a community cluster
You can have one or more Proxies in your organization
You can implement one or more Proxies and cluster them
● using the WebSphere Cluster Method (Network Deployment)
● individual Proxies with a Load Balancer in front of them
159. Important to know:
To configure LiveName integration in the Browser Meeting Access, SSO
between the Community Server and the Meeting Server is required.
The LTPA Token has to be exported from the Meeting Server and imported in
the community server. Live Name Integration works over the REST API in the
Proxy Server.
No Connectivity is required between the Meeting Server and the Media
Manager.
Audio and Video is possible only with the Sametime Connect Client Version
8.5. (Stand alone or Notes embedded client). This client first connects to the
Community Server. From there it receives the connectivity information to other
servers. Then it connects to the Media Manager (if required)
160. Important to know (cont)
The Meeting Server can be clustered using the WebSphere Network
Deployment. This can be configured and deployed with the Sametime System
Console.
The new Sametime Meeting Server consists of two components.
- the Meeting Server
- the Meeting Proxy
Clustering means that a meeting room is running only on one server at a time.
The Meeting Proxy servers have the information on witch Meeting Server
instance the Meeting Room is running and forward incoming requests to the
right server. Data is stored in the database. In case of a fail over the Meeting
Room will be started on another Meeting Server in the cluster immediately.
For external access a separate Sametime Meeting Server in your DMZ is
recommended for better security.
161. Lotus Sametime
Lotus Notes
or Web clients
Lotus
Sametime
Servers
Meetings 2
Meetings 1
WebSphere
Application
Server Proxy
Cluster
Clustered servers
use the web
services to support
high availability and
failover
Individual meetings
exist on a single
cluster member
Proxy server provides
caching and helps application
server scale; routes HTTP
traffic to correct node
Lotus Sametime 8.5 Meetings
Cluster Deployment
198. Important to know:
The Media Manager uses new Audio and Video codecs (H.264/MPEG4).
The Media Manager uses SIP for VoIP connectivity (Sametime Connect
Client or Notes Embedded Sametime Client).
The Media Manager can be connected to existing Audio and Video
conference systems and provides the interoperability of Sametime Clients
and other A/V endpoints.
The Media Manager is not a PBX. It is just a server with its own connectivity
and TCSPI SDK to connect to other systems.
This has nothing to do with Sametime Unified Telephony.
The Media Manager can be clustered for better scalability if required.
The components of a Media Manager can be split and implemented on
different machines for scalability.
206. Important to know:
The new Sametime 8.5 Connect Client can be installed as a stand alone
version or as Embedded Version in an existing Notes 8.5.1 or newer client.
This works with all language versions of the Notes Client.
The new Meeting Plug-In is automatically installed with this client.
227. We have now finished installing a complete Sametime 8.5 environment in
100 Minutes.
If you have any more questions, come to one of the microphones, please.
More information can be found in the Sametime InfoCenter:
http://publib.boulder.ibm.com/infocenter/sametime/v8r0/index.jsp
228. Other Sametime Sessions
• KEY102 Unified Communications keynote – vision, strategy and roadmap
• ID406 What's New in IBM Lotus Sametime 8.5
• ID402 Sametime System Console - Managing your Sametime Infrastructure
• ID405 Sametime Voice/Video
• AD306 Overview of Sametime 8.5 Browser IM Client/SDK and Proxy Server
• AD307 Web 2.0 Development with Sametime 8.5 Services
• BOOT104 Sametime 8.5 Deployment Workshop (Sunday)
• BP116 How Do I Get There From Here? The Route to Lotus Sametime 8.5
• BP117 Sametime Gateway - Business Case, Best Practices and Implementation
• ID401 Making the business case for Sametime and Unified Communications &
Collaboration
• ID403 Sametime Unified Telephony in Action: Putting it to Work for You
• ID404 Sametime Unified Telephony: Today and Tomorrow