Get Started Installing IBM Lotus Sametime You Too Can Be a WAS Admin! OR 140 Slides In 60 Minutes

Transcription

1 Get Started Installing IBM Lotus Sametime You Too Can Be a WAS Admin! OR 140 Slides In 60 Minutes Gabriella Davis Technical Director The Turtle Partnership

2 About Me Gabriella Davis The Turtle Partnership Technical Director Security, System Design, Deployment of Lotus software since 1989 This is the only accent I ve got. If you are the person who was having everything I said translated yesterday, I apologise in advance. 2

3 Lets get the legalise out of the way This slide presentation may contain the following copyrighted, trademarked, and/or restricted terms: IBM Lotus Sametime, IBM Lotus Websphere, IBM Lotus Domino, IBM Lotus Notes, IBM Lotus Symphony, LotusScript, IBM DB2 Microsoft Windows, Microsoft Excel, Microsoft Office Linux, Java, Adobe Acrobat, Adobe Flash 3

4 Agenda Sametime Components Questions You Should Be Asking A Little Bit About Websphere for Some Of You What Do You Need To Know Pre-Installation Checklist Installing A Pilot Post-Installation Questions 4

5 Sametime 8.5 Components 5

6 Sametime Community Server Instant Messaging Component Contains the old style Classic Meeting Center Based on Domino 8.5.(1) Does not require any WAS Can still be clustered for IM Can integrate with earlier ST IM servers Works with existing products ST Advanced ST Gateway 6

7 Sametime Community Server Few feature changes Can now be managed by the Sametime System Console within WAS if you have the 8.5.x Infrastructure Policy settings and server settings options are the same on the Sametime System Console and via stconfig.nsf If set via WAS they are only refreshed when the server starts or every 60 mins because they are cached in Domino 7

8 Sametime Community Server Infrastructure 8

9 Sametime Systems Console Manages all the other servers in the Sametime 8.5.x environment including the Domino Community Server Installed under WAS 7.0 Has a plugin menu to the WAS Integrated Solutions Console for Sametime 8.5 specific tasks Must be running for the other WAS servers to work 3 WAS Profiles dmgr (deployment manager) nodeagent STConsoleServer 9

10 Sametime System Console Infrastructure 10

11 Sametime System Console Connecting DB2 and LDAP Installation steps Management of servers Sametime shelf for SSC 11

12 Sametime Meeting Server Installed under WAS 7.0 Uses a DB2 database for handling meetings A meeting must take place on a single server Must use a different dedicated DB2 database than that used for Sametime System Console but can use the same DB2 server Meeting Server can be on a separate box from the System Console Integrates with the Domino IM server to allow instant meetings 3 WAS Profiles dmgr (deployment manager) nodeagent STMeetingServer STMeetingHttpProxy 12

13 Sametime Meeting Server Infrastructure Default URL 13

14 Sametime Meeting Server Meetings are immediate and persistent Meetings can be hidden and password protected Create Report Participants Library Chat Fast conversion, sharing and download Categorised by type View just Minutes or just Questions Record Application Sharing 14

15 Sametime Meeting Server Plugin / Client vs Browser Limited features in Browser no recording no audio / video no remote control / application sharing Install meeting room plugin with ST Connect for all features Installable for 8.5 Connect Client or upgraded Embedded client 15

16 Sametime Proxy Server Installed under WAS 7.0 Interface between browser and ST Community Server in Domino Provides no download / ajax IM client via a browser Customisable using stylesheets Limited functionality compared for ST client or embedded client Managed by the Sametime System Console 3 WAS Profiles dmgr (deployment manager) nodeagent STProxyServer 16

17 Sametime Proxy Server Default URL jsp 17

18 Sametime Media Server WAS 7.0 Intended for multi way audio and video in meetings Integrates with a Meeting Server but isn t installed with it Managed by the Sametime System Console The root cause of the NAT traversal issues 18

19 Embedded Client The current plugin for Sametime with the 8.5 client is based on Sametime A client side update is available along with a plugin to support and The client update includes the ability to start and go to meetings from within the Calendar 19

