Updating the websphere_configuration.properties file on the deployment 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
Procedure
- Log in to the deployment manager's Integrated Solutions Console as the WebSphere administrator.
- In the navigation tree, click System administration > Deployment Manager.
- In the General Properties section locate the Name field. Copy the deployment manager name to the clipboard. The deployment manager name is added to the was.server setting in the websphere_configuration.properties file.
- In the navigation tree, click System administration > Nodes
- In the Servers table, locate the Cluster name column. Copy the cluster name to the clipboard. The cluster name is to be added to the was.cluster setting in the websphere_configuration.properties file.
- In the navigation tree, click System administration > Cell. The cell name is needed for the was.cell name setting in the websphere_configuration.properties file.
- On the server hosting the deployment manager, locate the
WAS Profiles directory.
WAS_Install_root\WebSphere\AppServer\profiles
There are two folders on the Deployment Manager, one for the Deployment Manager instance (Dmgr01) and the other for the AppServer instance (AppSrv01). Note the name (using the exact case) of the Deployment Manger's profile name.
- On the deployment manager, navigate to the
\TMP\BWM
folder containing the extracted installation files. Open the SametimeMediaManager\BandwidthManager folder. - Update the websphere_configuration.properties file
as follows:
- 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 might be set to read-only.
- Open the websphere_configuration.properties file
for editing and change the following lines. These lines apply to any
Bandwidth Manager installation. Note: The was.db2.driver.path shown below requires forward slashes for use with Microsoft Windows.
was.language=Language_abbreviation was.server=Deployment_Manager_name was.cell=Deployment_Manager_cell_name was.profilename=Deployment_Manager_profile_name was.home=WAS_install_root was.hostname=Host_name 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
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)
- Deployment_Manager_name, Deployment_Manager_cell_name, Deployment_Manager_profile_name are the WebSphere Application Server server, cell, and profile names for the deployment manager 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 Microsoft™Windows™ this is typically C:/IBM/WebSphere/AppServer and
in Linux™ it is typically /opt/IBM/WebSphere/AppServer. Attention: In Windows, you must use the DOS-shortened versions of the directory names and forward slashes or the installation will fail; for example: C:/PROGRA~1/IBM/WebSphere/AppServer.
- Host_Name is the fully qualified host name of the Deployment Manager where you will install the Bandwidth Manager (the current WebSphere Application Server).
- 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.
- 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.
Note: The was.db2.driver.path setting requires forward slashes for use with Microsoft Windows.For example:was.language=ja was.server=DeploymentManager was.cell=WAScell was.profilename=DMServerProfile was.home=C:/PROGRA~1/IBM/WebSphere/AppServer was.hostname=DMserver.example.com 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 was.hostport=9043 was.sipport=5060 was.httpport-9060
- 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.
- Change the following lines when installing Bandwidth
Manager in a cluster.
If you have deployed a load balancer, use the port values and proxy.host values of load balancer.
was.cluster=Cluster_name proxy.host=Proxy_host_name proxy.port.http=Proxy_port proxy.port.sip=Proxy_sip_port portlet.node=Portlet_node_name
where:- Cluster_name is the name of the cluster.
- Proxy_host_name is the fully qualified host name of the load balancer that sits in front of the proxy server that sits in front of the cluster.
- Proxy_port is the HTTP port of the proxy server that is in front of the cluster.
- Proxy_sip_port is the SIP port of the proxy server that is in front of the cluster.
- Portlet_node_name is the node name of the WebSphere Application Server Administrative server. It can be found in the WebSphere Application Server Integrated Solutions Console under System administration > Deployment manager on the Runtime tab in the Node name field.
was.cluster=BWMCluster proxy.hostbwm.company.com= proxy.port.http=80 proxy.port.sip=5060 portlet.node=nodeBWMCellManager
- Save and close the file.
- Change the properties of the websphere_configuration.properties file
to make it editable if necessary.