Your SlideShare is downloading. ×
Installing sametime851-from-zero-to-hero-the next generation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Installing sametime851-from-zero-to-hero-the next generation

622
views

Published on

Published in: Technology, Business

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
622
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
53
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. © 2011 IBM Corporation Show 201 Installation and Setup of IBM Lotus Sametime 8.5.1 ”From Zero to Hero” The Next Generation Frank Altenburg | SME for Sametime | IBM Volker Juergensen | Senior IT Specialist | IBM
  • 2. 2 Agenda ● Components of IBM Lotus Sametime 8.5.1 ● Requirements for a IBM Lotus Sametime 8.5.1 Deployment ● Architecture of a IBM Lotus Sametime 8.5.1 pilot deployment ● The 21 steps to a IBM Lotus Sametime 8.5.1 pilot deployment
  • 3. 3 The IBM Lotus Sametime 8.5.1 Components we will cover ● Sametime System Console ● Sametime Community Server ● Sametime Proxy Server ● Sametime Meeting Server ● Sametime Media Manager ● Sametime Connect Client
  • 4. IBM Lotus Sametime System Level Architecture Sametime Gateway Community Server Media Manager Unified Telephony Advanced Server Meeting Server Sametime Proxy Sametime Clients External IM Communities Enterprise Phone System Embedded Applications, including Web Client, Portal, and Mobile Partner A/V Bridges SIP, RTP SIP, RTP VP VP VP VP VP VP HTTP HTTP HTTP SIP, XMPP SIP, TCSPI SIP Logical servers shown – may be combined physically depending on user workload
  • 5. IBM Lotus Sametime System Console Sametime Presence/IM Sametime Classic Meetings Sametime New Meetings Sametime Media Server Sametime Gateway DominoWebSphere DB2 LDAP Sametime Proxy SametimeSystemConsole ● Manage prerequisites. – System console manages all needed info for prerequisite components – No install/reinstall of IBM DB2® (for example) for each separate offering ● Centralize configuration. – Setup & testing of things like LDAP centralized in a single location, instead of various wizards in different installers ● Facilitate deployment planning. – Mechanism to plan the Sametime server deployment – Installation of server nodes is simpler, as the shared configuration already exists. Server installers are “headless”, and need no input from user ● Single point of action for administrative tasks – Example: Policies are managed from a single place for all components
  • 6. 6 ● Components of IBM Lotus Sametime 8.5.1 ● Requirements for a IBM Lotus Sametime 8.5.1 Deployment ● Architecture of a IBM Lotus Sametime 8.5.1 pilot deployment ● The 21 steps to a IBM Lotus Sametime 8.5.1 pilot deployment Agenda
  • 7. IBM Lotus Sametime 8.5.1 Prerequisites ● IBM Lotus Sametime 8.5.1 System Console Server requires ● IBM WebSphere Application Server 7.0.0.x (provided automatically via Install) ● IBM DB2 9.5 FP1 (provided automatically via Install) ● LDAP directory server (Supported IBM® Lotus® Domino® Directory LDAP, Microsoft® Active Directory, IBM Tivoli® Directory Server, SunOne® iPlanet®, Novell® eDirectory®) ● IBM Lotus Sametime 8.5.1 Sametime Community Server requires ● IBM Lotus Domino 8.0.x, 8.5, 8.5.1 or 8.5.2 (32 Bit Version only) ● LDAP directory server ● IBM Lotus Sametime 8.5.1 Proxy Server requires ● IBM WebSphere Application Server 7.0.0.x (provided automatically via Install) ● IBM Lotus Sametime Community Server (Version >= 7.5.1) ● IBM Lotus Sametime 8.5.1 Meeting Server requires ● IBM WebSphere Application Server 7.0.0.x (provided automatically via Install) ● IBM DB2 9.5 FP1 (provided automatically via Install) ● LDAP directory server ● IBM Lotus Sametime 8.5.1 Media Manager requires ● IBM WebSphere Application Server 7.0.0.x (provided automatically via Install) ● IBM Lotus Sametime 8.5.1 Community Server ● LDAP directory server
  • 8. ● Software requirements ● Client ● Windows XP (SP2), Vista and Windows 7 – 32 and 64 bit (Sametime Connect 8.5.1 or Notes 8.5.1 / 8.5.2 upgrade) ● Server ● Windows Server 2003/2008 - 32 and 64 bit (Do not use the R2 Version) ● Linux (RHEL, SLES) - 32 and 64 bit ● AIX 5.3/6.1 ● i5/OS 5.4, 6.1 ● Solaris 10 ● ESX 4.0 is now supported ● Browsers ● Microsoft® Internet Explorer 6.x, 7.x, 8.0 (Windows) ● Firefox 2.x and 3.x (Windows, Mac, Linux) ● Safari 3.2 and 4.0.x (Mac) ● Other ● Domino 8.0 /8.5/8.5.1/8.5.2 for Community Server / 'Classic' meetings ● Websphere Application Server 7 for new servers and gateway (included) ● DB2 9.5 FP1 for new servers and gateway (included) IBM Lotus Sametime 8.5.1 Prerequisites (continued)
  • 9. Other requirements ● Make sure that all servers you want to use can be resolved in DNS. ● If DNS is not available then list all full qualified server names and IP addresses from all servers in the hosts file and publish this file to all servers. ● The machine hosting the Media Server does not work with a DNS alias. You must configure the full qualified host name (including domain part) and use this for the installation. ● If you use Windows 2008 as Operating System, then you need to start all installations and configurations in „Administrative mode“. ● You need a LDAP Server hosting your user base. This can be a Domino LDAP or Microsoft Active Directory or any other supported V3 LDAP.
  • 10. Required files for a deployment on Windows For a Windows installation you need to download these files from Passport Advantage: CZLF6ML.zip DB2 9.5 FP1 Limited Use for Sametime CZIH7ML.zip Sametime System Console CZIG0ML.zip Sametime Community Server Standard CZIG9ML.zip Sametime Proxy Server CZIG3ML.zip Sametime Meeting Server CZIH5ML.zip Sametime Media Manager CZII3ML.zip Sametime Connect Client Standard Create a directory, for example “C:Install”, on the servers where you want to install. Then unpack the downloaded files into this directory. Just unpack the files required for your deployment architecture on the particular server.
  • 11. 11 ● Components of IBM Lotus Sametime 8.5.1 ● Requirements for a IBM Lotus Sametime 8.5.1 Deployment ● Architecture of a IBM Lotus Sametime 8.5.1 pilot deployment ● The 21 steps to a IBM Lotus Sametime 8.5.1 pilot deployment Agenda
  • 12. Different ways to a pilot deployment ● The Sametime Install Guide (“recommended small pilot deployment”) describes to distribute the Domino and WebSphere based services on different servers. ● You can also install all components on separate servers. This is more for production environments or bigger pilots. ● You can use any mix between these two previous methods. ● In this example we will install on 3 servers: ─ Server1: DB2 Server, Sametime System Console, Sametime Meeting Server ─ Server2: Sametime Community Server ─ Server3: Sametime Media Manager ─ An existing LDAP Server (we use AD in this example) Our reasons for this scenario: ● No need for special IP configuration ● Works well with 32Bit OS using up to 4GB RAM ● Easiest and fastest way to have all components up and running with the smallest number of required boxes ● This script works well for all ways.
  • 13. Sametime Media Manager Active Directory LDAP DB2 9.5 Server Sametime System Console Sametime Meeting Server ldap.renovations.com proxy.renovations.com Sametime Proxy Server Sametime Community Server chat.renovations.com meeting.renovations.com IBM Lotus Sametime 8.5.1 – our deployment
  • 14. ● 1 server for the IBM DB2 Server, IBM Lotus Sametime 8.5.1 System Console, IBM Lotus Sametime 8.5.1 Meeting Server Dual CPU, 4GB RAM or more, 50GB disk space or more ● 1 server for Sametime 8.5.1 Community Server Single CPU, 2GB RAM or more, 10GB disk space or more ● 1 Server for Sametime 8.5.1 Proxy Server and Sametime 8.5.1 Media Manager Dual CPU, 3GB RAM or more, 20GB disk space or more ● Various client endpoints Hardware required for this Pilot Example Deployment With such a configuration you can host up to ● 800 concurrent Meeting Participants * ● 10.000 concurrent Sametime Clients * ● 300 concurrent Media Streams * ● 5000 concurrent Proxy web client users * * Ask you IBM representative for more detailed sizing information in a defined environment
  • 15. IBM Lotus Sametime 8.5.1 Our pilot recommendation Compared with the first version (last year's session) of this document installing Sametime 8.5, we have now changed our recommendation for a pilot deployment. The reason for the change is the increased experience and many successful installations using this method in the last 6 months.
  • 16. 16 ● Components of IBM Lotus Sametime 8.5.1 ● Requirements for a IBM Lotus Sametime 8.5.1 Deployment ● Architecture of a IBM Lotus Sametime 8.5.1 pilot deployment ● The 21 steps to a IBM Lotus Sametime 8.5.1 pilot deployment Agenda
  • 17. The 21 steps to deploy a complete Sametime 8.5.1 environment 1.Set up or use an existing LDAP server 2.Install the IBM DB2 server 3.Create the IBM Lotus Sametime System Console database 4.Install the IBM Lotus Sametime System Console 5.Log in to the IBM Lotus Sametime System Console 6.Configure the LDAP server connection Prerequisite 7.Run the guided activity to configure the IBM Lotus Sametime Community Server installation 8.Install the IBM Lotus Sametime Community Server
  • 18. The 21 steps to implement a complete Sametime 8.5 environment (continued) 9. Enable trust between the IBM Lotus Sametime Community Server and the IBM Lotus Sametime Proxy Server 10.Run the guided activity to configure the IBM Lotus Sametime Proxy Server installation 11.Install the IBM Lotus Sametime Proxy Server 12.Create the IBM Lotus Sametime Meeting Server database 13.Configure the DB2 Meeting server database connection Prerequisite 14.Run the guided activity to configure the IBM Lotus Sametime Meeting Server installation 15.Install the IBM Lotus Sametime Meeting Server
  • 19. The 21 steps to implement a complete Sametime 8.5 environment (continued) 16.Enable trust between the IBM Lotus Sametime Community Server and the IBM Lotus Sametime Media Manager 17.Run the guided activity to prepare the IBM Lotus Sametime Media Manager installation 18.Install the IBM Lotus Sametime Media Manager 19.Install a IBM Lotus Sametime Connect client 20.Configure the Meeting Plug-In on the IBM Lotus Sametime Connect client 21.Configure the Sametime Meeting Room in the IBM Lotus Sametime Connect Client Meeting Plug-In to use Audio and Video
  • 20. STEP ONE: Setup an LDAP Server Summary This step installs or identifies the LDAP server containing the User directory you want to use for your Sametime implementation.
  • 21. The LDAP Server In most environments a LDAP server is already present. If you use Domino it is simple to just enable LDAP on one of the Domino Directory Servers. If you use an existing LDAP Server other then Domino, it is important to use a V3 compliant LDAP. Make sure you have all relevant data from the LDAP system. (use ldapsearch, Apache LDAP studio or another LDAP browser to get the relevant LDAP information - an LDIF extract of a user and a group) A security related recommendation is to have a Bind DN. This means a user record in the LDAP that can be used for authenticated access to the data in the LDAP server. We use the „LDAP Bind“ user in this example. The LDAP connection can be configured with SSL encryption. Make sure that your have access to the required certificate.
  • 22. In this example we use an existing Microsoft Active Directory 2003 server. If you plan to use other LDAP servers then step 6 can be different, dependent on the used LDAP directory. See the Sametime InfoCenter for more details.
  • 23. An example for the LDAPSEARCH command to an Active Directory and the results:
  • 24. STEP TWO: Install the IBM DB2 Server Summary This step installs the IBM DB2 9.5 Server. We like to use a CMD command line window to enter some of the commands and start the installers. For that we have created a short cut in our fast start section. You can use the Windows Explorer as well to navigate to the destination directory and double click the installation file (lanuchpad.exe) The two steps to create a DB2 database need the database name as a command line parameter. We would recommend using a CMD command line window to enter this commands.
  • 25. Enter the command “cd InstallSametimeDB2” and press the “Enter” key. Enter the command “Launchpad” and press the “Enter” key.
  • 26. Just click the “Install IBM DB2” link.
  • 27. And again click the “Install IBM DB2” link.
  • 28. The Installation Manager is starting up
  • 29. Click the “Next” button to continue.
  • 30. Accept the terms in the license agreement and click the “Next” button to continue
  • 31. Remove “Program Files” and click the “Next” button to continue We recommend to use path names without spaces (as some scripts may require this) and also shorten the path name so that the typical limits of some operating systems and appliacations for path + file name length are avoided.
  • 32. Click the “Install” button to install the Installation Manager.
  • 33. The installation Manager is now installing
  • 34. Click the „Restart Installation Manager“ button to continue.
  • 35. Installation Manager is re-launching. Now click the „Install“ icon to continue.
  • 36. Select „DB2 – Version 9.5.0.0“ and click the „Next“ button to continue.
  • 37. Accept the terms in the license agreement and click the “Next” button to continue.
  • 38. Remove “Program Files” and click the “Next” button to continue. We recommend to use path names without spaces (as some scripts may require this) and also shorten the path name so that the typical limits of some operating systems and appliacations for path + file name length are avoided.
  • 39. Again remove “Program Files” and click the “Next” button to continue.
  • 40. Click the “Next” button to continue.
  • 41. Enter the DB2 Administrator Username (we use the default “db2admin”) and enter the DB2 Administrator Password twice. Then click the “Next” button to continue If you use Windows 2008, be sure to enter a password that meets the password policy. The DB2 Admin User password should not be longer then 8 characters. Change the local security policy to allow passwords with 8 characters length. This db2admin user will be created as a local user or as a Active Directory User. This can not be done if the user already exists. Same with the 2 groups that the DB2 Installer adds.
  • 42. Click the “Install” button to install the DB2 Server
  • 43. The Installation Manager installs the IBM DB2 Server now. This step takes approximately 10 to 15 minutes.
  • 44. Important to know... Your DB2 Database Server is a sensitive component in your Sametime Environment. It stores all the predefined configuration data and holds the information how to communicate with your servers for administration and maintenance. We highly recommend to make regularly a backup of your DB2 database using a DB2 aware backup software, or export data and backup the exported data. It is possible to implement your DB2 Server for high availability and load balancing using DB2 methods. For more information check into the DB2 InfoCenter, or download and read the RedBook „High Availability and Disaster Recovery Options for DB2 on Linux, UNIX, and Windows“
  • 45. When the installation has finished successfully, click the „Finish“ button and then close the Installation Manager and the Launchpad.
  • 46. STEP THREE: Create a DB2 Database for the Sametime System Console Summary This step creates the Sametime System Console Database on the DB2 Server. If you want to use a dedicated DB2 server or if you already have a DB2 9.5 Server environment available, you can find the Database creation scripts in the DB2 installation package or in the particular installer directory of the Sametime System Console and the Sametime Meeting Server. Use the existing CMD command line or open a new one.
  • 47. Enter the command “cd c:installSametimeDB2”.
  • 48. Enter the command “createSCDb.bat STSC”. The name of the database should not be the name of the Sametime System Console Server. If your SSC is named „stsc.renovations.com“ then you can not name the database STSC. Then you need to use another name for example „STSCDB“. In this example we use „meeting.renovations.com“. So we dont have any issue with the Database Name „STSC“.
  • 49. The DB2 database is now created and confgured. Be sure that you see „The SQL command completed successfully.“ response after every command. If you don't see this responses or get an error message, be sure that your DB2 server is up and running (listening on Port 50.000 or 50.001) and you are authenticated with the correct user and password.
  • 50. STEP FOUR: Install the IBM Lotus Sametime System Console Server Summary This step installs the Sametime System Console Server.
  • 51. Navigate to the „C:InstallSametimeSystemConsole“ directory and enter the command „Launchpad“
  • 52. The Sametime 8.5.1 Launchpad opens. Click the „Install IBM Lotus Sametime System Console“ link on the left side.
  • 53. Now click the link „Launch IBM Lotus Sametime System Console 8.5.1 Installation“
  • 54. The Installation Manager is now loading.
  • 55. Click the „Install“ icon to start the installation.
  • 56. Select „IBM Sametime System Console server“ and „Version 8.5.1“. Then click the „Next“ button to continue.
  • 57. Accept the terms in the license agreement and click the „Next“ button to continue.
  • 58. Enter the correct path (remove „Program Files“ and click the „Next“ button to continue. The Package group is the installation destination for the IBM Lotus WebSphere base files. The first installation requires the creation of a new package group. If you install more WebSphere based applications on the same hardware (like the Sametime Proxy Server and the Sametime Meeting Server) they can use the existing package group. Then you cannot change the installation path.
  • 59. Click the „Next“ button to continue.
  • 60. In this screen you define the WebSphere Application Server administrative user. You need to authenticate with this user to access the Sametime System Console. It is important that this user does not exist in your LDAP. In this example we use the standard „wasadmin“. Enter the password twice and click the „Next“ button to continue.
  • 61. Enter the host name of your DB2 server and the DB2 Administrator password. In this example we have installed the DB2 server on the „meeting.renovations.com“ server. Then click the „Validate“ button to continue.
  • 62. If the DB2 connection was successful, then you should see that the text in the button has changed to „Validated“. Now click the „Next“ button to continue.
  • 63. Click the „Install“ button to install the Sametime System Console Server.
  • 64. The Installation Manager now installs the Sametime System Console. This step can take approximately 30 to 45 Minutes.
  • 65. Important to know... If you plan to use the IBM Lotus Sametime System Console, you should install this part first. But it is possible to add an already installed Sametime Server to the System Console for managing and administration. This can be done with every new Sametime component. By the way, if you lose your already installed System Console server, you can revert it back by installing a new one and add the already installed Sametime components to it using post install registration utilities.Can be found in <product install root>/console directory) Be sure to make a backup of all related data and files (DB2 and WebSphere) because it is much faster to restore a backup if a failure occurs. You will see that it is worth to learn about the Sametime System Console and use it very soon!
  • 66. The Sametime System Console server has installed successfully. Click the „Finish“ button and close the Installation Manager and the Launchpad.
  • 67. STEP FIVE: Log in to the IBM Lotus Sametime System Console Server Summary Start your preferred Browser, enter the System Console URL and log in. In this example we use the Internet Explorer.
  • 68. Enter the URL „http://meeting.renovations.com:8700/ibm/console“. The WebSphere Application Server Administrative interface (the Integrated Solutions Console ISC) is always secured by SSL. Therefore you will be redirected to HTTPS and the port 8701 automatically. You are prompted to accept the default certificate. For different browsers the procedure to accept this IBM signed certificate is different. You can use the direct URL: „https://meeting.renovations.com:8701/ibm/console“.
  • 69. The IBM signed certificate is not trusted by the browser. Click the „Yes“ button to accept the certificate. (this dialog is different using other browsers)
  • 70. Enter the WebSphere Application Server Administrative User name and its password. We use „wasadmin“. Then click the „Log in“ button to continue.
  • 71. You have now reached the IBM Lotus Sametime System Console. Next step is to configure the LDAP connectivity.
  • 72. STEP SIX: Configure the „Connect to LDAP Server“ Prerequisite. Summary In this step you configure the LDAP connectivity in the Sametime System Console. This is used for the Sametime Community Server installation as well as in the Sametime Meeting Server and Media Manager installation. You can change this LDAP connectivity later. But this will not apply to any Deployment Plan or to any already installed server. Any changes needs to be done in the servers configuration directly. (Community, Meeting, Media) This is only for the first installation of the servers before creating the Deployment Plan. Click the „S a m e tim e S ys te m C ons ole “ link.
  • 73. Now click the „Sametime Prerequisites“ link. Next click the „Connect to LDAP Servers“ link.
  • 74. On any Sametime System Console Screen you can find additional information on the middle part of the page. There are Links to the official Sametime InfoCenter for the particular step you want to do next.
  • 75. To connect to an LDAP server click the „Add“ button to continue.
  • 76. Configure the LDAP connectivity information on this screen. - The Deployment Name can be anything describing this LDAP connection. - The Host name should be the Full Qualified Host name. The Port depends on the LDAP. - An MS AD LDAP Server normally uses the Port 3268. Other LDAP Systems use the Port 389. - Do not use the secure connection unless you have imported the certificate from the LDAP server. - The Bind Distinguished Name should be the full qualified Distinguished Name (DN) of the Bind user. - Be sure to enable the checkbox „Is used by the System Console“. This is required that you can assign users and groups to policies later on. Click the „Next“ button to continue.
  • 77. The system now connects to the LDAP server, authenticates and requests the LDAP parameters. It detects the possible Base DN's and the Directory type. Select the right Base DN on this screen. Check the „Configure advanced LDAP settings“ checkbox to see more LDAP parameters. Click the „Next“ button to continue.
  • 78. If you use Domino LDAP then this step is a little different. Note: A drop-down list typically displays from which you select a base DN that is detected by the guided activity; however, the list does not display when Domino® LDAP is being used. Additionally, Domino LDAP is the only LDAP that uses a blank base DN, while WebSphere® requires a base DN for federating repositories. Since WebSphere does not let you federate an LDAP directory with an empty base DN, it sets the base DN to C=US. The LDAP repositories are listed by base DN after they are federated. Failure to specify a base distinguished name will prevent authenticated users from creating and attending meetings on the Lotus Sametime Meeting Server.
  • 79. Important to know... Because WebSphere requires a Base DN, your Sametime Community Server will be configured with a Base DN as well. This is done in the Directory Assistance (DA.NSF) and the LDAP Document in the STCONFIG.NSF database. In some situations (specially if you have multiple directories with different Organizations in your LDAP) it is required to empty this BaseDN field in the DA.NSF and STCONFIG.NSF databases. Specially the BaseDN for Groups has to be removed. I assume you have not created your groups with a “/renovations” at the end. This is the marker for the “O=renovations” Base DN. And only then the groups can be found. So remove the Base DN in the Domino based Sametime Community Server is useful in most cases. But for the WebSphere Servers connecting to the Domino LDAP (Sametime System Console, Sametime Meeting Server and Sametime Media Manager) you need to do additional configuration steps if you have multiple directories in your Domino LDAP server. For example if the users in the first directory are registered with the certifier “O=renovations” and in the second directory with the certifier “O=IBM”, then you need to add a federated repository in the Integrated Solutions Console, configure the “O=IBM” setting in both fields and select the same LDAP server repository.
  • 80. Click the „Next“ button to continue. The Home Sametime Server field has to be filled only if you have a Sametime Community Cluster or more then one Sametime Community Server in your community.
  • 81. Click the „Next“ button to continue.
  • 82. Click the „Finish“ button to save the settings and configure the LDAP connection in the Symetime System Console Server.
  • 83. The LDAP connection is now successfully created and the Sametime System Console server configured. This is a mayor security configuration change that requires a WebSphere server restart.
  • 84. To restart the server, the easiest way is to restart the Windows Services. Starting with Sametime 8.5.1 the installer installs the required services in the operating system. First open the Services view in the Operating System.
  • 85. Then set all of the 3 WebSphere services to automatic. Double click the service. In the “General” tab, near “Startup type” select “Automatic”. Then click the “Apply” button.
  • 86. When this is done for all 3 services, then you can easily restart the Sametime System Console by restarting the operating system. Note: During the Sametime 8.5.1 installation, the required server processes are starting automatically. The services are added at the end of the installation. This means just after the installation the IBM WebSphere services are shown as not started, but the tasks are running. If you now try to start the services in the services view, this will fail. You need to restart the operating system once, and then you can start / stop the services in the services dialog.
  • 87. STEP SEVEN: Run the Guided Activity to configure the IBM Lotus Sametime Community Server installation Summary This guided activity takes you through the steps of creating a deployment plan, which collects information that pre-populates installation screens. We suppose you have your own Lotus Domino Server on that you want to install your Sametime Community Server. It is recommended to not implement this server in your existing Lotus Domino domain. Using a separate Domino Domain gives you independency. You can easily configure your server with LDAP authentication and you are version free. Do not install unwanted installation options like DOLS, DECS, RNRMGR or LDAP. But it is important to enable the HTTP task for the next installation step. In this example we have installed a Domino 8.5.2 Server level.
  • 88. Some slides with my best practices installing a Domino Server hosting a Sametime Community Server.
  • 89. Be sure that the full qualified host name is listed in both fields (see below). If not, just edit the field.
  • 90. Important to know... Configure your Domino Server hosting the Sametime Community Server in a separate Domain. Do not implement this server in your existing Mail Domain. ● You are version independent and can use another domino version then in your Mail Domain ● You are independent in the Directory Design and can use a standard design or a newer design ● Your Domino Directory is empty – it does not contain any users. Makes it easier to implement LDAP ● Add all your collaboration servers (Sametime and/or QuickR) into this Domain ● You can use an existing certifier from your production mail domain to register the server ID. Then you don't need cross certification, can access the server from your Admin Client and Notes Client SSO to Sametime works without any additional configuration ● You can copy an existing SSO LtpaToken Document from your Production Domain to your Collaboration Domain. Add the Sametime Server(s) first and then copy the document.
  • 91. Be sure that your Domino Server is up and running and the HTTP Task is started.
  • 92. Start your Browser now and connect to the Sametime System Console. Then login as described in Step 5. Now click on „Sametime System Console“ and then „Guided Activities“.
  • 93. Click the „Install Sametime Community Server“ link.
  • 94. Confirm that „Create a New Deployment Plan“ is checked and click the „Next“ button.
  • 95. Enter a name for your Community Server Deployment Plan. In this example we just name it „Chat Server“. Then click the „Next“ button to continue.
  • 96. We want to install the Product Version 8.5.1. Leave it as it is and just click the „Next“ button.
  • 97. Enter the Host name of your running Domino Server. The port should only be changed if your Domino HTTP task listens on another port. Enter the Domino Administrators User ID and the password. In this example we use „Domino Admin“. Click the „Next“ button to continue.
  • 98. On Windows it is standard to use the local Sametime Server for Slide Conversion. But it is possible that you have a stand alone Slide Conversion server running. Then you can fill this settings. In this example we just click the „Next“ button to continue.
  • 99. Select the LDAP you want to use for the Sametime Community Server. In this example we use the „Renovations AD LDAP“. (it is the only one we have). Then click the „Next“ button to continue.
  • 100. HTTP Tunneling is required if your Sametime Clients need to connect to your Sametime Server through a Web Proxy or Reverse Proxy Server. But then performance can be slower. Only enable HTTP tunneling when urgently required. Then click the „Next“ button to continue.
  • 101. Confirm all settings and then click the „Finish“ button.
  • 102. You have now successfully created a deployment plan for your Sametime Community Server. The next step is to install the Sametime Community Server.
  • 103. STEP EIGHT: Install the IBM Lotus Sametime Community Server Summary In this step you install the IBM Lotus Sametime Community Server using the Sametime System Console. Before you can start the installation you need to quit the Lotus Domino Server first. Enter the „quit“ command in the Lotus Domino Console and wait until the console disappears.
  • 104. When the Domino Console has disappeared you can open a new CMD line window and navigate to the installation directory. In this example we use: „cd C:InstallSametimeStandardServerServer“. Then enter the command to start the installer „setupwin32.exe“
  • 105. The Lotus Install Shield Wizard is starting up. Confirm the English language or select your preferred language for the installer. Then click the „OK“ button.
  • 106. Click the „Next“ button to continue.
  • 107. Accept the terms in the license agreement anc click the „Next“ button.
  • 108. We want to install the Sametime Community Server using the predefined Deployment Plan in the Sametime System Console. To go this way just accept the default „Yes“ answer and click the „Next“ button.
  • 109. Enter the Host name of the Sametime System Console. In this example we use „meeting.renovations.com“ because we have installed the SSC on this host. The default port for communication is „9443“ (using SSL encryption) Port „9080“ would be in use for unencrypted communication. The WebSphere Administrative User and password is required. We use our standard user name „wasadmin“. The last field is the local host name where you want to install your Sametime Community Server. By default it just displays the host name. Add the domain to get the full qualified hostname in the field. We use „chat.renovations.com“. Then click the „Next“ button.
  • 110. Select the Deployment plan that you have created for your Community Server. We use the „Chat Server“ plan. Then click the „Next“ button.
  • 111. Crosscheck that all settings are correct. Then click the „Install“ button.
  • 112. The Install Shield Wizzard is now installing the Lotus Sametime Community Server on top of your existing Domino Server installation using the predefined Settings from the Deployment Plan in the Sametime System Console. This step takes approximately 2 – 3 Minutes.
  • 113. Important to know... The Sametime Community Server Deployment Plan Guided Activity checks the existence of the Domino Administrator user ID and that this user can authenticate with its HTTP password. Therefore it is required to install the Domino Server before the Sametime Community Server Deployment Plan is created. Later it is possible to change this credentials if the Domino Administrator user changes. This can be done in the Sametime System Console.
  • 114. Important to know... The Sametime 8.5.1 Community Server reads the policy configuration from the Sametime System Console during startup and then every hour. (This can be configured) The first startup of the Sametime Community Servers requires the SSC to get the Policy configuration. Then it caches this data in the local „policies.user.xml“ file. This can be found in the Domino program directory. This means the Sametime Community Server can start and run even if the SSC is not available.
  • 115. When the installation was successfully click the „Finish“ button.
  • 116. Now you can start the Lotus Sametime Server by double click the Domino Server icon on the desktop. If you have configured to start the Domino Server as a service you can start the Service as well or restart the OS. Then the service should start up automatically.
  • 117. Confirm that all Sametime related Services (HTTP JVM and Sametime Services) start up correctly. A full start of a Sametime Server with all tasks can take up to 5 Minutes. You can check the „Task Manager“ and there the „Processes“ view to check that all 41 Tasks starting with the letters „ST...“ are started.
  • 118. STEP NINE: Enable Trust between the Sametime Community Server, the Sametime Proxy Server and the Sametime Media Manager. Summary In this step you configure the Sametime Community Server to trust the Sametime proxy Server and the Sametime Media Manager. The Sametime Proxy Server and Media Manager need to connect to the Sametime Community Server on the Virtual Places (VP) Server Port 1516 to the Sametime Community Server. Normally a Sametime Community Server only allows this connection if the connecting server is known (another Sametime Server in the same Community) or is trusted in the Trusted IP's field in the configuration database. Other Servers you need to trust can be Blackberry Servers, the Sametime Gateway, Sametime Advanced Server, SUT Server, WebSphere Portal Server or other servers who want to connect using the VP Server protocoll.
  • 119. Open the Sametime System Console, Log in and navigate to the Sametime Community Server by clicking on „Sametime System Console“ then „Sametime Servers“ and then „Sametime Community Servers“.
  • 120. Click the link to your Community Server. We click on „Chat Server“ because this is our name for the Community Server Deployment Plan. The „Edit“ link allows you to change the authentication credentials to the Sametime Community Server (Domino Administrator Username, Password and Port)
  • 121. The Sametime Community Server configuration screen appears. Go to the bottom of the screen to find the „Trusted Servers“ Setting.
  • 122. Enter the IP address of the Server you want to allow connecting to the Sametime Community Server. In this example we use the IP „192.168.30.30“. Because we want to install the Sametime Proxy Server and the Sametime Media Manager on the same box, sharing the same IP address, we need to enter only one IP here. Now click the „OK“ button to save the changes to the Community Server configuration.
  • 123. The Sametime Community Server requires a Server restart for most of the configuration changes. Now restart the Sametime Community Server by entering the command „restart server“ in the Domino Console window. Never use this command in a production Sametime server because it can happen that not all Sametime tasks are stopped before the domino server restarts. This can cause massive problems for starting the Sametime Services. It takes up to 5 Minutes until the Sametime Community Server is completely restarted and all 41 Sametime tasks are again active.
  • 124. STEP Ten: Run the guided activity to configure the IBM Lotus Sametime Proxy Server deployment plan Summary Use the Lotus Sametime System Console to prepare to install a Lotus Sametime Proxy Server by pre-populating values required for installation. In the Sametime System Console click on „Sametime System Console“, then on „Sametime Guided Activities“ and then click „Install Sametime Proxy Server“.
  • 125. Confirm that „Create a New Deployment Plan“ is checked and click the „Next“ button.
  • 126. Enter a name for your Proxy Server Deployment Plan. In this example we just name it „Proxy Server“. Then click the „Next“ button to continue.
  • 127. We want to install the actual version 8.5.1. just click the „Next“ button to continue.
  • 128. Select the Community Server you want your Proxy Server to connect to. You need to connect only to one Community Server. The Proxy Server gets information about other Servers in the community and connects to this servers automatic. (Don't forget to enable trust on the other servers as well) In this example we just select the „Chat Server“. Then click „Next“ to continue.
  • 129. The default setting is „Cell Profile“ that we use this example. If you plan to implement the Sametime Proxy Server in a clustered environment, then select „Network Deployment“ and one of the components. Note that it is not possible to implement a Cell Profile and a Network Deployment on the same box. Click „Next“ to continue.
  • 130. Enter the full qualified host name of your proxy server. In this example we use „proxy.renovations.com“. Enter a WebSphere administrative user name and its password twice. We just use the standard „wasadmin“ name. Click the „Next“ button to continue.
  • 131. Control your settings and if all is correct click the „Finish“ button to save the new deployment plan.
  • 132. STEP ELEVEN: Install the IBM Lotus Sametime Proxy Server using the predefined Deployment Plan Summary This step installs the Sametime Proxy Server using the pre-defined Deployment plan in the Sametime System Console.
  • 133. Navigate to the Installation Directory and start the launchpad installer. We use a Windows CMD command window and enter the commands: „cd InstallSametimeProxyServer“ and just „launchpad“
  • 134. The Sametime Proxy Launchpad Installer is loading. Click the link „Install IBM Lotus Sametime Proxy Server“
  • 135. Now click the link „Launch IBM Lotus Sametime proxy Server 8.5.1 Installation“
  • 136. The IBM Installation Manager is loading.
  • 137. Click „Next“ to continue.
  • 138. Accept the terms in the license agreement and click the „Next“ button.
  • 139. Remove the „Program Files“ part in the path and click the „Next“ button.
  • 140. Click the „Install“ button to start the Install Manager installation.
  • 141. The Installation Manager is now installing. This process takes approximately 20 seconds.
  • 142. When the Installation Manager has been installed successfully, click the „Restart Installation Manager“ button.
  • 143. To Install the Sametime Proxy Server click the „Install“ icon.
  • 144. Check the „IBM Sametime Proxy server“ and „Version 8.5.1“ entries. They are unchecked by default. Then click the „Next“ button.
  • 145. Accept the terms in the license agreement and click the „Next“ button.
  • 146. Remove again the „Program Files“ part in the path and click the „Next“ button.
  • 147. Once more remove the „Program Files“ part in the path and click the „Next“ button.
  • 148. We want to use the predefined Deployment Plan from the Sametime System console. Just click the „Next“ button to continue.
  • 149. Enter the Sametime System Console Server information and credentials to authenticate. In our example we use „meeting.renovations.com“ as SSC Server name and „wasadmin“ as the WebSphere Administrative User name. The last field is the host name where we want to install the Sametime Proxy Server. Here we use „proxy.renovations.com“. Then click the „Validate“ button to check the connection to the System Console Server.
  • 150. The connection to the Sametime System Console was successful when the button text „Validate“ changes to „Validated“. Click the „Next“ button to continue.
  • 151. Select your Sametime Proxy Server Deployment plan that you have created in the previous step. We use our „Proxy Server“. Then click the „Next“ button to continue.
  • 152. Control your settings again and then click the „Next“ button to continue.
  • 153. Start the installation by clicking the „Install“ button.
  • 154. The Sametime Proxy Server is now installing. This step takes approximately 30 to 45 minutes if installing as first WebSphere instance on a Server. If you install the proxy Server as second Sametime Component on top of another Sametime Server (SSC or Media Manager) it takes only 10 to 15 minutes because the WebSphere binaries are already installed.
  • 155. Important to know... The Sametime Proxy Server: ● does not need a Database ● does not need a LDAP connection ● is just a Web Interface for browser access to the Sametime Community Services ●Web based Sametime Connect Client ● supplies the new Web API for Web based application integration ● can be implemented with or without the SSC ● can be connected to existing older Sametime Servers ● can be connected to a community cluster You can have one or more Proxies in your organization You can implement one or more Proxies and cluster them ● using the WebSphere Cluster Method (Network Deployment) ● individual Proxies with a Load Balancer or RRDNS in front of them By default the Sametime Proxy Server installs to use Port 9080 and 9443 (SSL). If you want to use Port 80 and 443 you need to enter the Sametime Proxy ISC on Port 8600 and change the port settings in the Application Server. Do this change when the installation has finished successfully.
  • 156. When the Sametime Proxy Server has installed successfully just click the „Finish“ button and exit the Installation Manager and Launchpad. To configure your Start and Stop batches proceed the same way as on Page 85 and following (end of step 6) when the installation has finished successfully.
  • 157. To test your Sametime Proxy Server installation and the connection to your Sametime Community Server, open a Browser window and navigate to the URL: „http://proxy.renovations.com:9080/stwebclient/index.jsp“. You should see this page: Now click the „Launch Sametime“ button.
  • 158. Enter the user name and password of any user in the directory and click the „Log In“ button. You are authenticated to the Sametime Community Server and see your (new) buddy list.
  • 159. STEP TWELVE: Create the IBM Lotus Sametime Meeting Server database Summary In this step you create the second DB2 Database that is required for the Sametime Meeting Server.
  • 160. In a CMD command line window navigate to the Sametime Meeting Server installation directory. We use the „cd InstallSametimeMeetingServer“ command. Then enter the command to create the Meeting Database. We use the Database name „STMS“ and enter the command: „createMeetingDb.bat STMS“ The name of the database should not be the name of the Sametime Meeting Server. If your Meeting Server is named „stms.renovations.com“ then you can not name the database STMS. Then you need to use another name for example „STMSDB“. In this example we use „meeting.renovations.com“. So we dont have any issue with the Database Name „STMS“.
  • 161. The Database creation takes approximately 2 – 3 minutes. You should confirm that the database is created and configured successfully. Check that you find the message „The SQL command completed successfully“ after every command.
  • 162. STEP THIRTEEN: Configure the „Connect to DB2 Database“ for the Sametime Meeting Server Database Summary In this step you configure the connection to the Sametime Meeting Server Database on your DB2 Server.
  • 163. In your Sametime System Console click on „Sametime System Console“ then „Sametime Prerequisites“ and then „Connect to DB2 Database“.
  • 164. Click the „Add“ button.
  • 165. Fill the form with your DB2 Servers host name, the name of the Database you created in the previous step and the DB2 Administrator credentials. In this example we use „meeting.renovations.com“ for the DB2 Server host name, „STMS“ for the Database Name and „db2admin“ for the DB2 administrative user name. In some installations the access port can be „50001“ or different. Then click the „Finish“ button to save your settings.
  • 166. You have now created successfully your DB2 Database connection for the Sametime Meeting Server database. The next step is to create a deployment plan for your Sametime Meeting Server.
  • 167. STEP FOURTEEN: Run the guided activity to configure the IBM Lotus Sametime Meeting Server deployment plan Summary This step is to preconfigure the settings for the Sametime Meeting Server installation.
  • 168. In your Sametime System Console click on „Sametime System Console“ then „Sametime Guided Activities“ and then on „Install Sametime Meeting Server“.
  • 169. Use the first entry „Create a New Deployment Plan“ and click the „Next“ button.
  • 170. Enter a name for your Meeting Server Deployment Plan. In this example we use „Meeting Server“. Then click the „Next“ button to continue.
  • 171. We want to install the product version „8.5.1“. Click the „Next“ button to continue.
  • 172. Leave the default „Cell Profile“ checked and click the „Next“ button to continue.
  • 173. Enter the full qualified host name of your Sametime Meeting Server. In this example we use „meeting.renovations.com“. Enter a WebSphere administrative user name and its password twice. We just use the standard „wasadmin“ name. Click the „Next“ button to continue.
  • 174. Select your Sametime Meeting Server Database connection and click the „Next“ button. Select your LDAP connection and click the „Next“ button.
  • 175. Check your settings and then click the „Finish“ button to save the new Deployment Plan.
  • 176. You have now successfully created a Deployment Plan for the Sametime Meeting Server installation. The next step is to install the Sametime Meeting Server.
  • 177. STEP FIVTEEN: Install the IBM Lotus Sametime Meeting Server Summary In this step you install the Sametime Meeting Server using the preconfigured settings in the deployment plan on the Sametime System Console.
  • 178. In a CMD command line window navigate to the Sametime Meeting Server install directory. We do this with the command: „cd InstallSametimeMeetingServer“. Then start the Launchpad installer with the command „launchpad“.
  • 179. Click the „Install IBM Lotus Sametime Meeting Server“ link.
  • 180. Click the „Launch IBM Lotus Sametime Meeting Server 8.5.1 Installation“ link.
  • 181. The Installation Manager is starting loading.
  • 182. Just click the „Install“ icon to start the Sametime Meeting Server installation.
  • 183. Check the „IBM Sametime Meetings server“ and „Version 8.5.1“ entries. They are unchecked by default. Then click the „Next“ button.
  • 184. Accept the terms in the license agreement and click the „Next“ button.
  • 185. Because we have already installed a WebSphere based Sametime Server on this box, (The Sametime System Console) we can reuse the installed binaries. The installer detects this and checks the „Use the existing package group“. And therefore the path is greyed and can not be changed. Click the „Next“ button to continue.
  • 186. We want to use the predefined Deployment Plan from the Sametime System Console. Click the „Next“ button to continue.
  • 187. Enter the Sametime System Console Server information and credentials to authenticate. In our example we use „meeting.renovations.com“ as SSC Server name and „wasadmin“ as the WebSphere Administrative User name. The last field is the host name where we want to install the Sametime Meeting Server. Here we use „meeting.renovations.com“. Then click the „Validate“ button to check the connection to the System Console Server.
  • 188. The connection to the Sametime System Console was successful when the button text „Validate“ changes to „Validated“. Click the „Next“ button to continue.
  • 189. Select your Sametime Meeting Server Deployment plan that you have created in the previous step. We use our „Meeting Server“. Then click the „Next“ button to continue.
  • 190. Control the settings you received from the System Console. Then click the „Next“ button.
  • 191. To start the installation click the „Install“ button.
  • 192. The Sametime Meeting Server is now installing. This takes approximately 30 to 45 minutes. But because we already have the binaries installed and reuse this data, the installation is much shorter. It then takes only 15 to 20 minutes.
  • 193. Important to know... To configure LiveName integration in the Browser Meeting interface, SSO between the Community Server and the Meeting Server is required. The LTPA Token has to be exported from the Meeting Server and imported in the community server. Live Name Integration works over the REST API in the Proxy Server. You can find the required steps in the Sametime InfoCenter. Configure this setting when the Meeting Server, the Community Server and the Proxy Server have been installed successfully. No Connectivity is required between the Meeting Server and the Media Manager. Audio and Video is possible only with the Sametime Connect Client Version 8.5 or newer. (Stand alone or Notes embedded client). This client first connects to the Community Server. From there it receives the connectivity information to other servers. Then it connects to the Media Manager with SIP protocol.
  • 194. Important to know... The Meeting Server can be clustered using the WebSphere Network Deployment. This can be configured and deployed with the Sametime System Console. The new Sametime Meeting Server consists of two components. - the Meeting Server - the Meeting HTTP Proxy Clustering means that a meeting room is running only on one server at a time. The Meeting Proxy servers have the information on witch Meeting Server instance the Meeting Room is running and forward incoming requests to the right server. Meeting data are stored only in the database. In case of a fail over the Meeting Room will be started on another Meeting Server in the cluster immediately. For external access a separate Sametime Meeting Server in your DMZ is recommended for better security.
  • 195. Lotus Sametime Lotus Notes or Web clients Lotus Sametime Servers Meetings 2 Meetings 1 WebSphere Application Server Proxy Cluster Clustered servers use the web services to support high availability and failover Individual meetings exist on a single cluster member Proxy server provides caching and helps application server scale; routes HTTP traffic to correct node Lotus Sametime 8.5.1 Meetings Cluster Deployment
  • 196. Presence & Instant Msg Meetings 1 Lotus Sametime Lotus Notes Clients Lotus Sametime 8.5.1Lotus Sametime 8.5.1 External Meetings DeploymentExternal Meetings Deployment Lotus Sametime Web Clients Lotus Sametime Servers Meetings 2 Lotus Sametime Web Clients Lotus Sametime Lotus Notes Clients External participants Internal participants
  • 197. You have now successfully installed the Sametime Meeting Server. Click the „Finish“ button and exit the Installation Manager and Launchpad. To configure your Start and Stop batches proceed the same way as on Page 85 and following (end of step 6) when the installation has finished successfully.
  • 198. You can test the Meeting Server Browser access simple by opening a Browser window and enter the URL: „http://meeting.renovations.com“. You will be automatic redirected to the „/stmeetings“ page. You should see this page:
  • 199. To authenticate to the Sametime Meeting Server use one of the „Log In“ links (3 possible locations for this link.
  • 200. Enter a User name and password (who is in the LDAP directory) and click the „Log In“ button.
  • 201. You are now logged in and can create a new meeting room using the „New Meeting Room“ link.
  • 202. Just enter a name for your Meeting Room. Then click the “Save” button.
  • 203. Your new Meeting Room has been created successfully.
  • 204. STEP SIXTEEN: Enable Trust between the IBM Lotus Sametime Community Server and the IBM Lotus Sametime Media Manager Summary In this step you configure the Sametime Community Server to allow the Sametime Media Manager to connect on port 1516 with the VP protocoll. Because we have the Sametime Proxy Server and the Sametime Media Manager running on the same box, they share the same IP address. We already have configured this trust for the Sametime Proxy Server. There is no need to configure this step in this example. If you want to deploy your Sametime Media Manager on another box, then you need to configure this Trust. See step Nine and follow the instructions there.
  • 205. STEP SEVENTEEN: Run the Guided Activity to configure the IBM Lotus Sametime Media Manager Deployment plan Summary In this step you prepare the installation of the Sametime 8.5.1 Media Manager.
  • 206. In your Sametime System Console click on „Sametime System Console“ then „Sametime Guided Activities“ and then „Install Sametime Media Manager“
  • 207. We want to „Create a New Deployment Plan“ for the Sametime Media Manager. Click the „Next“ button to continue.
  • 208. Enter a name for your Media Manager Deployment. In this example we use „Media Manager“. Then click the „Next“ button to continue.
  • 209. We want to install the product version „8.5.1“. Click the „Next“ button to continue.
  • 210. We want to install all Media Manager components in this server. It is possible to split the components to separate machines for clustering. If you plan to cluster later you should use separat boxes for each of the 3 components. We accept the default setting „Install All Components“. Click the „Next“ button to continue.
  • 211. When installing all components in one box then only the „Cell Profile“ is possible. Don't change the default setting and click the „Next“ button to continue.
  • 212. Enter the full qualified host name of your Sametime Media Manager Server. In this example we use „proxy.renovations.com“. Enter a WebSphere administrative user name and its password twice. We just use the standard „wasadmin“ name. Click the „Next“ button to continue.
  • 213. Select the Community Server to which the Media Manager should connect to. In our example we use the „Chat Server“. Then click the „Next“ button to continue.
  • 214. Control that all settings are correct. Then click the „Finish“ button to save the Deployment Plan.
  • 215. You have now successfully created the Sametime Media Manager Deployment Plan. The next step is to install the Sametime media Manager.
  • 216. STEP EIGHTEEN: Install the IBM Lotus Sametime Media Manager Summary In this step you install the Sametime 8.5.1 Media Manager.
  • 217. In a CMD command line window we navigate to the installation directory of the Sametime media Manager. In our example we use the command: „cd InstallSametimeMediaManagement“. Then we start the installation with the Launchpad installer by entering the „launchpad“ command.
  • 218. The Sametime Launchpad Installer is starting up. Click the „Install IBM Lotus Sametime Media Manager“ link to continue.
  • 219. Click the „Launch IBM Lotus Sametime media Manager 8.5.1 Installation“ link.
  • 220. The Installation Manager is starting up.
  • 221. To install the Sametime Media Manager click the „Install“ icon.
  • 222. Check the „IBM Sametime Media server“ and „Version 8.5.1“ entries. They are unchecked by default. Then click the „Next“ button.
  • 223. Accept the terms in the license agreement and click the „Next“ button to continue.
  • 224. We use the existing package group. Click the „Next“ button to continue.
  • 225. We want to use the predefined deployment plan in the Sametime System Console for this installation. Click the „Next“ button to continue.
  • 226. Enter the Sametime System Console Server information and credentials to authenticate. In our example we use „meeting.renovations.com“ as SSC Server name and „wasadmin“ as the WebSphere Administrative User name. The last field is the host name where we want to install the Sametime Media Manager. Here we use „proxy.renovations.com“. Then click the „Validate“ button to check the connection to the System Console Server.
  • 227. The installer checks the connectivity to the Sametime System Console. When this was successful the text in the button changes from „Validate“ to „Validated“. Click the „Next“ button to continue.
  • 228. Select your Media Manager Deployment plan. We use the „Media Manager“ plan. Then click the „Next“ button to continue.
  • 229. Control your installation data that where read from the Deployment plan on the Sametime System Console. Then click the „Next“ button to continue.
  • 230. To start the installation click the „Install“ button.
  • 231. The Installation Manager now installs the Media Manager. This installation will take approximately 30 to 45 minutes. But because we are installing on a machine where the WebSphere binaries are already installed (with the Sametime proxy Server), this step will be skipped and it takes only 10 to 15 minutes.
  • 232. Important to know... The Media Manager uses new Audio and Video codecs (H.264/MPEG4). The Media Manager uses SIP for VoIP connectivity (Sametime Connect Client or Notes Embedded Sametime Client). The Media Manager can be connected to existing Audio and Video conference systems and provides the interoperability of Sametime Clients and other A/V endpoints. The Media Manager is not exactly a PBX. It is just a server with its own connectivity and TCSPI SDK to connect to other systems. This has nothing to do with Sametime Unified Telephony.
  • 233. The Media Manager can be clustered for better scalability if required. The components of a Media Manager can be split and implemented on different machines for scalability. In the actual release only the SIP Proxy Registrar and the Conference Manager can be clustered. The Packet switcher can not be clustered. This is the cause for the need to have several boxes to cluster the Media Manager server. Sametime 8.5.1 Media Manager has been extended for encrypted Media traffic transfer (TLS) and more participants in a single conference. This version of the Media Manager still does not support NAT traversal. If you want to communicate by Audio/Video over the Internet use VPN. Important to know...
  • 234. You have now successfully installed the Sametime Media Manager Server. Click the „Finish“ button then close the Installation Manager and the Launchpad installer. To configure your Start and Stop batches proceed the same way as on Page 85 and following (end of step 6) when the installation has finished successfully.
  • 235. STEP NINETEEN: Install the IBM Lotus Sametime Connect Client Summary In this step you install the Sametime 8.5.1 Connect Client Standard.
  • 236. Navigate to the installation directory. We use a CMD command line window and enter the command: „cd InstallSametimeStandardClientsametimecilent.standaloneWindows“. Then start the installer by entering „sametime-connect.exe“.
  • 237. We want the installation files to be stored in a temporary directory. So we use the default setting. Then click the „Next“ button.
  • 238. The installation files are now extracted.
  • 239. Select your preferred language for the installation and click the „OK“ button.
  • 240. The Lotus Sametime Connect Install Shield Wizard has started. Click the „Next“ button to continue.
  • 241. Accept the terms in the license agreement and click the „Next“ button to continue.
  • 242. My recommendation again is to remove the „Program Files“ part of the path and then click the „Next“ button to continue.
  • 243. Check the settings and click the „Install“ button to start the installation.
  • 244. The Install Shield Wizard now installs the Sametime Connect Client. This process takes approximately 3 to 5 minutes.
  • 245. Important to know... The new Sametime 8.5.1 Connect Client can be installed as a stand alone version or as Embedded Version in an existing Notes 8.5.1 or newer client. This works with all language versions of the Notes Client. The new Meeting Plug-In is automatically installed with this client. The SUT Client is installed with the new Sametime 8.5.1 Connect Client installer. The Sametime Connect Client is available for Windows, Linux and MAC platforms.
  • 246. You have now successfully installed the Sametime Connect Client. Leave the check box to Launch the Client checked and click the „Finish“ button to start the configuration.
  • 247. The Lotus Sametime Connect Client is now starting up.
  • 248. Fill the configuration form with your Sametime Community Server host name and User credentials in the LDAP directory. In this example we use „chat.renovations.com“ for the host name and „Sam Curman“ as user. If you prefer to have the password saved and log in automatically, then check the 2 check boxes. Then click the „Log In“ button.
  • 249. After some seconds the question for saving chat transcripts will pop up. To make it easy just click the „No“ button. This can be configured later.
  • 250. You have now successfully installed the Sametime Connect Client Version 8.5.1. The next step is to configure the Sametime Meetings Plugin
  • 251. STEP TWENTY: Configure the IBM Lotus Sametime Client Meetings Plugin Summary In this step you configure your Sametime Meetings Plugin to connect to your Meeting Server.
  • 252. In your Sametime Connect Client click on „File“ and then in the menu on „Preferences“.
  • 253. In the Preferences menu click on „Sametime Meeting Rooms“ and then on „Meeting Room Servers“.
  • 254. To add a new Sametime Meeting Room Server just click the Button „Add Meeting Room Server ...“.
  • 255. In the „Identity“ section you can configure the Community Server settings from where the authentication information is coming from. We use our „chat.renovations.com“ server. In the „Connection settings“ section we enter the Sametime Meeting Server host name. We use „meeting.renovations.com“. Then click the „OK“ button to save the changes.
  • 256. You will now find an entry for your new meeting server. Click the „Apply“ button to save the changes to your preferences. Then click the „OK“ button to close the preferences screen.
  • 257. Open the Sametime Meetings Plugin. We now see a meeting room that was created before (in the Web Meeting Interface).
  • 258. To access the Meeting Room „Sams Room“ just click the „Enter Room“ link.
  • 259. You are now accessing the Sametime Meeting Room „Sams Room“ with the Sametime Connect Client User interface.
  • 260. STEP TWENTYONE: Configure the Meeting Room to use Audio and Video Summary In this step you configure your Sametime Meeting Room to use Audio and Video features over the Media Manager Server.
  • 261. In your Sametime Connect Client, in the Sametime Meetings Plugin click the „More Actions“ link in one of the meeting rooms.
  • 262. Click the „Edit ...“ button to change the Meeting Room settings.
  • 263. In the Edit Meeting Room Settings page in the „Audio Conferences“ section click the button near „Unspecified“. There you should find an entry „Sametime Audio/Video Conferencing“. Select this option, enable „Video“ and click the „OK“ button.
  • 264. Now enter the Meeting Room again by clicking the „Enter Room“ link.
  • 265. You can now see Telephone symbol in the Conferencing section at the top left corner. If you click the Telephone icon you can join the call with your computer for Audio and Video.
  • 266. Additional Steps after the installation: The Sametime 8.5.1 Meeting Server now has a URL redirection to the “/stmeetings” page. This is not implemented in the Sametime Proxy Server. Here you still need to enter the “/stwebclient/index.jsp” in the url to access the server. It is possible to connect directly to the “stwebclient/popup.jsp” page. To get the WebSphere application that can be installed on the Sametime Proxy Server for the automatic redirection (like in the Meeting Server) you can contact the author of this presentation. If you want to implement SSL to access your Sametime Meeting or Sametime Proxy Server, additional configuration steps are required. See the Lotus Sametime InfoCenter for more details. Automatic URL redirection to https (SSL) can be configured. To get the install instructions you can contact the author of this document.
  • 267. Ports to access the Integrated Solutions Console of the particular Servers This are the standard ports when the servers are installed with the Cell profile method. HTTP HTTPS Sametime Meeting Server 8500 8501 Sametime Proxy Server 8600 8601 Sametime System Console 8700 8701 Sametime Media Manager 8800 8801
  • 268. 274 Unified Communications Sessions ● AD306 - IBM Lotus Sametime Proxy: A Collaborative Recipe for Success William Holmes Wednesday 4:15-5:15pm DL S. Hemisphere I ● AD307 - Application Development with the IBM Lotus Sametime SDK: From Java to Web 2.0Marlon Machdo Monday 2:15-3:15pm DL S. Hemisphere 1 ● BP102 – Get Started Installing IBM Lotus Sametime 8.5.1 – You Too Can Be a WAS Admin! Gabriella Davis (The Turtle Partnership) Tuesday 3:30- 4:30pm SW 5-6 ● BP120 Sametime Gateway: The Business Case, Implementation and Best Practices Chris Miller (Connectria) Tuesday 11:15- 12:15pm DL S. Hemisphere II ● BP121 - The SUT "WOW Factor": How to Surprise and Delight Enterprise Voice ArchitectsDavid Price (MeridianIT) Wednesday 11:15-12:15 SW 7-10 ● JMP202 Sametime 8.5.1 Deployment Workshop Wes Morgan Sunday 4:00-6:00pm DL S. Hemisphere 1 ● BOF203: Avaya: Communication-Enabled Applications: Avaya's Agile Communication Environment John Bednarek (Avaya) Tuesday 5:45- 6:45pm SW Macaw 1 ● BOF207: Considerations for Your IBM Lotus Sametime Deployment Uri Segev Monday 6:15-7:15pm SW Parrot 1 ● BOF215: IBM Lotus Sametime Best Practices, Tips, Tricks and Experiences Frank Altenburg, Volker Juergensen Thursday 7:00-8:00am SW Toucan 1 ● BOF216: Integrating Video with UC Peter Lurie (Polycom) Wednesday 5:45-6:45pm SW Parrot 1 ● BOF219: ShoreTel: IP Telephony Integration for IBM Lotus Sametime Users Kurt Kruger (ShoreTel) Monday 5:45-6:45pm SW Parrot 2ne ● BOF405: IBM Lotus Sametime 8.5 Discussion Forum Andy Higgins (IMCollaboration) Tuesday 7:00-8:00am SW Osprey ● INV106 - Unified Communications and Collaboration Strategy and Roadmap Caleb Barlow, John Del Pizzo Monday 5:00pm DL N Hemisphere A-E ● ID501 - What's New in IBM Lotus Sametime? Robert Ingram, Amy Travis Tuesday 1:30-2:30pm SW 5-6 ● ID502 - Join the Lotus Sametime Communications Revolution Now! Pat Galvin, Binh Nguyen Wednesday 8:30-9:30am SW 5-6 ● ID503 - Lotus Sametime Meetings: Today, Tomorrow - and Beyond Amy Travis, Ron Pontrich Wednesday 1:30-2:30 DL S. Hemisphere II ● ID504 - IBM Lotus Sametime Mobile: Native Meetings and Messaging Joe Scherpa, Steve Babin Tuesday 4:45-5:45 DL S. Hemisphere III ● ID505 - Network Architecture for IBM Lotus Sametime Audio/Video Uri Segev, Anat Fradin Wednesday 1:30-2:30 DL S. Hemisphere III ● ID506 - Planning and Implementing a High Availability Sametime 8.5.x Deployment Uri Segev, Tony Payne Thursday 8:30-9:30am SW 7-10 ● ID507 - IBM Lotus Sametime Unified Telephony: Today and Tomorrow David Marshak, Tracee Wolf Wednesday 10-11:00 DL S. Hemisphere III ● ID508 - IBM Lotus Sametime Web-enabled Audio/Video Conferencing Bhavuk Srivastava, Sagar Joshi Monday 3:45-4:45 SW 3-4 ● ID509 - Unified Communications and Collaboration: Clicking to Collaborate Sam McHan, Dennis Shafto Monday 5:00-6:00pm SW 3-4 ● ID510 - Using Voice and Video in IBM Lotus Sametime Tracee Wolf, Jodi Rajaniemi Wednesday 3:00-4:00pm DL S. Hemisphere II ● SHOW201- From Zero to Hero: IBM Lotus Sametime 8.5.1 Installation Frank Altenburg, Volker Juergensen Tuesday 2:00-3:45pm SW Osprey
  • 269. 275 Do you have any questions? Don't forget to fill in the evaluation form. Thank you.
  • 270. © 2011 IBM Corporation 276 Legal Disclaimer © IBM Corporation 2011. All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.