webMethods Event Routing 10.3 | 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 2.3.2 or 5.6.4 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.
When using Elasticsearch, you can persist events using Secure Socket Layer (SSL).
For more information about persisting events over SSL to an Elasticsearch instance, see Configuring SSL for Event Persistence .
* To create Event Routing services of type Event Persistence for Elasticsearch:
1. In Command Central, navigate to Environments > Instances > All > instance_name > Event Routing > Configuration.
2. Select Event Persistence from the drop-down menu.
3. Click Plus icon, and then select Elasticsearch 2.3.2 or Elasticsearch 5.6.4 for the service type.
4. Specify values for the fields in the following table as explained in the description column:
Field
Description
Service Name
Required. The name of 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.
Note: You cannot rename an existing service. If you want to modify the service name, you must delete the existing service and create a new one with a different name.
Service Description
Optional. A description of the new service.
Cluster URI(s)
Required. A comma-separated list of servers in an Elasticsearch cluster to which the Event Persistence service can connect. If the initial host is unavailable, Event Persistence attempts to connect to the other servers in the cluster. Specify the URI of the servers in the Elasticsearch cluster as follows: elasticsearch://host:port, where host is the host name of the server, and port is the port on which the server listens for incoming requests.
The default value is elasticsearch://localhost:9300.
Cluster Name
Required. The name of the Elasticsearch cluster.
Index Name
Required. The name of the index in which the events are stored.
Note: Elasticsearch supports only lowercase index names.
Core threads
Required. The number of threads to keep in the pool at all times. The default value is 5.
Maximum Threads
Required. The maximum number of threads on which to run bulk indexing tasks. The default value is 10.
Queue Size
Required. 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)
Required. The time limit in seconds for which threads remain idle before being terminated. The default value is 5.
Pre-Start Core Threads
Required. Whether the core threads start immediately rather than as work is pulled from the queue. Values are true or false (default).
Batch Size
Required. The number of events that are written to Elasticsearch with a single write operation. The default value is 1000.
Note: If the Elasticsearch service queues a batch of events before the batch write timer expires, the service immediately persists all queued events to Elasticsearch.
Batch Write Timer(sec)
Required. Batch write frequency in seconds. The default value is 15.
Note: If the batch write timer expires before the Elasticsearch service queues a batch of events, all currently queued events are persisted to Elasticsearch.
Enable SSL
Required. Enable or disable SSL for both REST and TCP ports. The default value is false.
For more information about how to configure SSL for Event Persistence, see Configuring SSL for Event Persistence .
Key Store
Optional. Specify the absolute file path to the Java KeyStore (JKS) file as follows: folder/sub_folder/filename.
Trust Store
Optional. Specify the absolute file path to the JKS truststore file as follows: folder/sub_folder/filename.
5. Save your changes.
Event Routing Event Routing detects that the configuration has been updated, and starts to use the new settings automatically.
Copyright © 2010-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.