Collecting required information and preparing for Bandwidth Manager installation

IBM® Sametime® Bandwidth Manager has its own deployment manager; it is not managed using the Sametime System Console. The Bandwidth Manager is a WebSphere® Application Server-based server. It is the only server in the Sametime server family which is not installed using the IBM Installation Manager or Install Shield based installer. The WebSphere Application Server and the required prerequisites need to be deployed and configured manually according to the instructions in this documentation. To deploy the Bandwidth Manager, you need to collect the information listed in Table 1 of this topic. It is important to note the version of WebSphere Application Server and the WebSphere Application Server Update Installer.

Before you begin

The following servers must be installed prior to installing Sametime Bandwidth Manager:
  • IBM DB2® Server
  • LDAP Server
  • Sametime System Console
  • Sametime Community Server
  • Sametime SIP Proxy/Registrar
  • Sametime Conference Manager
  • Sametime Video Manager
  • Sametime Video MCU

About this task

The examples in Table 1 are for servers running on Microsoft™ Windows™.

Table 1. Information needed during Bandwidth Manger installation
Item Description Record your value here
LDAP Server Hostname The fully qualified host name of the LDAP server being used by the Sametime environment. This should match the server the System Console uses as well as the LDAP server used by Community servers.
LDAP server port The port used by the LDAP server. Typical default ports are 389 or 636 for SSL.
LDAP bind account name The name of a service account used to access the LDAP directory.
LDAP bind account password Password used for the LDAP directory. This password should not expire.
DB2 Server Hostname The fully qualified hostname of the DB2 server.
DB2 Server Port The port used by the DB2 server, is usually port 50000 or 50001
Load balancer address for the bandwidth manager cluster Use a network appliance to create a load balanced address on ports 5060, 5061, and 80. Record the fully qualified hostname of the load balanced address. For example, bwm.example.com

Network Address Translation (NAT) forwarding is needed to permit the Load Balancer to communicate with the WebSphere proxy server. The Load Balancer's physical IP address is used in health checking for the Load Balancer. Two virtual IP addresses are needed: one for the cluster IP address and one for the NAT IP address.

Note: IP forwarding is supported with WebSphere Application Server Fixpack 33.
"Service advisor" IP addresses for the load balancer List all of the IP addresses that are used by the load balancer to connect, that is, the IP addresses that are performing the health checking for the load balancer. There are typically two, but there can be more.
Software Staging Directory The location where you copy all of the files to be installed. For example, X:\Install
Installation Manager Installation Directory The location where you install the IBM Install Manager. For example, X:\IBM\Installation Manager\eclipse
Shared Resource Directory The shared files used by Install Manager and WebSphere Application Server. For example, X:\IBM\SSPShared
Bandwidth Manager installation directory Location where Bandwidth Manager is installed. For example, X:\IBM\WebSphere\BWM