The ESB profile of WSO2 Enterprise Integrator (WSO2 EI) WebSocket protocol implementation is based on the WebSocket protocol, and allows full-duplex message mediation.
Following is a sample WebSocket inbound endpoint configuration:
WebSocket inbound endpoint parameters
|The netty listener port on which the WebSocket inbound listens.||Yes|
|The client broadcast level that defines how WebSocket frames are broadcasted from the WebSocket inbound endpoint to the client. Broadcast happens based on the subscriber path client connected to the WebSocket inbound endpoint. The three possible levels are as follows:|
0 - Only a unique client can receive the frame from a WebSocket inbound endpoint.
1 - All the clients connected with the same subscriber path receives the WebSocket frame.
2 - All the clients connected with the same subscriber path, except the one who publishes the frame to the inbound, receives the WebSocket frame.
|The sequence for the back-end to client mediation.||Yes|
|The fault sequence for the back-end to client mediation path.||Yes|
|The size of the netty boss pool.||No|
|The size of the worker thread pool.||No|
|Specify one or more custom subprotocol handler classes that are required. Separate each custom subprotocol handler class using a semicolon.||No|
Specifies the content type of the Web Socket frames that are received from the inbound endpoint.
|Specifies the status code of the closed web socket frame sent when the inbound endpoint is closed.||No|
|Specifies the status message of the closed web socket frame when the inbound endpoint is closed.||No|
The fully qualified class name of a pipeline handler class that you implemented.