20 Mobile Clients Sametime Mobile 8.5 Unified Communication and Collaboration (UCC) New ST client based on Expeditor Windows mobile 6.0 and 6.1 initially IPhone browser support Blackberry Storm and Bold support (9250, 9550, 9700) 20

21 What s Missing In Sametime 8.5.x Clustering for Meetings / Failover and Load Balancing Scheduling of Meetings Currently A/V via NAT or via VMware (and via some VPNs) 21

22 Questions You Should Be Asking 22

23 So Should You Deploy Sametime 8.5.1? You already have Sametime No reason not to upgrade to Check that existing plugin solutions you are using will continue to work For a SMB or limited use meeting/av deployment all the WAS components and DB2 can install onto a single server (4+ processors, 6+GB RAM) Ideally we would keep the meetings and media servers on separate hardware from the other components to allow for expanding demand for resources Virtual Servers are your friend My default choice for any WAS based software 23

24 Can You Migrate In Stages? Co-existence of classic style meeting center supports existing meetings Domino is maintained for IM so offers coexistence with older versions of Sametime Available upgrade to the embedded Sametime in the Notes client (which is currently based on ST 8.0.2) Available upgrade to mail template to create meetings in new Meeting Center (instead of on Domino) 24

25 What About Getting Rid Of Domino Completely? IM is remaining on Domino as it performs well, clusters easily and there is little perceived value in re-engineering it 25

26 A Little Bit About Websphere For Some Of You 26

27 Websphere Infrastructure Environment for running multiple application servers which can be completely isolated from each other Requires separate data store (in this case DB2) Requires separate SMTP (if your application uses it) LDAP (if you want to use a directory) Sametime System Console is 3 separate server instances as is the Media Manager as is the Proxy Server the Meeting Server is 4 separate server instances (so that s 13 server instances in total on one box for those that are counting!) You can install separate components on separate boxes such as the Meeting Server but you will need to install an ISC alongside 27

28 Websphere 7.0 First Lotus product to use WAS 7.0 Sametime Advanced, Gateway and EMS all used different 6.x versions WAS can cluster and can centrally manage server configurations but only if versions match Lotus products are very specific about which WAS versions they need 28

29 DB2 Data Store DB2 server installs as part of the Sametime System Console process Creation of the required DB2 databases is done via batch files in a DB2 command window You will need a basic understanding of DB2, the command window and administration to be able to fully support your environment understanding how to backup / restore / drop and delete databases Don t try and manage the security for the Sametime applications via the DB2 interface only via the Sametime Systems Console 29

30 LDAP Integration The Sametime Environment under Websphere needs an LDAP server to connect to this should be the same directory as used by the Domino IM server You can use multiple LDAP servers in Websphere configured as Federated Repositories Each repository much use a unique set of credentials In our demo environment the Domino IM server is configured for LDAP and the Websphere servers point to that as an LDAP source 30

31 What Do You Need To Know? 31

32 What Do You Need To Know: Websphere How to access to solutions console via a browser and login How to access other servers (and find out which ports they are on) via a browser Understanding of networking such as checking for listening ports How to update Websphere configuration and take backups of properties files How to find logs How to start and stop servers Adding additional administrators 32

33 What Do You Need To Know: DB2 How to work with DB2 tools such as command line and administration DB2 concepts such as the catalog and why you need to drop a database before deleting it How to verify if databases exist on a server 33

34 What Do You Need To Know: LDAP What is a schema How you need to pass a query to your LDAP server How to perform an ldap browse independently for testing Softerra s LDAPBrowser is a good free tool The difference between your LDAP directory and the Websphere local repository 34

35 Pre-Installation 35

36 Decisions Prior to Installing What components to install Do you want to allow IM access for non ST clients Limited Use Meeting Server Media Server Platform Handling Coexistence and Migration How many servers / how much potential growth Only Meeting and Proxy servers can be clustered 36

