Sametime 9 Meetings deployment Open Mic July 23rd 2014

Transcription

1 Sametime 9 Meetings deployment Open Mic July 23rd 2014 Tony Payne Senior Software Engineer - Sametime Ginni Saini Software Engineer Sametime Support Joshua Edwards Software Engineer Sametime Support IBM Collaboration Solutions

2 Agenda Getting Started Planning Installing Clustering Tuning Extending to the extranet Meetings Recordings Q&A 2

3 Getting Started PreRequisites Sametime System Console DB (included with SSC) If upgrading from x, can use existing DB2 or upgrade LDAP 1 Available host for standalone, 2-3 hosts for clustering Hostnames in DNS Software Needed Sametime Meetings 9.0 Latest 3

4 Getting Started The IBM Sametime Meeting Server runs on WebSphere Application Server. It requires an IBM DB2 database and an LDAP server. The Meeting Server provides a central meeting place for members of the community. When combined with the Sametime Media Manager, meeting rooms can be enhanced with audio-visual features. Before installing the IBM Sametime Meeting Server on AIX, Linux, Solaris, or Windows create a database to store its data. Run the scripts that come with the Sametime Meeting Server package - also included with Sametime in the DB2 installation package. 4

5 Getting Started Base Meeting Server The Base Meeting Server role provides meeting rooms with optional audio and video. A meeting room is a virtual construct that is loaded on demand. You can have personal URLs to meeting rooms. Data used in a meeting (for example, the documents loaded into the meeting and the document library), is stored in a DB2 database. Users can have multiple meeting rooms because each room is created on demand. For example, a project manager may have a meeting room for the people he manages, another meeting room for the project team, and a third meeting room for external clients. Content in meeting room libraries can be used for specific meeting rooms or audiences. Think of on-demand meeting rooms instead of scheduled meetings. All client connections (except audio and video) use HTTP so that proxy servers are navigated more easily. You can install a Base Meeting Server on IBM AIX, IBM i, Linux, and Microsoft Windows. Chat and awareness within a meeting room is provided by the Sametime Community Server. Use Sametime policies to determine which the features will be available in meetings (for example, allowing people to record meetings for later playback, white board tools, and polltaking during the meeting). 5

6 Getting Started Document Conversion Server Recording Capturer Server The Document Conversion Server transforms files stored in the Meeting Room Library for optimal display. You can install the Document Conversion Server on IBM AIX, IBM i, Microsoft Windows, and all Linux servers except for those running on IBM System z. For information about the quality of document conversion by operating system, see the topic Installing the Document Converter Server on AIX, Linux, or Windows. To improve performance, you can deploy an additional Meeting Server and configure it with only this role. Typically, Meeting Servers that run on Microsoft Windows do not require conversion services because documents and presentations display clearly without any intervention. A Recording Capturer Server hosts the real-time recording of online meetings. If you want to enable recorded meetings, then at least one Meeting Server must be configured with this role. In small deployments, the Recording Capturer Server is typically installed on the same server as the Base Meeting Server. In large deployments, the best practice is to install the Recording Capturer on a dedicated server. You can install a Capturer Server on IBM AIX, Linux or Windows. Recording Renderer Server A Recording Renderer Server opens files stored by the Capturer Server, transforms them into movie files, and stores the files so that users can download and view them. You can only install a Renderer Server on Windows. If the Renderer Server shares a computer with any other Meeting Server configuration roles, then the computer must be running Windows. 6

7 Getting Started High Availability How you cluster the Meeting Server depends on the configuration roles you deploy: Base Meeting Server plus any other roles on a single computer: Base Meeting And Conversion Server only: This is considered a pilot deployment useful for small organizations, and cannot be clustered. You can only deploy this topology on Windows because that is the only operating system supported by the Capturer Server. You can deploy multiple servers using the Base Meeting Server role, and then cluster them using WebSphere ND to provide high availability and failover. Capturer and Renderer roles: In an enterprise environment you should deploy each of these roles onto a separate server. These roles cannot be clustered using WebSphere Network Deployment. To provide high availability and failover, you can deploy multiple servers with a particular role, and then deploy a load balancer in front of the servers to distribute workload. You can only deploy these server farms do this with servers that host the same configuration role, and each computer in the server farm can only host a single role. 7

