ABAP Push Channels as Repository Objects

For each WebSocket communication you have to use an APC that is defined as repository object. APCs can be created in the Repository Browser of the ABAP Workbench using the context menu of a package under the menu entry Connectivity. Another option is provided by the Connecivity Browser of the Object Navigator that is callable for APCs directly using transaction SAPC.

Each Push Channel has two more repository objects that are generated when creating a Push Channel:

A node in the ICF service tree that is displayed in transaction SICF. This node, like every ICF service, represents the web address of the Push Channel. It can be activated or deactivated, but not be tested directly.
Instead, other systems like a web browser supporting the WebSocket protocol can communicate with the Push Channel using this address.
An APC handler class that is stored as global class in the ABAP class library and can be processed in the Class Builder. The APC framework generates an instance of the class as APC handler during communication with a Push Channel.

Optionally, a sub-protocol for the WebSocket protocol can be assigned to a Push Channel. Currently, only the assignment of the SAP-specific Push Channel Protocol (PCP) is supported. The generated APC handler class inherits from another superclass corresponding to the protocol used and binds other interfaces that enable a specific access to this protocol.

Example

As an example, see the ABAP Push Channels DEMO_APC und DEMO_APC_PCP in package SABAPDEMOS.