The Push Database

Good Intranet Server maintains a database of push messages and push deliverables. A push deliverable corresponds to an instance of a push message that is to be sent to a specific handheld. For example, if the server sends a push message for three handhelds, there will be three push deliverables corresponding to the push message.

Deliverables in the push database always have a delivery state. For example, when the server accepts a push message for delivery to one or more handhelds, each destination handheld has a corresponding deliverable and the state of each of these deliverable state is pending. When an instance of the push message associated with a deliverable is sent to a handheld and the handheld acknowledges receipt of the message, the deliverable's state is delivered. (For a list and descriptions of the states a deliverable can have in the database, see Delivery and Result Notification States)

The push database is limited to push messages that are "current." Once a push message has been delivered to all target handhelds, it is deleted from the database. In addition, messages assigned a deliver-before time are deleted when they reach their deliver-before time, and messages over 30 days old are deleted.

Good Intranet Server provides two command-line utilities for accessing data in a push database:

• Report command

The Report Tool generates XML reports on the push messages in a push database. You can generate a report on all messages in the database, and you can use the tool to restrict the report to specific push messages, handhelds, content IDs, and delivery states (for example, pending or delivered). The Report Tool must be run on a system with file access to the push database (for example, you can run the tool on the same host as Good Intranet Server). For information on the Report Tool, see Generating Push Reports

• Status command

The Status command allows you to query the server for the current status of the deliverables in a specific push message. Status must be run from a host that is allowed to perform push operations. For more information, see Checking Push Status

Delivery and Result Notification States

The following table lists push delivery states:

Push Delivery States

Delivery State	Description
pending	Message from the push initiator has been accepted for delivery, but not yet sent.
delayed	Message accepted for delivery, but the message contains a deliver-after time, so delivery is delayed until that time.
enroute	Message sent over the air to the destination handheld, but an acknowledgment of delivery has not been received, yet.
delivered	The destination handheld has acknowledged receipt of the message.
replaced by newer deliverable	The message was not delivered because before delivery was requested, a new version of the same content was received from the push initiator and sent instead.
cancelled	Message cancelled, either by the push initiator or through the Cancel command.
expired	Message could not be sent before the deliver-before time occurred.
rejected	The message was rejected because of a problem in the push message format.
specified push-id is not unique	The message was rejected because there is another message with the same push ID.
failed	The server was unable to deliver the message.
specified address is invalid	The server was unable to deliver the message because of an incorrect email address.
delivery attempts exceeded	The server sent the push message out five times without getting an acknowledgment from the handheld.

The following table lists push result notification states:

Result Notification Statues

Notification State	Description
notify delivered	The final delivery state of the message was successfully sent to the address specified in the push-message header's ppg-notify-requested-to attribute.
notify not requested	No result notification was sent because the push message did not contain a ppg-notify-requested-to address.
notify failed	The final delivery state could not be sent to the address specified in the push-message header's ppg-notify-requested-to attribute.