8 A Simple Websphere CELL 8

9 Sametime Meeting Server - Clustering Configuring a cluster of IBM Sametime Meeting Servers involves several tasks configuring the cluster settings configuring an IBM WebSphere proxy server for the cluster optionally deploying an IBM Load Balancer in front of the cluster. Two types of clusters: synchronizing system clocks Vertical cluster - consists of multiple application servers running on each physical node of the cell Horizontal cluster - includes a Primary node plus one or more Secondary nodes, all running the same application. Each node contains one cluster member. Note: Create the cluster of servers first then configure the cluster then start the DM and all node agents and application servers in the cluster. 9

10 Clustering Concepts Typically you cluster servers for Application management High availability, fail over and scalability Both Vertical and Horizontal clustering is supported As soon as you cluster Sametime Meeting Servers, a WAS HTTP Proxy is required Can host a WAS proxy server on any node in the cluster (except the SSC) but due to system resources, you may want to host it on its own computer. Never cluster the WAS HTTP Proxies! Code on the proxy determines what node the room is being attended on If you have multiple, you must configure a loadbalancer to front end them Clustering across the WAN is not supported Clustering is not required to take advantage of a WAS HTTP Proxy 10

11 How a WAS Proxy Determines Routing Important to understand when using a WAS Proxy to jump a firewall The DCS_UNICAST_ADDRESS is the primary channel When DCS reports a server is up the WAS Proxy adds it to the pool When DCS reports a server is down the WAS Proxy removes it from the pool If there are no available servers to route the URI a 503 is returned to the client Remember while you may only be using a WAS HTTP Proxy for a given service, it is still aware of the entire cell When using a WAS Proxy the end user connect to the following ports Using distinct virtual hosts are key to insure that routing is correctly done. PROXY_HTTP_ADDRESS PROXY_HTTPS_ADDRESS And the WAS Proxy then routes the request to the appropriate back end server(s) WebContainer ports A WAS proxy can be on the same node as other application servers 11

12 What is a Virtual Host? Simply put - a virtual host ties an application's 'context root' (URI) to host:port combination(s) By default - we use the "default_host" - this primarily uses * for the hostname(s) (match any) When we create distinct Virtual hosts - we can be very specific. 'meetings.company.com' is in the "stmeeting_host" 'stproxy.company.com' is in the "stproxy_host" Both applications are assigned to their own virtual hosts IF the WAS HTTP Proxy ip address has 2 DNS aliases - 'meetings.company.com' and 'stproxy.company.com' when the WAS HTTP Proxy gets a request for ' it knows to correctly route it to one of the nodes that has the Sametime Meetings application and not to any other node that also has a 'root (/)' context If we only had the default_host and * - it would not know how to distinguish the request Remember - even if you have a WAS HTTP Proxy on a node that only listens for "Sametime Meeting" addresses, the WAS HTTP Proxy is a "cell" level item and it still knows about and can route to the other nodes in the cell if there is another context root that matches 12

13 A WAS Cluster (HTTP) for Meetings 13

14 Planning Create STMS database on db2 Know your LDAP server! LDAP server hostname Port : SSL or non-ssl Required to have the "mail" attribute assigned to each user - must be a unique string Jumping a firewall to allow external access? Integrating Sametime Proxy for awareness and WebAV? Must have its own unique hostname Create the following deployment plans DB2 Guided Activity for STMS database LDAP Guided Activity Primary Node plan for STMeetings Atleast 1 Secondary Node plan for STMeetings As stated before the WAS HTTP Proxy can be run on one of the nodes For optimum performance, create a 2nd SN plan that is for the WAS HTTP Proxy 14

15 Installing Install one node at a time Upgrade directly to latest IFR 1 release Once installation is complete, then cluster To create a standalone WAS HTTP Proxy If installing a standalone node for the WAS HTTP Proxy, do not 'cluster' this node lookupname=administering+sametime+standard interim+feature+release+1+d ocumentation#action=opendocument&res_title=optional_adding_a_standalone_webs phere_proxy_server_to_the_cluster_st852ifr1&content=pdcontent If Adding a WAS HTTP Proxy to an existing node lookupname=administering+sametime+standard interim+feature+release+1+d ocumentation#action=opendocument&res_title=configuring_a_websphere_proxy_ser ver_st852ifr1&content=pdcontent 15

