The architecture diagram shows a complete Push Service solution that includes the server-side library and the client-side library. The libraries work together to deliver content from the Push Initiator to a push-enabled application.
|Push Initiator||The Push Initiator is the application that creates request messages (such as a push request, cancel request, or status-query request) and response messages (such as a result-notification response) using the server-side library and submits them to the push proxy gateway (PPG). The Push Initiator also uses the server-side library to process subscription-related requests that it receives from the push-enabled application on the BlackBerry device.|
|Server-side library||You can use the Push Service SDK as the server-side library or you can provide your own library. If you use the Push Service SDK, the server-side library provides the Java APIs that the Push Initiator uses to interact with the PPG. The Push Initiator also uses the server-side library to process subscription-related requests that it receives from the push-enabled application on the device. For information about developing a Push Initiator using the Push Service SDK, see the Push Service SDK documentation.|
|Push Proxy Gateway||The PPG processes push request messages and status-query messages that it receives from the Push Initiator. After the PPG processes a push request message, it sends a response message that communicates the overall outcome of the push message. The response message contains a result code or a PAP error code.|
|Push-enabled application||The push-enabled application runs on a device, and might send subscription-related requests to the Push Initiator. The push-enabled application uses the client-side library to create a PushService object, create and destroy a channel, and receive push messages.|
Last modified: 2014-05-14