mike4soa building/testing/scaling Open ESB

Using the two BPEL projects from the Camel SE examples, this tutorial documents the steps to build the PORouter3 example, using a modified Camel router.

This Camel router checks the size of the orderPrice and if less than 500 routes to the file-writing-BPEL, otherwise routes to the database-inserting-BPEL.

1. build service units (SUs)
   1. build “database-insert BPEL” SU
   2. build “file-write BPEL” SU
   3. build “route-to-BPELs Camel” SU
2. create/configure/build PORouter3 Composite Application (Service Assembly)
   1. create Service Assembly
   2. add “route-to-BPELs Camel” SU
   3. add “database-insert BPEL” SU
   4. add “file-write BPEL” SU
   5. build Composite Application project
   6. add SOAP SU
   7. connect SOAP to “route-to-BPELs Camel”
   8. connect “route-to-BPELs Camel” to “database-insert BPEL”
   9. (skipped)
   10. connect “route-to-BPELs Camel” to “file-write BPEL”
   11. rebuild Composite Application project
3. Less Than 500 Test
   1. create testcase
   2. edit input
   3. run test and edit captured output
   4. rerun test
   5. inspect written file
4. Greater Than (or equal to) 500 Test
   1. create testcase
   2. edit input
   3. run test and edit captured output
   4. rerun test
   5. inspect database

---

Notes:
1. FYI, endpoint names are global in Open ESB, so for the sample projects we are using, only one Composite Application can be deployed (and started) at one time, to avoid endpoint-already-in-use kinds of errors. (alternatively, we could change the project names and namespaces in the wsdl to deploy similar Service Units in different Composite Applications at the same time).
2. at step 3, there should be no Composite Applications deployed. Running the test should perform several pre-requisite steps not mentioned explicitly in the tutorial steps, namely: start glassfish if needed, deploy the composite application, and start the Composite Application.