Running Multiple External Databases On A Single Database Server - 3Com 3CR15600 - Enterprise Management Suite Getting Started Manual

Table 24 IBM DB2 DB Section of the server.properties File (continued)
Field
DBFile
DBUserName
DBPassword
PM.DBURL [optional]
6 Save and close the server.properties file.
7 Restart the EMS server.
Note that JDBC will not work if the CSSID is set to 65535 (i.e.
"unknown"). The character set should be set to a valid country. This issue
is described in detail in document number 29290926 "Character
Conversion Errors with Job CCSID 65535" on the IBM web site. Refer to:
http://www-912.ibm.com/s_dir/slkbase.NSF/0/9ea41ee0c6099d1e86256
caa006e4b59?OpenDocument

Running Multiple External Databases on a Single Database Server

Some external databases allow you to run multiple database instances on
the same database server.This can be helpful, especially when a network
designer splits the management domain into separate databases, with a
separate EMS server managing a different set of SNMP devices (useful for
different geographical locations).
If you choose to do this, follow these guidelines:
A single EMS server can only connect to a single database instance.
■
Active EMS servers cannot share database instances. Each active EMS
■
server must have exclusive read-write access to a particular database.
If you choose to deploy multiple EMS databases on the same database
server (for example, EMSDB1 and EMSDB2), only one instance of EMS
should ever be connected to any particular database.
Description
The specific location of the EMS database file/directory that
contains all data. This is used to compute the database size.
NOTE: If you deploy the database on a separate server, you
cannot use this option.
The username used to connect to the database.
The password used to connect to the database.
URL to connect to a different database for historical data
collection. Only used if the optional Historical Data Collection
package is installed. Same format as DBURL.
Database Configuration 73