Overview:
=========
  The purpose of the bpm5processor quickstart sample is to demonstrate the
  ability of the ESB to process an action on a single JBPM 5 process, and the
  ability of the ESBWorkItemHandler to send a message back to the ESB. 

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.

  This quickstart shows how to start, and then abort a process.   This 
  quickstart uses the jBPM 5 evaluation demo, starts the process as
  'krisv', and then aborts it.

  The session and process ID information are stored within the message
  context.


Setting up BRMS 
=======================================

Follow the SOA-P / jBPM5 Integration Guide steps to install BRMS on top 
of SOA-P and activate HornetQ within SOA-P.  

Copy the two MVEL files from this quickstart into jboss-human-task-server.war's
WEB-INF/classes/org/jbpm directory.

Then, edit the web.xml of jbpm-human-task-server.war

In the following section, specify the mvel scripts provided here to add users
for this example :

      <!-- DefaultUsers.mvel is used to insert Administrator as it is required for task server to operate -->
      <init-param>
        <param-name>load.users</param-name>
        <param-value>classpath:/org/jbpm/LoadUsers.mvel</param-value>
      </init-param>
      <!-- use classpath:/org/jbpm/task/servlet/SampleGroups.mvel to configure sample users for demo purpose-->
      <init-param>
        <param-name>load.groups</param-name>
        <param-value>classpath:/org/jbpm/LoadGroups.mvel</param-value>
      </init-param>

To Run:
===========================
  1. In a command terminal window in this folder ("Window1"), type 'ant deploy'.
  2. Open another command terminal window in this folder ("Window2"), type
     'ant runtest'.
  3. Switch back to Application Server console to see the output from the ESB
  4. In this folder ("Window1"), type 'ant undeploy'.


Expected Results:
===========================

The expected results here are that the first service starts a jbpm5 process in sample.bpmn that notifies an ESB process.   
The BPM5Processor action starts the process, and once the process is started, the ESBWorkItemHandler registered is used
to send a message to the second ESB service.    The second ESB service (EsbJbpm5Example:Printer) then prints the message
to the console.


0:10:21,484 INFO  [STDOUT] Message structure: 
00:10:21,490 INFO  [STDOUT] [Hello World].
00:10:21,514 INFO  [Bpm5Processor] startProcess
00:10:21,521 INFO  [InquiryHelper] uddi:juddi.apache.org:7e11d471-a7a3-4ae8-8530-eceb9de146de is modified Mon Jun 11 00:10:06 EDT 2012 1339387806742
00:10:21,560 INFO  [STDOUT] Message structure: 
00:10:21,561 INFO  [STDOUT] [ message: [ JBOSS_XML ]
header: [ To: JMSEpr [ PortReference < <wsa:Address jms:127.0.0.1:1099#queue/quickstart_bpm5processor_Request_abort/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:destination-name : queue/quickstart_bpm5processor_Request_abort/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 50410ca7-5f46-4cb7-81f8-13d9027cb9fc RelatesTo: jms:correlationID#50410ca7-5f46-4cb7-81f8-13d9027cb9fc ]
context: {}
body: [ objects: {org.jboss.soa.esb.message.defaultEntry=, ServiceName=Deferred serialized value: 5b1e4029, ServiceCategory=Deferred serialized value: 1f06727b} ]
fault: [  ]
attachments: [ Named:{}, Unnamed:[] ]
properties: [ {org.jboss.soa.esb.message.transport.type=Deferred serialized value: 11e85f2b, JMSXDeliveryCount=1, org.jboss.soa.esb.message.byte.size=2883, javax.jms.message.redelivered=false, org.jboss.soa.esb.message.source=Deferred serialized value: 2ec0093c} ] ]