16 Installing Sametime Meeting server Guided Activity 16

17 Guided Activity Contd... 17

18 Guided Activity Contd... 18

19 Guided Activity Contd... 19

20 Guided Activity Contd... 20

21 Sametime Meeting Server Verify Install Log in to the server - try creating a new meeting room. From a web browser, navigate to the Meeting Room Center using URL: To verify the port number being used by the application, log in to the console of the Deployment Manager and enter the following URL: is the default port when the Meeting Server is installed as a Cell Profile is the default port when the Meeting Server is installed as a PN and federated to the SSC Click Servers -> WebSphere application servers -> STMeetingServer -> ports -> WC_defaulthost to find the port number. 21

22 Sametime Meeting Server Verify Install Can also verify the HTTP port number used by the Meeting Server using AboutThisProfile.txt file - use the setting specified for the HTTP transport port. The default profile name is short_host_namestmpnprofile1 when you use a deployment plan to install the server. Using meeting server URL -click Log In, enter user name and password to log in to the Meeting Center. Click New Meeting Room, then fill in the fields - click Save. The new meeting appears in the list of meetings that you own. Click Enter Meeting Room below the name of the new meeting to join the meeting. 22

23 Sametime Meeting Server Room Administration Assigning administrators to the Meeting Room Center This allows for administrators to access details about the meeting rooms themselves. 23

24 Sametime Meeting Server Document Conversion Sametime Meeting Server lets you take files of various formats - e.g. slides, images, and documents and converts them so they can be shared in a meeting room as slides. Meeting Server uses the file system on the server to store and convert documents and presentations to slides. There are certain required steps to configure the server for document conversion technology Note: There are no special configuration steps for using document conversion technology on Windows servers 24

25 Cluster WebSphere Application Servers 25

26 Click Next to begin the clustering activity 26

27 Select Product to Cluster Select the product server to cluster, and then click Next. The list only displays Sametime products for which one or more servers have been installed and registered with SSC. 27

28 Select or create a Cluster To create a cluster: Click Create Cluster if you are setting up a new cluster. Type a descriptive name for the cluster in the Cluster Name field. For example, if you are creating a cluster of Sametime Meeting Servers, you will probably want to indicate that in the cluster name so you can easily identify it later. Click Next To modify an existing cluster; for example, to add a new cluster member: Click Select Existing Cluster. Select a cluster in the Cluster Name list. If you are going to add a node or cluster member to the cluster, you must use the same Sametime product. e.g, you cannot add a Sametime Meeting Server cluster member to a cluster of Sametime Proxy Servers. Click Next 28

29 Select or create a Cluster 29

30 Select the Deployment Manager In the Select Deployment Manager list, select the SSC as the cluster's deployment manager, and click Next. Every cluster must have exactly one Deployment Manager; the SSC can function as the Deployment Manager for multiple clusters. 30

31 Create the Cluster with the Primary Node You created and federated a primary node when you installed the first server for this product. Make sure that the Primary Node's application server is running. Click Create cluster to configure the cluster settings, and then click Next 31

32 Select One or More Secondary Nodes If you are creating a horizontal cluster where each node is hosted on a separate computer, add one or more secondary nodes to the cluster. You created and federated the secondary nodes when you installed them. In the Secondary Node Name list, click the node you want to add to the cluster and click Next. 32

33 Add Cluster Members If you are creating a vertical cluster where multiple copies of the application are hosted on a single computer, add one or more "cluster members" to the Primary Node. If you are creating a horizontal cluster, add one cluster member to each of the secondary nodes you federated in the previous step. The table lists Cluster Members, the Node that the cluster resides on, and the Status of each cluster member. Each node in the cluster needs to have at least one cluster member created on it for the node to be used in the cluster. The status of a Cluster Member will be "Clustered" if the cluster member has been completely configured on the node. If the status is "Ready to Cluster", select the Cluster Member and use the "Add to Cluster" button to finish configuring the cluster member. 33

