Adding and removing modules

Use the Configuration page to add or remove individual IBM® Sametime® Bandwidth Manager modules.

About this task

The Bandwidth Manager comprises three different modules:

Bandwidth Pool Manager: Manages bandwidth allocations.
Media Session Controller: Implements the business logic of the bandwidth management component (such as user lookup and application of policies).
SIP Frontend: Handles incoming SIP requests and acts as SIP proxy.

Several instances of the same module type can be set up to improve scalability; use the Configuration tab to add or remove individual modules.

Procedure

On the computer hosting the Sametime Bandwidth Manager, log in to the IBM WebSphere® Application Server Integrated Solutions Console as the WebSphere administrator.
Click Sametime Servers > Bandwidth Manager.
Click the Configuration tab.
Locate the modules table (it appears after the property settings).

Do one of the following:

Delete a module by selecting the module in the table, and then clicking the Delete button.

Add a module by clicking the New button and entering the following information before clicking OK:

Table 1. Module properties
Column 1 lists the module properties and column 2 explains how to fill them in.
Property	Value
Component type	The type of the component instance: Bandwidth Pool Manager, Media Session Controller, or SIP Front end.
Server name	The full IBM WebSphere Application Server name of the server where this component was installed, in the following format: `Cell_name\Node_name\Server_name` for example, Windows Websphere302Node01Cell\Websphere302Node01\server1 Linux Websphere302Node01Cell/Websphere302Node01/server1
HTTP URI	The HTTP URL of this particular instance of the component, in the following format http://`Host_name:HTTP_port/Application_path` where `Host_name` is the host name or IP address of the WebSphere Application Server where the component is installed, and `HTTP_port` is the number of HTTP port that is configured for this server.
Cluster HTTP URI	The common HTTP URL for all instances of the given component type on the cluster (for a single server installation use the same value as for the HTTP URI field).
SIP URI	The SIP address of the bandwidth management component of this instance of the "SIP Frontend" (leave it blank for other types). It should be defined in the following format `sip:Host_name:SIP_port` where `Host_name` is the host name or IP address of the WebSphere Application Server where the component is installed, and `SIP_port` is the number of the SIP port that is configured for this server. This value should match the destination address as configured in the SIP Proxy routing rule.
Cluster SIP URI	The common SIP address for all instances of "SIP Frontend" on the cluster (for single-server installation use the same value as for SIP URI). This value should match the destination address as configured in the SIP Proxy routing rule.
Priority	The priority of the current instance. This is an integer value used only for "Bandwidth Pool Manager" components to determine which instance will be acting as the primary server. Smaller number indicate higher priority).

Save your changes by clicking the Save link in the "Messages" box at the beginning of the page.