THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The BPEL XML file, servicemix.xml, contains two components and a supporting bean. One component waits for a file to be deposited into the the inbox directory, retrieves it, creates a normalized message that contains the file, then sends the message to the Normalized Message Router (NMR). The NMR routes the file to another component, which deposits it into an outbox directory.
Running the BPEL Example
This example uses PXE integration to demonstrate the use of BPEL with ServiceMix.
| Warning | ||
|---|---|---|
| ||
Note that ServiceMix works on any Java SE 1.4 or later environment; however to use PXE you need to use a Java SE 5 or later platform. So before trying to run this demo, use Java 1.5 to startup ServiceMix |
Firstly you need to run servicemix with a JNDI context configured so that PXE can be deployed.
| Code Block |
|---|
cd examples/bpel
servicemix servicemix.xml
|
You should now have PXE deployed with a JBI service engine together with a deployment unit for a specific BPEL process.
To trigger the business process you can send it messages. This happens by default if you type
| Code Block |
|---|
ant
|
which will compile and run a simple JMS client which performs a JMS based request-response into the ServiceMix container before returning the results to the console
We support WS-BPEL via the PXE BPEL Engine from FiveSight.
...