Overview:
=========
  This Quickstart demonsrates how the ActiveBPEL BPEL Engine can be used to
  orchestrate business process flow through JBoss ESB.

  It also demonstrates a number of other features of the ESB:
  1. Exposing a Webservice interface for a Service that doesn't have a
     Webservice interface (using the SOAPProcessor action).  In this example,
     the Service being exposed is a legacy EJB based Order Management Service.
  2. How to use a jaxb-intros.xml config to "Introduce" JAXB Annotations on a
     Java interface/typeset that isn't annotated for use with JAXB and how to
     add this config on a JBossWS Webservice endpoint deployment.
  3. Easily transforming a CSV based notification message into a Java object
     that's then used to populate a SOAP request. See next.
  3. Making an invocation on an external Webserivce from within an Action
     Processing Pipeline using the SOAPCleint action.

  See docs folder.

Running this quickstart:
========================
  Please refer to 'ant help-quickstarts' for prerequisites about the quickstarts
  and a more detailed descripton of the different ways to run the quickstarts.

  Note, this quickstart requires an ESB and JBossWS installation into
  JBoss AS 4.2.1.GA.  Installation instructions for both can be found in the
  install/readme.txt.

  NOTE: This Quickstart DOES NOT run Standalone, or on the ESB Server.  It only runs on the
        JBoss Application Server (v4.2.xGA).

  The ActiveBPEL Engine (v3.1) must now be installed on an instance of Tomcat on your
  system.  The processes in this Quickstart are pre-built to run on version 3.1 of
  the ActiveBPEl Engine.  If you are running on a newer version of the ActiveBPEL
  Engine, you may need to redeploy these processes.  
  
  Version 3.1 of the ActiveBpel Engine can be downloaded from:
     http://www.active-endpoints.com/active-bpel-engine-download.htm#final31

  ActiveBPEL Installation Guide:
     http://www.active-endpoints.com/installation-guide.htm
  
  Setting up ActiveBPEL:
  1. Ensure that the value of the 'directory' attribute on the
     'notificationChannel' (jboss-esb.xml) matches the value of the
     'order.approval.drop.location' property in
     'webservice_bpel/services/order-manager/order-manager.properties'.
  2. Make sure your Tomcat deployment at '${env.CATALINA_HOME}' is configured
     such that it's ports do not clash with those of your running JBoss AS. See
     '${env.CATALINA_HOME}/conf/server.xml'.
  3. Make sure your Tomcat deployment at '${env.CATALINA_HOME}' is configured to
     listen for HTTP traffic on port 18080. See
     '${env.CATALINA_HOME}/conf/server.xml'.
  4. Start your Tomcat deployment at '${env.CATALINA_HOME}'.
  5. Goto 'Deployed Processes' on the BPEL Console
     (http://localhost:18080/BpelAdmin) and confirm that the 'Customer' and
     'OrderProcess' BPEL processes are deployed.

To Run:
=======
  1. In a command terminal window in this folder, type 'ant deploy'.
  2. Start your favorite SOAP client (e.g. SOAPUI) and load the
     'RetailerService' WSDL (http://localhost:18080/active-bpel/services/RetailerService?wsdl).
  3. Load the SOAP client (RetailerServiceBinding/SubmitOrder) with the sample order in
     'bpel/resources/sampleData/submit-order-01.xml'.
  4. Submit the new order using the SOAP UI client.
  5. View the state of the new process in 'Active Processes' on the BPEL
     Console.  Will appear as 'Running'.
  6. Drill into the 'Running' OrderProcess process (select it).
  7. Drill down, you will see that the process is waiting on an
     acknowledgement/notification from the OrderManager service
     (WaitForNotificationFromOrderManager).
  8  Goto http://localhost:8080/order-manager/ (note, not port '18080').
     From here, you can approve the order.
  9. When finished, undeploy the application by typing 'ant undeploy'.
    