Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

The websocket-local event receiver should be used if the event source is a web socket client. Such event sources need to connect to the inbuilt websocket server of WSO2 CEP DAS for the CEP DAS to receive events. However, if the event source is a web socket server, the CEP DAS should connect to it in order to receive events. In such scenarios, use the WebSocket Event Receiver.

...

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

Info

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

Super-tenant/TenantURL Formats
Super-tenantws://localhost:";<DAS_Server_Port>"/inputwebsocket/<receiver_name>

wss://localhost:";<DAS_SSL_Server_Port>"/inputwebsocket/<receiver_name>";
 
Tenantws://localhost:";<DAS_Server_Port>"/t/<tenant_domain>/ inputwebsocket/<receiver_name>

wss://localhost:";<DAS_SSL_Server_Port>"/t/<tenant_domain>/
inputwebsocket/<receiver_name>";
 

e.g., If the receiver name is WebSocketLocalInputEventReceiver 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"/inputwebsocket/WebSocketLocalInputEventReceiver
wss://localhost:";9443"/inputwebsocket/WebSocketLocalInputEventReceiver ";
 
Tenantws://localhost:";9763"/t/mycompany.com/inputwebsocket/WebSocketLocalInputEventReceiver

wss://localhost:";9443"/t/mycompany.com/
inputwebsocket/WebSocketLocalInputEventReceiver";

Related samples

For more information on websocket-local event receiver type, see the following sample in WSO2 CEP Documentation.

...