Configuration in stores.conf
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.
The format of the file is:
[store_name] # mandatory -- square brackets included. type = dbstore dbstore_driver_url = JDBCURL dbstore_driver_username = username dbstore_driver_password = password [processor_id = processor-id]
| Parameter Name | Description |
|---|---|
| [store_name] | [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. |
| type=dbstore | Identifies the store type. This parameter is required for all store types. The type can be:
For information about the parameters used to configure file-based stores, see stores.conf. |
| dbstore_driver_url | Provides the location of the database server. The URL entered uses the syntax specified by the JDBC driver for your database.
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. |
| dbstore_driver_username | The username that the EMS server uses to access the database.
Note that this user must have read and write permissions to the database. |
| dbstore_driver_password | 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 tibemsadmin Options for more information about using tibemsadmin to mangle passwords. |
| processor_id | 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. This parameter has similar requirements, limitations, and benefits as the processor_ids parameter in tibemsd.conf. For use guidelines, see Performance Tuning. |
Example Using Microsoft SQL Server
[$sys.meta] type=dbstore dbstore_driver_url=jdbc:sqlserver://sqlsrv_1:1433;databaseName=sysmeta dbstore_driver_username=admin dbstore_driver_password=admin123 [$sys.failsafe] type=dbstore dbstore_driver_url=jdbc:sqlserver://sqlsrv_1:1433;databaseName=sysfs dbstore_driver_username=admin dbstore_driver_password=admin123
Example Using Oracle
[$sys.meta] type=dbstore dbstore_driver_url=jdbc:oracle:thin:adminmeta/admin123@osrv_1:1521:orclperf dbstore_driver_username=adminmeta dbstore_driver_password=admin123 [$sys.failsafe] type=dbstore dbstore_driver_url=jdbc:oracle:thin:adminfs/admin123@osrv_1:1521:orclperf dbstore_driver_username=adminfs dbstore_driver_password=admin123
Example Using Oracle RAC
[$sys.failsafe] type=dbstore 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
For more information, see Configuration for the Oracle RAC Database below.