The Camel routes used in this example are explained by the following diagram:
To run this example project build the project and deploy to ServiceMix
according to the steps below.
- Install JBoss Developer Studio 8.1.0 [https://www.jboss.org/products/devstudio.html]
- Install Apache Maven 3+ [http://maven.apache.org]
- Install JBoss Fuse 6.2.x [https://www.jboss.org/products/fuse.html]
- Build this project so bundles are deployed into your local maven repo
$ mvn clean install
- Start JBoss Fuse
$ bin/fuse
- Add this projects features.xml config to Fuse from the Console (makes it easier to install bundles with all required dependencies)
JBossFuse:karaf@root> features:addUrl mvn:org.fusesource.examples/rest-mft-ws/4.0-SNAPSHOT/xml/features
- Install the project.
JBossFuse:karaf@root> features:install rest-mft-osgi
- To calculate a digital signature required for sending test files, there are existing routes in the rest-mft-file module.
$ cp /target/calculateSignature
To see what happened look at the log file, either from the console
JBossFuse:karaf@root> log:display
or from the command line
$ tail -f data/log/fuse.log
For your test file, you will see an LAU value printed. Copy this value as you'll need it later.
- To test the WS, use apache-jmeter with the JMX project included in rest-mft-ws/src/test/jmeter. Update the JMX project to reference your test files, using the LAU calculated for each test file in step 5.
If you hit any problems please let the Fuse team know on the forums [https://community.jboss.org/en/jbossfuse] or contact me directly.