Settings for creating and configuring database stores are managed in the EMS server, and are transparent to clients. To configure the database stores feature, follow these steps:
Includes all the JAR files required by the EMS server when employing the database store feature. This parameter must be set when a store of type
dbstore has been created in the
stores.conf file.
Required JAR files are determined by the installed Hibernate release, and are documented in the
README.txt file that is located in the
lib/ directory of the Hibernate distribution. Many of these JAR files are version-specific, and the required versions may change with new Hibernate releases. You should verify the required version and modify the
dbstore_classpath variable accordingly.
If you are using Hibernate release 3.2.5, for example, the dbstore_classpath should include paths to the following JAR files:
For an example, see EMS_HOME/samples/config/tibemsd-db.conf.
The SQL dialect is defined by Hibernate. For a list of databases and the associated dialects, see the readme.txt file located in the Hibernate install directory archive.
This section describes parameters configured for each database store in the stores.conf file. The
stores.conf includes definitions for both database and file-based stores. For information about configuring file-based stores, see
stores.conf on page 244.
[store_name] # mandatory -- square brackets included.
dbstore_driver_url =
JDBCURL
dbstore_driver_username =
username
dbstore_driver_password =
password
[processor_id =
processor-id]
|
|
|
[store_name] is the name that identifies this store configuration.
Note that the square brackets [ ] DO NOT indicate that the store_name is an option; they must be included around the name.
|
|
Identifies the store type. This parameter is required for all store types. The type can be:
•
|
file — for file-based stores.
|
|
|
Provides the location of the database server. The URL entered uses the syntax specified by the JDBC driver for your database.
Please see documentation specific to your JDBC driver for more information. If you are using an Oracle RAC database, also see Using a TAF Configured URL.
|
|
|
|
The password that the server uses, in conjunction with the username provided in dbstore_driver_username, to access the database.
You can mangle this and other passwords by way of the tibemsadmin tool. See Table 15, tibemsadmin Options for more information about using tibemsadmin to mangle passwords.
|
|
When specified, the EMS Server binds the storage thread of this store to the specified processor.
Do not use this parameter if the default behavior provides sufficient throughput. If no processor ID is specified for a store, the store is not bound to a specific processor.
Specify the processor-id as an integer. The processor ID is numbered starting at 0 and continuing to the number of processors available, minus 1. For example, if you have four processors, the available processor IDs are 0, 1, 2, and 3.
This parameter has similar requirements, limitations, and benefits as the processor_ids parameter in tibemsd.conf. For use guidelines, see Performance Tuning.
|
dbstore_driver_url=jdbc:mysql://mysqlsrv_1:3306/sysfs
dbstore_driver_username=admin
dbstore_driver_password=admin123
dbstore_driver_url=jdbc:mysql://mysqlsrv_1:3306/sysmeta
dbstore_driver_username=admin
dbstore_driver_password=admin123
dbstore_driver_url=jdbc:sqlserver://sqlsrv_1:3415;databaseName=sysmeta
dbstore_driver_username=admin
dbstore_driver_password=admin123
dbstore_driver_url=jdbc:sqlserver://sqlsrv_1:3415;databaseName=sysfs
dbstore_driver_username=admin
dbstore_driver_password=admin123
dbstore_driver_url=jdbc:oracle:thin:adminmeta/admin123@osrv_1:1521:orclperf
dbstore_driver_username=adminmeta
dbstore_driver_password=admin123
dbstore_driver_url=jdbc:oracle:thin:adminfs/admin123@osrv_1:1521:orclperf
dbstore_driver_username=adminfs
dbstore_driver_password=admin123
dbstore_driver_url=jdbc:oracle:oci:<user>/<passwd>@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host1>)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=<host2>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=orcl)(FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC)(RETRIES=180)(DELAY=5))))
dbstore_driver_username=admin
dbstore_driver_password=admin123
dbstore_driver_url=jdbc:db2://db2srv_1:50000/SYSMETA
dbstore_driver_username=admin
dbstore_driver_password=admin123
dbstore_driver_url=jdbc:db2://db2srv_1:50000/SYSFS
dbstore_driver_username=admin
dbstore_driver_password=admin123
The TIBCO Enterprise Message Service server must connect to the Oracle RAC 10g or 11g database using the Oracle JDBC OCI driver and TAF configuration.
To ensure that the EMS server does not lose its connection to the database during a database failover, the server should connect to the database using a Transparent Application Failover (TAF) configured URL. For example: