Você está na página 1de 306

Sametime 9 STEW

Author: Rob Fox Super Sametime Worldwide Technical Leader


Worldwide ICS Technical Sales
partnering with
IBM ISV & Developer Relations

IBM Sametime 9.0 Swap Meet

Lab Manual 1.1

Lab 0

Sametime 9.0 Installation Started From


the Bottom to the Top

1
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Introduction:
This lab is designed to show you how to install Sametime 9 from the bottom to the top from scratch. The
target audience for this lab are those who have familiarity with basic networking, VMware, and Sametime
8.5.x. Some Linux experience is helpful but not necessary we all have to start at the bottom to get to
the top.

Description:
You will start with three, clean VMware images one Windows image (sametime9vm.demos.ibm.com),
two Linux images (sametime9avvm.demos.ibm.com, & sametime9mcuvm.demos.ibm.com), and
install Sametime components, including the System Console, Community server, Proxy server, Meeting
server, Media Manager, Video Manager, and Video MCU in this lab, and configure everything accordingly.
Make sure all images can ping each other back and forth, both ways, BEFORE proceeding.

Objective:
This lab will explain the following tasks:

How to install IBM Installation Manager, WebSphere and DB2 on Windows and Linux
How to create Deployment Plans and install Sametime servers
How to configure Single Sign-On (SSO), Domino LDAP, WebSphere security settings

How to write scripts on Windows and Linux for start up and shutdown purposes

How to learn patience and persistence and have fun while being smart

2
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Procedure:
PREPARE THE VMWARE IMAGES

Networking: After downloading and extracting the Windows 2008 R2 Core and Red Hat Enterprise Linux 6
Video Manager VMware images (or providing your own clean images), the Linux image must be cloned to be the
Video MCU image. The extracted folder can be copied as well, as long as I copied it is selected at first boot, and
a new MAC address is generated in the VM preferences under Network Adapter Advanced Settings before first
start up. Then, you will use static IP addresses (or determine new IP addresses) for the Windows and Linux
boxes, update hosts files, and change the network interface back to eth0 on Linux. All servers are configured to
use VMware bridged networking functionality, and can optionally use DHCP to get proper IP address
configuration. For this example, we will manually set an IP address on the servers, however, any IP network
addresses will work as long as all three machines are on the same network. Verify all servers can ping each other
BEFORE proceeding, making note on Windows that Symantec Endpoint Protection may have to be adjusted to
allow ICMP requests from other servers, and in the Windows Network Center, the network will need to be set to
Private. Any clients will be configured similarly, with hosts files updated.
System requirements: VMware Workstation 7-9 / VMware Fusion 3-5 / VMware ESXi 4-5 Workstation 10
does not currently work with the prepared images. In VMware Workstation, be sure to use the 'Fit all virtual
machine memory into reserved host RAM' setting under Edit / Preferences / Memory. To deploy all 3 servers with
all services running, including A/V, a host with 20GBs of memory or more, or two hosts with 12GBs of memory or
more is recommended. The Windows & Video MCU server is allocated 8GBs of memory with the Video Manager
server set to 2GBs lowering the VMware image memory usage may prevent all services from starting up,
however if you do not need everything running, lower specs will be fine. For performance purposes, the Windows
box has a static 4GB swap file, and the Linux box as a 4GB swap partition this should be the minimum size
page file for all systems.
Sametime architecture:
Server 1: Windows 2008 R2 (sametime9vm.demos.ibm.com) -> Domino LDAP, DB2, System Console,
Community, Proxy, Meetings, Media
Server 2: Red Hat Enterprise Linux 6.4 (sametime9avvm.demos.ibm.com) -> Cloud DB, Video Manager
Server 3: Red Hat Enterprise Linux 6.4 (sametime9mcuvm.demos.ibm.com) -> Video MCU

Step 1 After downloading, extract the sametime9vm-base-win2k8.vmwarevm.zip.* and


sametime9avvm-base-rhel6.vmwarevm.zip.* with your favorite multiple part unzipping
program, such as 7-Zip into a directory on the host machine such as vmimages. Note: to save
time if not disk space, you may consider extracting the Sametime 9 installation files as well.

3
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 2 First, we need to make sure VMware is configured for our large memory server images. On
the host computer, before starting any VMware servers, in VMware Workstation, go to Edit /
Preferences / Memory and select Fit all virtual memory into reserved host RAM. It is
extremely important to do this BEFORE start any images failure to do so will result in the
servers running a magnitude of order slower. Also be sure to Reserved Memory as high as
possible. Note: Due to Mac OS X managing memory more efficiently, VMware Fusion does not
have an equivalent setting.

Step 3 Next, we'll need to clone the Linux image so we'll have our two required servers a Video
Manager image and a Video MCU image. Open the two VMware images but do not start
them. Click on the Sametime 9 Video RHEL6 Base image, choose VM Manage Clone,
select a full clone, name it Sametime 9 Video MCU RHEL6 Base, and put it in the same
location as the other images with a folder name of sametime9mcuvm.vmwarevm, click
Finish. Note: On Mac OS X, you can just copy the whole sametime9avvm.vmwarevm
package and paste it in the same location, renaming it sametime9mcuvm.vmwarevm.

4
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

On Windows, it is necessary to generate a new MAC address on the newly cloned VM as well.
Go to the VM's network adaptor settings, push Advanced, and then push the Generate button
in the MAC address section.

5
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 4 Next we must configure the Video MCU image server settings. It requires 8 GB of ram (8192)
& 4 CPU cores. If your machine is low on resources, the image will function with 7 GB of ram
(7168) & 4 CPU cores but may perform poorly. These are the absolute minimum hardware
requirements for the MCU, they cannot be lowered additionally. The original Sametime 9
Video image should be renamed to Sametime 9 Video Manager RHEL6 Base, and requires 1
CPU core & 2 GB (2048) of ram, or 1.9 GB (1920) of ram minimum.

Step 5 The three VMware images are properly configured for Sametime 9's system requirements.

More detailed Sametime 9 System Requirements are on the Sametime wiki & linked here for your convenience:
http://www-01.ibm.com/support/docview.wss?uid=swg27039649

SETTING UP AND STARTING THE WINDOWS CORE, LINUX VIDEO MANAGER & LINUX MCU
SERVER

The Windows image has it's fully qualified DNS name and an alias used for the Sametime Proxy Server to avoid
JSESSION conflicts when using web chat. We will map both names to whatever the new IP address is for the
newly deployed environment.

Start all of the Windows and Linux VMware images. On Windows, log in as 'Administrator' with the
password of 'passw0rd'. On Linux, log in as 'root' with the password of 'collabrocks'. We'll start with the
Linux image.
Step 6 Open a Terminal window. Determine the IP address of the Linux server by typing 'ifconfig'. We
will then update the hosts file by typing 'vi /etc/hosts' or double clicking the 'Edit hosts file' short
cut on the desktop.

6
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

The Windows FQDNs are sametime9vm.demos.ibm.com and sametime9imvm.demos.ibm.com. The two


Linux FQDNs are sametime9avvm.demos.ibm.com and sametime9mcuvm.demos.ibm.com..

Step 7 If you notice the network interface is 'eth1' it needs to be 'eth0'. This sometimes occurs when
cloning a VMware image the Video MCU needs 'eth0' to function properly. If it is already
'eth0', ignore these steps. Otherwise, we will edit the name by issuing the command 'vi
/etc/udev/rules.d/70-persistent-net.rules'.

7
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 8 Notice the previous network interface & MAC address with the name of eth0, and the new MAC
address from the current network interface named eth1.

8
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 9 Remove the old eth0 line, and update the current network interface line to use eth0. Save and
quit.

9
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 10 Edit the hosts file by either issuing the command 'vi /etc/hosts' or double clicking the 'Edit hosts
file' icon on the desktop.

Step 11 Update the hosts file entry with the IP address for the Linux server's hostname entry of
'sametime9avvm.demos.ibm.com' and 'sametime9mcuvm.demos.ibm.com'. If you know
the new Windows IP address, update the two hostname entries there as well.

10
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

On the second Linux VM that will be your VMCU, to change the hostname to
sametime9mcuvm, at a command prompt type hostname sametime9mcuvm, and then
edit /etc/sysconfig/network with the updated hostname of sametime9mcuvm.

Additionally, you can change IP addresses by clicking on System Preferences Network


Connections and Editing the Auto eth0 option in the IPv4 Settings tab, or opening a Terminal
command and typing system-config-network and following the prompts.

11
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 12 Restart the Linux server(s) by issuing the command 'shutdown -r now'.

Similarly to what we did on the Linux Video Manager & MCU server, we will update hosts files, update IP
addresses in the Sametime recordings file, and update the IP address of the Video MCU in the Sametime System
Console. No restart is typically required.

Step 13 On the Windows server, open a command prompt and determine the current IP address by
typing 'ipconfig /all'.

12
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 14 Taking note of the current Windows IP address, and the current Linux IP addresses, update the
Windows hosts file accordingly. There is a shortcut on the desktop named 'Hosts', or you can
navigate to in via C:\Windows\system32\drivers\etc\hosts

13
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 15 Navigate to the Windows Control Panel / Network and Sharing Center section. Make sure
Private network is selected so Windows Firewall and Symantec don't block ports. If you on a
host only network, you may not be able to choose Private network for security purposes.
Change the default Unidentified Network properties to Private by opening a command prompt
and typing secpol.msc, then navigating to Network List Manager Unidentified Networks
and changing the Location type to Private. Note: This is a security risk any network will
always be trusted.

14
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

If Symantec is blocking traffic, you can configure it to allow our specific, private IP addresses.
Open Symantec Endpoint Protection and click the Options next to Network Threat Protection
and click Configure Firewall Rules. Add a new rule, give it a name like Sametime 9, Allow
this traffic on All network adapters, and on the Hosts tab either populate the IP addresses
with 192.168.200.201-192.168.200.203 or the Subnet with 192.168.200.0 / 255.255.0.0.

15
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

If you wish to use static IP addresses, you can set them here as well.

16
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 16 Ping all machines with all machines. If every host can ping all hosts, proceed, otherwise,
continue troubleshooting and do not pass go. All machines resolvable? Excellent! Now we
can finally begin the Sametime 9 installation... get ready!

PREPARE WINDOWS 2008 R2 FOR SAMETIME 9

In order for Sametime Meeting recordings to work properly, it is necessary to install the Windows Desktop
Experience. It will install the necessary Windows Media Video DLLs required for rendering the captured meeting
activity. Additionally, to avoid network port conflicts with Domino, we must adjust Windows system level TCP
parameters so internal running services don't interfere with Domino processes.

17
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 17 On the sametime9vm.demos.ibm.com image, go to the Windows Control Panel Programs


& Features and click on Turn Windows Features on & off.

18
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 18 Select Features and choose Add Features.

19
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 19 Select Telnet Client & Desktop Experience. You'll be prompted to install Ink Support as well.
Then hit Next.

20
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 20 Confirm you selections of Desktop Experience, Ink Support and Telnet Client, and press Install.

Step 21 You'll be asked to restart when the installation is complete, but don't do that yet. The task will
finalize at next start up, and Desktop Experience will be installed.

21
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 22 Open the Administrator Command prompt and type 'netsh int tcp show global'. You'll see your
current TCP Global Parameters. They need to be disabled, but we'll make a backup first.

22
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 23 Run regedit, navigate to the


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters key,
and export it, saving to the Documents folder.

Step 24 Run these four commands:


netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global congestionprovider=none

23
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 25 Type 'netsh int tcp show global' again to see if the changes went into effect. Reboot the server.

Windows 2012 R2 is ready for Sametime..

INSTALL DB2

IBM DB2 10.1 is the data store repository Sametime 9 uses for System Console settings, Meeting room
information and files, and Proxy offline messages for chat and mobile. It is no longer installed as part of the
Sametime 9 installer itself it must be deployed manually, but fortunately the installation is straight forward. After
this installation, make sure the green DB2 cylinder icon in the Windows system tray is ALWAYS running , and
there is no red error box, or the WebSphere servers will not operate correctly.

Step 26 Locate your Sametime 9 installation files it is recommended to access these archives from an
external hard drive or a network file share. Extract the DB2_10.1_Win.zip file to C:\Temp, and
run setup.exe as Administrator. Choose Install a Product, then push the Install Now button

24
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

under DB2 Workgroup Server Edition Version 10.1.

25
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 27 Click Next, accept the license agreement, and choose Typical installation type.

26
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 28 Select Install DB2 Workgroup Server Edition.

Step 29 The install directory should be C:\IBM\SQLLIB. This is where the main program files live
the databases themselves will be in C:\DB2.

27
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

I recommend installing all Sametime software into C:\IBM. I highly recommend against using
the Program Files default, as it may present issues with spaces in paths, length of paths,
permissions on paths, etc.

Step 30 Choose C:\IBM\IBM SSH Server for the install path, and allow it to automatically start up. This
will enable you to remotely login to this server via ssh (or putty) and issue db2 commands if
necessary.

28
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 31 Name the local user account db2admin and create a password. I'll be using passw0rd for
this exercise.

29
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Keep in mind, this account must adhere to any local Windows security policies, so make sure
to create a password that is compliant, however be careful with certain special characters are
they may interfere with some XML files and WebSphere scripting events.

Step 32 Click Next to create the default DB2 instance called DB2 (no need to configure anything
additionally), uncheck Set up your DB2 server to send notifications (not needed) and hit Next,
and enable OS security and use the defaults for users and groups.

30
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 33 Confirm your selections and push the Install button. While files are copying, Symantec
Security may prompt to allow core DB2 processes such as db2nmpcfg.exe to access the
network allow this and remember the answer.

31
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

32
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 34 Congratulations DB2 is successfully installed. You will be prompted with a First Steps
dialog box to create a sample database close this box, there is no need. Reboot Windows.

INSTALL DOMINO 9

We will be installing Domino 9.0 to use not only as a Sametime 9 Community server, but also as an LDAP server
for our environment. Note that we must use the 32-bit version of Domino 9 because the Sametime 9 Community
server is a 32-bit application if you use the wrong version of Domino, the Community installation will not detect
the Domino 9 instance. The Domino installation process is well known, simple, straight forward, and we'll be
installing it in the normal way, so not every snapshot will be pasted.

Step 35 As an Administrator, double click on the Domino9.0_Win.exe file, extract the files to C:\Temp,
accept the license agreement and install Domino to the C:\IBM\Domino directory.

33
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 36 For the Domino Data Files directory, choose C:\IBM\Domino\data, select Domino Enterprise
Server, and verify your choices before hitting Next to begin the installation:

34
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 37 Once the installation is complete, click Finish to close the installer, and back on the Windows
desktop, double click on the IBM Domino Server to start the Domino Server Setup wizard.

35
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 38 Select Set up the first server or a stand-alone server and choose a server name of
sametime9vm with a title of Sametime 9 Community Server and push Next.

36
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 39 For Organization name, type demos and create a password. This exercise will continue to use
passw0rd as the password for everything going forward.

37
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 40 For the Domino domain name field, type demos as well, and name the Domino Administrator
Domino Admin with a password of passw0rd.

38
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 41

Step 42 For Internet services, this Domino server will need the Web Browsers (HTTP servers) and
Directory services (LDAP services). Click the Customize button to verify those two options
are selected.

39
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 43

Step 44 Next, click the Customize button and verify TCP/IP is checked, and the fully qualified domain
name is fill out appropriately.

40
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 45

Using the fully qualified DNS name here is extremely important for single sign on operation (SSO), logging in,
awareness, etc make sure this is not a short name or many aspects of Sametime will fail.

Step 46 Verify Prohibit Anonymous access & Add LocalDomainAdmins group are checked, verify
your settings, and push Setup and Finish to complete the Domino server installation.

41
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 47

Step 48 Next, we will install the Domino Administrator Client to administer the Domino server. As an
Administrator, double click on the DOMINO_DESI_ADM_9.0_32B_WIN_EN.exe archive
located on the companion X: drive in the sametime9vm Windows image, extract the files to
C:\Temp, accept the license agreement and chose to install into the C:\IBM\Notes and
C:\IBM\Notes\Data directories.

42
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 49 Select the Notes Client, Domino Designer (we won't be using it for this lab but it's a handy
tool), Domino Administrator with Migration Tools, Connections, Feed Reader, OpenSocial
and Sametime so you get all of the new social aspects of Notes/Domino 9.

43
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 50 Choose to make Notes the defaults, but since we are running with low memory restrictions, do
no Launch parts of Notes at start up. Choose Next and Finish.

Step 51 We will now connect the Domino Administrator client to our Domino server. Back on the
Windows Desktop, as an Administrator, double click on the IBM Domino Server icon again
and choose Start Domino as a Windows service, but uncheck Always start Domino and
push OK the Domino server will now start up. You should go to the services control panel
and make sure that the service is not set to automatic.

44
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 52 Back on the Windows Desktop, as an Administrator, double click on the IBM Domino Admin
icon, type in Domino Admin for Your name, and sametime9vm/demos for the Domino server,
making sure to check the box to connect to it.

Step 53 Type in the password of passw0rd, skip setting up instant messaging (we haven't gotten that
far yet) and all of the other services and client Finish. The Domino Admin client is connected.
Click on the DEMOS Domain tab to see all of the possible actions.

45
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Domino is now ready.

CONFIGURE DOMINO LDAP

With Classic Sametime Meetings no longer in the picture, it is less of an obstacle to use the local Domino server
as our LDAP instance. There are still numerous modifications to be made, but otherwise, it will perform all of the
directory operations we need. Because we'll need to start LDAP independently of Domino often, we'll create a
script to start the nldap.exe service, and then the WebSphere components will be able to connect and start up.

We will build our LDAP repository using an LDIF from our One Demo World community, which has users
prepopulated with pictures, addresses, phone numbers, email address and other extensive pieces of metadata.
Sametime requires these LDAP attributes for meeting and telephony functionality, as well is business card
displays. But first, we will manually register a few users to begin.

Step 54 Click on the DEMOS Domain tab of the Domino Administrator highlighting the People &
Groups tab & click People. Open the Domino Admin person document, add an email address
such as dadmin@demos.ibm.com, save & close. To begin adding more users, click on
People on the right and then push Register.

46
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 55 Supply the Certifier ID located in C:\iBM\Domino\data\cert.id using the Server


sametime9vm/demos, push OK, enter the password of passw0rd and hit Enter.

47
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 56 Now you should register yourself using your own name. In the Basics section, fill out a first,
last, & short name; a password of passw0rd, using Notes as mail, and create an ID. Tick the
Advanced check box to view more tabs.

48
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 57 Click on the Password Options button and check the Set Internet password box users will
be unable to log into Sametime chat or meetings without an internet password created.

49
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 58 In the iD info section, allow the user ID to exist in the Domino directory and on the local file
system at C:\IBM\Notes\Data\ids\people. This will allow easier Notes ID file management
later.

50
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 59 Once complete, push the green check box to add the new user to the registration queue. You
can add a few more users if you wish multi point A/V meetings are usually easier to conduct
with more than one person. When finished with this first allotment of users, push the Register
All button, and they will be created in the Domino directory. Don't push the Done button quite
yet after the registration is complete, push the Migrate People button.

51
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 60 Browse to the LDIF file, X:\Notes_Installs\demos.ibm.com LDAP v3.5.ldif, push OK, and
choose LDIF entries, and then finally push the Migrate button and then Done. 91 people
should be successfully queued for registration with 0 errors.

52
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 61 You'll see the 91 people in the LDIF. Push Register All again to register all of them, and then
push the Done button. Once back at the People view in the Domino Administrator, push
Control+Shift+F9 to refresh the view, which will also refresh the LDAP process.

53
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 62 Look in the Groups view in the Domino Administrator. Notice there are only 3 entries. Domino's
LDIF migration tool does not import groups in an LDIF, so we will do this manually by copying
from a database into this view. Click on File Application Open , and choose X:\Group
db\Placeholder for groups.nsf . Select all 18 entries, and click Edit Copy.

54
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 63 Go back to the demo's Directory Groups page, and paste the entries into the view to populate it
with the correct groups .

55
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 64 When using an LDAP server, typically applications specify a base Distinguished Name (base
DN), such as o=demos, to begin searching for names and groups. When using Domino LDAP,
if you use a base DN, the only entries that are returned are those with the Domino domain
name separated by a slash at the end of them, such as Rob Fox/demos.

When registering users, you'll notice in each Person document that the first entry for each user
name is the full name with a slash and domain name, so they show up properly in LDAP, but
each Group document does not have this slash domain name, so it will not appear in LDAP.

We could use a blank base DN, as the groups will appear in the very root of the LDAP directory
tree, but it is preferable for WebSphere to use a real base DN, so we must add a slash domain
name to each group entry. Additionally, we will add a semi colon and then the current group
name as well so existing apps and ACLs will still be able to see the previous name in addition
to the new name.

In conclusion, a group named Administrators becomes Administrators/demos ;


Administrators, like in this example - Company Wide becomes Company Wide/demos ;
Company Wide.

56
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 65 Add /demos (slash demos) to all 18 groups in the Domino directory groups view. You will be
warned that it is recommended that the slash character not be used in the Group Name field.
Push OK and continue. When finished with all groups, push Control+Shift+F9 again to refresh
the view for the nldap.exe process. Ignore the LocalDomainAdmins, OtherDomainServers and
the LocalDomainServers.

57
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 66 To test our users and group, we will use an LDAP browser Softerra LDAP Browser 4.5 is
currently installed. Since Domino is still running, the LDAP service is running as well. Run the
LDAP client, create a profile name, use sametime9vm.demos.ibm.com as the server name
(or localhost), port 389 (LDAP port), and a base DN of o=demos.

58
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 67 To get the most attributes returned, rather than binding anonymously, use a pre defined user,
often thought of as a bind ID. The Domino Administrator account will accommodate this task
well. For the principal name, use cn=Domino Admin,o=demos, with a password of
passw0rd. Save the password and push Finish.

59
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 68 Choose the user you manually created. You should see the cn, mail, uid, and other LDAP
attributes. Next click on a group, such as Office of the CEO make sure it appears and it is
populated correctly.

60
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 69 Note: We may have to run an agent that will open and save each person document of
everyone entered via LDIF due to those entries not being created conventionally. Also, the
Domino Admin does not import photos nor the PhotoURL LDAP attribute needed for Sametime
business cards we'll address this later, but for now, lets create this simple agent.
In the Domino Administrator while in the People and Groups / People view, at the top click
Create Agent. In the properties box that appears, name this agent Update Person Docs.
In the client on the left under Objects, first click on Options and make sure the only values
there are Option Public, then click on Initialize and copy / paste the following LotusScript text,
then save & close the document:

Sub Initialize
Dim s As New NotesSession
Dim db As NotesDatabase
Dim dc As NotesDocumentCollection
Dim dt As New NotesDateTime("01/01/80")
Dim doc As NotesDocument
Dim item As NotesItem

Set db = s.CurrentDatabase
Set dc = db.Search("Form = 'Person'",dt, 0)

For i = 1 To dc.Count
Set doc = dc.GetNthDocument(i)
Print "Working on... " + doc.FullName(0)
Call doc.ComputeWithForm(False, False)
Call doc.Save(False, False)
61
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Next
Messagebox "Agent is finished running.", 0, "Lotus Notes"
End Sub

Note: When using Domino Designer, it enforces strong typing, so the LotusScript won't work as
pictured until that option is removed as detailed above, or the i integer is declared
specifically. Domino Administrator is not so picky, for better or for worse.

Step 70 Now to run our newly created agent. In the Persons view, push Control + A to select all 91+
persons, then click at the top Actions Update Person Docs you will see Verifying... in
the bottom message window for everyone. When this agent finishes... Our directory is
compete.

Domino LDAP is now ready.

INSTALL IBM INSTALLATION MANAGER

Sametime 9 no longer installs Installation Manager and WebSphere automatically for the user. Fortunately, both
of these installations are straight forward, and give more clarity on exactly how Sametime is laid down. Once we
install Installation Manager, 1.6.2, we can then use it to install WebSphere 8.5.5, WebSphere iFixes, and then the
Sametime 9 server components themselves. This is also the means of installing future Sametime hot fixes no
more nightmare upgrade scenarios.

Step 71 Extract IM_1.6.2_Win.agent.installer.win32.*.exe into C:\Temp, run install.exe as


Administrator, check the box for Version 1.6.2, and accept the license agreement. The

62
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Installation Manager Directory should be C:\IBM\Installation Manager\eclipse.

Step 72 Push the Install button, and shortly afterwards, it will complete. Push Restart Installation
Manager. We will now prepare to install WebSphere 8.5.5.

IBM products can now be installed.

INSTALL WEBSPHERE

Now that the IBM Installation Manager 1.6.2 has been installed, we can install WebSphere 8.5.5, and the required
iFixes. Once we've installed WebSphere, we can finally start installing the Sametime 9 server components.

Step 73 Extract the three WAS_ND_V8.5.5_#_OF_3.zip and the


Sametime9.0.0_WebSphereiFixes.zip so they are all in the same directory in C:\Temp. You
should see disk1, disk2, & disk3 in the same folder, and the 11 iFixes in another directory as
well.

63
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 74 Go into the Preferences of the IBM Installation Manager, select Repositories, and push the Add
Repository button.

64
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 75 Go to the drive location (C:\Temp) where the three WebSphere installation zips were extracted
into one directory, and point to the repository.config file. This will add the WebSphere
installation files to IBM Installation Manager.

65
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 76 It will be added to the repository as shown. Uncheck the Search service repositories option.
We need to add the iFixes next.

66
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 77 Push the Add Repository button again, and add all 11 iFix zip files. Once complete, push OK to
begin the installation of WebSphere 8.5.5.

67
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 78 Begin the installation process by clicking the Install button. Select WebSphere 8.5.5 and push
Next.

