Updating the websphere_configuration.properties file for the stand-alone Bandwidth Manager

Update the websphere_configuration.properties file included in the IBM® Sametime® Bandwidth Manager installation package and add settings for your deployment.

About this task

The websphere_configuration.properties file is used during installation to configure IBM WebSphere® Application Server settings needed by the Bandwidth Manager. Update the file and specify settings for your deployment as explained here. Values defined in the properties files are case sensitive to the deployment names used. When entering values, verify that they match the case used in the deployment names.

Procedure

  1. Navigate to the \TMP\BWM folder on Windows, or the /TMP/BWM folder on Linux, containing the extracted installation files.
  2. Update the websphere_configuration.properties file as follows:
    1. Change the properties of the websphere_configuration.properties file to make it editable if necessary.

      This file was supplied with the Bandwidth Manager installation package and may be set to read-only.

    2. Open the websphere_configuration.properties file for editing and change the following lines:
      was.language=Language_abbreviation
      was.node=Node_name
      was.server=Server_name
      was.cell=Cell_name
      was.profilename=Profile_name
      was.home=WAS_install_root
      was.hostname=Host_name
      was.hostport=Host_port
      was.sipport=SIP_port
      was.httpport=HTTP_port
      was.userid=WAS_admin_username
      was.password=WAS_admin_password
      was.db2.driver.path=${WAS_INSTALL_ROOT}/deploytool/itp/plugins/com.ibm.datatools.db2_2.1.102.vBuild_date/driver
      Note: Specify the formatting of the path in the properties file to be in keeping with your operating system conventions. Enter the path in the last line of the file in the format that matches your platform:

      Windows -- For this path, forward slashes are required.was.db2.driver.path=${WAS_INSTALL_ROOT}/deploytool/itp/plugins/com.ibm.datatools.db2_2.1.102.vBuild_date/driver

      Linux -- was.db2.driver.path=${WAS_INSTALL_ROOT}/deploytool/itp/plugins/com.ibm.datatools.db2_2.1.102.vBuild_date/driver

      where:
      • Language_abbreviation defines the language to be used for console and log messages produced by the Bandwidth Manager server or administrative interface. This setting does not affect messages that are presented to end users. Use one of the following language abbreviations to choose the language. If the parameter is missing, the default Language is English.
        • en (English)
        • de (German)
        • es (Spanish)
        • fr (French)
        • it (Italian)
        • ja (Japanese)
        • ko (Korean)
        • pt_BR (Brazilian Portuguese)
        • zh (Simplified Chinese)
        • zh_TW (Traditional Chinese)
      • Node_name, Server_name, Cell_name, Profile_name and are the WebSphere Application Server node, server, cell, and profile names where the Bandwidth Manager application will be installed (the current WebSphere Application Server instance).
      • WAS_install_root is the root directory where WebSphere Application Server is installed. In MicrosoftWindows this is typically C:/Program Files/WebSphere/AppServer and in Linux it is typically /opt/IBM/WebSphere/AppServer.
      • Host_Name is the IP address or the fully qualified domain name of the server where you will install the Bandwidth Manager (the current WebSphere Application Server).
      • On an unclustered server, Host_port, SIP_port, and HTTP_port correspond to the values that are used by the target profile in WebSphere Application Server for WC_adminhost, SIP_DEFAULTHOST, and WC_defaulthost, respectively.

        On a clustered node, Host_port and HTTP_port correspond to the values that are used by the Deployment Manager profile in WebSphere Application Server for WC_adminhost and WC_defaulthost, respectively. Find these values in the Integrated Solutions Console by navigating to System Administration > Deployment Manager. In the Additional Properties section, select Ports.

        On a clustered node, SIP_Port corresponds to the value used by the target WebSphere Application Server for SIP_DEFAULTHOST. Find this value in the Integrated Solutions Console by navigating to Application Servers > server_name. In the Communications section, select Ports.

      • WAS_admin_username and WAS_admin_password are the credentials of the WebSphere administrator (the credentials used for logging in to the Integrated Solutions Console). If administrative security is not enabled, you can omit the credentials.
      • ${WAS_INSTALL_ROOT} represents the WebSphere Application Server root installation directory. The install program looks for this exact designation; do not change it. Be sure to enter the path in the format used by your operating system.
      • Build_date is the build date that corresponds to the JDBC driver build date. To find the correct number, open the WAS-Install-Root/deploytool/itp/plugins folder and locate the folder named com.ibm.datatools.db2_2.0.102.vBuild_date, where Build_date is a 12-digit number.
      For example:
      was.language=ja
      was.node=myWASnode
      was.server=myWASserver
      was.cell=myWAScell
      was.profilename=AppServerProfile
      was.home=C:/PROGRA~1/IBM/WebSphere/AppServer
      was.hostname=myWASserver.example.com
      was.hostport=9060
      was.sipport=5060
      was.httpport=9080
      was.userid=wasadmin
      was.password=passw0rd
      was.db2.driver.path=${WAS_INSTALL_ROOT}/deploytool/itp/plugins/com.ibm.datatools.db2_2.1.102.v20091026_1945/driver
    3. Save and close the file.