HP 3000 Manuals HP 3000 Manuals
The Use of Acknowledgments and Replies on Messages
The Intrinsics provide the option for applications to support full two
way acknowledgments and replies.
Replies to a Message from HP Desk
Messages extracted from HP Desk using HPDGateReceive always include a
tt_message_id transaction record. If the gateway application returns a
REPLY to the sender by submitting an HPDGateSend, this reply must contain
a tt_ack_id transaction record. This tt_ack_id must include the Message
Reference Number field from the tt_message_id transaction record of the
original message. This allows HP Desk to associate the reply with the
sender of the original message.
Replies to a Message from a Non-HP Desk System
If the application wants to be able to receive replies to messages it has
sent into HP Desk, messages submitted by HPDGateSend must include a
tt_message_id transaction record. In this situation the tt_message_id is
generated by the application software, not HP Desk. It will be carried
with the message as it passes through the HP Desk network. If the HP
Desk recipient of the message replies, the reply that is generated
contains a tt_ack_id record which holds the user generated message
identification information submitted with the original message.
Acknowledgments to a Message from HP Desk
[REV BEG]
Messages extracted from HP Desk using HPDGateReceive always include a
tt_ack_level transaction record to identify the level of acknowledgment
requested for the message. This transaction record will be generated
even if no acknowledgment were requested, in which case, the tt_ack_level
would be 0. The message will also include a tt_message_id transaction
record.[REV END]
If the gateway application wants to return Acknowledgments, the
acknowledgment submitted to HPDGateSend must include a tt_ack_id
transaction record containing all the information from the tt_message_id
transaction record of the original message. This allows the
acknowledgment to be associated with the correct item in the original
sender's Pending Tray. The level of acknowledgment being returned is
defined in the tt_body_type transaction record. For example, an
acknowledgment submitted to HPDGateSend will have the following format:
Transaction Record Content
tt_body_type_id Body type = 212, 213 or 214 (Received, Delivered
or Read Ack)
Body class = 0 (standard deliverable item)
tt_creator Name/address of the recipient of the original
message being acknowledged
tt_ack_id A copy of the tt_message_id record supplied in the
original message
tt_to Address of the creator/sender of the original
message being acknowledged. The creator name will
be ignored if supplied.
No other transaction types need appear in the file.
Acknowledgments to a Message from a Non-HP Desk System
If the gateway application wants HP Desk to acknowledge messages sent
into HP Desk using HPDGateSend, the message must include both
tt_ack_level and tt_message_id transaction records. tt_message_id
contains application generated message identification information. When
HP Desk acknowledges the message, the acknowledgment generated in
response to HPDGateReceive contains a tt_ack_id transaction record with
the message id from the original message.
Replies and Acknowledgment to Replies
The procedure described above also allows for replies to be made to
replies and for Acknowledgments to be set and generated on replies
(assuming the gateway application wants to provide this).
Replies generated by HP Desk using HPDGateReceive contain:
tt_ack_id with the user generated message id of the original
message
tt_ack_level describing the acknowledgment level required on this
reply
tt_message_id containing the HP Desk generated message id of this reply
Replies generated by the gateway application and submitted through
HPDGateSend may contain:
tt_ack_id with HP Desk generated message id of the original message
tt_ack_level acknowledgment level required on this reply
tt_message_id user generated message id of this reply