<?xml-stylesheet type="text/xsl" href="../../web/sc2html.xsl" title="scenario"?>
<scenario xmlns="http://www.wstf.org">
 <metadata>
  <number>sc011</number>
  <title>ProcessStandardCodes via ProcessMessage</title>
  <date>2010/10/20</date>
  <status>Preview</status>
 </metadata>

 <abstract>
    This scenario covers the basic process of submitting
    and receiving a basic STAR BOD (Business Object Document). For the purposes of this scenario
    the GetStandardCodes BOD (Business Object Document) will be submitted to the receiver and the
    ShowStandardCodes BOD (Business Object Document) will be returned. The StandardCodes Noun (subject of the Business Object Document) is often used
    for prototyping due to its simplicity and lack of potentially distracting business context. 
    <p/>
    STAR endpoints have two options, a generic WSDL which can
    accept any type of BOD (Business Object Document) (thus requiring only one endpoint) or a
   BOD (Business Object Document)-specific WSDL which requires an endpoint for each type of BOD (Business Object Document)
    submitted. This scenario will cover the more commonly used
    generic WSDL.<p/>
    <p>Username &amp; password authentication over SSL via   WS-Security is required by the basic STAR Web Services specification.  Endpoints implementing this
      scenario must implement authentication through use of a WS-Security username token (a test username and password is supplied with the scenario).
      It is also highly recommended that  endpoints implementing this scenario implement SSL enabled endpoints, but this requirement is relaxed only for this specific scenario 
      which is focused specifically on the basic STAR web services messaging.
    </p>
 </abstract>

 <section title="Dependencies">
    <scope>
      <technology name="SOAP 1.1"
      url="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/" />
      <technology name="WS-Security Username Token"
      url="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" />
    </scope>
 </section>

</scenario>


