
OpenEdge OrderInfo Sample Web Service
-------------------------------------------------------

This sample application provides customer and order information 
from the sports2000 database.  It demonstrates the use of static
TEMP-TABLES, connecting to the AppServer, and the use of SOAP Headers 
in a session-managed environment.

The Web service and sample client code is located in
   <DLC-DIR>/src/samples/webservices/OrderInfo

Included in the directory above are:
   /VB_client     - a VB.NET Web services client
   /Java_client   - a Java Axis Web services client
   /ABL_client    - an OpenEdge ABL Web services client
   /OE_webservice - the OpenEdge Web service


Running the Session-Managed OpenEdge Web service
-------------------------------------------------------- 

1. In order to run one of the sample clients that communicate with the 
   OrderInfo Web service application, you must perform the following tasks 
   in order to configure and deploy the Web service in the WSA environment:
        - Install and Configure a JSE
        - Install the WSA
        - Configure the WSA

   For details on configuring the WSA, refer to the "Configuring a Web Services 
   Adapter Installation" Section in the "Open Edge Application Server: 
   Administration" documentation.

2. Once you have completed the tasks to configure the WSA (mentioned above),
   you can then deploy the OrderInfo Web service. 

   Use the OrderInfo.wsm file (created by the Proxygen utility) found in
   the OE_webservice directory to deploy the Web service to the WSA instance.
 
   For details, refer to the "Deploying and Managing OpenEdge Web 
   Services" section in the "Open Edge Application Server: 
   Administration" documentation.

   When the Web service is deployed, you must then enable it. Details on
   this step are also discussed in the documentation just mentioned. 

3. On the system running the AppServer broker, create a subdirectory
   OrderInfo in your OpenEdge work directory. Copy all the .p's and 
   .r's from OE_webservice into this directory. Typically
   this same system is also running the WSA adapter.

   At this point, you should have an AppServer running.  
   The AppServer should be running with an asbroker1 AppServer instance 
   with its operating mode set to state-reset.  The OrderInfo directory
   should be on the AppServer's PROPATH.  