37 Cells and Nodes - A Brief Detour Each Websphere Server is installed in a Node Each Node must exist within a Cell A single Cell can contain multiple separate WAS servers in different Nodes Each server is isolated from the other within the Cell Clustering is done at a Node level within a Cell Clustering for Sametime 8.5 is not for load balancing but for failover 37

38 Deployment Manager and Profiles The deployment manager within a Cell contains the configuration for all nodes in that cell Also responsible for Websphere authentication and security Uses each server s nodeagent to update the Node Each Node takes its configuration from its deployment manager and stores it in its profile If you change the cell configuration you have to reload the deployment manager If you cluster then the deployment manager in the cell services all nodes in the cluster regardless of where they are located 38

39 Node Agents Starts and stops each server If the server is a deployed cluster node it doesn t have its own Node agent Synchronizes between deployment manager and the server 39

40 Servers The server is a java process performing a function / application Proxy Server Meeting Server Meeting HTTP Proxy Sametime System Console Every server runs on its own discrete port None of them run on port 80 or 443, you need a proxy for that 40

41 Network Deployment Servers can be deployed via Network Deployment whereby a central Websphere server handles the configuration of multiple nodes and distributes them to different hardware This is only useful is all your nodes are using the same version of Websphere This can t be used for managing the infrastructure of several Lotus products as each currently uses a different version of Websphere 41

42 In Other Words Have some idea of your future direction and potential growth before you start Build a single server cluster if you think you might want to cluster in the future Don t install everything on one box unless you are happy to reinstall later 42

43 Getting your ducks in a row DNS, DNS, DNS Make sure every server you are going to install on can ping its own FQHN and that of all other servers LDAP source and LDAP credentials Test using LDAPBrowser WAS credentials to be used during install DB2 location 43

44 LDAPBrowser An ldapbrowser (eg this one from Softerra) allows you to verify LDAP credentials and connectivity 44

45 Installing A Pilot (single server) 45

46 Installing - Step 1. DB2 Starting with DB2 IBM Installation Manager will briefly install itself first to manage this and other installs if it s not already in place Sametime System Console download contains CreateSCDB program login using db2 account you just created default db name is STSC but can be anything you choose it will automatically be federated into the Sametime Console the db2 account that is created will be local to the installer server a local account MUST meet password complexity defined by the server or the Domain Controller The installer will fail with status=87 when it tries to create the account otherwise Once installed DB2 will be on port Use the General Administration tool in Windows to verify the database STSC is created 46

47 Installing - Step 1. DB2 47

48 Installing - Step 1. DB2 48

49 Installing - Step 1. DB2 Don t install under \program files\ - you want as short an install path as possible. I use drive:\ibm 49

50 Installing - Step 1. DB2 Click Install 50

51 Installing - Step 1. DB2 51

52 Installing - Step 1. DB2 52

53 Installing - Step 1. DB2 Again - don t use \program files\ to install under 53

54 Installing - Step 1. DB2 Since this is the first server installed on this machine, we use a new Package Group 54

55 Installing - Step 1. DB2 This is a new local account being created. The password MUST conform to your local security policy - but it won t warn you if it doesn t. The install will just fail. If in doubt, try creating a test local account with the same password you want to use. 55

56 Installing - Step 1. DB2 The install may take some time (I ve seen it take 2hrs on slower machines). Don t be tempted to press cancel. Monitor the available disk space. If you run out the install will just fail and you may have to rollback 56

57 Installing - Step 1. DB2 Run CreateSCDB from its extracted directory in a command prompt CreateSCDB STSC This may take several minutes during which you will have a blank screen before the commands start running. The Screenshot here shows a successful completion of the process 57

58 Testing Ensure DB2 is running and listening on port In DB2 administration - verify that the STSC database is created 58

59 Installing - Step 2. SSC Run launchpad from within Sametime System Console extracted files Once SSC is installed login and verify the ISC has the correct menus login using was creds created during SSC install We re going to step through these System Pre- Reqs as the next stages of the install 59

60 Installing - Step 2. SSC 60

61 Installing - Step 2. SSC Our existing package group is for DB2 so this is our first WAS package group and we create a new one for the SSC 61

62 Installing - Step 2. SSC 62

63 Installing - Step 2. SSC The installer will create Node and Cell names based on the computer name baltic Your computer name shouldn t be more than 8 chars FQHN has to resolve. Use a local host entry if necessary These are your admin credentials for the SSC you are about to create. You ll type these A LOT 63

64 Installing - Step 2. SSC Here we verify the DB2 is installed, listening and has the required DB2 database in place The Validate button becomes Validated when you click it if all is OK 64

65 Installing - Step 2. SSC 65

66 Testing Login to SSC on Verify Sametime System Console menu is present 66

67 Installing - Step 3. Configuring LDAP Guided task under SSC Will validate the LDAP credentials in real time Requires a base_dn If you are using Domino you probably won t have one a blank base_dn will be set in the background as c=us and ignored for Domino LDAP sources Federated under WAS security You can add additional LDAP sources there too Used by ALL components Make sure all servers are using the same LDAP source 67

68 Installing - Step 3. Configuring LDAP Test all of this in an external LDAPBrowser from the installation machine before starting 68

69 Installing - Step 3. Configuring LDAP If using Domino the search base is empty during install usually 69

70 Installing - Step 3. Configuring LDAP Once installed you should see the LDAP profile listed 70

71 Installing - Step 3. Configuring LDAP Post installation, you can modify the LDAP settings here by configuring the Federated repository that was created in the background 71

72 Testing From within SSC Security - Users and Groups - Manage Users Search your LDAP directory 72

73 Installing - Step 4. Community Server Community Server under Domino can be installed via the SSC or standalone If installed via the SSC, the Domino administration interface for ST isn t used The SSC needs to be given Domino credentials with Sametime admin rights You can also tell the SSC about multiplexors So your Sametime IM infrastructure needn t change 73

74 Installing - Step 4. Community Server 74

75 Installing - Step 4. Community Server 75

76 Installing - Step 4. Community Server 76

77 Installing - Step 4. Community Server 77

78 Installing - Step 4. Community Server When you click Next it will attempt to access the Domino server using the credentials you have listed here. If it fails, try accessing the Domino server yourself using these credentials and a browser 78

79 Installing - Step 4. Community Server 79

80 Installing - Step 4. Community Server Which LDAP server do you want Domino to use. Note using the Domino Directory instead of LDAP isn t an option with SSC Deployment 80

81 Installing - Step 4. Community Server 81

82 Installing - Step 4. Community Server 82

83 Installing - Step 4. Community Server This is the Domino ST installer we all know. Now however you get an additional prompt to install via the SSC if you want 83

84 Installing - Step 4. Community Server These are our SSC details The SSC must be running at this point 84

85 Installing - Step 4. Community Server This is the deployment plan we just created Installer looks for deployment plans that match this hostname 85

86 Installing - Step 4. Community Server 86

87 Testing Log into Community Server via Sametime IM client If upgrading ensure buddy list is present Verify you presence awareness is working and you can see people online New Presence services replace ST Buddylist service 87

88 Installing - Step 5. Proxy Server Optional Install Not needed for IM Not needed for Meetings Provides a browser based ajax IM client Can be used in place of stlinks as there is no java Can be used against older Sametime IM servers Multiple proxy servers can be used to support large scale deployments of browser IM client or browser based IM features 88

89 Installing - Step 5. Proxy Server 89

90 Installing - Step 5. Proxy Server 90

91 Installing - Step 5. Proxy Server 91

92 Installing - Step 5. Proxy Server 92

93 Installing - Step 5. Proxy Server You would install as a Cell profile if there is already another WAS instance on this server eg. the SSC You would install as a primary Node if you are installing the first Proxy server in a cluster on its own machine 93

94 Installing - Step 5. Proxy Server 94

95 Installing - Step 5. Proxy Server 95

96 Installing - Step 5. Proxy Server 96

97 Installing - Step 5. Proxy Server The SSC package group already exists on this server so we ll use it 97

98 Installing - Step 5. Proxy Server 98

99 Installing - Step 5. Proxy Server 99

100 Installing - Step 5. Proxy Server 100

