IBM Lotus Sametime Media Manager Cluster Deployment Walk-through Part VI- Bandwidth Manager IBM Corporation

Size: px

Start display at page:

Download "IBM Lotus Sametime Media Manager Cluster Deployment Walk-through Part VI- Bandwidth Manager IBM Corporation"

Felicia Stevenson
6 years ago
Views:

1 IBM Lotus Sametime Media Manager Cluster Deployment Walk-through Part VI- Bandwidth Manager

2 Prerequisites for this part of the walk-through We've completed parts I, II, II, IV, and V Lotus Domino 8.5.x is installed and running LDAP is configured on the Domino server Sametime Community Server 8.5.x is installed and running The WebSphere instance for the SSC is located at WebSphere install root /opt/ibm/websphere/appserver Media Manager is installed and running A DB2 server is installed and running with accessible administrator login credentials (to a DB instance)

3 Create the Database for Bandwidth Manager In this step, you create the database for the Bandwidth Manager in preparation for the install of the BWM server cluster

4 From a command terminal on the machine where DB2 is running (stavm204.raleigh.ibm.com), login as the DB administrator (in this case db2inst1) and launch the DB2 Control Center application. Note you might need to grant permission to this user to run GUI programs with xhost +local:db2inst1 run as root if this is not done automatically at OS boot)

5 Click OK on default selection for the view of Advanced

6 Highlight All Databases, click on Selected on the toolbar and then......click on Create Database > Standard.. on the pulldown.

7 Choose a name for the BWM database (here we pick BWM_DATA) set the default page size to 8K and then click Next

8 Click Next to accept the defaults for storage path

9 Set Code set to UTF-8, Collating Sequence to UCA400_NO, and click Next

10 Review your settings and click Finish to create the database

11 Click Close after the database is created to remove the message pop-up and then close the DB2 Control Center if you desire

12 Create the WebSphere Profiles for the Bandwidth Manager In this step, you create the WebSphere profiles for the Bandwidth Manager server cluster. These profiles is created in a cell that is separate from the SSC and Media Manager cell. This separation of cells for BWM is a restriction for the release. Since they are separate, we need to create a Deployment Manager environment to host the cluster. We do leverage the existing WebSphere binaries that are already installed for the Media Manager on the target machines. First, we create the Deployment manager cell profile on one machine, and then the Primary node profile on the other.

13 On the machine where the Deployment Manager is to be installed, as root open a command terminal, navigate to the /opt/ibm/webspheremm/appserver/bin/profilemanagement directory, and launch the profile management tool, pmt.sh

14 Click Launch Profile Management Tool

15 Click Create

16 Select Management environment, and click Next

17 Select Deployment manager server type, and click Next

18 Select Advanced profile creation, and click Next

19 Check the box to deploy the admin console, and click Next

20 Choose a profile name and matching profile directory (BWMDMgrProfile), and click Next

21 Choose a node name and a cell name, and click Next

22 Choose an administrator name and password, and click Next

23 Keep the default certificate selections, and click Next

24 Choose a keystore password, and click Next

25 Confirm and make note of the port assignments, including the administrative console port of 9060, and click Next

26 Click Next

27 Confirm selections and click Create

28 Click Finish

29 Click Installation verification

30 Verify that the verification tool completes successfully

31 On the machine where the Primary node is to be installed, as root open a command terminal, navigate to the /opt/ibm/webspheremm/appserver/bin/profilemanagement directory, and launch the profile management tool, pmt.sh

32 Click Launch Profile Management Tool

33 Click Create

34 Select Application server environment, and click Next

35 Select Advanced profile creation option, and click Next

36 Deselect the option to deploy the administrative console since we will be federating this profile and node into the Deployment manager we previously created. Also deselect the option to deploy the default application. Click Next

37 Choose a profile name and matching profile directory (BWMAppProfile1), and click Next

