Hello Partner Documentation Revised: 1/29/2004 $ASQHelloPartner Data Model.doc.doc Page 1 of 3 Version 1.0 (January, 29, 2004) Phase Initiated Test Tool Name 4.3 Hello Partner Documentation.doc and 4.3 Hello Partner Appendix D Additions.doc Description This document describes the steps required for executing the Hello Partner test. Doc Type Internal Optional Reference Usage The Hello Partner test is used to test connectivity and security in the test and production environments. New User: This is a recommended test for any new connections. Experienced User: X.0 Hello Partner Table of Contents X.1 Introduction and Scope of Effort This section of the Ag eStandards document defines the data exchange interfaces necessary to support the interchange of test transactions confirming network dial-tone between systems. HelloPartner The HelloPartner Transaction takes place between two network connections. It enables partners to confirm dial-tone connectivity that will allow business transactions to flow. X.1.1 Key Scope Assumptions • This transaction may be used in Business-to-Business (B2B) and Business-to-Marketplace communications. • This transaction is not necessarily intended to be integrated into any business application. • This transaction is intended to confirm connectivity dial tone between two integration processing systems. • Before a HelloPartner transaction can be processed, the sender must be defined in the receiver’s integration processing system. X.1.2 Key Business Model Assumptions This transaction may be used to test connectivity in test, quality and production environments. The response to a HelloPartner is a ReceiptAcknowledgment or ReceiptAcknowledgmentAcception. It is not necessary for both partners to initiate a HelloPartner transaction to confirm functional dial-tone. X.2 Business Process Diagrams with Descriptions X.2.1 HelloPartner The business process model for exchanging HelloPartner is depicted in the following diagram. Hello Partner Documentation Revised: 1/29/2004 $ASQHelloPartner Data Model.doc.doc Page 2 of 3 Sender Receiver Wants to confirm connectivity with a Partner Wants to connect with partner1 HelloPartner HelloPartner The HelloPartner process is Sender-initiated. The Sender generates the HelloPartner from their system. Transmission of this HelloPartner must be directly between the Sender and Receiver. The process ends when the Receiver sends a Receipt Acknowledgement. Disapproval is likely handled by e-mail notification or phone conversation. Disputed resolution is an off line process directly between the Sender and Receiver. B2B Model In a B2B process, directly between Sender and Receiver a HelloPartner is created by the Sender and transmitted to the Receiver. X.2.1.2 Scenarios for HelloPartner A HelloPartner is always Sender-initiated. There are four possible outcomes: • The Sender generates a HelloPartner and Receiver returns a receipt acknowledgement. • The Sender generates a HelloPartner and Receiver returns a receipt acknowledgment exception. In this scenario the transaction should still be considered complete in that both integration servers have successfully communicated. • The Sender generates a HelloPartner and Receiver returns a receipt acknowledgment general exception. In this scenario the transaction should still be considered complete in that both integration servers have successfully communicated. • The Sender generates a HelloPartner and does not receive a 200 IP return code. Debugging is required at this point. • The Sender generates a HelloPartner and the Receiver is not able to post one of the receipt acknowledgments. Debugging is required at this point. X.3.1 Release Information April 2004 Scheduled publication date Hello Partner Documentation Revised: 1/29/2004 $ASQHelloPartner Data Model.doc.doc Page 3 of 3 X.3.2 HelloPartner Data Model The following diagram shows the graphical representation of the HelloPartner Data Model: Insert diagram here: Appendix D – Data Dictionary HelloPartner Definition: Structure with information required to test network Dial-tone Datatype: Structure HelloPartnerBody Definition: EStandards Body Structure. Contains the message-specific metadata in up to two sections: Properties and Details Datatype: Structure HelloPartnerProperties Definition: EStandards Properties Structure. It contains the message ‘meta-data’ or ‘common data’. Datatype: Structure HelloPartnerDetails Definition: EStandards Details Structure. It contains the remainder of the message data which was not covered under “Properties” (which is the message ‘meta-data’ or ‘common data’). Datatype: Structure HelloPartnerMessage Definition: Free-form textual description of message Datatype: String Datalength: 1,255