68
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 79 Select all of the iFixes for WebSphere 8.5.5 and push Next.

Step 80 Accept the license agreement, and choose C:\IBM\IMShared as the shared resources
directory. Files that may be reused across different installations will reside here.

69
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 81 The package group the installer is referring to is where the main WebSphere home directory
will live. Again, we want to avoid Program Files due to spaces, length of paths, and permission
restrictions, so we install to C:\IBM\WebSphere\AppServer.

70
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 82 For Sametime, we require the WebSphere Full Profile, so verify that option is checked. We
don't see sample applications. It is very important to note that we need to uncheck the 32-bit
SDK for Java and only check the 64-bit SDK for Java as we'll be running WebSphere
application in 64-bit mode.

71
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 83 Verify all components are present, including iFixes, and begin the installation. This will take
approximately 15 minutes on a moderate machine.

72
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 84 Once the installation is complete, you will be shown all of the files installed, and asked to
create a profile via the Profile Management Tool. Sametime will do this for us, so choose None
and hit Finish.

73
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 85 Congratulations WebSphere is installed. Now we are finally ready to install our first
Sametime 9 component. This is an excellent point to take a state snapshot, so shutdown
Windows and in VMware, snapshot the image.

WebSphere can now be used to install Sametime components.

INSTALL SYSTEM CONSOLE

We will now install the Sametime 9 System Console. The System Console, or SSC,is the unified location for all
administration and deployment scenarios for Sametime 9. First we will create the Db2 database for all
configuration information to be stored in, and then we will install the product using Installation Manager.

Step 86 Extract SametimeSystemConsole.zip, Before we begin the installation, we need to create the
System Console database. All of the scripts needed to do so are in the newly extracted
DatabaseScripts directory.

74
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 87 Open up an Administrator Command Prompt, and navigate to the extracted


\SametimeSystemConsole\DatabaseScripts\SystemConsole directory, and run the
command 'createSCDb.bat STSC db2admin'. The batch file actually creates the database for
Sametime, the STSC is the name of the database we are creating (can be something else as
long as it's under 8 characters long) and db2admin is the DB2 Administrator we created when
we installed DB2.

75
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 88 This command takes a few minutes to run and may appear not to be doing anything. It is.
Eventually, you will get a window full of 'The SQL command completed successfully'.

Step 89 To verify the database was created correctly, from the Windows Start Menu, click on IBM DB2
DB2COPY1 (Default) Command Window Administrator and type 'db2 connect to
STSC'. A Connection should be established to the database.

76
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 90 Now we can begin the proper System Console installation. You could add the repository.config
located in the extracted directories to the IBM Installation Manager, and use it to install System
Console, but that is needless extra work. Using the launcher is effectively the same thing. Run
launchpad.exe, click on Install IBM Sametime System Console, and click Launch System
Console Installation. choose Install, and check the IBM Sametime System Console server
Version 9.0.0.0 option.

77
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 91 Accept the license agreement, and similarly to how WebSphere needs a home directory, the
64-bit Sametime server files need a home directory as well. Use C:\IBM\SametimeServer.

78
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 92 Check the box to Sametime System Console server 9.0.0.0, hit next, and then enter the path of
WebSphere home, which is C:/IBM/WebSphere/AppServer. Push the Validate button to
prove to Sametime you know what you are talking about. Once validated, you can hit Next.

79
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 93 We are now configuring WAS. By default, the WebSphere Cell and Node are based on the
short name (see our previous enablement on details of what a WAS cell and node are), so
leave the defaults. For host name, use the fully qualified DNS name (FQDN), that is
sametime9vm.demos.ibm.com. For the WebSphere administrator user ID, we must use
someone not in the Domino LDAP, so use wasadmin, and give her/him a password of
passw0rd. Hit Next.

80
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 94 Now we must enter our DB2 database repository connection information. We installed DB2 on
this same box, so type sametime9vm.demos.ibm.com for the FQDN. DB2 on Windows by
default uses port 50000, and on Linux uses 50001 since we're on Windows, enter 50000 for
the port. We chose the name STSC for the database where all of our Sametime configuration
and deployment information will be stored, and we used db2admin and passw0rd for our DB2
Admin credentials. Push Validate since Sametime trusts you.. but wants to verify you.

81
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 95 Once you've confirmed everything, push the Install button. This process could take up to 1.5
hours on a moderately spec'ed machine.

82
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 96 Congratulations, the installation should have completed successfully. If there were issues,
examine the logs, accessible via the 'View Log File' link, correct the problem and try again,
however the System Console is a pretty straight forward install. When finished, push Finish,
and we will test.

83
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 97 To test, open a web browser to http://sametime9vm.demos.ibm.com:8700/admin . Accept


the self signed certificate by adding the exception.

84
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 98 Login with wasadmin and passw0rd. You will be presented with the main WebSphere Admin
Console page. On the left you'll see various WAS admin tasks, and at the bottom of that list
you'll see the Sametime System Console list, with all of the Sametime 9 related tasks.

85
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 99 The last task we will do here is to adjust the maximum Java heap size, so the WebSphere
deployment manager won't run out of memory as we use it more and more. Starting on the
left, click on System administration Deployment manager Java and Process
Management Process definition Java Virtual Machine and change the Maximum heap
size to 2048MB and push OK and Save. WebSphere will need to be restarted.

86
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 100 To stop and start WebSphere, you can use Windows services, but I've seen instances of where
the status isn't reported correctly, or servers don't stop and start as they should. For this
exercise, we'll use the command line to stop the servers. For the Sametime System Console,
there are three servers to account for.

WebSphere has two components the deployment manager and the node agent. The
deployment manager (dmgr) handles all aspects of WAS administration and is where the GUI
to the admin console is derived from. The node agent (nodeagent) starts and stops servers
accordingly if you use the GUI to do so. Since we made a change to the deployment manager
itself, we'll need to restart it. The third component is the System Console itself, which is simply
a WAS application called STConsoleServer.

To start and stop these servers manually, we have to go into each servers profile directory in
the WAS home and run the start and stop scripts with parameters. Here are the three
commands for stopping the Sametime System Console completely this is also the order they
should be stopped in. Open an Administrator Command Prompt and type the following three
commands:
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\bin\stopServer.bat
STConsoleServer -username wasadmin -password passw0rd
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\bin\stopNode.bat -username
wasadmin -password passw0rd
C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\bin\stopManager.bat -username
wasadmin -password passw0rd

87
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Notice how the System Console application and node agent live in the STSCAppProfile
directory, and the deployment manager itself lives in an STSCDMgrProfile directory. Also,
because stopping a server is an admin task, we must specify the WAS admin credentials to do
so. All three servers will report Server <name> stop completed when they are shut down
properly.

Step 101 Now, to start the the servers manually, we do so in the opposite order we stopped them. The
deployment manager must be running first since it is the core of WebSphere. Next, we'll need
to start the node agent which controls the application servers, and finally we start the System
Console application server itself. Notice we don't need to specify a user name or password. At
the command prompt type these commands:

C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\bin\startManager.bat
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\bin\startNode.bat
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\bin\startServer.bat
STConsoleServer

88
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 102 Wise words were spoken - work smarter, not harder. On the desktop, create batch files that
do this for you, as we will be restarting servers frequently. Here is startSSC.bat :

@echo off
time /t
call C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\bin\startManager.bat
call C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\bin\startNode.bat
call C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\bin\startServer.bat STConsoleServer
time /t
call pause

Step 103 Here is a stopSSC.bat as well:

@echo off
time /t
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\bin\stopServer.bat STConsoleServer -username
wasadmin -password passw0rd
C:\IBM\WebSphere\AppServer\profiles\STSCAppProfile\bin\stopNode.bat -username wasadmin -password
89
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

passw0rd
C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\bin\stopManager.bat -username wasadmin -password
passw0rd
time /t
call pause

Step 104 The last thing to configure is Domino LDAP Sametime 9 requires an LDAP version 3
compliant directory server for user and group look ups, and our freshly configured local server
will do the job. This will not only provide an easy way to configure the remaining Sametime 9
components that depend on LDAP (System Console, Meetings, Community), it will reconfigure
the base WebSphere instance to use Domino LDAP as it's directory. Because we are using
Domino as our Community base and LDAP base, we will make a short script that will allow us
to start LDAP independently of Domino. The LDAP task is located in C:\IBM\Domino and is
called nldap.exe .

90
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 105 Create a script on the desktop called startLDAP.bat on the Windows desktop that look like this
(you may or may not need quotes around the path):

@echo off
time /t
call C:\IBM\Domino\nldap.exe

Note: Whenever this script is run, a Domino LDAP / nldap.exe console window will appear. Do
NOT close it, as this will kill the LDAP process instead minimize it to avoid any accidents or
temptation.

Step 106 Domino should still be running, therefore LDAP should still be running you can confirm with
Softerra to make sure it can connect correctly. If not already, log into the WAS Admin Console,
and click on the left Sametime System Console Sametime Prerequisites Connect to
LDAP Server. Push the Add button.

91
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 107 With many LDAP servers (Active Directory's Global catalog on port 3268 comes to mind), when
we bind with an ID rather than use Anonymous, more LDAP attributes are returned, and
Domino is no exception. Choose Authenticated Access, enter a Deployment Name (can be
anything, for example, Domino LDAP), Host Name is sametime9vm.demos.ibm.com , port is
389, do not check Secure LDAP, use cn=Domino Admin,o=demos & passw0rd for the Bind
distinguished name (DN) and password, and push Next.

92
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 108 We want to start our directory search at the base of the LDAP tree, so we'll use o=demos for
the LDAP base entry, and check the advanced settings option, and click Next.

93
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 109 We will now need to configure a person entry and group entry. We can look at an individual
and a group to determine all of the names for each attributes, and then enter them into
WebSphere accordingly. If Softerra isn't already running, start it and connect to the local
Domino LDAP. Choose any person entry, and take note of the user attributes, such as their
objectclass, cn, uid, mail, telephonenumber, photourl, jpegphoto, etc.

94
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 110 Now we must map attributes to the fields presented. Object class = inetOrgPerson, LDAP
user search base = o=demos (this is useful if our people and groups are in different trees),
UUID: dominounid, Display name = cn, similar name distinguisher = uid, email = mail, Home
Sametime server = sametimeserver (we won't be using this field in our single server
deployment, so it can be left blank). Note we would only use Distinguished Name rather than
UUID: dominounid if we are using Domino Name Address book rather than Domino LDAP
proper. The Sametime 9 Wiki has more information.

LDAP search filters are used for authentication and searching for users and groups.
Fortunately, we don't have to type up the syntax for these search filters as WebSphere will do
that for us based on the base DN and the attributes we specify here for authentication and
search. Sametime Meetings REQUIRES the mail attribute be FIRST for authentication and
search, so for both of these fields, we'll use mail;cn;uid. This means we can authenticate with
a users email address (robfox@demos.ibm.com), cn OR display name (Rob Fox), OR unique
ID (rfox) AND they must be an inetOrgPerson (a person with Internet attributes). The resultant
search filter would look like this if we were to type it out manually:

(&(objectclass=inetOrgPerson)(|(mail=%s)(cn=%s)(uid=%s)))

95
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 111 Now let's do the same for a group LDAP entry. Observe the objectclass, cn, mail,
displayname, member, etc attributes. Note some other LDAP server use uniquemember to
identify members of a group rather than Domino's use of member.

96
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 112 Armed with the correct information, populate the fields accordingly. Object class =
groupOfNames, LDAP group search base (handy if groups are located somewhere else in the
tree) = o=demos, display name = cn, similar name distinguisher = mail, group membership
attribute = member. Click Next.

97
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 113 Verify all attributes are correct and push Finish. WebSphere is now configured to use Domino
LDAP as one of it's repositories. IMMEDIATELY restart all the WAS servers doing anything
else in the Admin Console before restarting could cause the server to not be able to login
again. Which is bad. Also, given that WAS is now configured for LDAP use, LDAP must
ALWAYS be running BEFORE starting up WebSphere. If you forget this, you won't be able to
log into WAS nor stop it without killing the java.exe processes, which could cause corruption,
and prevent WAS from starting up ever again. This is also bad. Avoid all this by remembering
to always start LDAP before starting WebSphere, and keeping in mind stopping Domino will
stop the nldap.exe process.

98
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 114 If you are still able to login as wasadmin after restarting the WAS server, congratulations,
you've successfully configured the Sametime System Console. You may consider taking a
system snapshot at this point.

WebSphere is using Domino LDAP as it's person repository.

INSTALL COMMUNITY

With Domino installed and LDAP configured, we can now install the Sametime Community server, which provides
the chat and rich presence and awareness for the Sametime 9 server stack. We will install the Community server
on top of the Domino server, and then we can install the remaining Sametime components, which are all
WebSphere based applications. With System Console installed, we use it to create a Deployment Plan, and then
run our installation media, point to the System Console to retrieve installation information, and then let it lay down
files as needed. Using System Console to deploy the various Sametime components makes things much easier
to install and configure. Note the System Console is now a REQUIRED component for Community it is no

99
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

longer possible to deploy a Community server without an SSC due to how policies are now handled via the
System Console.

Step 115 Verify LDAP is running FIRST, then verify WebSphere is running, and finally verify Domino is
running. Log into the Sametime System Console, and navigate to Sametime System
Console Sametime Guided Activities Install Sametime Community Server. Select
Create a New Deployment Plan, and push Next.

Step 116 Name the deployment something like Sametime 9.0 Community Server or ST9_Comm or
whatever you wish, hit Next, choose version 9.0.0 , hit Next, then for the Domino server host
name use sametime9vm.demos.ibm.com , use HTTP port 80, Domino User ID of Domino
Admin and passw0rd. This step verifies the Domino server exists, and the user specified is
an admin as it connects to Domino's web port. If all of the information is correct, hit Next to
proceed. Note, on some Domino installations, you may have to use the Domino Domain name
with the Domino Administrator name, like Domino Admin/demos, or the full canonical name
like cn=Domino Admin,o=demos your mileage may vary.

100
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 117 Next choose the Domino LDAP server we previously deployed, and do not check HTTP
tunneling, verify your settings, and push Finish. You have completed the first step to installing
a Sametime server.

101
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 118 You will now see your Sametime 9 Community server ready for installation. Now it is time to
start the actual installation.

102
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 119 Here is where it gets a little tricky. The Domino server cannot be running while Community
server is installing, but we need Domino LDAP to be running so the System Console can
register the Community server. To work around this issue, we will leave Domino and LDAP
running until right before the Community installation checks for running Notes processes. We
will then stop them, let the Sametime installer do it's check, and IMMEDIATELY restart JUST
the nldap.exe process via our script. We'll begin by extracting STD_SERVER_WIN.zip to
C:\Temp , running setupwin32.exe, choosing your language, and sitting at the Welcome to
IBM Sametime Server 9.0 screen. Do NOT hit Next until we stop Domino first.

103
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 120 STOP the Domino server. You can do this by double clicking the Domino Console icon, logging
in, and type quit at the command line, or going to Windows Services, selecting IBM Domino
Server and choosing Stop. Note this will kill the nldap.exe process underneath which will
make WebSphere VERY cranky, so we must restart LDAP individually as quickly as possible.

104
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

105
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 121 Once Domino is stopped, click next you'll see the license agreement. STOP.

Before accepting it, IMMEDIATELY double click on the startLDAP.bat script on the Windows
desktop to get LDAP up and running again after the Sametime installer has checked for
running Notes processes. Once LDAP has successfully restarted, then proceed to accept the
license agreement.

Step 122 The installer will determine if a Domino server ID has a password (don't do that), and will ask if
you want to use the Sametime System Console. Choose yes, and fill out the fields accordingly.
Sametime System Console hostname = sametime9vm.demos.ibm.com, Use SSL =
106
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

checked, SSC port = 9443, SSC admin = wasadmin/passw0rd, FQDN of the Sametime
server we are installing on, which is this same box = sametime9vm.demos.ibm.com. Hit next
as the installer looks for the correct matching deployment plan.

Step 123 The Sametime 9.0 Community Server deployment plan previously specified should appear.
Click next, and verify the settings. If everything is correct, push the Install button.

107
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 124 Files will install. When finished, you will be prompted to reboot the system. Choose no, but
shutdown WebSphere via stopSSC.bat and then restart the system. After Windows comes
back, the correct order to restart everything is startLDAP.bat, then startSSC.bat, then the IBM
Domino Server. Do NOT close the startLDAP.bat console or that will stop the LDAP process,
wreaking havoc on all things WebSphere. Congratulations, the Sametime Community server is
complete.

The Sametime Connect Rich Clients are located on the X: partition. You may now use them to chat, with rich
presence and awareness.

INSTALL PROXY

The remainder of the Sametime 9 server components we will be installing from here on out (save for the Video
MCU) are all WebSphere based applications, and they follow a very similar process, which is create a database in
DB2, connect to that database, create a deployment plan, and run the Installation Manager which deploys the
Sametime applications into WebSphere.

Next up is the Sametime Proxy, which, despite it's name, provides rich presence and chat over the web, and also
is the server Android and iOS mobile chat clients will connect to. The Sametime Proxy is also required to provide
awareness in the Sametime Meeting room, and is required for web A/V. Finally, developers utilizing the
Sametime SDK will connect to the Sametime Proxy server and will use REST APIs to do Sametime functions.

108
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

The Sametime Proxy server only needs the System Console and Community server running it does not
connect to LDAP, however we still need LDAP running for the SSC to work properly. Let's begin now.

Step 125 First, we will create the data store where offline messages will be held, similar to how we
created the database for SSC. Extract SametimeProxyServer.zip to C:\Temp . Open an
admin command prompt, and navigate to the
\SametimeProxyServer\DatabaseScripts\ProxyServer directory, and run the command to
create the Proxy database called STPS:
createProxyDB.bat STPS db2admin

Step 126 The database SQL commands should complete successfully. Opening a DB2 Command
Prompt with the command db2 connect to STPS should return successfully, as before.

109
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 127 Now in WebSphere, we must tell SSC about this database Login as wasadmin and under
Sametime System Console Sametime Prerequisites Connect to DB2 Databases you
will see the previously created STSC database used for System Console. Push Add.

110
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 128 The DB2 host name = sametime9vm.demos.ibm.com , port = 50000, the name of the
Sametime Proxy database we just created = STPS, user credentials = db2admin/passw0rd.
Leave IBM i unchecked, and hit Finish. If the SSC can connect to the database successfully, it
will return.

111
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 129 Now under Sametime Guided Activities, we will choose Sametime Proxy Server, Create a New
Deployment Plan, specify a name such as Sametime 9.0 Proxy Server, and choose 9.0.0,
similarly to how we've done before. However since this is a WebSphere product, we must
choose between a Primary Node, Secondary Node, or a Cell deployment of the Proxy server.

If this was the second server in a cluster, we'd choose secondary node. If this was a stand
alone WebSphere server that was NOT going to use an existing WAS deployment manager,
we would choose cell. However, since we are using the System Console as our WAS
deployment manager, and this is the first Proxy server in our deployment, we will choose
Primary Node. Click Next.

112
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Note, even if we were deploying the Proxy server on a separate box, we'd still choose Primary
Node and use the deployment manager remotely WebSphere would handle those
connections for us.

Step 130 When we installed the initial WebSphere deployment, it created a cell we want to use our
System Console / WAS server as the cell that will control and administer this Sametime Proxy
WAS application server. Choose the System Console option.

113
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 131

Step 132 The next screen will ask for the hostname and WAS administrator name we want to specify for
this WAS app server. Because we will be installing the Meeting server on this same box, we
will need to use a DNS alias to avoid JSESSION cookie conflicts when clients connect to
Meetings from a browser. We will still install the Proxy server with the same host name, but in
all configuration, we will use a DNS alias of sametime9imvm.demos.ibm.com. Add the entry
now to the Windows hosts file located at C:Windows\system32\drivers\etc\hosts.

114
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 133 Back in WebSphere, specify the host name of the Proxy server, which will be
sametime9vm.demos.ibm.com. We are NOT using the DNS alias here, because
WebSphere may not recognize the server properly, and not iterate important WAS ports, which
may cause conflicts, and prevent other servers (such as the Meeting server when installed on
the same box) from starting up. Manually editing multiple serverindex.xml files is not fun, so
we use the same host name of sametime9vm.demos.ibm.com for now. Make the user ID
wasadmin/passw0rd. Note, this can be something different than the main WAS administer
name, but it is best to keep these credentials the same across all application servers we'll be
installing.

115
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 134 Choose the Community Server this Proxy will connect to, which will be the already
installed/registered Sametime 9.0 Community Server previously specified, select the STPS
database previously created, verify your settings, and press Finish.

116
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

117
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 135 The Sametime Proxy is now ready to install. You can view the summary if you'd like.

Step 136 Go to the extracted \SametimeProxyServer directory and as an administrator run


launchpad.exe. Like any WebSphere application, you can install the product by running the
Installation Manager itself, adding a repository, and pointing to the repository.config file, but
running the Launch Pad effectively does the same thing. Click on Install / Launch IBM
Sametime Proxy Server 9.0.0 Installation, click Install, choose the Proxy server 9.0.0.0, accept
the license agreements, and select the 64-bit C:\IBM\SametimeServer existing package
group. Click next.

118
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 137 Check the box to Use Lotus Sametime System Console to install, click Next, and validate the
existing WAS location. At the SSC login screen, specify the System Console information,
similar to previous steps. For the host name of the offering, use
sametime9vm.demos.ibm.com, since we are installing the Proxy on this same box (but NOT
using the DNS alias yet again, using the alias here will BREAK the Meeting Server install
next, so stick with the actual host name). Validate and click Next.

119
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 138 The Sametime 9.0 Proxy Server deployment plan will appear select it, and validate the
settings.

120
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 139 Verify Domino LDAP, the Community server, and the System Console are all running, then hit
Install. The installation will take approximately an hour on a moderate machine.

121
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 140 The installation should complete successfully, as it too is a pretty straight forward installation. If
not, view the installation logs, correct the problem, and try again. Very easy for me to type that
huh?

122
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 141 Similarly to how we created startSSC.bat, let's create startProxy.bat note the path names
may be slightly different:

@echo off
time /t
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STPPNProfile1\bin\startNode.bat"
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STPPNProfile1\bin\startServer.bat"
STProxyServer
time /t
call pause

123
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 142 Here is stopProxy.bat:


@echo off
time /t
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STPPNProfile1\bin\stopServer.bat"
STProxyServer -username wasadmin -password passw0rd
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STPPNProfile1\bin\stopNode.bat"
-username wasadmin -password passw0rd
time /t
call pause

Step 143 Now we shall test our Proxy server via the web chat client. Verify the Community server is
running (look in Windows services and make sure all of the Sametime services are started if
not, start STCommunity Launch to kick them off manually) and open a web browser to navigate
to this URL:
http://sametime9imvm.demos.ibm.com:9081
We are using the alias rather than the actual host name to avoid login and awareness
problems due to conflicting web browser cookies with web meetings and web chat.

124
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 144 Click on Launch Sametime, log in with your user name and password (such as Rob
Fox/passw0rd) and click Log in.

125
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

126
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 145 Boom. Awareness. Web chat. Done.

Step 146 If you are not able to log in, again verify LDAP is running, the Community server is running, and
all of the Sametime services are running. Congratulations, the Sametime Proxy server is
complete.

You no longer need to install the Rich Client you can now chat with just a web browser.

127
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

INSTALL MEETINGS

The Sametime Meeting server provides document and screen sharing, persistent rooms, group chat, and a
document library for users. When coupled with the Sametime Proxy server and Sametime Media servers, it
supports multi-window A/V via the Sametime Rich Client and the web browser it even records audio and screen
sharing. The Meeting server installation can be tricky, but with these steps, you'll have no problems deploying it
correct, the first time.

The installation process is similar to previous components, that is, create the DB2 database, create the
deployment plan, and install the product, so I won't repeat things you should be familiar with at this point. I
recommend installing all 4 components of the Meeting server to avoid complications later. Let's get it started.

Step 147 As usual, extract SametimeMeetingServer.zip , open a command prompt and navigate to the
\SametimeMeetingServer\DatabaseScripts directory, and run the createMeetingDb.bat
STMS db2admin command.

Verify with the db2 connect to STMS command.

Step 148 In the SSC, go to Sametime Prerequisites Connect to DB2 Databases , click Add, and
specify the STMS database, click Finish.

128
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 149 Now that the data store is recognized, we'll create a deployment plan for the Meeting server.
Click on Guided Activities Install Meeting Server, Create a New Deployment plan, type a
name such as Sametime 9.0 Meeting Server, choose version 9.0.0, and at the Meeting
Server Roles Configuration screen, select ALL FOUR options.

129
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

I will explain each of these pieces:


1.)The Base Meeting Server is the room server itself that provides sharing, A/V when
applicable, etc. This should always be selected on the first Meeting server.
2.) The Meeting Document Converter handles server side document conversion. This
component can be installed on separate boxes to off load CPU and disk resources. We will be
installing this locally.
3.) The Meeting Recording Capturer is the piece that captures audio, annotations, and
screen & document share when recording a meeting. This too can be installed on a separate
machine for performance off loading.
4.) The Meeting Recording Renderer takes all of the assets from a meeting via the capturer
and converts it into a digestible H.264 .MOV file or a Windows Media Video file. This piece is
Windows only, even if you choose to not record your meeting as WMV files this is also why
we needed the Windows Desktop Experience, to install the Windows Media video files. This
component, like the others, can be installed on a remote server.

It IS possible to install an all in one Meeting server without checking all of these boxes, and go
back later to add them they are not pieces installed, but roles that can be enabled but doing
so is a time consuming task, so I always recommend checking all boxes the first time, every
time.