34 Add Cluster Members Vertical cluster: To add new cluster member, click New. Select the default name generated for the cluster member or enter your own cluster member server name. Select the Primary Node to create the cluster member on. Click Add to Cluster The status will change from "Ready to cluster" to "Clustered". If you want to add more Vertical cluster members, click New to add another row to the table, and then fill out the information accordingly. Click Next. 34

35 Add Cluster Members Horizontal cluster: For each Secondary Node you added a cluster member is pre-populated into the table for you, one on each of the Secondary Nodes. Select the default cluster member name for each server or update with your own name One at a time, select each cluster member and click Add to Cluster. Do not proceed until the current cluster member's status changes from "Ready to cluster" to "Clustered"; then you can add the next cluster member. Click Next. 35

36 Add Cluster Members 36

37 Deployment Summary Click Finish to save the cluster configuration. Complete the cluster's configuration by performing the following tasks: 1. Synchronizing and restarting nodes in the cluster 2. Restarting the application servers in the cluster 37

38 Clustering lookupname=administering+sametime+standard interim+feature+release+1+docume ntation#action=opendocument&res_title=clustering_sametime_meeting_servers_st852ifr1&co ntent=pdcontent 38

39 Tuning For larger deployments, follow the tuning guide These settings help to optimize the environment for 'maximum capacity' by tuning the JVM heap, Garbage Collection and caching capabilities Be sure to understand the document and your environment fully before implementing the guidelines 39

40 Meetings Recordings Capturer and Renderer 40

41 Meeting Recording There are 4 parts to meeting Recordings. General Capture Audio Capture Render Rest API Application In order for recordings to function there must be at least 1 capture server and 1 render server(windows only). 41

42 Bullet 1 Page 12 heading Bullet Capture Mapping Deployment Plan to Configuration Capture Server URL Recording.capture.serverAddress URL of the Meeting Server that is configured with the Basic Meeting Server role recording.capture.meetingserverad Used by the capture server to dress connect to meeting via SDK. Directory where Capture files will be stored recording.capture.rootpath Base path for writing capture files. UNC path with forward slashes if remote. ex. //fileserver.mycompany.com/capture User ID for Capture Server to record meetings recording.capture.user and JAAS Auth Data Alias strecordings Recordings user. strecbot Password for Capture Server JAAS Auth Data Alias strecordings Used by the recording REST api to connect to a SPECIFIC capture server to start/stop recordings. Recordings user password. 42

43 Capture Settings Defined Capture Server URL Need a deployment plan per capture server. The setting will never contain the value of a load balancer or Websphere proxy fronting the meeting server. This setting will be a specific application server running the capture role. Ex. meetingserver.mycompany.com:

44 Capture Settings Defined URL of the Meeting Server that is configured with the Basic Meeting Server role URL that tells the capturer server where it needs to go for meetings. What does this mean? For a single meeting server the setting would need the host and port of the Websphere server running the meeting or the Websphere proxy fronting the meeting if one is in use. Ex. meetingserver.mycompany.com:9080 For a cluster this setting would need to be the Websphere proxy fronting the cluster or a load balancer fronting the Websphere proxies in the event you have multiple Websphere proxies. Ex. meetingproxy.mycompany.com or meetinglb.mycompany.com An easy way to remember this is that the setting would contain the same path that a client goes through to connect to the meeting server. 44

45 Capture Settings Defined Directory where Capture files will be stored Tells the capturer where to write the meeting Stream files. It is okay to use a drive letter if the capture will occur locally. If using multiple capture servers or if the capture and render servers are split that directory can be directed to a shared network resource using a unc path with java friendly forward slashes. ex. //fileserver.mycompany.com/capture *Note: Our installer and post install does not provision any of the volumes specified for recording or renders so the administrator will need to provision these resources and then simply configure the server to point to the correct locations. 45

46 Capture Settings Defined User ID for Capture Server to record meetings strecbot Password for Capture Server The password itself is not exposed in the actual configuration. 46

47 Page 2 heading Bullet 1 Bullet 2 *Note if these values need to be modified after deployment the settings must be manually modified in the file stavrecorder-config.xml. Additionally, the turn settings are only needed if there is a firewall between the capture server and the Video MCU. 47

48 STAV Recorder Settings Defined Hostname for the local audio capture application. This host name must be resolvable and routable from the SIP Proxy/Registrar As you might have guessed this host name must be resolvable and routable from the SIP Proxy/Registrar or cluster. It is specific to the node where the av recorder is running on. Ex.<configuration name="recorderserverhost" value="meetingserver.mycompany.com"/> 48

49 STAV Recorder Settings Defined Port on which the local audio recorder application listens for SIP invitations Similar to hostname field this port must be available to the SIP Proxy/Registrar or cluster. It is specific to the node where the av recorder is running on. If using tls be sure and use the secure tls port. Ex. <configuration name="recorderserverport" value="5061"/> 49

50 STAV Recorder Settings Defined Audio Recorder IP with outbound connectivity to TURN/MCU If a firewall exists between the capture and Video MCU then this setting must be used. In order to install the meeting server properly this setting is required. After an install if the setting is not needed as is the case when the capturer can connect to the Video MCU directly, it may be removed from stavrecorder-config.xml after the install is complete. In a multiple nic scenario this needs to be the nic that resolves the setting Hostname for the local audio capture application in the configuration. Note: It is not always necessary to use this setting even if a turn server exists. Ex. <configuration name="preferredoutboundip" value=""/> 50

51 STAV Recorder Settings Defined SIP Proxy Registrar and Turn Settings These settings are going to be the same hostnames, ports, and transport that your client will use to connect with the environment. It is specific to the node where the av recorder is running on. Ex. <configuration name="proxyserverhost" value="spr.mycompany.com"/> <configuration name="proxyserverport" value="5081"/> <configuration name="siptransportprotocol" value="tls"/> In our scenario since we will not need to make use of the turn server the settings will not be populated. Ex. <configuration name="turnserverudphost" value=""/> <configuration name="turnserverudpport" value=""/> <configuration name="turnservertcphost" value=""/> <configuration name="turnservertcpport" value=""/> 51

52 Directory where Render files will be stored recording.render.rootpath Base path for writing capture files. UNC path with forward slashes if remote. //fileserver.mycompany.com/render Horizontal resolution in output recording.render.renderwidth movie files Horizontal resolution Vertial resolution in output movie files recording.render.renderheight Vertical resolution Number of days that recordings are valid for download recording.daystolive Expiration timeframe expressed in days. Number of days until expired recordings are deleted recording.filesystem.gracedays Grace period for users before the file is removed from the storage. Number of simultaneous renders allowed per cpu core recording.render.schedulingpolicy CoreMultiplier Used to control render scheduling for the server. 52

53 STAV Render Settings Defined Directory where Render files will be stored Location of where rendered files will be located. Similar to Recordings Directory if the path needs to be a shared drive use a unc path with java forward slashes rather than drive letter paths. Ex. //fileserver.mycompany.com/render 53

54 Recording Configuration Settings In a cluster scenario the following two parameters will be set to false for any of the base cluster members. If the Capture and Render are combined for a farm then both should be set to true. Example of a combined Capture and Render Server 54

55 Linux Document Conversion Make the following changes on the Sametime Meeting Server that you installed with the Document Conversion configuration role. 1) If you have legally licensed true-type fonts available, copy them to /opt/ibm/websphere/stmeetingsserver/stellent/fonts. Make sure that the extensions for the fonts are lowercase (*.ttf) and each font has the correct permission level (755). 2) Set the following environment variables. The WebSphere path might be different in your deployment. PATH=$PATH:/opt/IBM/WebSphere/STMeetingsServer/stellent export PATH LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/IBM/WebSphere/STMeetingsServer/stellent export LD_LIBRARY_PATH GDFONTPATH=/opt/IBM/WebSphere/STMeetingsServer/stellent/fonts export GDFONTPATH Note: The LD_LIBRARY_PATH variable can be overwritten by other scripts. If you are able to convert image files and not other documents (.txt,.doc,.ppt, etc.), then this might be the cause. Type 'set' in a terminal to see if this variable is still set and has the correct value. Note: The GDFONTPATH variable must not contain a ':' in the beginning. The only value that should be set here is the path to the fonts. Do not append anything before or after. 55

56 Linux Document Conversion Recommended steps for a successful setup. Run the servers as root. Set the environment variables in the actual meeting start script itself. Ex.startServer.sh #!/bin/sh PATH=$PATH:/opt/IBM/WebSphere/STMeetingsServer/stellent export PATH LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/IBM/WebSphere/STMeetingsServer/stellent export LD_LIBRARY_PATH GDFONTPATH=/opt/IBM/WebSphere/STMeetingsServer/stellent/fonts export GDFONTPATH bindir=`dirname ${0}` ${bindir}/setupcmdline.sh ${WAS_HOME}/bin/startServer.sh "$@" One final consideration is that since we require the render server to be on Windows and need Windows desktop experience if an admin wishes to deploy everything on one box for meetings then they will need to setup the meeting server on a Windows machine rather than linux. 56

57 Extending Sametime Meetings 57

58 Why should we extend our communications to the outside? Add awareness and chat capabilites to external partners and in applications Hold internal meetings with remote employees Hold external meetings with external partners Extend AV capabilities beyond the firewall Add Mobile Access Real-time social communications virtually wherever you are working. Online presence indicators and enterprise instant messaging on Apple ios, Google Android, Research In Motion BlackBerry, Nokia Symbian and Microsoft Windows Mobile handheld devices Business cards with contact information Instant messaging for one-on-one conversations and group messaging Intuitive user interface that manages multiple active chat sessions on small screens. Chat history Use browser-based meetings on your Apple ipad or Android tablet to join Sametime meeting rooms directly from URLs in the calendar or messaging application 58

59 Mobile Access Sametime Meetings Sametime mobile meetings with browser and app options. create new meeting rooms or search for meeting rooms by room or owner name control a presentation as well as use annotation and zoom tools. Android Client Or participate in Sametime online meetings from your Apple ipad, Android-based tablet or BlackBerry smartphone. IOS Client Use browser-based meetings on your Apple ipad or Android tablet to join Sametime meeting rooms directly from URLs in the calendar or messaging application Note: Requires IFR 1 to be installed 59

60 Extending Meeting Services 3 Scenarios Fully Separated Internal and external Meetings Allowing external access to internal Meetings All of the above! Security Concerns to be aware of DB2 Access required LDAP access required SSL Highly recommended in all scenarios If you're going to allow external access to internal meetings, you will want to consider Authentication Meeting Passwords Document Upload restrictions Remember, Browser users cannot remote control a shared screen. 60

61 Fully Separated Internal and external Meetings Deploy as a standalone cell Will include its own deployment manager and ISC for local WAS administration No communication with the internal Sametime cell from a Websphere perspective Communication with the Sametime System Console is Over HTTP for administration of Sametime Meeting features (from SSC) Over HTTP for Install and Upgrades (to SSC) When Planning the deployment in the SSC Choose the cell option Ports to open from the DMZ to internal network 9080/9443 to the Sametime System Console for installation and registration 389/636 to LDAP 50000/50001 to DB2 for Meeting Data storage Use a separate database for external meetings Ports to open to the Sametime Meeting Server from the Internet 9080/9443 for Web traffic (configurable) 80/443 if you choose to deploy a WAS HTTP Proxy 61

62 Fully Separated Internal and external Meetings 62

63 Allowing external access to internal Meetings Deploy a Websphere HTTP Proxy to the DMZ Will use the Sametime System console for WAS administration Will be part of the internal Sametime cell from a Websphere perspective Communication with the Sametime System Console is After installation, the Application Server will be removed and you will create a WAS HTTP Proxy on that node Ports to open from the DMZ to internal network 9080/9443/8701/8703 to the Sametime System Console for installation and registration 389/636 to LDAP (required) Websphere Key Ports - defined later in the presentation Web Container ports to the internal Meeting Server Nodes Ports to open to the Sametime Meeting Server from the Internet The proxy will route HTTP traffic to the internal Meeting nodes over the Web Container ports When Planning the deployment in the SSC Choose the SN option Over HTTP for Install and Upgrades (to SSC) 80/443 Don't forget about access to Sametime Proxy in this scenario! 63

64 Allowing external access to internal Meetings 64

65 Press *1 on your telephone to ask a question. Visit our Support Technical Exchange page or our Facebook page for details on future events. To help shape the future of IBM software, take this quality survey and share your opinion of IBM software used within your organization: IBM Collaboration Solutions Support page IBM Collaboration Services Support 65