<H3>Special Instructions</H3> <ul> <li>You must successfully test synchronous web services with a testing partner (XDS.b_Consumer_Query_Retrieve) before attempting testing asynchronous web services with that partner. The synchronous test must be graded and approved before starting asynchronous tests.</li> <li>To get credit for testing asynchronous web services for your actor, you must successfully test all transactions required of your actor over asynchronous web services. This requirement is described in detail in section 10.2.4 Asynchronous Web Services Exchange Option in the Async WS Exchange supplement dated 10/10/2008. </li> </ul> <H3>Description</H3> <p>This tests the query & retrieval of a document using Asynchronous Web Services:  Doc Consumer-->Doc Registry then Doc Consumer-->Doc Repository.</p> <ol> <li>Test though NIST proxy to allow evaluation of SOAP header attributes necessary for async web services. A NIST proxy (technically a reverse proxy) is running in front of each vendor actor that can accept an asynchronous web service transaction.   Configuration information is available from Bill Majurski.</li> <ul> <li>Configure the sending system (Consumer) to use the proxy.  This means the message will be sent to nist1:xxxx (where xxxx is the port assigned by NIST) but the HTTP header and the WS:To header will indicate the full target vendor actor endpoint.</li> <li>Confirm your configuration and the readiness of the NIST proxy with Bill Majurski of NIST before initiating the test.</li> <li>Evaluation of your WS: Headers will be done from the proxy console.</li> </ul> <li>Test directly with partner to show proper exchange of data.</li> </ol>  <H3>Evaluation</H3> <ul> <li>Be prepared to show system logs that allow verification of asynchronous nature of exchange.</li> <li>Be prepared to show proper actor operation.</li> </ul>