WSO2 Complex Event Processor is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.
||
Skip to end of metadata
Go to start of metadata

WebSocket local event publisher is an internal event publisher that comes with WSO2 products by default. You can configure it with XML, text, and JSON output mapping types.

The websocket-local event publisher should be used when the CEP publishes to a websocket client. Websocket clients need to connect to the inbuilt websocket server of WSO2 CEP for the events to be published. However, when the CEP publishes to a web socket server, the CEP should connect to the websocket server in order to publish events. In such scenarios, use the WebSocket Event Publisher.

Creating a WebSocket local event publisher

For instructions on creating a WebSocket local event publisher, see Configuring CEP to Create Alerts.

Configuring global properties

The following global properties can be set for WebSocket local event publisher type in the <CEP_HOME>/repository/conf/output-event-adapters.xml file. These properties apply to all the publishers of the web socket-local type. If a global property available by default is removed, the default value of the property is considered.

Custom properties cannot be added as global properties.

Property KeyDescriptionData TypeDefault Value
minThreadThe minimum number of threads (including idle threads) that should be available in the thread pool at a given time.Integer8
maxThreadThe maximum number of threads (including idle threads) that should be available in the thread pool at a given time.Integer100
keepAliveTimeInMillisThe maximum number of milliseconds that idle threads should be kept alive when the total number of threads in the pool exceeds the number of cores in the machine.Integer20000
jobQueueSizeThe maximum number of milliseconds that idle threads should be kept alive when the total number of threads in the pool exceeds the number of cores in the machine.Integer10000

Configuring adapter properties

There are not any adapter-specific properties for the WebSocket local event publisher as shown below.

WebSocket local event publisher

When multi-tenancy is used, the URL formats used to publish events are as follows.

Super-tenant/TenantURL Formats
Super-tenant ws://localhost:";<CEP_Server_Port>"/outputwebsocket/<publisher_name>

 wss://localhost:";<CEP_SSL_Server_Port>"/outputwebsocket/<publisher_name>";
 
Tenantws://localhost:";<CEP_Server_Port>"/t/<tenant_domain>/outputwebsocket/<publisher_name>

wss://localhost:";<CEP_SSL_Server_Port>"/t/<tenant_domain>/outputwebsocket/<publisher_name>";
 

e.g., If the publisher name is WebSocketLocalOutputEventPublisher and the tenant domain is mycompany.com, the URL would be as follows when you use the default server ports.

Super-tenant/TenantURL Formats
Super-tenantws://localhost:";9763"/outputwebsocket/WebSocketLocalOutputEventPublisher

wss://localhost:";9443"/outputwebsocket/WebSocketLocalOutputEventPublisher ";
 
Tenantws://localhost:";9763"/t/mycompany.com/outputwebsocket/WebSocketLocalOutputEventPublisher

wss://localhost:";9443"/t/mycompany.com/outputwebsocket/WebSocketLocalOutputEventPublisher";

Related samples

For more information on websocket-local event publisher type, see the following sample.

  • No labels