38 Choose a node name and server name (we number them 1 since they'll be in a cluster) and click Next

39 Choose an administrator name and password, and click Next

40 Keep the default certificate selections, and click Next

41 Choose a keystore password, and click Next

42 Confirm and make note of the port assignment for the SOAP connector port (8883) and click Next

43 Click Next

44 Click Next

45 Confirm selections and click Create

46 Click Finish

47 Click Installation verification

48 Verify that the verification tool completes successfully

49 Create the Bandwidth Manager Cluster In this step, you create the cluster in WebSphere for the Bandwidth Manager. First we need to federate the node for the BWM server that we created.

50 In a browser, launch the administrative console for the Deployment manager. Note that this is the console associated with the profile we just created, and is NOT the Sametime System Console. We use the administrative port we noted from the profile creation. We use the login credentials we chose when we created the profile.

51 Before creating the actual cluster, we need to add the BWM server node we just created to the BWM cell. In the administrative console, navigate to System administration > Nodes

52 Click Add Node

53 Select Managed node and then click Next

54 Enter the host stavlab23.rtp.raleigh.ibm.com, the SOAP connector port 8883 we noted earlier for the server, the administrator ID and password, and the Deployment manager ID and password. Click OK

55 After the node is federated, click View the available nodes

56 This node stavlab23bwmnode1 will be the primary node for the cluster

57 Now navigate to Clusters > WebSphere application server clusters

58 Click New

59 Choose a name for the new cluster BWMCluster. Check the box to configure HTTP session memory-to-memory replication. Click Next

60 Select the option to create the first cluster member by converting the existing application server BWMServer1. Click Next

61 Choose a name for the second cluster member (BWMServer2) and select the other machine stavlab24.rtp.raleigh.ibm.com to host it. Click Add Member

62 Click Next

63 Click Finish

64 Click Save

65 Now we need to create the WAS Proxy that sits in front of the new cluster. Navigate to Servers > Server Types > WebSphere proxy servers

66 Click New

67 Select the node (stavlab23bwmnode1) that will host the proxy, and choose a name for the proxy, BWMProxy. Click Next

68 Select both HTTP and SIP as supported protocols and make sure the Generate unique ports option is checked. Click Next

69 Make sure the template proxy_server_foundation is selected and click Next

70 Click Finish

71 Click Save

72 Click BWMProxy so we can configure the cluster this proxy applies to

73 Expand SIP Proxy Server Settings and then click SIP proxy settings

74 Select the new cluster BWMCluster as the default cluster, and...

75 ...click Apply

76 Click Save

77 Since we have co-located the BWM cluster and proxy with other SIP components (the Media Manager), we need to resolve port conflicts with those components and also adjust the associated virtual host aliases. Navigate to Servers > Server Types > WebSphere proxy servers

78 Click BWMProxy

79 Click Ports

80 Click PROXY_SIPS_ADDRESS to change the port for secure SIP access

81 Change the port value to an unused one (5069) and click Apply

82 Click Save

83 Click PROXY_SIP_ADDRESS to change the port for unsecured SIP access

84 Change the port value to an unused one (5068) and click Apply

85 Click Save

86 Click Save

87 Now navigate to Servers > Server Types > WebSphere application servers

88 Click BWMServer1

89 Click Ports

90 Click SIP_DEFAULTHOST to change the port for unsecured SIP access

91 Change the port value to an unused one (5070) and click Apply

92 Click Save

93 Click SIP_DEFAULTHOST_SECURE to change the port for secured SIP access

94 Change the port value to an unused one (5071) and click Apply

95 Click Save

96 Now we need to adjust the Virtual host alias settings to match the new ports. Navigate to Environment > Virtual hosts

97 Click default_host

98 Click Host Aliases

99 Click New

100 Add the first of the new ports (5068) and click Apply

101 Click Save

102 Click New

103 Add the next of the new ports (5069) and click Apply

104 Click Save

105 Click New

106 Add the next of the new ports (5070) and click Apply

107 Click Save

108 Click New

109 Add the last of the new ports (5071) and click Apply

110 Click Save

111 To finish these configurations, we need to resynchronize the nodes in the cell for the cluster. Navigate to System administration > Nodes

112 Check the boxes next to the two cluster nodes and click Full Resynchronize

113 Resynchronization is initiated

114 Now we start the cluster. Navigate to Servers > Clusters > WebSphere application server clusters

115 Check the box next to the BWMCluster and then click Start. Click the refresh icon to check to see when the cluster is started.

116 The BWMCluster is started.

117 Finally, we start the proxy for the cluster. Navigate to Servers > Server Types> WebSphere proxy servers

118 Check the box next to the BWMProxy and then click Start.

119 The BWMProxy is started

120 Edit the Bandwidth Manager install property files In this step, you edit the db2.configuration.properties file and the websphere_configuration.properties file to prepare for the installation of Bandwidth Manager. Since an install for a Bandwidth Manager cluster must be performed from the profile where the Deployment manager is installed, we will do this step on the stavlab24.rtp.raleigh.ibm.com machine.

121 On the machine where the Deployment manager is installed, as root open a command terminal and copy the unarchived Bandwidth Manager install image to a temporary directory

122 Navigate to the temporary directory /tmp/bandwidthmanager

123 Edit the db2.connection.properties file and update the connection properties for the DB2 server where we created the BWM_DATA database. Make sure the db2.schema attribute is set to the db2.login value, but in uppercase

124 In the Deployment manager console, navigate to Servers > Server Types > WebSphere application servers

125 Make note of the cell name (stavlab24bwmcell) for the Deployment manager. This value is needed in the subsequent update of the websphere configuration file for the was.cell property

126 In a command terminal, navigate to the following directory: /opt/ibm/webspheremm/appserver/deploytool/itp/plugins and execute the ls command as noted to search for directories starting with com.ibm.datatools.db2_ We make a note of the complete directory name that is found, in this case, com.ibm.datatools.db2_ v _0407. This value is used in the websphere configuration file for the was.db2.driver.path property value

127 Back in the administrative console, navigate to System administration > Deployment manager

128 Click on the Runtime tab, and make note of the node name for the Deployment manager, in this case, stavlab24bwmcellmanager. This value is used in the portlet.node property of the websphere configuration file.

Edit the websphere_configuration.properties file, and update the was.cell, was.home, was.hostname, was.userid, was.password, was.db2.driver.path, was.cluster, proxy.host, proxy.port.http, proxy.port.sip, and portlet.

129 Edit the websphere_configuration.properties file, and update the was.cell, was.home, was.hostname, was.userid, was.password, was.db2.driver.path, was.cluster, proxy.host, proxy.port.http, proxy.port.sip, and portlet.node properties based on the information we previously gathered or selected (note that the was.server, was.node. was.profilename, was.hostport, was.sipport, and was.httpport properties are unused for a cluster install). We remember to uncomment all the cluster properties as well

130 Run the Bandwidth Manager install scripts In this step, you invoke an ant task to run the install scripts for Bandwidth Manager

131 On the machine where the Deployment manager is installed (stavlab24.rtp.raleigh.ibm.com), navigate to the temporary directory where the Bandwidth Manager install image is and also where we edited the properties files. Launch the ws_ant.sh script with the -Dinstall.db=true option to populate the database. Note that it does not matter which instance of the ws_ant.sh script is used as long as it is in the WebSphere home path for the Deployment manager of the Bandwidth Manager.

132 The installation takes between 4-10 minutes. Verify that the script ran successfully.

133 To verify that the install worked, navigate to Applications > Application Types > WebSphere enterprise applications.

134 We verify that there are three Bandwidth Manager applications listed (Do not try to start them yet! There are a few more steps before we start the actual cluster with applications)

135 Set up Secure Administrative Access to the Bandwidth Manager console In this step, we configure settings for securely accessing the Bandwidth Manager console

136 In the Administrative console, navigate to Security > Global security

137 Make sure Use Java 2 security to restrict application access is unchecked. Click Apply

138 Click Save

139 Navigate to Environment > Naming > CORBA Naming service groups

140 Click EVERYONE

141 Shift-Click to select all listed Roles. Click Apply

142 Click Save

143 Verify the EVERYONE group has Cos Naming Write, Delete, Create and Read

144 Navigate to Users and Groups > Manage Users

145 Click Create...

146 Choose a User ID (bwm) First/Last name, and a password for the new Administrative user. Click Create

147 Click Close

148 Navigate to Users and Groups > Administrative user roles

149 Click Add...

150 Click Search

151 Select the new user bwm and click the right-arrow to add it to the Mapped to role list

152 Shift-click all Roles in the Role(s) dialog box and select the user bwm. Click OK

153 Click Save

154 We need to restart the Deployment manager. Navigate to System administration > Deployment manager

155 From the Configuration tab, click Stop

156 Click OK

157 We have stopped the Deployment manager

158 While the Dmgr is stopped, we need to update the LDAP access security setting to enable the Bandwidth Manager to be able to access it. On the machine hosting the Deployment manager, stavlab24.rtp.raleigh.ibm.com, navigate to the WebSphere Identity Manager (WIM) config directory within the Dmgr path and edit the wimconfig.xml

159 Locate the issecurityenabled attribute and change its value to false. Save the file.

160 Navigate to the Dmgr profile bin directory and invoke./startmanager.sh

161 The Deployment manager is started

162 Log back into the Administrative console, but this time, use the new administrative user bwm. Once logged in, resynchronize the cluster nodes as shown earlier (during the cluster creation)

163 We now see a new entry in the left-hand navigation tree. Navigate to Sametime Servers > Bandwidth Manager

164 We see the Status page for the Bandwidth Manager console

165 Configure LDAP Access for Bandwidth Manager In this step, you configure settings to give Bandwidth Manager access to an LDAP directory of users

166 In the console, navigate to Security > Global security

167 Under Available realm definitions, make sure Federated repositories is selected. Click Set as current, and then Configure...

168 Click Add base entry to Realm...

169 Click Add Repository...

170 Choose a name for the new repository (we pick LDAP), select the Directory type (in our case, Lotus Domino), and enter the host name of the LDAP server, stavm204.raleigh.ibm.com. Enter the bind user ID and password and remove any Login properties present. Click Apply

171 Click Save

172 Enter the base entries for our LDAP server (o=aww) and click Apply

173 Click Save

174 Make sure the primary administrative user name is set to the name used to install Bandwidth Manager and click OK

175 Click Save

176 Return to edit the wimconfig.xml file and add a new config:attributes under the config:attributeconfiguration stanza that maps the uid property in the underlying LDAP directory to the WIM mail attribute. Note that this step might not be needed in all environments if the underyling LDAP server schema already has a mail attribute available in the user object class. As shown before, resynchronize the cluster nodes.

177 Now we need to restart the cluster. Navigate to Servers > Clusters > WebSphere application server clusters

178 Check the box next to BWMCluster and click Stop

179 Click the refresh icon to check for complete stoppage

180 Check the box again and click Start.

181 The cluster is re-started

182 Validate the Bandwidth Manager installation In this step, you validate the installation and post-install configuration of the Bandwidth Manager server

183 In the Administrative console (logged in as bwm), navigate back to Sametime Servers > Bandwidth Manager

184 Click Start/Restart

185 Click OK on the pop-up

186 The status of the applications turns to Starting. Click the refresh icon after several seconds

187 The status of the applications is now Active. Notice that the portlet tabs are all now activated. Click the Groups tab

188 Click New

189 Make sure User is selected in the Search by pull-down and enter * in the Search for field. Click Search

190 A list of users is returned in the Search results which verifies we have access to LDAP

191 Hook the Bandwidth Manager into Media Manager In this step, we set up routing from the Bandwidth Manager to the SIP Proxy and vice versa as well as enabling security between the two. First, we configure the Bandwidth Manager to use the SIP Proxy cluster for routing. Second, we set up trust between the two parties. Third, we configure TLS certificates. Finally, we walk through setting up the SIP Proxy routing rules that place the Bandwidth Manager in the path of all SIP dialog requests.

192 In the Administrative console (logged in as bwm), navigate back to Sametime Servers > Bandwidth Manager

193 Click the Configuration tab

194 In the Sip Server URI field, enter the secure SIP URI of the proxy for the SIP Proxy/Registrar, sips:stavlab23.rtp.raleigh.ibm.com:5063;transport=tls. Click Apply, and then click the Status tab

195 Click Start/Restart

196 Click OK

197 Now we set up trust within the SIP Proxy/Registrar to the Bandwidth Manager machine. From the WebSphere console for the SIP Proxy/Registrar, navigate to Servers > Clusters > WebSphere application server clusters

198 Click SPRCluster

199 Expand Cluster members, and then click Details

200 Click STMediaServer (the first cluster member)

201 Expand SIP Container settings, and then click SIP Container

202 Click Custom properties

203 Click com.ibm.ws.sip.security.trusted.iplist

204 Add the host name of the Bandwidth Manager proxy stavlab23.rtp.raleigh.ibm.com (note that this setting is not strictly required since the SIP Proxy and this machine are the same one, but we show this for demonstration purposes since in a more distributed environment, this step is necessary). Click OK

205 Click Save

206 Click Cluster members

207 Click STMediaServerSN (the secondary cluster member)

208 Expand SIP Container settings, and then click SIP Container

209 Click Custom properties

210 Click com.ibm.ws.sip.security.trusted.iplist

211 Add the host name of the Bandwidth Manager proxy stavlab23.rtp.raleigh.ibm.com. Click OK

212 Click Save

213 Now, we set up TLS (SSL) certificates. In the Sametime System Console, navigate to Security > SSL certificate and key management

214 Click Key stores and certificates

215 Click CellDefaultTrustStore

216 Click Signer certificates

217 Click Retrieve from port

218 Enter the host name of the Bandwidth Manager cluster proxy stavlab23.rtp.raleigh.ibm.com, and the secure SIP port Choose an alias (BWM) and click Retrieve signer information

219 Click OK

220 Click Save

221 Now, log into the Bandwidth Manager console, and navigate to Security > SSL certificate and key management

222 Click CellDefaultTrustStore

223 Click Signer certificates

224 Click Retrieve from port

225 Enter the host name of the SIP Proxy/Registrar cluster proxy stavlab23.rtp.raleigh.ibm.com, and the secure SIP port Choose an alias (sip proxy) and click Retrieve signer information

226 Click OK

227 Click Save

228 To finally hook the Bandwidth Manager into the system, we need to configure routing rules in the SIP Proxy. In the Sametime System Console, navigate to Sametime System Console > Sametime Servers > SIP Proxies and Registrars

229 Click SPRCluster

230 Click Proxy Administration

231 Click New to create the first of two rules.

232 Name the first new rule and give it a description. Select Method INVITE and check the box for Contact Header and enter a regular expression that matches the IP address and port of the Conference Manager. Check the box for User defined header and enter Content-Length and 0 as the name and value respectively...

233 ...and for the destination, select SIPS as the scheme, enter the host name of the Bandwidth Manager cluster proxy, and enter the secure port of the proxy. Click OK

234 Click New to create the second rule.

235 Name the second new rule and give it a description. Select Method INVITE and check the box for Contact Header and enter a regular expression that matches the IP address and port of the Conference Manager. Check the box for User defined header and enter Content-type and the regular expression as shown as the name and value respectively...

236 ...and for the destination, select SIPS as the scheme, enter the host name of the Bandwidth Manager cluster proxy, and enter the secure port of the proxy. Click OK

237 Make sure Add public IP to outgoing request is checked. Click OK.

238 Finally, restart the SIP Proxy/Registrar cluster as shown before.

239 Test an end-to-end call In this step, you finally test an Audio/Video call to validate the complete Media Manager and Bandwidth Manager installation

240 Log into the rich client and click Enter Room under the meeting room we used earlier to validate the base Media Manager installation (in Part V of the walk-through).

241 Click the green call icon under Voice and Video and then click Join call with my computer

242 The call is completed

243 In the Bandwidth Manager administrative console, navigate to Sametime Servers > Bandwidth Manager

244 Click the Monitoring tab

245 Note the Internet site now has a call in place and it is reporting 416 Kbps of bandwidth in use. Click Site Calls

246 Click the timestamp associated with the call Start Time

247 Note the call details. Click Ok

Installation and Setup of IBM Sametime From Zero to Hero Part 2 Edge Components

IBM Collaboration Solutions Installation and Setup of IBM Sametime 8.5.2 From Zero to Hero Part 2 Edge Components Frank Altenburg SME for Sametime IBM Collaboration Solutions mailto:frank.altenburg@de.ibm.com