Try OpenEdge Now
skip to main content
BPM Events User's Guide
Administering and operating BPM Events : BPM Events configuration parameters
 

BPM Events configuration parameters

The BPM Events configuration is specified in two files:
*bpmevents.conf: This configuration file contains configuration parameters specific to BPM Events.
*oebps.conf: This configuration file contains general configuration parameters that are shared across Business Process Server components, or configuration parameters about a specific component (here BPM Events) which is known also from administration tools.
The configuration file (bpmevents.conf) is modified through Business Process Portal. The Business Process Server installer automatically sets up some parameters that are installation dependent, like host names. Table 15 describes the configuration parameters found in the bpmevents.conf file. The default values are adjustable.
Caution: Be careful—making adjustments to some of the following values may cause BPM Events to perform in an unstable manner.
Table 15. BPM Events configuration parameters
Parameter name
Description
Default value
bpmevents.engine.debug
If set to "on", then the debug (trace) information is written to the log file.
off
bpmevents.engine.trace.dbaccess
If set to "on", then the database access information is written to the log file.
off
bpmevents.engine.trace.event
If set to "on", it then generates an entry for each event that is processed in bpmevents.log.
off
bpmevents.engine.trace.filter
If set to "on", then it writes the event filter used by BPM Events to fetch events from database to log file
off
bpmevents.engine.eventcachesize
Maximum number of events BPM Events can store in the cache. The cache is partially flushed when this limit is reached. A small cache size increases swapping in/out to database. Format: integer
10000
bpmevents.engine.emailer.senderaddress
The default sender e-mail address for BPM Events rules, when they use the action sendMail(). Format: e-mail
set by installer
bpmevents.engine.bizlogic.api.retry
The number of times BPM Events should retry to call BP Server API, when the connection fails. If set to "0", then it does not try. Format: integer
5
bpmevents.engine.bizlogic.api.sleeptime
The time interval (milliseconds) that BPM Events should wait before retrying to call BP Server API, in case the connection failed. Format: integer
10000
bpmevents.engine.bizlogic.api.innewtransaction
If set to "on", then it executes BP Server API in a new transaction otherwise executes in the BPM Events transaction
off
bpmevents.engine.ptnamecheckmode
Check whether or not PTName is defined in DB. useful for debugging
on
bpmevents.server.eventfiltermode
It generates event filter for event fetch optimization.
on
bpmevents.server.trace.xml
If set to "on", then it writes all the XML events received on jms/BPEventQueue to log file.
off
bpmevents.server.autoerrorrecovery
If set to "off", then the event reader is suspended when an internal error is caught. The server does not plan any new events.
on
bpmevents.server.eventsource.eventbatchsize
Maximum size of each batch of events fetched from the database. Format: integer
100
bpmevents.server.eventsource.sleeptime
Period in (milliseconds) between fetching two batches of events when there are no events in BizEvent table.
1000
bpmevents.server.eventsource. sleeptimewhenevents
Period in (milliseconds) between fetching two batches of events when there are still events in BizEvent table.
0
bpmevents.server.eventsource.retryinterval
Period in milliseconds between retrying the database connection.
30000
bpmevents.server.eventsource.maxdbretry
The maximum number of times BPM Events should retry to connect to database, when the connection fails. By default, the value is -1, which specifies that BPM Events continue trying until connection is reestablished.
-1
bpmevents.server.eventsource. maxtotalpreparedstatements
Maximum number of opened prepared statements. Format: integer
100
bpmevents.server.eventsource.maxgapretry
The maximum retry number when event gap found. the total amount of retry time is
bpmevents.server.eventsource.sleeptime *
bpmevents.server.eventsource.maxgapretry
Format: integer
60
bpmevents.server.callback
Any change in BPM Events states notified by invoking registered callback adapters.
false
bpmevents.server.jms
If set to "on", then it can receive events from the JMS server.
on
bpmevents.server.jms.adapter
Set the adapter for JMS message processing.
dom
bpmevents.server.jms.topic.admin
The topic used in monitoring and starting EventReader.
BPAdminTopic
bpmevents.server.jms.queue.integration
he queue used by BPM Events to listen to external messages.
BPEventQueue
bpmevents.server.jms.wait.interval
Time in seconds a JMS Message sender waits for replies from MonitorBeans or EventReaderBean.
120
There are some more parameters that are relevant to BPM Events—and also to other components—but are set at a more general level in oebps.conf. They can also be modified through Business Process Portal.