IBM Lotus Sametime Media Manager Cluster Deployment Walk-through Part I Overview and Planning IBM Corporation

Transcription

1 IBM Lotus Sametime Media Manager Cluster Deployment Walk-through Part I Overview and Planning

2 Scope and Overview The purpose of this walk-through is to demonstrate setting up a basic clustered Sametime Media Manager server environment from a bare set of machines to a fully-functional small deployment The walk-through assumes availability of a DB2 Server, Sametime Community, Sametime Meeting Server, and Sametime Proxy that have already been deployed, but for which the installer has administrative access The walk-through assumes only basic familiarity with DB2, WebSphere, and LDAP. However, the follower of these presentations should have a working knowledge of Linux OS, specifically Red Hat Enterprise 5.x. The installer should be familiar conceptually with how the Sametime Media Manager is deployed, but little to no knowledge is required of how to make that deployment happen

3 Cluster Pilot Environment Description Distributed deployment hosting Sametime Community, LDAP Server, DB2 server, Sametime Media Manager, Sametime Proxy Server, Sametime Meeting Server, and Sametime Bandwidth Manager Clustered Media Manager components (Conference Manager, SIP Proxy/Registrar, and Bandwidth Manager) Web A/V Deployment NAT/TURN Deployment Secured inter-server connections within Media Manager Sametime Clients Media Manager Community Server Meeting Server Proxy Server

4 Walkthrough Description The Walkthrough is divided into separate parts each part its own presentation: Part I Overview and Planning (this presentation) Part II SIP Proxy and Registrar installation Part III Conference Manager installation Part IV Packet Switcher installation Part V Call Validation Part VI Bandwidth Manager installation Part VII Web A/V Enablement Part VIII NAT and TURN installation

5 Prerequisites for this walk-through The installer has root access to all machines in the environment The Media Manager installation media is copied to temporary directories on the target machines (part CZYF1ML) Lotus Domino 8.5.x is installed and running LDAP is configured on the Domino server A DB2 9.5 (or later) server is installed and running with accessible administrator login credentials (to a DB instance) Sametime Community Server 8.5.x is installed and running Sametime Meeting Server is installed and running Sametime Proxy Server is installed and running A Sametime System Console (SSC) is installed with accessible administrator login credentials The WebSphere instance for the SSC is located at WebSphere install root /opt/ibm/websphere/appserver The installer's favorite browser on a client that can access the SSC WebSphere console

6 Cluster Pilot Physical Deployment At the end of part VIII, the server environment looks like this (focus components in yellow): stavm204.raleigh.ibm.com ( ) stavlab22.rtp.raleigh.ibm.com ( ) Sametime System Console Lotus Domino Sametime Community Server DB2 9.5 Sametime Meeting Server Sametime Proxy Server Packet Switcher TURN Server stavlab23.rtp.raleigh.ibm.com ( ) stavlab24.rtp.raleigh.ibm.com ( ) SPRCluster WS Proxy (SPR) SIP Proxy/Registrar PN SIP Proxy/Registrar SN WS Proxy (CM) Conference Focus PN CMCluster Conference Focus SN WS Proxy (BWM) BWM server PN BWMCluster BWM server SN

7 Environment Notes Certain steps that would normally be automated in a production environment are shown here manually for clarity (such as starting the applications as OS services) Synchronization of clocks across all nodes in the system is a required step in order to complete the installs. This step is not shown, but is easily done through adjustment of the date/time in the OS. In a production environment, this synchronization would normally be accomplished automatically using a technology such as NTR Certain shortcuts are taken in this pilot walkthrough that would normally not be done in true production such as co-location of proxies or certain Sametime components. These shortcuts were necessary due to machine resource limitations for the environment, and, in some cases, for clarity. However, these do not sacrifice understanding of the process to build out a true production environment, and all implications of such shortcuts are explained We used WebSphere node synchronization and server restarts quite liberally throughout the walkthrough. Although frequent such actions might not be strictly needed, we find this tends to mitigate strange problems during a complex install Now, let's begin!

8 Configure the Clustered Components Deployment Plans In this step, we prepare the Deployment Plans to install the Media Manager components that are to be clustered. In Sametime System Console, we create four different plans for Primary and Secondary nodes for the SIP Proxy/Registrar and the Conference Focus. We will create the plan for the Packet Switcher in a later presentation

9 In the Sametime System Console (SSC), navigate to Sametime System Console > Sametime Guided Activities > Install Sametime Media Manager

10 Click Next to create a new deployment plan

11 Enter a name for the first deployment plan to create the Primary Node instance of the SIP Proxy and Registrar. We choose SIPPR_PN. Click Next

12 Click Next to select the default version of 8.5.2

13 Select Install Proxy/Registrar and click Next

14 Select Primary Node and click Next

15 Select the SSC Deployment Manager in which to federate the node and click Next

16 Enter the host name of the target node stavlab23.rtp.raleigh.ibm.com and choose the primary administrator ID and password to be used for the node WebSphere instance and click Next

17 Check the selections and click Finish

18 The SIP Proxy/Registrar Primary node plan is created. Now click Next to create another plan for the Secondary node.

19 Choose a name for the secondary node (SIPPR_SN) and click Next

20 Click Next to select the default version of 8.5.2

21 Select Install Proxy/Registrar and click Next

22 Choose Secondary Node and click Next

23 Select the SSC Deployment Manager in which to federate the node and click Next

24 Enter the host name of the target node stavlab24.rtp.raleigh.ibm.com and choose the primary administrator ID and password to be used for the node WebSphere instance and click Next. We use wasadmin to be consistent with the rest of the system

25 Check the selections and click Finish

26 The SIP Proxy/Registrar Secondary node plan is created. Now click Next to create another plan for the Conference Manager Primary node.

27 Choose a name for the primary node (CM_PN) and click Next

28 Click Next to select the default version of 8.5.2

29 Select Install Conference Manager and click Next

30 Select Primary Node and click Next

31 Select the SSC Deployment Manager in which to federate the node and click Next

32 Enter the host name of the target node stavlab23.rtp.raleigh.ibm.com and choose the primary administrator ID and password to be used for the node WebSphere instance and click Next

33 Select the deployment plan for the SIP Proxy/Registrar primary node that this Conference Manager should connect to. Click Next

34 Select the Sametime Community Server to connect to. There is only one in our environment, stavm204_community. Click Next

35 Check the selections and click Finish

36 The Conference Manager Primary node plan is created. Now click Next to create another plan for the Conference Manager Secondary node.

37 Enter a name for the deployment plan to create the Secondary Node instance of the Conference Manager. We choose CM_SN. Click Next

38 Click Next to select the default version of 8.5.2

39 Select Install Conference Manager and click Next

40 Choose Secondary Node and click Next

41 Select the SSC Deployment Manager in which to federate the node and click Next

42 Enter the host name of the target node stavlab24.rtp.raleigh.ibm.com and choose the primary administrator ID and password to be used for the node WebSphere instance and click Next

43 Select the deployment plan for the SIP Proxy/Registrar secondary node that this Conference Manager should connect to. Click Next

44 Select the Sametime Community Server to connect to. There is only one in our environment, stavm204_community. Click Next

45 Check the selections and click Finish

46 The four Deployment Plans are now ready to install

47 Set the trusted IP addresses of the Media Manager servers In this step, we configure the Sametime Community server to trust connections from any of the Media Manager servers in our configuration

48 In the SSC, navigate Sametime System Console > Sametime Servers > Sametime Community Servers

49 Select the Deployment identifier for our community server, stavm204_community

50 In the configuration page, scroll to the bottom...

51 ...and add the first new server IP address, for the stavlab22.rtp.raleigh.ibm.com machine

52 Add the second new server IP address, for the stavlab23.rtp.raleigh.ibm.com machine

53 Add the third and last new server IP address, for the stavlab24.rtp.raleigh.ibm.com machine

54 Click OK