Building Your Event-Driven Architecture : Communicating between SoftwareAG Products Using Event Routing : Administering Event Routing : Configuring Services and Service Groups : Creating Event Persistence Services : Creating Event Persistence Services for Elasticsearch
Creating Event Persistence Services for Elasticsearch
With Event Persistence services, you can store events to an Elasticsearch storage engine. You create and administer Event Persistence services using the Software AG Command Central web interface.
Note:  
Event Persistence is not supported on Elasticsearch clusters with Shield enabled.
To create Event Routing services of type Event Persistence for Elasticsearch:
1. In Command Central, navigate to Environments > Instances > All > <profile_name> > Event Routing > Configuration tab, select Event Persistence from the drop-down menu, and then click Add.
2. In the Select Configuration dialog, select Elasticsearch for the service type and click OK.
3. In the Configuration Details dialog, define the following parameters for the service:
Parameter
Description
Service Name
Custom name for the new service. Specify a unique service name that starts with a character. Valid separator characters are periods (.) and dashes (-). The service name is not case-sensitive.
Important:  
You cannot rename a service which has already been created. If you wish to modify a service name, you must delete the old one and recreate a new one with a different name.
Service Description
Custom description for the new service.
Cluster Host
The host of the Elasticsearch server.
Cluster Port
The port number of the Elasticsearch server. The default value is 9300.
Cluster Name
The name of the Elasticsearch cluster.
Index Name
The name of the index in which the events will be stored.
Core threads
The number of threads to keep in the pool at all times. The default value is 5.
Maximum Threads
The maximum number of threads on which to run bulk indexing tasks. The default value is 10.
Queue Size
The size of the thread pools work queue. A value of 0 indicates an unlimited queue. A value other than 0 sets the number of pending bulk indexing tasks that can be queued before the processing thread blocks. The default value is 10.
Keep Alive(sec)
Sets the time limit for which threads may remain idle before being terminated. The default value is 5.
Pre-Start Core Threads
Whether the core threads must be started immediately rather than as work is pulled from the queue. Possible values are true or false (default).
Batch Size
The number of events that are written to Elasticsearch with a single write operation. The default value is 1000.
Note:  
If the Elasticsearch service enqueues a batch of events before the batch write timer expires, it will immediately persist all enqueued events to Elasticsearch.
Batch Write Timer Sec(sec)
Batch write frequency in seconds. The default value is 15.
Note:  
If the batch write timer expires before the Elasticsearch service enqueues a batch of events, all currently enqueued events will be persisted to Elasticsearch.
4. Save your changes.
Event Routing Event Routing detects that the configuration has been updated, and starts to use the new settings automatically.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback