![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This section describes the steps required to configure and deploy database stores. For general conceptual information about the multiple store feature, see Store Messages in Multiple Stores.
1. Enable the database store feature in the tibemsd.conf by setting the parameters:For detailed information about the dbstore parameters, see Configuration in tibemsd.conf. The jre_library parameter, which enables the JVM in the EMS server, is described in JVM Parameters.
2. Setup and configure stores in the stores.conf file.Messages are sent to different stores according to their destinations. You associate a destination with a specific store using the store parameter in the topics.conf and queues.conf files. You can also change store associations using the setprop topic or setprop queue command in the EMS Administration Tool.Multiple destinations can be mapped to the same store, either explicitly or using wildcards. Even if no stores are configured, the server sends persistent messages that are not associated with a store to default stores. See Default Store Files for more information.These parameters are set in the tibemsd.conf configuration file.dbstore_classpath = pathnameIncludes 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:
•
•
• Database-specific driver JAR file. Supported jar files are listed in Database Servers and Drivers in TIBCO Enterprise Message Service Installation.dbstore_driver_dialect = dialectThis 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 262.[store_name] # mandatory -- square brackets included.dbstore_driver_url = JDBCURLdbstore_driver_username = usernamedbstore_driver_password = password[processor_id = processor-id]
Table 56 Database Store File Parameters Note that the square brackets [ ] DO NOT indicate that the store_name is an option; they must be included around the name.
• file — for file-based stores.
• mstore — for mstores.
• dbstore — for database stores. 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 16, tibemsadmin Options for more information about using tibemsadmin to mangle passwords. 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.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |