Develop WebSocket applications
WebSocket 1.1 is enabled by default and builds on the 1.0 specification. WebSphere Application Server traditional uses the WebSocket protocol to enable applications to communicate using a full-duplex connection.
Use WebSocket endpoints to match an endpoint to a URI. Web applications can use URIs that match a WebSocket template, but do not map to WebSocket endpoints. The distinction between mapping a WebSocket endpoint to a URI, or allowing the URI to be treated as a non-WebSocket HTTP Request, is made by the presence or absence of an Upgrade header with a value of websocket in the request.
In addition to the WebSocket version 1.1 API defined in the specification, JSR 356, an API was added to the WAS implementation to allow a servlet or filter to request that the current HTTP request upgrade to start a WebSocket session. For more information about the additional API, see API Specifications.
Outbound WebSocket API calls are available in applications running on the server, but not in WAS client applications. See Types of client applications.
For information about developing WebSocket applications using WebSphere Developer Tools, see Developing WebSocket applications.