130
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 150 Just like our Proxy server, because this is the first one, we'll choose Primary Node for our
Meeting server WAS config type, choose our System Console as our deployment manager,
and then specify the name of the Meeting server, sametime9vm.demos.ibm.com, along with
wasadmin/passw0rd for ease. We don't need to use an alias for the Meeting server since we
already used one for the Proxy server. Select the STMS database after this screen, then Next.

131
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 151 This next page requires more explanation, so let's start with the first half.

Because we selected Meeting Capturer, we are NOT using a remote capturer, so the
URL for remote capture server field is grayed out. Empty values here mean local services.

The same logic can be used for the Document Conversion Server - we'll be doing that role
locally, so these two fields must be blanked out. Ignore their default server values they
should be empty, otherwise document conversion will NOT occur locally.

Now to configure the capture server. The Capture Server URL is the FQDN of the server with
the capturer installed, specifying the port the application is on. We don't know the port the
Meeting server will be on since we haven't installed it, but we can take a guess. When an
application server is installed on WebSphere, it defaults to 9080, and then each additional
application iterates by 1. So, if this Meeting server were a stand alone server, the port we'd
use would be 9080. However we've already installed two application servers on this box the
System Console, which has taken port 9080, and the Sametime Proxy, which has taken port
9081. In WebSphere, you can go to the Servers section, click on a server, and then scroll
down to the Ports item to verify what port the WC_default_host port is. Since 9080 and 9081
are taken, it is logical to assume that the Meeting server will be installed on port 9082.
Fortunately, if we guess wrong, we can always go back to Meeting settings or stavrecorder-
config.xml to change this. In conclusion, the value for both Capture Server URL and URL of
the Meeting Server that is configured with the Basic Meeting Server role is
http://sametime9vm.demos.ibm.com:9082 .
132
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

The Directory where the Capture files will be stored is C:/IBM/STCapture , keeping
everything (in this case, temp files) once again in the IBM directory. You MUST manually
create this directory NOW or the Installer will FAIL, even if you pushed the Validate button. My
pain is your benefit.

The User ID for Capture Server to record meetings should be anyone NOT in the LDAP this
user will be created in the local WAS file repository, similar to our local wasadmin user
strecbot is a fine default with the same password of passw0rd. This user will also have a J2C
alias created so the recording applications will be able to authenticate easier to perform their
functions, and wimconfig.xml will be updated by adding mail & uid login properties.

The Hostname of the local audio capture application is the FQDN of the Meeting server with
the capture role, in this case, again, it's sametime9vm.demos.ibm.com. As mentioned in the
screen shot, this address must be routable from the SIP Proxy/Registrar (Sametime Media)
server component, which we will install on this same host later.

The Port on which the local audio recorder application listens for SIP invitations also one
where we have to guess. The default here, 5061, will NOT work. Similar to how we deduced
port 9082, we must deduce the SIP port of the Meeting server when it is deployed. The first
and default SIP port is always 5060, and the secure TLS port is 5061, which is what the
System Console is using. Again, you can double check in the Ports section of each server for
SIP_DEFAULTHOST and it's secure version. WebSphere iterates these ports, but does so
backwards, so the next server (Proxy) gets the SIP ports of 5062 for secure and 5063 for
unsecured. Now with the Meeting server, the SIP ports should iterate with 5064 for secure and
5065 for unsecured SIP. We always want to use the secure TLS SIP port, so we're going to
guess our port is 5064. Again, my pain is your gain.

Finally for this section, the Audio Recorder IP with outbound connectivity to TURN/MCU is the
IP address that the Sametime Media components, the Video MCU (or a TURN server if using
one) will use to reach this server. This must be an IP address, not a host name, that is
pingable from the MCU. Use the IP address of the Meeting server.

Whew. Now to part 2.

133
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 152 Examine this screen shot, and I will explain the remaining fields.

We have not installed the Sametime Media Manager, which is the Conference Focus + SIP
Proxy/Registrar, but when we do, we will install it on this same box since it can run on Windows
and will simplify our deployment. So, for SIP Proxy/Registrar host use
sametime9vm.demos.ibm.com.

The Sametime SIP Proxy/Registrar always uses it's own SIP mechanism, which defaults to
5080 & 5081 for the secure TLS transport. Change the port to 5081 and choose TLS.

Since we are not using a TURN server, those settings can be left alone, but if needed, the
usual default of a TURN server is UDP port 3478.

Finally, for the Render server, the Directory where Render files will be stored is
C:/IBM/STRender , making sure to create this directory NOW or the install WILL FAIL. The
rest of the values are fine at their defaults.

Once everything is double and triple checked, click Next. Piece of cake, right?

Step 153 View the summary screen and push Finish. The Meeting server is Ready to Install. Now let's
see if we got everything correct. I would HIGHLY recommend taking a system snapshot JUST
in case something goes wrong with the Meeting installation there are a lot of moving pieces,
134
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

and it is far easier to just revert than try to manually remove a failed WebSphere application
and profile. Just saying.

Step 154 Run the Meeting Server launcher, choose Install, check 9.0.0.0, accept the license, and once
again choose the existing C:\IBM\SametimeServer 64-bit package location. You'll see the
Proxy and SSC installed as well.

135
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 155 Choose System Console to install, validate the C:/IBM/WebSphere/AppServer directory, and
fill out the SSC information, specifying the Meeting server host name of
sametime9vm.demos.ibm.com. Validate and hit Next.

136
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 156 Choose the Sametime 9 Meeting Server deployment plan, and verify the values. Take note of
some important values in the next three screen shots the audioRecordingCapturePort is
5064 based on the fact this is the third server on this same host and how secure SIP ports
iterate by 1, the directories C:/IBM/STRender and C:/IBMSTCapture , and the
proxyRegistrarTransportProtocol is TLS. Also note the validation button does not catch
everything, so again make sure the above directories exist, and the parameters are correct.

137
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 157 Next screen again, the validation can't verify something that doesn't exist yet, but the
proxyRegistrarHost will be sametime9vm.demos.ibm.com, the secure port 5081, and use
TLS when we install the Media Manager (the Conference Focus & SIP Proxy/Registrar) on this
same server later. Also, the IP address of 192.168.200.201 for the
audioRecordingPreferredOutboundIP will route properly from the MCU to the Meeting server
if the static local IPs are used whatever the correct IP address of the Meeting server is should
be this parameter. Additionally, note the recordingCaptureMeetingServerAddress is
http://sametime9vm.demos.ibm.com:9082, based on our guess that since the Meeting
server is the third server to be installed on this box, the port used with be 9082.

138
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 158 Final snapshot. Since our proxyRegistrarTransportProtocol is TLS, we are using port 5081
for the proxyRegistrarPort if we used 5080, TCP would be correct here. Since this box will
be hosting the capturer, the audioRecordingCaptureHost is sametime9vm.demos.ibm.com
and recordingCaptureServerAddress is http://sametime9vm.demos.ibm.com:9082, again,
deducing port 9082 will be the Meeting server port. Assuming the STCapture and STRender
directories were created, it is safe to start the installation. Good luck.

139
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 159 On a moderate machine, assuming no errors, a Meeting installation takes a bit over an hour.
Grab a bite and a drink.

140
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 160 Congratulations, the Meeting server installed without error if it didn't, check the log, correct
them, and try again, or revert back to your snapshot. Nothing to be ashamed of.

141
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 161 Let's create our startup scripts. startMeeting.bat:

@echo off
time /t
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STMPNProfile1\bin\startNode.bat"
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STMPNProfile1\bin\startServer.bat"
STMeetingServer
time /t
call pause

Step 162 Here is stopMeeting.bat:

142
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

@echo off
time /t
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STMPNProfile1\bin\stopServer.bat"
STMeetingServer -username wasadmin -password passw0rd
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STMPNProfile1\bin\stopNode.bat"
-username wasadmin -password passw0rd
time /t
call pause

Step 163 Let's double check out Sametime A/V recording settings. Refer to our WebSphere quick start
guide for more details, but WAS stores it's files in the deployment manager profile directory,
and then syncs them to each individual server's profile directory. We'll go to the main config file
and if we need to sync any changes, we can do so via WAS admin console System
Administration Nodes Resync All Nodes. The file we are looking for is named
stavrecorder-config.xml, and lives in (deep breath):
/IBM/WebSphere/AppServer/profiles/STSCDMgrProfile/config/cells/sametime9vmSSCCell/nodes/sametime9ST
MNode1/servers/STMeetingServer

143
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 164 Open this file in Notepad, Notepad++, WinVi, etc. Notice how it has all of the values we
needed, that is 5064, 5081, TLS, the IP address, and the host names of the not yet installed
but some to be SIP Proxy/Registrar. Good work.

144
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 165 Let's test the Meeting server. Note we have not configured the Sametime Proxy, nor single
sign on, so we won't have awareness, but we should make sure the Meeting server looks
correct. Verify everything is running, then in a web browser, navigate to
http://sametime9vm.demos.ibm.com:9082 log in with your favorite user (Rob
Fox/passw0rd).

145
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 166 The Meeting rooms page should appear. You can test creating a room like Rob's Meeting
Room if you'd like, but we should configure SSO first so we'll have green names in the room.
However, the Meeting server can work just fine as a stand alone server, without Proxy
integration it will just be missing awareness and A/V when those portions are deployed.

146
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 167 Congratulations the Meeting server is successfully installed. You get a cookie.

You may now have meetings via the client or the web with document sharing and screen sharing, along with
group chat.

CONFIGURE SINGLE SIGN ON

When we configure Single Sign On (SSO), this will allow the user to login to one server, such as the Meeting
server, but also be logged into other servers such as the Community or Proxy server without having to reenter
credentials. This process is done via tokens, which are unique strings stored in cookies in the web browser, that
verify identity. To configure SSO, we will import a unique SSO key into both WebSphere & Domino, and configure
the proper DNS domain name, which single sign-on depends upon, and restart servers. Once this is complete,
we will see green names in the Meeting room web page, and eventually, A/V. Let's go.

Step 168 First, let's specify the Sametime Proxy server URL to the Meeting server via it's configuration
page. Log into the SSC, go to Sametime System Console Sametime Servers
147
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Sametime Meeting Servers , click on the deployment, and push the Edit button.

Step 169 Scroll down to the meetingroomcenter.stProxyAddress entry, and populate it with the Dns
alias of the Sametime Proxy server, and it's port, which is:
http://sametime9imvm.demos.ibm.com:9081
The secure version, meetingroomcenter.stProxySSLAddress, of this URL is:
https://sametime9imvm.demos.ibm.com:9444
Push OK to accept the updates.
Similarly to how WebSphere iterates ports starting at 9080, for secure ports, it starts iterating at
9443, which is why the Proxy server, the second application on this WAS instance, is 9444.
Verify there is no slash at the end of either of those two URLs, or they will not work. Also, there
is no need to restart the Meeting server as these changes are picked up instantly if SSO
were already configured, we could pop into a meeting and see awareness. So let's do that.

148
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 170 While still in the SSC WAS Admin Console, go to Security Global Security
Authentication LTPA.

149
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 171 Here we will import the One Demo World SSO key, that will allow single sign on to all of the
servers using the ODW concept. In the cross cell SSO section, specify the password of (what
else) passw0rd and the path to the key file is:
X:\Notes_Installs\SSO_Assets\OnedemoWorldltpa.key
After pushing Import, push Save, but don't restart WAS just yet.

150
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 172 Next while still in the Global security section, click on Web and SIP security Single sign-
on (SSO).

151
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 173 Check the Enabled box, do not require SSL, and use demos.ibm.com for the Domain name.
It is important to check Interoperability Mode and for the LTPA V1 cookie name it must be
EXACTLY LtpaToken, with that EXACT proper casing. The LTPA V2 cookie name must be
EXACTLY LtpaToken2, with that EXACT proper casing. If these are not EXACTLY like this,
webA/V will not work due to mismatched cookie names. Note that the default WAS values are
not equal to this. Once again, my pain is your pleasure. Check 'Web inbound propagation and
push OK and Save.

152
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 174 Now, launch the IBM Domino Administrator, login with Domino Admin/passw0rd, and on the
Configuration tab under Web Web Server Configuration, scroll up in the view until you see
the Web SSO Configuration for LtpaToken Open this document.

153
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 175 Push the Edit SSO Configuration button, select Import WebSphere LTPA Keys, OK to
overwrite existing SSO keys, and once again point to the same path of the SSO key above.
Use the same password, passw0rd and push OK. The keys will import successfully.

Step 176 Notice the DNS Domain is .demos.ibm.com with a dot in front of it, unlike WebSphere. Also
notice the Token format is LtpaToken and LtpaToken2 this is why we chose interoperability
mode in WAS. If you don't check that box, only choose LtpaToken2 here. Finally, notice the
LDAP realm of defaultWIMFileBasedRealm this is important to be consistent across any
additional WebSphere based offerings such as Connections or SSO will not work. Verify the
Domino server name is correct and the expiration is 120 minutes like in WAS, and push Save &
Close.

