With the recently released functionality in Fuse integration services on OpenShift we're able to run our integration services in a microservice style architecture in docker containers. We've been architecting services for Fuse like this for a long time, but now we can take advantage of the automation, process isolation, and packaging benefits of Docker which is crucial for a microservices style deployment.
Note, this project is currently focused on using the productized (Red Hat supported) versions of the FIS (Fuse integration services) libraries and frameworks from the http://fabric8.io project. The following versions of community projects can be expected in the productized release (please check the Red Hat documentation for official guidance on versions)
| Project | Version |
|---|---|
| Apache Camel | 2.15.1.redhat-621084 |
| Apache ActiveMQ | 5.11.0.redhat-621084 |
| Apache CXF | 3.0.4.redhat-621084 |
| Apache Karaf maven plugin | 4.0.2.redhat-621079 |
| JBoss Fuse | 6.2.1.redhat-084 |
| Fabric8 - kubernetes-model | 1.0.22.redhat-079 |
| Fabric8 - kubernetes-client | 1.3.26.redhat-079 |
| Fabric8 | 2.2.0.redhat-079 |
| iPaaS Quickstarts | 2.2.0.redhat-079 |
The Camel routes used in this example are explained by the following diagram:
You should probably set up the basic developer tools to be able to go through these steps, examples. We will also cover more ideal workflows with developer-local setup of docker and openshift, so would be good to install the "optional" tools as well!
- Install JBoss Developer Studio 8.1.0 [https://www.jboss.org/products/devstudio.html]
- Install Apache Maven 3.2.x [http://maven.apache.org]
- Install JBoss Fuse 6.2.1 [https://www.jboss.org/products/fuse.html]
- Have access to an OpenShift installation
- (Optional, but recommended) Install the Red Hat CDK Beta for local development
- (Optional, but recommended) Install the native docker client libs for your operating system
- (Optional, but recommended) Install the native openshift client libs for your operating system
$ mvn clean install
This project ends up building a few important things:
- the project artifacts
- builds the jars as Apache Karaf bundles (if wish to deploy into karaf -- not required though)
- builds an Apache Karaf features file (if wish to deploy into karaf -- not required though)
- kubernetes.json files for each module, found in
target/classes/kubernetes.jsonof each sub-module - a single, comprehensive kubernetes.json that has all of the submodule descriptor files to install all in one found in
rider-auto-ose-installer/target/classes/kubernetes.json
To build and install the Docker microservices, please have a look at the docs for each module, or the all-in-one installer
- All-in-one: rider-auto-ose-installer
- rider-auto-ws
- rider-auto-file
- rider-auto-backend
- rider-auto-normalizer
To deploy A-MQ and the Rider-Auto demo on OpenShift, follow these steps:
oc login -u system:admin
mkdir -p /tmp/rider-auto
chmod 777 /tmp/rider-auto
chown -R 185:root /tmp/rider-auto
chcon -u system_u -r object_r -t svirt_sandbox_file_t -l s0 /tmp/rider-auto
oc create -f rider-auto-file/rider-auto-file-pv.json
oc get scc hostaccess -o json \
| sed '/\"users\"/a \"system:serviceaccount:rider-auto:jboss\",' \
| oc replace scc hostaccess -f -
oc login -u developer
oc new-project rider-auto --display-name="Dev project"
oc new-app -f amq.json
oc secret new fis-config-rider-auto-backend rider-auto-backend/src/main/resources/org.fusesource.examples.rider-auto-backend.cfg
oc secret new fis-config-rider-auto-normalizer rider-auto-normalizer/src/main/resources/org.fusesource.examples.rider-auto-normalizer.cfg
oc secret new fis-config-rider-auto-file rider-auto-file/src/main/resources/org.fusesource.examples.rider-auto-file.cfg
oc secret new fis-config-rider-auto-ws rider-auto-ws/src/main/resources/org.fusesource.examples.rider-auto-ws.cfg
oc new-app -f rider-auto-backend/rider-auto-backend-template-fis.json
oc new-app -f rider-auto-normalizer/rider-auto-normalizer-template-fis.json
oc new-app -f rider-auto-file/rider-auto-file-template-fis.json
oc new-app -f rider-auto-ws/rider-auto-ws-template-fis.json
For oc new-app you may override the following paramters (by using -p):
| Parameter | Default |
|---|---|
| GIT_REPO | https://github.com/jcordes73/rider-auto-openshift.git |
| A_MQ_SERVICE_NAME | broker |
Now you should be able to access the web-service at http://rider-auto-ws-rider-auto.apps.example.com/cxf/order?wsdl.
To test the file-sercice, do the following:
cp rider-auto-common/src/data/message1.xml /tmp/rider-auto/
How to stage images is described in the article Promoting Applications Across Environments
To stage the images from dev to test, follow these steps
oc policy add-role-to-user view tester
oc policy add-role-to-group system:image-puller system:serviceaccounts:rider-auto-testing -n rider-auto
oc tag rider-auto/rider-auto-backend:latest rider-auto-backend:promote
oc tag rider-auto/rider-auto-normalizer:latest rider-auto-normalizer:promote
oc tag rider-auto/rider-auto-file:latest rider-auto-file:promote
oc tag rider-auto/rider-auto-ws:latest rider-auto-ws:promote
oc login -u tester
oc new-project rider-auto-testing --display-name="QA project"
oc secret new fis-config-rider-auto-backend rider-auto-backend/src/main/resources/org.fusesource.examples.rider-auto-backend.cfg
oc secret new fis-config-rider-auto-normalizer rider-auto-normalizer/src/main/resources/org.fusesource.examples.rider-auto-normalizer.cfg
oc secret new fis-config-rider-auto-file rider-auto-file/src/main/resources/org.fusesource.examples.rider-auto-file.cfg
oc secret new fis-config-rider-auto-ws rider-auto-ws/src/main/resources/org.fusesource.examples.rider-auto-ws.cfg
oc new-app -f amq.json
oc new-app -f rider-auto-backend/rider-auto-backend-staging-template-fis.json
oc new-app -f rider-auto-normalizer/rider-auto-normalizer-staging-template-fis.json
oc new-app -f rider-auto-file/rider-auto-file-staging-template-fis.json
oc new-app -f rider-auto-ws/rider-auto-ws-staging-template-fis.json
oc delete svc rider-auto-ws
oc expose dc rider-auto-ws --port=80 --protocol=TCP --target-port=8080
$ 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/rider-auto-common/5.0-SNAPSHOT/xml/features
- Install the project.
JBossFuse:karaf@root> features:install rider-auto-osgi
- To test the file processing, there are existing files in the rider-auto-common module.
$ cp rider-auto-common/src/data/message1.xml /target/placeorder
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
- To test the WS, use your favorite WS tool (e.g. SoapUI) against the following WSDL hosted by the rider-auto-ws bundle.
If you hit any problems please let the Fuse team know on the forums [https://community.jboss.org/en/jbossfuse]