IBM Sametime 8.5.2 Installation - From Zero To Hero - Basics - 21.12.2011

89,092 views

Published on

A Sametime Installation can be verry complicated if you dont know how to start and how to architect your pilot. This slideshow gives you the complete instruction to implement a small pilot on 2 machines, and if you have the licenses to install Sametime Advanced.

Published in: Business, Technology
54 Comments
20 Likes
Statistics
Notes
  • Frank, in the sametime gateway installatión , after installing websphere fixes, if we go to the sametime gateway console and we try to run all tests the test about the websphere fixes level fails , showing that it requires fix level 13, instead of 15.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • @undefined CWWIM4537E No principal is found from the '${user.was.user}' any idea??
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Error in meeting when I try video:
    error 503. Unspecified Dial Failure

    in VMGR
    SECJ0369E: Authentication failed when using LTPA. The exception is com.ibm.websphere.wim.exception.PasswordCheckFailedException: CWWIM4537E No principal is found from the 'admin' principal name.

    Any ideas?
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • @frank,
    I followed your brilliant procedure, all looked successful, but I have an issue on Sametime Client, user can't start instant meeting, after selecting attendees, nothing happens... As I could see in several demo video, the meeting room should be opened automatically on the chair's desktop and waiting for attendees to join it, in my case : nothing triggers...nothing too on the attendees desktop...Have you ever seen this sort of issue ?
    For information Meeting & Proxy are sharing the same IP address, can it be
    Against by, scheduled meetings are working fine, users can join opened rooms without any issue
    Your help would be very helpful ;)
    Thanks
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • @frank Finally i found the problem. evidently It's not an SSO issue, that is because the port information 'meetingroomcenter.STProxyAddress' on SSC - Meeting Server is wrong. It should enter the correct port you are using. The port should 9081. Previously I am using port 9080. May be you should cek the tutorial because i found it no port entered but i am not sure too it caused av problem. But anyway thank you for your great tutorial, that's help us so much. I wrote this in my blog at http://www.johanes.org
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
89,092
On SlideShare
0
From Embeds
0
Number of Embeds
17,750
Actions
Shares
0
Downloads
4,422
Comments
54
Likes
20
Embeds 0
No embeds

No notes for slide

IBM Sametime 8.5.2 Installation - From Zero To Hero - Basics - 21.12.2011

  1. 1. IBM Collaboration Solutions Installation and Setup of IBM Sametime 8.5.2 ”From Zero to Hero” Part 1 - Basics Frank Altenburg | SME for Sametime | IBM Volker Juergensen | Senior IT Specialist | IBM Social Business New Version from December, 12. 2011 © 2009 IBM Corporation
  2. 2. Agenda ● Components of IBM Sametime 8.5.2 ● Requirements for a IBM Sametime 8.5.2 Deployment ● Architecture of a IBM Sametime 8.5.2 pilot deployment ● The 34 steps to a IBM Sametime 8.5.2 pilot deploymentSocial Business 2 © 2010 IBM Corporation
  3. 3. The IBM Sametime 8.5.2 Components we will cover In this Part 1: ● IBM DB2 Database Server ● IBM Sametime System Console ● IBM Sametime Community Server ● IBM Sametime Proxy Server ● IBM Sametime Meeting Server ● IBM Sametime Media Manager ● IBM Sametime Advanced Server (optional) ● IBM Sametime Connect Client In Part 2: ● IBM Sametime Community MUX (optional) ● IBM secure DMZ HTTP Proxy ● IBM Sametime SIP Proxy ● IBM Sametime TURN Server ● IBM Sametime Gateway In Part 3: ● Moving Sametime Servers to separate boxes ● Implementing additional Servers for clustering ● Clustering of Sametime ServersSocial Business 3 © 2010 IBM Corporation
  4. 4. IBM Sametime System Level Architecture Sametime Clients HTTP HTTP VPSIP, RTP SIP, RTP Meeting Advanced Server VP Server Community VP Server VP Media Unified Manager Telephony VP VP SIP SIP, TCSPI Partner Enterprise Phone Sametime Sametime System A/V Bridges Proxy Gateway SIP, XMPP HTTPLogical servers shown – may External IMbe combined physically Embedded Applications, Communitiesdepending on user workload including Web Client, Portal, and Mobile Social Business 4 © 2010 IBM Corporation
  5. 5. IBM Sametime System Console ● Manage prerequisites. – System console manages all needed info for prerequisite components – No install/reinstall of IBM DB2® (for example) for Sametime Domino each separate offering Presence/IM Sametime System Console Sametime ● Centralize configuration. Classic LDAP – Setup & testing of things like LDAP centralized in Meetings a single location, instead of various wizards in Sametime different installers New Meetings Facilitate deployment planning. WebSphere ● Sametime Media – Mechanism to plan the Sametime server Server deployment Sametime Proxy DB2 – Installation of server nodes is simpler, as the shared configuration already exists. Server Sametime installers are “headless”, and need no input Advanced from user ● Single point of action for administrative tasks – Example: Policies are managed from a single place for all componentsSocial Business 5 © 2010 IBM Corporation
  6. 6. Agenda ● Components of IBM Sametime 8.5.2 ● Requirements for a IBM Sametime 8.5.2 Deployment ● Architecture of a IBM Sametime 8.5.2 pilot deployment ● The 34 steps to a IBM Sametime 8.5.2 pilot deploymentSocial Business 6 © 2010 IBM Corporation
  7. 7. IBM Sametime 8.5.2 Prerequisites ● IBM Sametime 8.5.2 System Console Server requires ● IBM WebSphere Application Server 7.0.0.15 (provided automatically via Install) ● IBM DB2 9.7 or 9.5 FP1 ● LDAP directory server (Supported IBM® Lotus® Domino® Directory LDAP, Microsoft® Active Directory, IBM Tivoli® Directory Server, SunOne® iPlanet®, Novell® eDirectory®) ● IBM Sametime 8.5.2 Sametime Community Server requires ● IBM Lotus Domino 8.5.1 or 8.5.2 (32 Bit Version only) ● LDAP directory server ● IBM Sametime 8.5.2 Proxy Server requires ● IBM WebSphere Application Server 7.0.0.15 (provided automatically via Install) ● IBM Sametime Community Server (Version >= 7.5.1) ● IBM Sametime 8.5.2 Meeting Server requires ● IBM WebSphere Application Server 7.0.0.15 (provided automatically via Install) ● IBM DB2 9.5 FP1 (provided automatically via Install) ● LDAP directory server ● IBM Sametime 8.5.2 Media Manager requires ● IBM WebSphere Application Server 7.0.0.15 (provided automatically via Install) ● IBM Sametime 8.5.2 Community Server ● LDAP directory serverSocial Business 7 © 2010 IBM Corporation
  8. 8. IBM Sametime 8.5.2 Prerequisites (cont.) ● IBM Sametime 8.5.2 Advanced Server requires ● IBM WebSphere Application Server 7.0.0.15 (provided automatically via Install) ● IBM DB2 9.7 or 9.5 FP1 ● LDAP directory server (Supported IBM® Lotus® Domino® Directory LDAP, Microsoft® Active Directory, IBM Tivoli® Directory Server, SunOne® iPlanet®, Novell® eDirectory®) ● IBM Sametime Community Server (Version >= 8.0.1)Social Business 8 © 2010 IBM Corporation
  9. 9. IBM Sametime 8.5.2 Prerequisites (continued) ● Software requirements ● Client ● Windows XP (SP2), XP Tablet, Vista and Windows 7 – 32 and 64 bit ● MAC OS X 10.6.2 x86-64 and future OS fix packs ● RHEL 5.0 Update 4 Desktop Edition x86-32 and future OS fix packs ● SLED 10.0 SP3 and 11.0 SP1 32 and 64 bit and future OS fix packs ● Ubuntu 10.04 LTS x85-32 and future OS fix packs ● Server ● Windows Server 2003/2008 - 32 and 64 bit (including R2) ● Linux (RHEL, SLES) - 32 and 64 bit ● AIX 5.3/6.1 ● i5/OS 5.4, 6.1 ● Solaris 10 ● ESX and ESXi 4.0, MS Hyper-V R2 ● Browsers ● Microsoft® Internet Explorer 6.x, 7.x, 8.0 (Windows) ● Firefox 3.5 and 3.6 (Windows, Mac, Linux) ● Safari 5.0 (Mac) ● Other ● Domino 8.5.1/8.5.2 for Community Server / Classic meetings ● WebSphere Application Server 7 for new servers and gateway (included) ● DB2 9.7 for new servers and gateway (included)Social Business 9 © 2010 IBM Corporation
  10. 10. IBM Sametime 8.5.2 Prerequisites (continued) ● Software requirements ● For WEB A/V ● Microsoft® Internet Explorer 6.x(!!), 7.x, 8.0 (Windows) ● Firefox 3.5 and 3.6 (Windows, Mac) SPECIAL NOTE: Microsoft Internet Explorer 9, Apple Safari and Google Chrome are not supported with the Sametime Audio/Video Browser Plugin in this actual Sametime Version 8.5.2. We do not support any Linux based OS now for Browser A/V. Microsoft Internet Explorer 6 should work and is officially supported. But it is not recommended to use this version because it can cause issues when several parallel connections needs to be established with the meeting server.Social Business 10 © 2010 IBM Corporation
  11. 11. 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 Media Manager Server does not work when installing with a DNS alias. You must configure the full qualified machine host name (including domain part) and use this for the installation. This name does not need to be configured anywhere else and the client does not see it. ● 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.Social Business 11 © 2010 IBM Corporation
  12. 12. Required files for a deployment on Windows For a Windows installation you need to download these files from Passport Advantage: CZYG1ML.zip IBM DB2 9.7 32Bit Limited Use for Sametime CZ1GMML.zip IBM DB2 9.7 32Bit Net Search Extension (Optional) CZYF2ML.zip IBM Sametime System Console Server CZYD7ML.zip IBM Sametime Community Server Standard CZYE6ML.zip IBM Sametime Proxy Server CZYE0ML.zip IBM Sametime Meeting Server CZYF0ML.zip IBM Sametime Media Manager Server CZYH2ML.zip IBM Sametime Advanced Server (Optional) CZYF7ML.zip IBM Sametime Client Package 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. Even if you are installing on a 64Bit OS (Windows 2008 R2 64Bit) use the 32Bit DB2 and NSE. It just works and makes the installation easier.Social Business 12 © 2010 IBM Corporation
  13. 13. Agenda ● Components of IBM Sametime 8.5.2 ● Requirements for a IBM Sametime 8.5.2 Deployment ● Architecture of a IBM Sametime 8.5.2 pilot deployment ● The 34 steps to a IBM Sametime 8.5.2 pilot deploymentSocial Business 13 © 2010 IBM Corporation
  14. 14. IBM Sametime 8.5.2 - Our pilot recommendation Compared with the last version of this document installing IBM Lotus Sametime 8.5.1 (from Lotusphere 2011), we have changed again our recommendation for a pilot deployment. The reason for the change is the availability of new features in installation methods as well as our increased experience and many successful installations using this method in the last months. It is known that implementing several components, who provides web services on one box, require special network configuration. The services needs to be bind to individual IP addresses. This configuration is described fully and detailed later here in the document. The Sametime Advanced Server in this pilot deployment is optional and requires additional licensing. Do not install this server if you do not have purchased the required licenses. Without Sametime Advanced you can do the full installation of all components with just 2 machines.Social Business 14 © 2010 IBM Corporation
  15. 15. 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 2 servers plus one optional server for Sametime Advanced: ● Server1: DB2 Database Server, Sametime System Console, Sametime Meeting Server, Sametime Media Manager, Sametime Proxy Server ● Server2: Sametime Community Server ● Server3: Sametime Advanced Server (optional) ● An existing LDAP Server (we use AD in this example) Our reasons for this scenario: ● Reduction of boxes used for a complete deployment ● 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.Social Business 15 © 2010 IBM Corporation
  16. 16. IBM Sametime 8.5.2 – our pilot deployment DB2 9.5 Sametime Active Server System Directory Console LDAP ldap.renovations.com Sametime Media Manager sametime.renovations.com Sametime Sametime Community Advanced Sametime Sametime Server Server Meeting Proxy Server Server chat.renovations.com advanced.renovations.com meeting.renovations.com webchat.renovations.comSocial Business 16 © 2010 IBM Corporation
  17. 17. Hardware required for this Pilot Example Deployment ● 1 Server for the IBM DB2 Server, IBM Sametime 8.5.2 System Console, IBM Sametime 8.5.2 Meeting Server, IBM Sametime 8.5.2 Proxy Server, IBM Sametime 8.5.2 Media Manager Quad CPU, 8GB RAM or more, 100GB disk space or more, 64 Bit OS 1 GBit Network Interface with 2 IP addresses and 2 additional DNS Alias entries. ● 1 Server for IBM Sametime 8.5.1 Community Server Single CPU, 2GB RAM or more, 10GB disk space or more, 32 or 64 Bit OS 1 GBit Network Interface ● 1 Server for IBM Sametime 8.5.1 Advanced Server (Optional) Dual CPU, 4GB RAM or more, 20GB disk space or more, 32 or 64 Bit OS 1 Gbit Network Interface ● Various client endpoints With such a configuration you can host up to ● 500 concurrent Meeting Participants * ● 10.000 concurrent Sametime Clients * ● 300 concurrent Media Streams * ● 3000 concurrent Proxy web client users * * Ask you IBM representative for more detailed sizing information in a defined environmentSocial Business 17 © 2010 IBM Corporation
  18. 18. Special IP configuration for the WebSphere based Server As described before you should configure the machine hosting the WebSphere based servers with 2 IP addresses and 3 DNS entries. In this slide deck we use: Host Name: sametime.renovations.com IP: 192.168.30.10 This is the machines Host name. With this name we install the DB2 Server, the Sametime System Console and the Sametime Media Manager DNS Alias: meeting.renovations.com IP: 192.168.30.10 With this address we install the Sametime Meeting Server DNS Alias: webchat.renovations.com IP: 192.168.30.30 With this address we install the Sametime Proxy ServerSocial Business 18 © 2010 IBM Corporation
  19. 19. Required technical users for IBM Sametime 8.5.2 IBM Sametime requires some technical users for components to communicate in an authenticated mode. All of this users should be configured so that the password never expires and never needs to be changed. db2admin This user is created during installation of the DB2 server in the Operating System. Do not create this user in advance. It is the user for all IBM Sametime related components using DB2 to access their databases. Be sure to match the password policy requirements of the OS. wasadmin This is the user to access the IBM WebSphere components and to administer the system. This user must not exist in your LDAP directory. It is created during WebSphere installation in a local file repository. You can use the same user name and password for all components (makes it easier) or different names and passwords. But again, it does not work when this user exists in the LDAP.Social Business 19 © 2010 IBM Corporation
  20. 20. Required technical users for IBM Sametime 8.5.2 (cont) Domino Administrator This user is created during installation of Domino for the IBM Sametime Community Server. It is a best practice to not use a existing administrative account because it is the account with that the IBM Sametime System Console communicates with the Community Server. LDAP Bind User This is a user account in your LDAP directory. This account is used to connect in authenticated mode to the LDAP server to get all required attributes. It is possible to connect anonymously to the LDAP but then it does not work with some LDAP systems or the LDAP server requires special configuration to allow anonymous bind.Social Business 20 © 2010 IBM Corporation
  21. 21. Starting and stopping the WebSphere based Server In this pilot deployment we install and configure all WebSphere based Sametime servers using a single Cell. Then it is easy to administer all of them using just one administrative interface. (The Integrated Solutions Console of the Sametime System Console) With Sametime 8.5.1 the services where created automatically for all servers because we used for all of them a separate “Cell Profile” deployment. Now with IBM Sametime 8.5.2 we use the Network deployment method by implementing all servers as a Primary Node federated to the Deployment Manager of the Sametime System Console in just one Cell. Using this method the installer does not create some required components and it does not create some services in the Windows operating system. We need to manually create this components and Services. All the required steps are described in detail later in this slide deck.Social Business 21 © 2010 IBM Corporation
  22. 22. Audio/Video Plug-In for Browser access to Meeting RoomsThe Meeting Plug-In is shipped with the Media Manager in two formats.1.) Download VersionThis version files needs to be copied onto a Web Server that can beaccessed by the Browser from the client who want to access the Meetingsusing Audio and Video services. This could be the Domino basedSametime Community Server, the Sametime Proxy Server or the SametimeMeeting Server or any other web server in your organization.In this pilot deployment recommendation we use the Sametime Proxyserver for this service.To download and install this Plug-In it is required to have Administrativeaccess rights on Windows 7. With all other OS the user right is enough2.) Deployment VersionThis version can be deployed using your preferred deployment tool. Itcontains a MSI installer file. But be careful in some operating systems asWindows 7, it is required to install this version with administrative rights.Social Business 22 © 2010 IBM Corporation
  23. 23. Agenda ● Components of IBM Sametime 8.5.2 ● Requirements for a IBM Sametime 8.5.2 Deployment ● Architecture of a IBM Sametime 8.5.2 pilot deployment ● The 34 steps to a IBM Sametime 8.5.2 pilot deploymentSocial Business 23 © 2010 IBM Corporation
  24. 24. The 34 steps to deploy a complete Sametime 8.5.2 environment 1.Set up or use an existing LDAP server 2.Install the IBM DB2 server 3.Create the IBM Sametime System Console database 4.Install the IBM Sametime System Console 5.Log in to the IBM Sametime System Console 6.Configure the LDAP server connection Prerequisite 7.Run the guided activity to configure the IBM Sametime Community Server deployment plan 8.Install the IBM Sametime Community Server 9.Enable trust between the IBM Sametime Community Server and the IBM Sametime Proxy Server 10.Run the guided activity to configure the IBM Sametime Proxy Server deployment plan 11.Install the IBM Sametime Proxy Server 12.Configure the Sametime Proxy Server to bind to its webchat .renovations.com address and implement the services in the OS 13.Create the IBM Sametime Meeting Server databaseSocial Business 24 © 2010 IBM Corporation
  25. 25. The 34 steps to deploy a complete Sametime 8.5.2 environment(continued) 14.Configure the DB2 Meeting server database connection Prerequisite 15.Run the guided activity to configure the IBM Sametime Meeting Server deployment plan 16.Install the IBM Sametime Meeting Server 17.Configure the IBM Sametime Meeting Server to bind to its meeting.renovations.com name, create the Meeting HTTP Proxy Service and implement the services in the OS 18.Enable trust between the IBM Sametime Community Server and the IBM Sametime Media Manager 19.Run the guided activity to prepare the IBM Sametime Media Manager deployment plan 20.Install the IBM Sametime Media Manager 21.Configure the IBM Sametime Media Manager Server to bind to its sametime.renovations.com address and implement the services in the OS 22.Configure SSO for Online Awareness in Meeting with Browser accessSocial Business 25 © 2010 IBM Corporation
  26. 26. The 34 steps to deploy a complete Sametime 8.5.2 environment(continued)23.Configure the download of the Browser A/V PlugIn24.Enable trust between the IBM Sametime Community Server and the IBM Sametime Advanced Sever25.Install the Net Search Extension to DB226.Create the IBM Sametime Advanced Server database27.Configure the DB2 Advanced Server database connection Prerequisite28.Run the guided activity to configure the IBM Sametime Advanced Server installation29.Install the IBM Sametime Advanced Server30.Implement the services in the OS for the IBM Sametime Advanced Server31.Install a IBM Sametime Connect client32.Configure the Meeting Plug-In on the IBM Sametime Connect client33.Configure the Sametime Meeting Room in the IBM Sametime Connect Client Meeting Plug-In to use Audio and Video34.Configure the Sametime Connect Client for Sametime AdvancedSocial Business 26 © 2010 IBM Corporation
  27. 27. 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.Social Business 27 © 2010 IBM Corporation
  28. 28. The LDAP Server In most environments a LDAP server is already present. If you use Domino it is simple to just enable LDAP on one of the Domino Directory Servers. If you use an existing LDAP Server other then Domino, it is important to use a V3 compliant LDAP. Make sure you have all relevant data from the LDAP system. (use ldapsearch, Apache LDAP studio or another LDAP browser to get the relevant LDAP information - an LDIF extract of a user and a group) A security related recommendation is to have a Bind DN. This means a user 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. This is a technical user. His password should never expire. Otherwise the systems can not connect to the LDAP server anymore when this password is expired. The LDAP connection can be configured with SSL encryption. To configure your Sametime Servers connecting to LDAP with SSL (LDAPS), additional steps are required. Make sure that you have access to the required certificate. But we recommend to start without SSL and when all components work, start implementing LDAPS.Social Business 28 © 2010 IBM Corporation
  29. 29. 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 Product Documentation for more details.Social Business 29 © 2010 IBM Corporation
  30. 30. An example for the LDAPSEARCH command to an Active Directory and the results:Social Business 30 © 2010 IBM Corporation
  31. 31. STEP TWO: Install the IBM DB2 Server Summary This step installs the IBM DB2 9.7 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 (launchpad.exe) On Windows 2008 the Launchpad installer is not available now. You must use the package CZ1HLML.exe and install the DB2 Server with the setup.exe command in the „C:InstallWSERimage” directory. The installation screens are different then with the Launchpad installer. This package does not contain the Database creation scripts. You need to use the scripts in the particular server packages for the Sametime System Console or the Sametime Meeting Server.Social Business 31 © 2010 IBM Corporation
  32. 32. Enter the command “cd InstallSametimeDB2” and press the “Enter” key. Enter the command “Launchpad” and press the “Enter” key. Do not copy and paste any commands from this document into your CMD line. This does not work because this would copy some special characters.Social Business 32 © 2010 IBM Corporation
  33. 33. Just click the “Install IBM DB2” link.Social Business 33 © 2010 IBM Corporation
  34. 34. And again click the “Install IBM DB2” link.Social Business 34 © 2010 IBM Corporation
  35. 35. The Installation Manager is starting upSocial Business 35 © 2010 IBM Corporation
  36. 36. Click the “Next” button to continue.Social Business 36 © 2010 IBM Corporation
  37. 37. Accept the terms in the license agreement and click the “Next” button to continueSocial Business 37 © 2010 IBM Corporation
  38. 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 applications for path + file name length are avoided.Social Business 38 © 2010 IBM Corporation
  39. 39. Click the “Install” button to install the Installation Manager.Social Business 39 © 2010 IBM Corporation
  40. 40. The installation Manager is now installingSocial Business 40 © 2010 IBM Corporation
  41. 41. If you are using Windows 2008 R2 or Windows 2003 R2 then it can be possible that you run into a JAVA heap memory overflow. To prevent this issue change a parameter in The “IBMIM.INI” configuration file of the Sametime Install Manager. See the next 2 slides how to do this. And then click the „Restart Installation Manager“ button to continue.Social Business 41 © 2010 IBM Corporation
  42. 42. In the File Explorer navigate to your Install Managers eclipse directory “C:IBMInstall Managereclipse”. Then open the configuration file “IBMIM.ini” in notepad.Social Business 42 © 2010 IBM Corporation
  43. 43. Add he parameter “-Xmx1024m” at the end. Then save and close the file. This parameter is case sensitive. Now click the “Restart Installation Manager” button in your Install Manager screen to continue your Installation.Social Business 43 © 2010 IBM Corporation
  44. 44. Installation Manager is re-launching. Now click the „Install“ icon to continue.Social Business 44 © 2010 IBM Corporation
  45. 45. Select „DB2 – Version 9.7.0.0“ and click the „Next“ button to continue.Social Business 45 © 2010 IBM Corporation
  46. 46. Accept the terms in the license agreement and click the “Next” button to continue.Social Business 46 © 2010 IBM Corporation
  47. 47. 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 applications for path + file name length are avoided.Social Business 47 © 2010 IBM Corporation
  48. 48. Again remove “Program Files” and click the “Next” button to continue.Social Business 48 © 2010 IBM Corporation
  49. 49. Click the “Next” button to continue.Social Business 49 © 2010 IBM Corporation
  50. 50. 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.Social Business 50 © 2010 IBM Corporation
  51. 51. Click the “Install” button to install the DB2 ServerSocial Business 51 © 2010 IBM Corporation
  52. 52. The Installation Manager installs the IBM DB2 Server now. This step takes approximately 10 to 15 minutes.Social Business 52 © 2010 IBM Corporation
  53. 53. 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“ The 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.Social Business 53 © 2010 IBM Corporation
  54. 54. When the installation has finished successfully, click the „Finish“ button and then close the Installation Manager and the Launchpad.Social Business 54 © 2010 IBM Corporation
  55. 55. 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.7 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. Open a new CMD line window because then the newly set environment variables during the DB2 Server installation are in place. If you use Windows 2008 then log out and log in with the “db 2 a dm in ” user first.Social Business 55 © 2010 IBM Corporation
  56. 56. Enter the command “cd installSametimeDB2DatabaseScriptsSystemConsole”. Do not copy and paste any commands from this document into your CMD line. This does not work because this would copy some special characters.Social Business 56 © 2010 IBM Corporation
  57. 57. Enter the command “createSCDb.bat STSC db2admin”. 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“.Social Business 57 © 2010 IBM Corporation
  58. 58. The DB2 database is now created and confgured. Be sure that you see „The SQL command completed successfully.“ response after every command. If you dont 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.Social Business 58 © 2010 IBM Corporation
  59. 59. STEP FOUR: Install the IBM Sametime System Console Server Summary This step installs the Sametime System Console Server.Social Business 59 © 2010 IBM Corporation
  60. 60. Navigate to the „InstallSametimeSystemConsole“ directory and enter the command „Launchpad“Social Business 60 © 2010 IBM Corporation
  61. 61. The Sametime 8.5.2 Launchpad opens. Click the „Install IBM Lotus Sametime System Console“ link on the left side.Social Business 61 © 2010 IBM Corporation
  62. 62. Now click the link „Launch IBM Lotus Sametime System Console 8.5.2 Installation“Social Business 62 © 2010 IBM Corporation
  63. 63. The Installation Manager is now loading.Social Business 63 © 2010 IBM Corporation
  64. 64. Click the „Install“ icon to start the installation.Social Business 64 © 2010 IBM Corporation
  65. 65. Select „IBM Sametime System Console server“ and „Version 8.5.2“. Then click the „Next“ button to continue.Social Business 65 © 2010 IBM Corporation
  66. 66. Accept the terms in the license agreement and click the „Next“ button to continue.Social Business 66 © 2010 IBM Corporation
  67. 67. 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.Social Business 67 © 2010 IBM Corporation
  68. 68. Click the „Next“ button to continue.Social Business 68 © 2010 IBM Corporation
  69. 69. With IBM Sametime 8.5.2 it is possible to install Sametime on top of an existing Websphere 7.0.0.15 Server. We dont want to do this in this pilot deployment. Just click “Next” to continue.Social Business 69 © 2010 IBM Corporation
  70. 70. 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.Social Business 70 © 2010 IBM Corporation
  71. 71. Enter the host name of your DB2 server and the DB2 Administrator password. In this example we have installed the DB2 server on the „sametime.renovations.com“ server. Then click the „Validate“ button to continue.Social Business 71 © 2010 IBM Corporation
  72. 72. 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.Social Business 72 © 2010 IBM Corporation
  73. 73. Click the „Install“ button to install the Sametime System Console Server.Social Business 73 © 2010 IBM Corporation
  74. 74. The Installation Manager now installs the Sametime System Console. This step can take approximately 30 to 45 Minutes.Social Business 74 © 2010 IBM Corporation
  75. 75. 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!Social Business 75 © 2010 IBM Corporation
  76. 76. The Installer first unpacks the WebSphere Application Server install files Then he installs the WebSphere Application Server 7.0.0.3 binaries Then he creates the WebSphere profiles Then he installs the Update Installer Then he installs the Update to WebSphere 7.0.0.15 Then he install the application and configures everythingSocial Business 76 © 2010 IBM Corporation
  77. 77. In this directory is the log file where the installer logs its progress. The file increases up to approximately 302 KBytes. Director on Windows 2008: C:UsersAll UsersIBMInstallation Managerlogsant The last step is to configure the services and some post install tasks.Social Business 77 © 2010 IBM Corporation
  78. 78. The Sametime System Console server has installed successfully. Click the „Finish“ button and close the Installation Manager and the Launchpad.Social Business 78 © 2010 IBM Corporation
  79. 79. 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 Mozilla Firefox.Social Business 79 © 2010 IBM Corporation
  80. 80. Enter the URL „http://sametime.renovations.com:8700/admin“. Then click the “Add Exception” button. 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://sametime.renovations.com:8701/ibm/console“.Social Business 80 © 2010 IBM Corporation
  81. 81. The IBM signed certificate is not trusted by the browser. Click the „Get Certificate“ button to accept the certificate by clicking the “Confirm Security Exception Button”. (this dialog is different using other browsers)Social Business 81 © 2010 IBM Corporation
  82. 82. Enter the WebSphere Application Server Administrative User name and its password. We use „wasadmin“. Then click the „Log in“ button to continue.Social Business 82 © 2010 IBM Corporation
  83. 83. You have now reached the IBM Lotus Sametime System Console. Next step is to configure the LDAP connectivity.Social Business 83 © 2010 IBM Corporation
  84. 84. 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.Social Business 84 © 2010 IBM Corporation
  85. 85. Click the „S a m e t im e S y s te m C o n s o le “ link. Now click the „Sametime Prerequisites“ link. Next click the „Connect to LDAP Servers“ link.Social Business 85 © 2010 IBM Corporation
  86. 86. 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.Social Business 86 © 2010 IBM Corporation
  87. 87. To connect to an LDAP server click the „Add“ button to continue.Social Business 87 © 2010 IBM Corporation
  88. 88. Configure the LDAP connectivityinformation on this screen.- The Deployment Name can be anythingdescribing this LDAP connection.- The Host name should be the FullQualified Host name. The Port dependson the LDAP.- An MS AD LDAP Server normally usesthe Port 3268. Other LDAP Systems usethe Port 389.- Do not use the secure connectionunless you have imported the certificatefrom the LDAP server.- The Bind Distinguished Name shouldbe the full qualified Distinguished Name(DN) of the Bind user.Click the „Next“ button to continue.Social Business 88 © 2010 IBM Corporation
  89. 89. The system now connects to the LDAP server, authenticates and requests the LDAP parameters. It detects the possible Base DNs 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.Social Business 89 © 2010 IBM Corporation
  90. 90. For your information: 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.Social Business 90 © 2010 IBM Corporation
  91. 91. 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.Social Business 91 © 2010 IBM Corporation
  92. 92. 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.Social Business 92 © 2010 IBM Corporation
  93. 93. Click the „Next“ button to continue.Social Business 93 © 2010 IBM Corporation
  94. 94. Click the „Finish“ button to save the settings and configure the LDAP connection in the Symetime System Console Server.Social Business 94 © 2010 IBM Corporation
  95. 95. 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.Social Business 95 © 2010 IBM Corporation
  96. 96. 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.Social Business 96 © 2010 IBM Corporation
  97. 97. 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.Social Business 97 © 2010 IBM Corporation
  98. 98. 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.2 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.Social Business 98 © 2010 IBM Corporation
  99. 99. STEP SEVEN: Run the Guided Activity to configure the IBM Sametime Community Server deployment plan 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.Social Business 99 © 2010 IBM Corporation
  100. 100. Some slides with our best practices installing a Domino Server hosting a Sametime Community Server.Social Business 100 © 2010 IBM Corporation
  101. 101. Social Business 101 © 2010 IBM Corporation
  102. 102. Social Business 102 © 2010 IBM Corporation
  103. 103. Social Business 103 © 2010 IBM Corporation
  104. 104. Social Business 104 © 2010 IBM Corporation
  105. 105. Social Business 105 © 2010 IBM Corporation
  106. 106. Social Business 106 © 2010 IBM Corporation
  107. 107. Be sure that the full qualified host name is listed in both fields (see below). If not, just edit the field.Social Business 107 © 2010 IBM Corporation
  108. 108. 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 dont 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.Social Business 108 © 2010 IBM Corporation
  109. 109. Be sure that your Domino Server is up and running and the HTTP Task is started.Social Business 109 © 2010 IBM Corporation
  110. 110. 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“. Then click the „S a m e tim e S y s te m C o n s o le “ link.Social Business 110 © 2010 IBM Corporation
  111. 111. Confirm that „Create a New Deployment Plan“ is checked and click the „Next“ button.Social Business 111 © 2010 IBM Corporation
  112. 112. 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.Social Business 112 © 2010 IBM Corporation
  113. 113. We want to install the Product Version 8.5.2. Leave it as it is and just click the „Next“ button.Social Business 113 © 2010 IBM Corporation
  114. 114. 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.Social Business 114 © 2010 IBM Corporation
  115. 115. 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.Social Business 115 © 2010 IBM Corporation
  116. 116. 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.Social Business 116 © 2010 IBM Corporation
  117. 117. 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.Social Business 117 © 2010 IBM Corporation
  118. 118. Confirm all settings and then click the „Finish“ button.Social Business 118 © 2010 IBM Corporation
  119. 119. You have now successfully created a deployment plan for your Sametime Community Server. The next step is to install the Sametime Community Server.Social Business 119 © 2010 IBM Corporation
  120. 120. STEP EIGHT: Install the IBM 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.Social Business 120 © 2010 IBM Corporation
  121. 121. Enter the „quit“ command in the Lotus Domino Console and wait until the console disappears.Social Business 121 © 2010 IBM Corporation
  122. 122. 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“Social Business 122 © 2010 IBM Corporation
  123. 123. 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.Social Business 123 © 2010 IBM Corporation
  124. 124. The Installer is starting upSocial Business 124 © 2010 IBM Corporation
  125. 125. Click the „Next“ button to continue.Social Business 125 © 2010 IBM Corporation
  126. 126. Accept the terms in the license agreement anc click the „Next“ button.Social Business 126 © 2010 IBM Corporation
  127. 127. The Installer is checking whether the Domino ID has a password.Social Business 127 © 2010 IBM Corporation
  128. 128. 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.Social Business 128 © 2010 IBM Corporation
  129. 129. Enter the Host name of the Sametime System Console. In this example we use „sametime.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.Social Business 129 © 2010 IBM Corporation
  130. 130. Select the Deployment plan that you have created for your Community Server. We use the „Chat Server“ plan. Then click the „Next“ button.Social Business 130 © 2010 IBM Corporation
  131. 131. Crosscheck that all settings are correct. Then click the „Install“ button.Social Business 131 © 2010 IBM Corporation
  132. 132. 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.Social Business 132 © 2010 IBM Corporation
  133. 133. 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.Social Business 133 © 2010 IBM Corporation
  134. 134. Important to know... The Sametime 8.5.2 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.Social Business 134 © 2010 IBM Corporation
  135. 135. When the installation was successfully click the „Finish“ button.Social Business 135 © 2010 IBM Corporation
  136. 136. 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.Social Business 136 © 2010 IBM Corporation
  137. 137. 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.Social Business 137 © 2010 IBM Corporation
  138. 138. STEP NINE: Enable Trust between the Sametime Community Server, the Sametime Proxy Server, the Media Manager and the Sametime Advanced Summary Server In this step you configure the Sametime Community Server to trust the Sametime proxy Server. 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 IPs field in the configuration database. Other Servers you need to trust can be Blackberry Servers, the Sametime Gateway, Sametime Media Manager, Sametime Advanced Server, SUT Server, WebSphere Portal Server or other servers who want to connect using the VP Server protocoll.Social Business 138 © 2010 IBM Corporation
  139. 139. 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“.Social Business 139 © 2010 IBM Corporation
  140. 140. 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)Social Business 140 © 2010 IBM Corporation
  141. 141. The Sametime Community Server configuration screen appears. Go to the bottom of the screen to find the „Trusted Servers“ Setting.Social Business 141 © 2010 IBM Corporation
  142. 142. 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“ for the Sametime proxy Server and then click the “Add” Button. Now we add the IP “192.168.30.40” for the Sametime Advanced Server and then click the “Add” Button.Social Business 142 © 2010 IBM Corporation
  143. 143. Last is to add the IP “192.168.30.10” for the Sametime Media Manager Server andthen click the “Add” Button. We have now added all required IP addresses for this pilot deployment. Now click “OK” to continue.Social Business 143 © 2010 IBM Corporation
  144. 144. 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. Stop your Domino Server using the “Quit” command or by stopping the “Lotus Domino Service”. Wait until all ST... Tasks disappeared in your TaskManager. Then restart the Domino Server again. It takes up to 5 Minutes until the Sametime Community Server is completely restarted and all 41 Sametime tasks are again active.Social Business 144 © 2010 IBM Corporation
  145. 145. STEP TEN: Run the guided activity to configure the IBM 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“.Social Business 145 © 2010 IBM Corporation
  146. 146. Confirm that „Create a New Deployment Plan“ is checked and click the „Next“ button.Social Business 146 © 2010 IBM Corporation
  147. 147. 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.Social Business 147 © 2010 IBM Corporation
  148. 148. We want to install the actual version 8.5.2. just click the „Next“ button to continue.Social Business 148 © 2010 IBM Corporation
  149. 149. The default setting is „Primary Node“ that we use this example. If you plan to implement the Sametime Proxy Server in a standalone environment, then select „Cell“. Note that it is not possible to implement a Cell Profile and a Network Deployment on the same box. Click „Next“ to continue.Social Business 149 © 2010 IBM Corporation
  150. 150. A “Primary Node” can be federated to an existing Deployment Manager. Wewant to federate our environment to the Deployment Manager of our SametimeSystem Console. Select the “Systemconsole...”.Click „Next“ to continue.Social Business 150 © 2010 IBM Corporation
  151. 151. Enter the full qualified host name of your proxy server. In this example we use „webchat.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.Social Business 151 © 2010 IBM Corporation
  152. 152. 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. (Dont forget to enable trust on the other servers as well) In this example we just select the „Chat Server“. Then click „Next“ to continue.Social Business 152 © 2010 IBM Corporation
  153. 153. Control your settings and if all is correct click the „Finish“ button to save the new deployment plan.Social Business 153 © 2010 IBM Corporation
  154. 154. We have now successfully created our Sametime Proxy Server deployment plan.Social Business 154 © 2010 IBM Corporation
  155. 155. STEP ELEVEN: Install the IBM 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.Social Business 155 © 2010 IBM Corporation
  156. 156. 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“Social Business 156 © 2010 IBM Corporation
  157. 157. The Sametime Proxy Launchpad Installer is loading. Click the link „Install IBM Lotus Sametime Proxy Server“Social Business 157 © 2010 IBM Corporation
  158. 158. Now click the link „Launch IBM Lotus Sametime proxy Server 8.5.2 Installation“Social Business 158 © 2010 IBM Corporation
  159. 159. The IBM Installation Manager is loading.Social Business 159 © 2010 IBM Corporation
  160. 160. To Install the Sametime Proxy Server click the „Install“ icon.Social Business 160 © 2010 IBM Corporation
  161. 161. Check the „IBM Sametime Proxy server“ and „Version 8.5.2“ entries. They are unchecked by default. Then click the „Next“ button.Social Business 161 © 2010 IBM Corporation
  162. 162. Accept the terms in the license agreement and click the „Next“ button.Social Business 162 © 2010 IBM Corporation
  163. 163. Click the „Next“ button.Social Business 163 © 2010 IBM Corporation
  164. 164. We want to use the predefined Deployment Plan from the Sametime System console. Just click the „Next“ button to continue.Social Business 164 © 2010 IBM Corporation
  165. 165. With IBM Sametime 8.5.2 it is possible to install Sametime on top of an existing Websphere 7.0.0.15 Server. We dont want to do this in this pilot deployment. Just click “Next” to continue.Social Business 165 © 2010 IBM Corporation
  166. 166. Enter the Sametime System Console Server information and credentials to authenticate. In our example we use „sametime.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 „webchat.renovations.com“. Then click the „Validate“ button to check the connection to the System Console Server.Social Business 166 © 2010 IBM Corporation
  167. 167. The connection to the Sametime System Console was successful when the button text „Validate“ changes to „Validated“. Click the „Next“ button to continue.Social Business 167 © 2010 IBM Corporation
  168. 168. 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.Social Business 168 © 2010 IBM Corporation
  169. 169. Control your settings again and then click the „Next“ button to continue.Social Business 169 © 2010 IBM Corporation
  170. 170. Start the installation by clicking the „Install“ button.Social Business 170 © 2010 IBM Corporation
  171. 171. 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.Social Business 171 © 2010 IBM Corporation
  172. 172. The Sametime Proxy Server Installer creates the WebSphere Profiles. Then it installs the Sametime Proxy application and configures everything.Social Business 172 © 2010 IBM Corporation
  173. 173. 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.Social Business 173 © 2010 IBM Corporation
  174. 174. When the Sametime Proxy Server has installed successfully just click the „Finish“ button and exit the Installation Manager and Launchpad.Social Business 174 © 2010 IBM Corporation
  175. 175. 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://webchat.renovations.com:9081“.Social Business 175 © 2010 IBM Corporation
  176. 176. You are now redirected to “http://webchat.renovations.com:9081/stwebclient/index.jsp” Now click the „Launch Sametime“ button.Social Business 176 © 2010 IBM Corporation
  177. 177. 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.Social Business 177 © 2010 IBM Corporation
  178. 178. STEP TWELVE: Post Install Tasks for the IBM Sametime Proxy Server Summary This step configures the Sametime Proxy Server to start up automatically when the OS is restarted and to bin to its own IP „192.168.30.30“and Hostname „webchat.renovations.com“.Social Business 178 © 2010 IBM Corporation
  179. 179. After the installation only the Sametime Proxy Server Service is created. To create the service for the nodeagent we first need the path to the ProxyServer profile. Use the File explorer and navigate to the right directory. In our example it is “C:IBMWebSphereAppServerprofileswebchatSTPPNProfile1”. Mark the address and copy it to the clip board with Ctrl-C.Social Business 179 © 2010 IBM Corporation
  180. 180. Now open a CMD-Line window and navigate to the WebSphere Application Server binaries Directory. In our Pilot this is “C:IBMWebSphereAppServerbin”.Social Business 180 © 2010 IBM Corporation
  181. 181. Now you need to enter a long command to create the service. For the path copy the path from the clipboard. wasservice -add STProxyServer_NA -serverName nodeagent -profilePath C:IBMWebSphereAppServerprofileswebchatSTPPNProfile1 -stopArgs “-username wasservice -password passw0rd” -encodeParams Check that the service was created successfully. If something is wrong use the “wasservice -remove” command to remove your wrongly created service. Do not copy and paste any commands from this document into your CMD line. This does not work because this would copy some special characters.Social Business 181 © 2010 IBM Corporation
  182. 182. Now we need to configure the dependencies. The nodeagent needs to be started first – before the Sametime Proxy Server. For that we need the exact name of the service. Open the Services view and then open the properties window of the Sametime Proxy Server service. Take the Service Name from here.Social Business 182 © 2010 IBM Corporation
  183. 183. Go back to your CMD-Line window, and enter the command: Sc config “IBMWAS70Service – STProxyServer” depend= “IBMWAS70Service – STProxyServer_NA” Check that the change in the service configuration was successfull. Do not copy and paste any commands from this document into your CMD line. This does not work because this would copy some special characters.Social Business 183 © 2010 IBM Corporation
  184. 184. If you now check the Dependencies of your Sametime proxy Server, then you see that it depends on the Sametime Proxy Server nodeagent.Social Business 184 © 2010 IBM Corporation
  185. 185. We have the Deployment Manager of the Cell and the Proxy Server on the same box, so we can configure another dependency. Go back to your CMD-Line window and enter the command: Sc config “IBMWAS70Service – STProxyServer_NA” depend= “IBMWAS70Service – STConsoleServer_DM” Do not copy and paste any commands from this document into your CMD line. This does not work because this would copy some special characters.Social Business 185 © 2010 IBM Corporation
  186. 186. Now we have configured the nodeagent of our proxy server to be only started when the DMGR of your Cell is started.Social Business 186 © 2010 IBM Corporation
  187. 187. Now we need to configure the Sametime Proxy Server to listen on its own IP address and host name only. This needs to be done in the Integrated Solutions Console. We need to create a Virtual Hosts configuration first. Click on “Environment” and then on “Virtual Hosts”Social Business 187 © 2010 IBM Corporation
  188. 188. Now we want to add our own virtual hosts configuration by clicking the “New” button.Social Business 188 © 2010 IBM Corporation
  189. 189. Enter a name for the new virtual hosts configuration. We use “STProxy_host”. Then click the “OK” button.Social Business 189 © 2010 IBM Corporation
  190. 190. Now we open our new created virtual hosts configuration.Social Business 190 © 2010 IBM Corporation
  191. 191. We click the “Host aliases” link on the right side.Social Business 191 © 2010 IBM Corporation
  192. 192. Now we want to bind our ports to the host name. So we click the “New” button to create a new alias.Social Business 192 © 2010 IBM Corporation
  193. 193. Now we enter the hostname “webchat.renovations.com” and the Port “9081”. Then we clickthe “OK” button.Social Business 193 © 2010 IBM Corporation
  194. 194. We need another Host alias configuration so we click just again the “New” buttonSocial Business 194 © 2010 IBM Corporation
  195. 195. Then we enter again “webchat.renovations.com” and the Port “9444”.Now we click the “OK” Button.Social Business 195 © 2010 IBM Corporation
  196. 196. We need another Host alias configuration so we click just again the “New” buttonSocial Business 196 © 2010 IBM Corporation
  197. 197. Then we enter again “webchat.renovations.com” and the Port “80”.Now we click the “OK” Button.Social Business 197 © 2010 IBM Corporation
  198. 198. We need another Host alias configuration so we click just again the “New” buttonSocial Business 198 © 2010 IBM Corporation
  199. 199. Then we enter again “webchat.renovations.com” and the Port “443”.Now we click the “OK” Button.Social Business 199 © 2010 IBM Corporation
  200. 200. Now it is time to save the configuration changes. Just click the “Save” link in the top.Social Business 200 © 2010 IBM Corporation
  201. 201. Next step is to configure the Sametime Proxy application to use the newly creates STProxy_host definition. Click on “Applications” - “Application Types” - “WebSphere enterprise applications”Social Business 201 © 2010 IBM Corporation
  202. 202. Click the “SametimeProxy” Server application.Social Business 202 © 2010 IBM Corporation
  203. 203. Click the “virtual_hosts” link on the right side.Social Business 203 © 2010 IBM Corporation
  204. 204. In all application modules select our newly created “STProxy_host” definition and then click the “OK” button.Social Business 204 © 2010 IBM Corporation
  205. 205. Now we should save this configuration change by clicking the “Save” link in the top of the screen.Social Business 205 © 2010 IBM Corporation
  206. 206. Now we need to bind the Ports in the Sametime Proxy Server to the hostname webchat.renovations.com. For this click on “Servers” - “Server Types” - “WebSphere application servers”.Social Business 206 © 2010 IBM Corporation
  207. 207. Click the “STProxyServer” server.Social Business 207 © 2010 IBM Corporation
  208. 208. On the right side a little down, you find the “Ports” link. Just click this link now.Social Business 208 © 2010 IBM Corporation
  209. 209. We want to change the “WC_defaulthost” setting first. So click this link.Social Business 209 © 2010 IBM Corporation
  210. 210. Enter “webchat.renovations.com” in the “Host” field and click the “OK” button.Social Business 210 © 2010 IBM Corporation
  211. 211. Then click the “WC_defaulthost_secure” link.Social Business 211 © 2010 IBM Corporation
  212. 212. Enter “webchat.renovations.com” in the “Host” field and click the “OK” button.Social Business 212 © 2010 IBM Corporation
  213. 213. Now it is time to save the last changes. Click the “Save” link here.Social Business 213 © 2010 IBM Corporation
  214. 214. We need to restart the Sametime Proxy Server for the changes can take effect. Easiest way is to set all services to “Automatic” and restart the operating system. Then wait until all services have started. Check in your Task Manager that you can see 5 Java.exe tasks, consuming huge amount of memory, running.Social Business 214 © 2010 IBM Corporation
  215. 215. STEP THIRTEEN: Create the IBM Sametime Meeting Server database Summary In this step you create the second DB2 Database that is required for the Sametime Meeting Server.Social Business 215 © 2010 IBM Corporation

×