154
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 177 Now we need to restart Domino's HTTP server this is restart all of the Sametime web servlets
with the proper SSO configuration. It is preferable to just restart HTTP rather than the whole
Domino server since it will take out LDAP, which we would like to avoid. On the Windows
desktop, double click on the IBM Domino Console (be careful, the icons are similar), click on
File Open Server and choose the sametime9vm server using Domino Admin and port
2050.

155
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 178 Type tell http quit in the Domino command box. As soon as you see HTTP Server:
Shutdown, immediately type load http. We want to do this quickly because if some of the
core Sametime processes don't get a response back from their web servlets in a timely
fashion, the Community server will stop. We can be sneaky by doing it this way.

156
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 179 Close the Domino Console (don't stop the Server Controller), and now we need to stop the
WebSphere Sametime servers. They should be stopped in reverse order, so, run the stop
scripts in the order:
stopMeetings.bat
stopProxy.bat
stopSSC.bat

Then restart all WAS servers in order, MAKING SURE LDAP is still running:
startSSC.bat
startProxy.bat
startMeeting.bat

Clear out your cache and cookies in your web browser and try logging into the Meeting room
page again you should see green awareness.

Step 180 Go ahead and create a Meeting room something like Rob's Meeting Room, and enter the
room, You should see green names in the participant list on the left tab. Groovy.

157
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 181 Congratulation you've installed and configured single sign-on for Sametime Meetings and
Proxy. Good going. I HIGHLY recommend a system snapshot before moving on to the next
phase deploying audio/video.

You now have rich presence in your meetings, and are ready to audio and video.

CREATE MEDIA DEPLOYMENT PLANS

The Sametime Media experience provides rich, multi-windowed audio/video across the Sametime client, the web,
and even Android and iOS mobile clients. Audio & Video can both be initiated from a meeting or a chat window,
or they can be added to existing conferences and dialogs all of this is brought to us by the latest in A/V
technology using AVC H.264 & SVC codecs via OEM. This gives flexibility & dynamic performance with our A/ V.

There are four components to the Sametime Media servers the Conference Focus which manages A/V
conferences, the SIP Proxy/Registrar which manages SIP invitations, the Video Manager (DMA) that controls
media, and the Video MCU that actually creates the streams. The Video Manager and Video MCU are both Linux
only, and they are stand alone servers, meaning that you cannot install them on the same box as any other
Sametime pieces. This is why we need three servers for a full Sametime deployment.

Before we install the Sametime Media server, contrary to how we've deployed everything thus far, we need to

158
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

create deployment plans for ALL of these pieces so they are all aware of each other. Neglecting to do this will
cause installation FAILURES, since vital configuration information will be missing. There are manual scripts that
can be ran to work around these failures but it is preferable to allow the installation to do all of its tasks as
intended. They include registering with the SSC, adding a SIP peer & creating the conference template.

Finally, the order of creating these deployment plans is VERY important creating these plans out of order will
cause failures. Also, installation order is VERY important installing the servers out of order will cause failures as
well. The order is 1.) Video Manager, 2.) Conference Focus + SIP Proxy/Registrar, 3.) Video MCU. Let's go.

Step 182 First, as discussed above, we must create the deployment plan for the Video Manager. Note,
if we were installing the Conference Focus and SIP Proxy/Registrar separately, we would
actually deploy the SP/R first, and then the VMGR, followed by the CF & MCU. However, we
will be installing the CF+SP/R together, so the Video Manager is first.

Logging in as wasadmin, in the System Console, go to Sametime Guided Activities Install


Sametime Media Manager. Select Create a New Deployment Plan and push Next. Name this
deployment something meaningful like Sametime 9.0 Video Manager Server, click Next,
select 9.0.0, click Next, and choose the Install Video Manager option.

Step 183 Unlike the Sametime Proxy and Meeting server, the Video Manager is a stand alone
WebSphere instance it is not controlled by the SSC deployment manager, nor does it use
DB2 as it's data store it uses a local, small database server called IBM Solid DB. This will be
installed on our first Linux image rather than our Windows image, so we use it's host name of
sametime9avvm.demos.ibm.com. Will we also use wasadmin/passw0rd for consistency.
159
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

160
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 184 Verify everything is correct and push Finish. One down, two to go.

Step 185 The stand alone, Linux only Video Manager is ready to install. Since we are installing the
Conference Focus + SIP Proxy/Registrar together, it will be our next component. Select
Create a New Deployment Plan again and click next.

161
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 186 Give this deployment a meaningful name such as Sametime 9.0 Media Manager, click next,
select 9.0.0, click Next, and choose the Install PR + CF option.

162
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 187 We will be installing the CF+SP/R on our Windows box under the SSC DMGR. Choose
Primary Node and then select the System Console deployment manager.

163
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 188 Like previous servers, use sametime9vm.demos.ibm.com as the WAS host name since we're
installing on the same machine, and use wasadmin/passw0rd.

164
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 189 Select the Sametime 9.0 Community Server, and then choose to Add a Sametime Video
Manager, and select the previously created deployment plan for the Sametime 9.0 Video
Manager Server.

165
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

166
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 190 Verify settings are correct, and click Finish.

Step 191 The Conference Focus + SIP Proxy/Registrar is ready to install. Now let's create the last
deployment plan for the Video MCU.

167
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 192 Give the deployment a descriptive name like Sametime_9.0_Video_MCU_Server. Unlike
the other deployment plans, this name CANNOT have any spaces it it, as the MCU installation
scripts doesn't parse spaces. Next choose 9.0.0, then select the Install Video MCU toggle
and click Next.

168
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 193 We are going to install the Video MCU on our second Linux image, as it too is a stand alone
server, but it is not a WebSphere component it is a number of binaries installed via RPMs.
For the host name choose sametime9mcuvm.demos.ibm.com and the usual
wasadmin/passw0rd.

169
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

170
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 194 Verify the host name is correctly the second Linux server (sametime9mcuvm) and click Finish.

Step 195 All three Sametime Media components are now ready to install, and were installed in the
proper order, which means installations should have the information they need.
Congratulations.

171
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 196 Now it is time to switch to the first Linux server and install the Video Manager.

You now have prepared to deploy the Media components.

INSTALL VIDEO MANAGER

The Sametime 9 Video Manager is the OEM component that controls media streams for the second OEM
component, the Video MCU. It is a stand alone, Linux only component that has it's own WebSphere instance,
which is not controlled directly by the deployment manager of the System Console. Before installing this product,
it is VERY important that deployment plans for ALL media servers have been set up and are ready for install, or
the Video Manager install will not install completely, requiring several manual steps (registering with SSC, creating
the A/V template, creating a SIP peer, creating a profile). With the Video Manager and Video MCU deployed,
multi-window A/V will function. Note point to point video does not need either of these components, just the
Conference Focus & SIP Proxy/Registrar. First we need to install the IBM Installation Manager 1.6.2 and
WebSphere 8.5.5 with iFixes, just like in Windows, then we can install the Video Manager similarly as well. We
will begin.

Step 197 Log into the desktop of the first Linux image with root and a password of collabrocks. Verify
your network connection, and retrieve your IP address by opening a Terminal window and

172
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

