Data store profile settings
Use this page to configure the runtime properties of a data store.
The event data store is used to persist events received by the event server.
To view this administrative console page, click Resources > Common
Event Infrastructure Provider > Data Store Profile > data_store_profile.
Configuration tab
-
Name
- Specifies the administrative name for the data store profile.
-
JNDI Name
- Specifies the JNDI name to which this profile is bound.
-
Description
- Describes the data store profile for your administrative records.
-
Category
- Specifies the category for the data store profile, which you can
use to classify or group the resource.
-
Query Threshold
- Specifies the maximum number of events that can be read in a single
transaction.
Use this setting to protect the integrity of the system. If a query attempts
to read too many events from the database, an excessive amount of Java and
RDBMS resources can be consumed.
Data type |
Integer |
Default |
100 000 |
Range |
1 to 2147483647 |
-
SQL Cache Size
- Specifies the maximum number of transformed XPath expressions that
will be cached in memory. When the threshold is reached, the least recently
used expression is removed from the cache.
Transforming event selector expressions (defined as XPath expressions)
to SQL can require a considerable amount of system resources, but XPath expressions
that are found in the cache do not need to be transformed to SQL. Therefore,
you can use this setting to tune performance.
Data type |
Integer |
Default |
1000 |
Range |
0 to 2147483647. A value of 0 indicates that no transformed XPath
expressions are cached. |
-
Maximum Connection Retries
- Specifies the maximum number of times that the data store attempts
to obtain a connection from the connection pool.
Data type |
Integer |
Default |
2 |
Range |
0 to 2147483647. A value of 0 indicates that no retries are attempted.
If a connection cannot be obtained in the first attempt, an error message
is displayed. |
-
Maximum Purge Transaction Size
- Specifies the maximum number of events that can be deleted from
the database in a single transaction.
Use this setting to protect the integrity of the system. Deleting too many
events from the database can create very large transaction logs and can impact
performance.
Data type |
Integer |
Default |
100 000 |
Range |
1 to 2147483647 |
-
Schema Name
- Specifies the database schema that contains the event tables. Do
not change this value.
The schema name is used to build SQL statements that have fully qualified
table names, which enables you to have multiple instances of the event database.
Data type |
String |
Default |
cei |