Customizing the event runtime environment

Before starting the event runtime for the first time, you might want to make configuration changes to some of the components in the runtime environment.

Configuring the event runtime database for Decision Server Events
The event runtime requires the use of a database. There are various configuration tasks that you might need to do to the database, depending on your environment.
Editing the setenv files
You must edit the setenv files as part of the configuration steps to complete your installation.
Changing the event runtime messaging provider
If you have configured your event runtime to use one messaging provider but you want to change to another messaging provider, or if you chose not to configure a messaging provider when creating or augmenting your Decision Server Events profile, you must do some additional configuration.
Setting properties
Configuration properties for the event runtime are stored in WebSphere® Application Server. You might want to change properties because they determine the configurable behaviour of Decision Server Events. There are three ways to set event runtime properties.
Configuring the event runtime to record history
If you want to record history, you must configure the event runtime to record history. Otherwise, you cannot monitor events, actions, filters, or data in real time through user-defined charts, nor can you run reports or use track events. Recording history preserves the delivery of real-time history records across system restarts.
Configuring the durable event queue
Decision Server Events uses a file system based event queue to ensure that durable events are not lost if a server fails.
Configuring how time-delayed event rules and actions are handled after a shutdown
The evaluation of events and actions is typically done as soon as possible, but you can delay the evaluation based on user-defined criteria. If a server shuts down, there might be event rules and actions scheduled to fire while the server was down. You can configure how the event runtime handles these time-delayed event rules and actions when it restarts.
Configuring the event runtime to store step data in memory
For performance reasons, you might choose to store step data in memory.
Configuring the event runtime to store context data in ObjectGrid
The context table uses the default cache. As a potentially higher-performing alternative, you can configure the context table to use ObjectGrid. You cannot use ObjectGrid as the context table on z/OS®.
Tuning your event runtime configuration
Some tuning of the system might lead to higher performance when processing events.
Configuring multiple Decision Server Events profiles to coexist
If you have multiple profiles of Decision Server Events on one computer, you must configure the WebSphere eXtreme Scale catalog service for the profiles to coexist.
Configuring technology connectors on a separate computer
Technology connectors can be run on the same computer as the event runtime, or they can be run on a separate computer or operating system.
Configuring the User Console connector to use a WebSphere Application Server data source
The User Console connector accesses its tables by using data connections. If you have configured Decision Server Events to use a WebSphere Application Server data source when accessing the event runtime, you must make further configuration changes to enable the User Console connector to function. You must do this task if you are using an embedded Apache Derby database.

Parent topic: Configuring Decision Server Events on WebSphere Application Server