typing the ifconfig command. Using your editor of choice (mine is vi because I'm old school)
update the /etc/hosts file with the correct host name for the Windows server and Linux servers
as needed. VERIFY BOTH servers can ping each other back and forth BEFORE proceeding.

Step 198 First we must get the Linux environment prepared. There are many scripts that run during
install and run time that need various levels of access, so we must make sure the sudo
command has the things we need in it. To edit sudo, from a Terminal window use the
command visudo.

173
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 199 Do a search for the value requiretty by pushing the / key and typing the search term. Notice
how it is not commented out with a bang (!) character in front of it.

174
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 200 Comment out the command by putting an explanation point in front of the value so it looks like:
Defaults !requiretty
To write and quit, type a colon (:) and wq and hit Enter.

175
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 201 We need to now copy the installation files to the Linux server. There is a Share directory on
the Linux desktop we can mount a file share on. If you don't have the files local, here are some
quick commands to mount a Windows share, assuming the directory with the installation media
has been shared by Windows. First create in the /tmp directory a Media directory.

176
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 202 Change to the Desktop directory and run the mount command for example:
mount -o nounix,sec=ntlmssp,username=rfox //mymacbookpro.lexington.ibm.com/rfox
Share. Alternatively, you can use VMware's shared folders options, which will mount the host's
Desktop directory in the /mnt/ directory.

177
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 203 Copy the Linux IBM Installation Manager (IM_1.6.2_Lin_agent.installer.linux.*.zip),


WebSphere (same 3 zips as before) and iFixes (same zip), and SametimeMediaManager.zip
to the local /tmp/Media directory.

178
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 204 Make an IM directory in the /tmp/Media directory and change into that IM directory. Start by
unzipping the IBM Installation Manager zip file with the unzip IM_1.6.2*.zip command.

179
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

180
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 205 After unzipping the archive, kick off the installation by running ./install .

Step 206 The Installation Manager process is identical to the Windows process. Proceed accordingly as
done previously.

181
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

182
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 207 Install IBM Installation Manager in the /opt/IBM/InstallationManager/eclipse directory.

183
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 208 Verify your settings, and push the Install button.

Step 209 The installation should go quickly. When finished, push the Restart Installation Manager
button, and then Exit.

184
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 210 Remove the IM directory from the /tmp/Media/IM directory and create a WAS directory there to
hold the files extracted from the three WAS zip files.

185
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

186
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 211 Unzip the three WAS_ND_V8.5.5_*_OF_3.zip into the WAS directory.

Step 212 Create an iFixes directory, change into it, and extract the
Sametime9.0.0_WebSphereiFixes.zip there as well.

187
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

188
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 213 After the files are extracted, run the Installation Manager from the Applications menu.

189
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 214 Exactly as we did in Windows, go to the Preferences to add the repositories.

Step 215 After pushing Add Repository, browse to the /tmp/Media/WAS directory and point to the
repository.config file and click OK.

190
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

191
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 216 Do the same for the 11 iFixes. in the /tmp/Media/WAS/iFixes directory.

192
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 217 Verify all of the repositories are correct and push OK.

193
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 218 As before, click Install and choose WebSphere 8.5.5.0 and click Next.

194
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 219 Check all of the iFixes and click Next, and accept the license agreement.

195
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 220 Choose the /opt/IBM/IMShared directory to keep shared files in, and click Next.

196
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 221 Create a new package group under /opt/IBM/WebSphere/AppServer .

197
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 222 Select your language, and as before you want the full profile and only the 64-bit SDK files.

198
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 223 Verify and push Install.

199
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 224 The installation should take over an hour. When complete, select None and Finish.

Step 225 Remove the WAS directory in /tmp/Media and create a VMGR in it's place to extract the
SametimeMediaManager.zip archive to.

200
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 226 Make the extracted SametimeMediaManager directory executable with the command:
chmod -R 755 SametimeMediaManager
Then change into the directory and run the installer with ./launchpad.sh .

201
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 227 The Launch Pad uses firefox, so make sure it is installed and in the path test by typing
firefox and verifying the browser window appears. Once the Launch Pad appears, click Install
and Launch as we did in Windows.

202
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

203
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 228 Click Install & choose the Sametime 9.0.0.0 Media Manager (the Video Manager) & hit Next.

Step 229 Accept the license agreement, and create a new 64-bit package group for the Sametime Media
Manager to live in under /opt/IBM/SametimeServer .

204
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 230 After hitting Next and choosing System Console to install, verify the existing WebSphere
directory /opt/IBM/WebSphere/AppServer and push Next.

205
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 231 This process hasn't changed. Enter the System Console FQDN of
sametime9vm.demos.ibm.com, choose SSL, port 9443, wasadmin/passw0rd, and enter the
host name of our Video Manager, which is sametime9avvm.demos.ibm.com. Click Validate
and Next.

206
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

207
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 232 Click the deployment plan for the Video Manager and click Next.

208
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 233 Validate all settings.

209
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 234 Once everything is validated, push the Install button. This process will take over an hour.

Step 235 Since we created deployment plans for all components, this install worked perfectly. If we had
not, we would have generated several warnings, which would point us to scripts to manually
run in the /opt/IBM/SametimeServer/console directory, which we would prefer to avoid. Good
job. Click Finish and let's test.

210
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 236 Let's test the Polycom DMA web interface to verify the Video Manager is working properly.
Open a web browser (with Adobe Flash enabled) and navigate to this URL:
https://sametime9avvm.demos.ibm.com:8443/dma7000
Accept the trusted site exception and log into the DMA web admin with the username admin
and password admin.

211
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 237 The interface looks like this. Feel free to look around, looking at the alerts, settings, etc, but
don't edit anything. Obviously.

212
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 238 Now we test the WebSphere instance (since the Video Manager isn't using the System
Console deployment manager) by visiting the URL:
http://sametime9avvm.demos.ibm.com:9060/admin
Accept the site exception and login with wasadmin/passw0rd.

213
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 239 The Video Manager needs to use Ipv4 rather than Ipv6, so we must add a parameter in
WebSphere to prefer it. Click on Server Server Types WebSphere application servers
STMediaServer .

214
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 240 Click on Server Infrastructure Java and Process Management Process Definition
Additional Properties Java Virtual Machine Custom Properties and push the New
button.

215
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

216
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 241 Name this new property java.net.preferIPv4Stack with a value of true.

217
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 242 Save the configuration.

Step 243 The server now needs to be restarted. The data store, IBM Solid DB, must ALWAYS be
running BEFORE starting WebSphere, or the Video Manager will not work correctly. To start
the IBM Solid DB, change into the /opt/solidDB/soliddb-7.0 and issue the command
./standalone_eval_server_start . Then to stop the WebSphere server, issue the command:
/opt/IBM/WebSphere/profiles/sametime9STMSPNProfile1/bin/stopServer.sh
STMediaServer -username wasadmin -password passw0rd

218
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 244 Start the Video Manager WebSphere server:


/opt/IBM/WebSphere/profiles/sametime9STMSPNProfile1/bin/startServer.sh
STMediaServer

219
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 245 Now, log into the System Console web admin, click on the Sametime System Console section
and click on Sametime Video Manager Servers and click through the settings without making
any changes you should not have any errors. Pro-Tip: The Video Manager cannot be
deployed on the public Internet while using public DNS entries see the Sametime 9 Tech
notes for more information.

220
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 246 Congratulations, the Video Manager is complete. Great going.

You cannot do video yet, but a major component is installed and ready to the next components.

INSTALL CONFERENCE FOCUS + SIP PROXY/REGISTRAR

The Conference Focus + SIP Proxy/Registrar (also referred to as CF+SP/R or Media Manager) can be installed
on Windows or Linux. It sets up A/V conferences and registrants, and if you only want point-to-point A/V or
telephony, this is the only Sametime Media server necessary. This must be installed AFTER the Video Manager
but before the Video MCU. Note the Conference Focus uses 5060/5061 for it's SIP/Secure ports on a stand
alone box, 5067/5066 on this deployment since there are 3 other servers already installed, and the SIP
Proxy/Registrar uses it's own SIP ports of 5080/5081.

221
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 247 Switch back to the Windows server.

Step 248 The process for installing this component has not changed. Extract the
SametimeMediaManager.zip, run launchpad.exe.

222
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

223
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 249 Click Install and choose the Sametime 9.0.0.0 Media Manager.

224
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 250 Accept the license agreement, use the existing C:\IBM\SametimeServer 64-bit existing
package group. Notice the other servers that are installed.

Step 251 Choose the System Console option, validate the C:/IBM/WebSphere/AppServer directory,
and enter the information for the System Console, and use sametime9vm.demos.ibm.com for
the host name of the CF+SP/R (Sametime Media Manager). Hit Validate and Next.

225
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

226
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 252 Choose the deployment plan for Media Manager Server (PRCF).

227
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 253 Validate the settings and push Next.

228
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 254 Push the Install button. This process takes about an hour to install.

229
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 255 The installation finishes.

Step 256 Now to validate some settings. On the System Console WAS Admin Console, go to Servers
WebSphere application servers STMediaServer Process definition Java
Virtual Machine Custom properties and validate the java.net.preferIPv4Stack = true .

230
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 257 Verify various settings in stavconfig.xml located in (your path could vary, deep breath):
C:\IBM\WebSphere\AppServer\profiles\STSCDMgrProfile\config\cells\sametime9vmSSC
Cell\nodes\sametime9STMSNode2\servers\STMediaServer

231
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 258 Let's create our scripts again on the desktop. Here is stopMedia.bat:
@echo off
time /t
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STMSPNProfile2\bin\stopServer.bat"
STMediaServer -username wasadmin -password passw0rd
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STMSPNProfile2\bin\stopNode.bat"
-username wasadmin -password passw0rd
time /t
call pause

Step 259 Here is startMedia.bat:


@echo off
time /t
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STMSPNProfile2\bin\startNode.bat"
call "C:\IBM\WebSphere\AppServer\profiles\sametime9STMSPNProfile2\bin\startServer.bat"
STMediaServer

232
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

time /t
call pause

Step 260 Congratulations, the Conference Focus + SIP Proxy/Registrar is installed. We only have one
more server to install, the Video MCU.

You may not have point-to-point, 1 on 1 chat with the rich client. The Video MCU and Video Manager are only
needed for multi-window A/V.

INSTALL VIDEO MCU

The final Sametime Media component we will install is the Video MCU, which replaces the Sametime 8.5 Packet
Switcher component, that actually handles the video and audio streams (it does not do any mixing of streams).
This server, like the OEM Video Manager, is a stand alone, Linux only server, that requires 4 CPU cores and
8GB of memory at a MINIMUM. It is not WebSphere based, nor does it use IBM Installation Manager, rather it
installs binaries via RPM manager, including Apache. The files are all installed on the root / file system and
cannot be modified make sure there is plenty of disk space on that partition. Important files run in the /tmp
directory, so if you have a tmpwatch cron job running daily, disable it. Also, the MCU IP services MUST use the
eth0 NIC anything else will cause problems at start up and run time. Once this server is installed and the Video
Manager is configured to use it, web A/V will work as will n-way video via the rich client. We will use the second
Linux VMware image for this component. Here we go.

Step 261 Log into the desktop of the second Linux image with root and a password of collabrocks.
Verify your network connection, and retrieve your IP address by opening a Terminal window
and typing the ifconfig command. Verify you are using eth0 or the Video MCU will NOT work
properly. Using your editor of choice (mine is vi because I'm hard core) update the /etc/hosts
file with the correct host name for the Windows server and Linux servers as needed. VERIFY
ALL servers can ping each other back and forth BEFORE proceeding.

Just like in the first Linux image, mount a share, copy over the SametimeVideoMCU.zip
archive, and extract it.

233
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 262 Before beginning this installation, we'll need to prepare the environment by installing the dialog
and java packages. To install dialog, simply type yum install dialog.

234
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 263 To install java, similarly type yum install java. You can determine where java was installed via
the which java command.

235
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 264 The Video MCU needs a large number of 32-bit and 64-bit RPMs to be installed. I suggest a
script to easily install all of them in one or two commands. The specific RPMs are listed on the
Sametime 9 Wiki in the tech notes section. Install the pre-req RPMs. Refer to this link for
more details:

http://www-01.ibm.com/support/docview.wss?rs=0&context=SSCKJBV&uid=swg21649532

236
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 265 Many RPMs will already be installed, but a few will not, especially 32-bit packages. Install
them. Here is the script of the two commands the first installs system packages that should
already be present on the machine. The second are the packages specific to the Video MCU.
See the link above for further details.

#/bin/bash

yum install glibc iptables keyutils-libs krb5-libs libcom_err libgcc libselinux libstdc++ libxml2 nss-softokn-freebl openssl
samba-winbind zlib libsmbclient e2fsprogs e2fsprogs-libs glibc glibc-common- iptables iptables-ipv6 keyutils keyutils-
libs krb5-libs krb5-workstation libcom_err libgcc libselinux libselinux-python libselinux-utils libss libstdc++ libtalloc libtdb
libxml2- libxml2-python openssl samba-client samba-common samba-winbind-clients zlib

yum install glibc-2.12-1.*.el6.x86_64 glibc-2.12-1.*.el6.i686 glibc-common-2.12-1.*.el6.x86_64 zlib-1.2.3-*.el6.x86_64


zlib-1.2.3-*.el6.i686 libgcc-4.4.7-*.el6.i686 libgcc-4.4.7-*.el6.x86_64 libstdc++-4.4.7-*.el6.i686 libstdc++-4.4.7-
*.el6.x86_64 libxml2-2.7.6-*.el6_4.1.i686 libxml2-2.7.6-*.el6_4.1.x86_64 openldap-2.4.23-*.el6_4.1.i686 openldap-
2.4.23-*.el6_4.1.x86_64 openssl098e-0.9.8e-*.el6_2.2.x86_64 openssl098e-0.9.8e-*.el6_2.2.i686 cyrus-sasl-lib-2.1.23-
*.el6_3.1.x86_64 cyrus-sasl-lib-2.1.23-*.el6_3.1.i686 compat-expat1-1.95.8-*.el6.i686 mailcap-2.1.31-*.el6.noarch

237
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 266 Change into the directory where SametimeVideoMCU.zip was extracted and edit
console.properties.

238
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 267 Populate the fields. They are explained, but two things to remember. The deployment plan
name cannot have a space in it, and the JAVA_HOME has to be the directory where the Java
jre directory physically is located in.

SSCHostName=sametime9vm.demos.ibm.com
SSCHTTPPort=9080
SSCHTTPSPort=9443
SSCSSLEnabled=true
SSCUserName=wasadmin
SSCPassword=passw0rd
depName=Sametime_9.0_Video_MCU_Server
localHostName=sametime9mcuvm.demos.ibm.com
JAVA_HOME=/opt/IBM/ibm-java-i386-60
ACCEPT_LICENSE=true

239
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 268 Run the installation script. Since this image is Redhat Enterprise Linux 6, we will run
./installvideomcu_RHEL6.sh.

240
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

241
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 269 The information will be verified if all is correct, the RPMs will begin to install.

Step 270 After the RPMs have installed, the script will attempt to start the Video MCU by using the
command service soft_mcu start. This may take some time. If it does not start to finish the
install, it is probably a missing RPM or problem with the mcms or apache users. Correct the
issue, uninstall completely (details are in the Troubleshooting section of the Sametime 9 Wiki)
and start again. Look for the InstallValidator.log in /tmp/startup_logs/ - it will show if the pre-
req RPMs were installed, accounts were created, and if code was actually installed. View this
log regardless of a successful or failed installation of the MCU, just for reference.

242
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 271 Pay attention to the validity checks it will tell you exactly what went wrong with an install, if
anything. Once the installation is complete, issue the command chmod 644
/tmp/httpd.*.conf. You can look at logs such as the validation in /tmp/startup_logs/ or in the
STVideoMCU directory. You can also check the status of the soft_mcu service with the
command service soft_mcu status .

243
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 272 We are almost finished with the MCU we need to tell the Video Manager about it. Log into
the System Console, go to the Video Manager section, and click on Configure Video MCU.

244
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 273 Determine the IP address of Video MCU (the host name will NOT work) and populate the fields
accordingly. For example, if you are using my local static IPs, the Video MCU IP address is
192.168.200.203. Verify again both the Video Manager and Video MCU can ping each other.

245
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 274 Apache (httpd) and the MCU server (soft_mcu) are set up by default to start up at boot time. If
you don't want to do this as it will take much longer to get to the Linux desktop, go to System
Administration Services.

246
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 275 Pushing the Disable button will prevent the service from starting at boot time, which may be
helpful for troubleshooting purposes.

247
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 276 Do the same thing for the soft_mcu service pushing the Disable button only removes it from
start up. This service potentially can take a very long time to start due to it's 4 CPU core and
8GB memory hardware requirements, so I prefer to start it manually when I'm ready.

248
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 277 The Sametime 9 Video MCU is installed correct. Congratulation! Now for the final
configuration steps, and we are finished. Are you prepared?

You now are almost ready for multi-window, Hollywood Squares video.

FINAL CONFIGURATION STEPS

We have installed all components, and now need to do some configuration to make audio/video work correctly.
First, Anonymous must be allowed to enter a room so the A/V component can display. Second, it is REQUIRED
to exchange certificates between the Video Manager and the Conference Focus so they can connect to each
other to manage A/V sessions. Third, we'll set up some scripts to make starting and stopping servers easier, and
lastly we'll set up pictures for business cards in the rich client and web client. We are in the home stretch, so let's
get right to it.

Step 278 First, we'll set up an Anonymous user to allow web A/V to function. In the System Console,
click on Users & Group Manager Users and search for the Anonymous ID. If it is not

249
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

already there, create one.

Step 279 The Anonymous user needs to be in the AnonymousUsers role for the SIP Registrar this is
located in Applications All Applications IBM Lotus SIP Registrar Security Role to
User/Group Mapping.

250
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 280 Next, the anonymous token authorization must be enabled and the anonymous ID must be set
in two similarly named properties the fist is located in Security Global Security Trust
Association Interceptors com.ibm.sip.auth.AnonymousTokenAuthTAI with
enable.anonymous.token.auth.tai = true and anonymous.user.id = anonymous.

251
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 281 We'll need to add the exact same values to the second property,
com.ibm.sip.auth.AnonymousAuthTAI just as we did above. Check
enable.anonymous.auth.tai and push Edit.

252
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 282 Change enable.anonymous.auth.tai to true, push OK, then add another property named
anonymous.user.id with a value of anonymous and push OK.

253
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 283 Save the configuration the Conference Focus + SIP Proxy/Registrar will need to be restarted
for those values to take affect use your previously created stopMedia.bat and
startMedia.bat scripts, but don't restart quite yet.

254
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 284 Now, we will exchange self signed certificates between the Video Manager and the Conference
Focus. We'll start with the Conference Focus, which is deployed on the System Console
server, and have it import the certificate from the Video Manager. Go to Security SSL
certificate and key management Key stores and certificates CellDefaultTrustStore.

255
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

256
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 285 Click on Signer certificates then push the Retrieve from Port button.

Step 286 Enter the host name of the Video Manager, sametime9avvm.demos.ibm.com, and it's secure
SIP port, 5061, enter a description such as Sametime 9.0 Video Manager Certificate and
push the Retrieve Signer Information button. The Conference Focus WebSphere will
automatically connect to the Video Manager WebSphere instance and import the SSL
certificate. Push OK.

257
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

258
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 287 Once imported, save the WAS configuration.

Step 288 Log out and log into the WAS admin console of the Video Manager server, which is
http://sametime9avvm.demos.ibm.com:9060/admin. As usual, use wasadmin/passw0rd.

259
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 289 Similarly to what we did above, once in the WAS admin on the Video Manager, click on
Security SSL certificate and key management Key stores and certificates but this
time, click on NodeVMGRTrustStore. This is a stand alone WebSphere instance rather than a
network deployment instance, so there is no cell.

260
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

261
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 290 Click on Signer Certificates and push Retrieve from port.

Step 291 This time, we will enter the host name of the Conference Focus, which is
sametime9vm.demos.ibm.com, and the secure SIP the Conference Focus is using, which is
port 5066, which you can verify in the Ports section of the STMediaServer application. Give
this a descriptive name like Sametime 9.0 Conference Manager Certificate and push
Retrieve signer information.

262
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

263
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 292 Once the information is retrieved, push OK, and then Save the WAS profile configuration.

Step 293 Now we should restart the Media components. Because I'm lazy highly efficient, we will use
scripts located in the /root directory of our Video Manager and Video MCU then we can just
type ./startVMGR.sh and ./startVMCU.sh to kick off these components. As usual, note that
your paths may slightly vary. Here is stopVMGR.sh:

#/bin/bash

/opt/IBM/WebSphere/AppServer/profiles/sametime9STMSPNProfile1/bin/stopServer.sh
STMediaServer -username wasadmin -password passw0rd
cd /opt/solidDB/soliddb-7.0/
./standalone_eval_server_stop
read -p "Press Enter to continue..."

startVMGR.sh:

#/bin/bash

cd /opt/solidDB/soliddb-7.0/
./standalone_eval_server_start
264
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

/opt/IBM/WebSphere/AppServer/profiles/sametime9STMSPNProfile1/bin/startServer.sh
STMediaServer
read -p "Press Enter to continue..."

On the Video MCU, here is stopVMCU.sh:

#/bin/bash

service soft_mcu stop


service httpd stop
read -p "Press Enter to continue..."

And startVMCU.sh:

#/bin/bash

service httpd start


service soft_mcu start
read -p "Press Enter to continue..."

Let's go ahead and run stopVMGR.sh on our Video Manager. Note you usually don't need
to stop the Solid DB so you can hit Control+C to break out of the script, but if you need to, the
default Solid DB username and password are both admin.

Step 294 Start the Video Manager with your startVMGR.sh script.

Step 295 The Video MCU usually doesn't need to be restarted as the Video Manager connects to it as
necessary and doesn't have configuration information per se. Let's look at what ports are
being used on the Video Manager with this netstat command:
netstat -na | grep ':5060\|:5061\|:5080\|:5081\|:5560\|:5561\|:5067\|:5066\|:8080'
On both the Video Manager and Video MCU we want to see services listening on port 5060.
We also want to see 5061, 5080, & 5081 on the VMGR, and 8080 on the VMCU.

265
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 296 We can run the top Linux command to see running processes. On the VMGR we want to
see a large java process and solid process, while on the VMCU we want to see a large
number of services beginning with ASS, AMP, mcms, video, etc, all owned by the mcms user.

266
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 297 Back on the Windows server, it's time we consolidated our stopMedia.bat, stopMeeting.bat,
stopProxy.bat & stopSSC.bat into a stopAll.bat, in that order, that will look similar to this.

Step 298 Also, we should combine our startSSC.bat, startProxy.bat, startMeeting.bat, &
startMedia.bat , in that order, into a startAll.bat. Note it is IMPARITIVE that LDAP be
running first BEFORE any of these WebSphere services start up add a:
echo Verify LDAP is running

267
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

call pause
...to the beginning of this script if you need a reminder.

268
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 299 We can restart all boxes now. Here is what stopAll.bat will look like:

Step 300 Again, if we stop Domino, it will stop LDAP, so remember to restart LDAP stand alone before
starting ANY WAS servers.

269
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

270
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 301 After starting LDAP, we then start the WebSphere Sametime servers.

Step 302 The last item we start on the Windows box is the Domino server. We start this component last
to avoid port conflicts with WebSphere as Domino and the Community server sometimes
randomly bind on ports WebSphere uses to function.

271
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 303 Now, we will configure pictures for the web client and the rich client. The web client uses a
PhotoURL field in LDAP to retrieve the picture over HTTP, and the rich client uses pictures
inside of the LDAP server. First we'll set up web URLs for users. Navigate to
UserInfoConfig.xml located in C:\IBM\Domino and open it in Notepad/Notepad++.

272
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 304 Edit the Photo fieldname to be jpegPhoto:binary (more on that later) and then add the line:
<Detail Id=PhotoURL fieldname=photourl type=text/plain />

273
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 305 Log into System Console in the Sametime Community Server section, click on Business cards,
and add or subtract any fields you want to appear.

274
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 306 Change the photo field to a User Defined field of jpegphoto;binary. We must do this because
to add photo into Domino LDAP, you must use a 3 rd party LDAP tool, which Domino handles
differently.

275
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 307 Once this is done and the Community server restarted, when logging in with the Sametime
Proxy web chat client, photos for users will be referenced from the PhotoURL field in LDAP.
We'll use Domino as our web server to copy the JPG photos to, and update our hand
registered users with a proper web URL to point to these JPGs. Create a directory under
C:\IBM\Domino\data\domino\html called photos.

276
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 308 Open the Domino Admin client, open a person document, and in the Miscellaneous field, add
the URL http://sametime9vm.demos.ibm.com/photos/Rob_Fox_96x96.jpg (or whatever the
name of your business card picture is). The size should be 96x96 pixels.

277
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 309 Save & close this document, refresh the Person view with the Control + Shift + F9 button, and
go to Softerra to make sure this field appears in LDAP.

278
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

279
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 310 Log into the web chat client and boom my, er, your picture appears.

Step 311 Once you've confirmed this works for your user, you should extend the same courtesy for all of
the other users. In your downloads directory or in X:\, locate photos.zip, and extract it to the
same location above, C:\IBM\Domino\data\domino\html\photos .

280
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

We'll need a way to update everyone's person document to have the PhotoURL field we can
use a Domino agent, or we can use an LDIF with an LDAP editor. Let's do that.

Step 312 For the Rich Client, photos must be in the LDAP, so we will insert them using Apache
Directory Studio, a free LDAP editor (Softerra is a read only tool). We'll need to configure
Domino to allow write access to LDAP users for this to work. Go back to the Domino Admin
client, and in the Configuration Server Configurations section push Add
Configuration.

281
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

282
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 313 In the Basics tab, check Yes to use for all servers.

Step 314 Click on the LDAP tab and review the exposed LDAP attributes and how they map to fields in
Domino.

283
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 315 Toggle the Allow LDAP Users Write Access radio button, save/close, and restart the LDAP
service, keeping in mind this must be done QUICKLY or all of the WebSphere process will
Break Badly.

284
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 316 Fire up Apache Directory Studio and create a connection profile to the Domino LDAP
similarly to how it was done for Softerra. Go to the user you created mine looks like this:

285
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 317 Click on New Attribute, select jpegPhoto, click Finish, then browse to the JPG we copied
previously it will import into Domino, like magic. Do this for all 91 users you may consider
hiring an intern to do this.

286
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 318 You can verify that data is present by looking at the Document Properties of the Person
document and looking at the jpegPhoto field in the Domino Admin client:

287
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 319 ...and looking at Softerra double clicking the attribute will present a picture.

Step 320 The Community server will auto refresh every 60 minutes, or you can restart it. When logging
in with the rich client, you will see your photo in glorious Technicolor.

288
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 321 The LDAP editor, now that Domino LDAP write access is enabled, can import an LDIF file that
can add LDAP attribute values this is how we'll update the PhotoURL attribute. In Apache
Directory Studio, after connecting to our Domino LDAP, choose File Import LDAP
Browser LDIF into LDAP. Browse to the demos.ibm.com LDAP v3.5 update.ldif file,
check Update existing entries, and push Finish.

289
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Refresh the LDAP view to see the newly added attributes. Yay.

Step 322 Amazingly, we are finally finished deploying Sametime 9 congratulations reward yourself
with a tasty burger. Now, we will do the ultimate test attending a web meeting with A/V.
Good luck!

You now have pictures working, and A/V working in the web browser and rich client. Time to confirm.

THE FINAL SHODOWN ATTENDING A WEBA/V MEETING

We have successfully deployed Sametime 9 with the System Console, the Community Server, the Proxy Server,
the Meeting Server, the Video Manager, the Conference Focus + SIP Proxy/Registrar, and the Video MCU
Server. The easiest way to test all of those components is to attend a web A/V meeting. Attending the meeting
prove 1.) Meetings work, 2.) The Community server works due to awareness, 3.) the Proxy server works due to
green names, 4.) SSO works due to green names, 5.) all three Media servers work due to A/V in the meeting, and
6.) recordings will verify document conversion and audio capture is working. This is your final exam good luck!
Information about the section should go hear. Explain what the section is about and what the user will do and
why they are doing it.