101 Installing - Step 5. Proxy Server 101

102 Installing - Step 5. Proxy Server You will need to modify the configuration of the Community server in SSC to add the ip address of the Proxy server as a Trusted IP That will require restarting the Community Server 102

103 Testing Log into Community Server via Proxy by browsing to 103

104 Installing - Step 6. Installing Media Manager Optional Install Provides Audio and Video services for meetings Can t be clustered Can be used by multiple meeting servers High CPU NAT Traversal issues currently only works when clients are on same network if you don t have camera and mic on your client, you can t set up a meeting with A/V services 104

105 Installing - Step 6. Installing Media Manager 105

106 Installing - Step 6. Installing Media Manager 106

107 Installing - Step 6. Installing Media Manager In a large scale A/V deployment you may want to distribute the components around your network on multiple machines 107

108 Installing - Step 6. Installing Media Manager 108

109 Installing - Step 6. Installing Media Manager 109

110 Installing - Step 6. Installing Media Manager 110

111 Installing - Step 6. Installing Media Manager 111

112 Installing - Step 6. Installing Media Manager 112

113 Installing - Step 7. Creating Meeting Server Database DB2 Database needed for each meeting server Must use different DB2 db than System Console Script provided with MeetingServer installer files to create the database CreateMeetingDB STMS STMS is the default name, but it can be anything 113

114 Installing - Step 7. Creating Meeting Server Database Run CreateMeetingDB from its extracted directory in a command prompt CreateMeetingDB STMS This may take several minutes during which you will have a blank screen before the commands start running. 114

115 Installing - Step 7. Creating Meeting Server Database Once created you will need to go into the SSC and Connect the new database by adding a new connection 115

116 Installing - Step 8. Installing Meeting Server Multiple meeting servers can be installed Meeting servers can be clustered clustering is failover only all attendees must be on the same server 116

117 Installing - Step 8. Installing Meeting Server 117

118 Installing - Step 8. Installing Meeting Server 118

119 Installing - Step 8. Installing Meeting Server 119

120 Installing - Step 8. Installing Meeting Server You would install as a Cell profile if there is already another WAS instance on this server eg. the SSC or Proxy server You would install as a primary Node if you are installing the first Meeting server in a cluster on its own machine and as Secondary node if this is an additional meeting server 120

121 Installing - Step 8. Installing Meeting Server 121

122 Installing - Step 8. Installing Meeting Server 122

123 Installing - Step 8. Installing Meeting Server 123

124 Installing - Step 8. Installing Meeting Server 124

125 Installing - Step 8. Installing Meeting Server 125

126 Installing - Step 8. Installing Meeting Server 126

127 Installing - Step 8. Installing Meeting Server 127

128 Installing - Step 8. Installing Meeting Server 128

129 Installing - Step 8. Installing Meeting Server 129

130 Installing - Step 8. Installing Meeting Server 130

131 Testing Browse to meeting server on if installed as a cluster node then use port 9080 for testing 131

132 Installing - Step 9 & If you installed the Proxy or Meeting server as a Primary or Secondary Node you won t see them under the SSC - Don t Worry! First you have to create a cluster and join those newly installed servers to it Then you may want to create a proxy service so you can access them on Port 80 The Meeting Server, when installed as a cluster node, does not include the STMeetingHTTPProxy 132

133 Post-Installation 133

134 Policies - IM All policies are managed from the SSC If you modify policies via the Domino interface, these will be overwritten by WAS Changing a policy in WAS will take up to an hour to refresh in Domino 134

135 Policies - Meeting Server Meeting server settings are managed from within the SSC The Meeting server settings in Domino do not apply to the new WAS meeting server but the WAS policies include a section for the Classic meeting server 135

136 Policies - Meeting Server Create multiple polices, assigned to users to control who can use which features Ability to create persistent meetings Ability to create instant meetings Application sharing File sharing etc 136

137 Policies - Media Manager 137

138 Questions? Gabriella Davis Skype: GabriellaDavis 138

139 Legal Disclaimer IBM Corporation 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. 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. 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. 139