Update the db2.connection.properties file
included in the IBM® Sametime® Bandwidth Manager
installation package and add settings for your deployment.
About this task
The db2.connection.properties file is
used during installation to create a new connection to the Bandwidth
Manager database hosted on the deployment's IBM DB2® server. Update
the file and specify settings for your deployment as explained here.
Perform these steps on the deployment manager if you have created
a cluster.
Procedure
- Navigate to the
\TMP\BWM
folder containing
the extracted installation files.Note: The db2.connection.properties file
is in the same directory as the installation files. If the BWM installation
files are in a directory other than \TMP\BWM
, look
for the db2.connection.properties file in the
directory containing the installation files.
- Update the db2.connection.properties file
as follows:
- Change the properties of the db2.connection.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.
- Open the db2.connection.properties file
for editing and change the following lines:
db2.login=DB2Username
db2.password=DB2Password
db2.connection.address=HostName
db2.connection.port=50000 or other DB2 port
db2.schema=SCHEMANAME typically the DB2USERNAME
db2.connection.database=Database_name, that is, BWM_DATA
where:
- DB2Username and DB2Password are
the credentials of the user who created the BWM_DATA database (usually
the DB2 instance
owner).
- HostName can be a short name, fully qualified
domain name, or an IP address as long as it is addressable by both
the install program and the Bandwidth Manager runtime. A fully qualified
domain name is recommended. You can use a short name if it is defined
in the local hosts file, for example system32/driver/etc/hosts on Windows™ or /etc/hosts on Linux™.
- DB2Port is the DB2 server network
port. The default is 50000, but change this to the appropriate value
if your DB2 server
uses a different port.
- SchemaName is the name of the database schema
used by the Bandwidth Manager. Typically the default database schema
is used, which is named the same as the DB2USERNAME,
but the schema must be in uppercase letters. On Linux, the schema name is case sensitive.
- Database_nme must be the same value that you
used when you created the Bandwidth Manager database. The examples
in this documentation use "BWM_DATA" as the database name.
For example:
db2.login=myDB2user
db2.password=myDB2passw0rd
db2.connection.address=db2svr.example.com
db2.connection.port=50000
db2.schema=MYDB2USER
db2.connection.database=BWM_DATA
- Save and close the file.
- Browse to the scripts/jacl directory.
- Rename the tuneWASSIP70.jacl file
to tuneWASSIP70.jacl.ORIG
- Copy the hotfix version of this file into the same directory.