Step 323 Log into the Meeting Server with your registered ID. The URL is
http://sametime9vm.demos.ibm.com:9082.

290
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 324 You don't have any Meetings rooms yet, so create one. This will verify Meeting functionality.
Push the New Meeting Room button.

291
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 325 Give the room a descriptive name like Rob's Meeting Room or Rob's Video Room. If you
can see A/V options in this page, this confirms the Conference Focus + SIP Proxy/Registrar is
functioning. Choose Sametime Audio/Video Conferencing.

292
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 326 If you have multiple A/V templates, you can pick them here. This confirms the Video Manager
(DMA) is functioning. Push Save.

293
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 327 You are taken back to the Meetings page. Your meetings listed verifies the Meeting server is
working, and green names confirm SSO, the Proxy server and Community server are all
working. So far, so good.

294
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 328 The first time you enter a Meeting room, you'll be prompted for the web A/V plugin. This shows
the Proxy server is doing it's job serving out that plugin. Install it and restart the browser,
keeping in mind this is a 32-bit only plugin.

295
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 329 Once back in the meeting, go to the camera icon if you are given an option to Start a Call,
that means that SSO is configured properly (remember, it is properly cased like LtpaToken &
LtpaToken2). Also notice the green name at the top of the page. Start a call with the
computer.

296
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 330 If you see yourself, congratulations, this means that the Video MCU is streaming audio and
video media excellent work. I'm very proud.

297
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 331 Push the Add File button on the lower left of the Meeting room and add a file, such as a
Symphony document.

298
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 332 If the document appears, the document conversion application is working. Finally let's test
recordings. Push the Record button in the upper right corner.

299
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

300
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 333 Choose H.264/mov for broader compatibility beyond Windows Media Video, and push Start.

Step 334 If you do not receive any errors, that confirms the Windows Desktop Experience is installed,
and the recordings capturer app is working. Add some more participants, switch slides,
annotate and speak so your recording is worth someone's time to watch it later.

301
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 335 After a minute or two, push the red Stop Recording button. You can view recording while still in
the meeting or in the meetings view either is fine.

302
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

303
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 336 Click on your meeting. This shows the recording renderer app is working properly.

Step 337 Watch your masterpiece - if you hear audio, this confirms the stavrecorder-config.xml is
correct. If not, when troubleshooting, you should be keeping in mind the SIP port for the
Meeting application is probably 5064 and will be in the Meeting server's virtual host
(default_host for this deployment), and the port to connect to the SIP Proxy is probably TLS
port 5081. Also the strecbot user was created, a J2C alias was created for that user, and
defaultWIMFileBasedRealm was updated in wimconfig.xml to allow logins with uid and mail.
Fantastic.

304
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Step 338 Congratulations!!! You are the best!!! A winner is you!!! Now, let's take a WebSphere backup
and a VMware snapshot and call it a day. On the WebSphere servers, change into the
/IBM/WebSphere/AppServer/bin directory and run the backupConfig.bat -nostop command
(backupConfig.sh on Linux).

305
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales
Sametime 9 STEW

Someone owes you a drink. Me too.

You can do everything you are now a Sametime 9 guru. Excellent. Outstanding.

Summary:

At this point, you have successfully installed a complete stack for Sametime 9.0. You are now ready for the
social with the greatest software in the world for collaboration.

306
COPYRIGHT IBM CORPORATION 2013. ALL RIGHTS RESERVED.
IBM ISV & Developer Relations & Worldwide ICS Technical Sales

Você também pode gostar