1 of 1 people found this helpful
We got a production system running with the following configuration. The reason we went down the fuse fabric path was because it was in line with our product development that utilises ActiveMQ, Camel and CXF intensively. It was a pain getting started but its stable now.
Our processes deployed in Fuse are long running job interfaced through CXF, scheduled by ActiveMQ and routed through Camel.
Server A - zookeeper - application_container - broker master
Server B - zookeeper - application_container - broker slave
Server C - zookeeper - application_container
I still have the documentation pertaining to the installation if you interested.
thanks a lot for your answer - I would be very interested in the documentaion you mentioned...
We are also planning to set up Fabric in a production environment and I am also very interested in the documentation you mention. Care to share once more ?
Yes Fabric is production ready and there are already a lot of production deployments.
As the community around Fabric is growing, Fabric itself becomes more stable & robust.
If you are starting with Fabric now, I would suggest you to have a look at the alpha release of JBoss Fuse 6.1 (the final release is just a couple of months away), which contains tons of usability improvements (including git based profile datastore, improved management console based on hawtio & also a lot stability improvements).
I am also planning to set up Fabric in a production environment and I am also very interested in the documentation you mention. Care to share your insights again? Much appreciated!
I have used jboss-fuse-full-6.0.0.redhat-024 and jboss-fuse-full-6.1.0.redhat-139.zip for development. As for production I am using fuse-fabric-7.3.0.redhat-139.zip as the management is still deciding on the purchase of a license. The fuse-fabric-7.3.0.redhat-139.zip is similar to jboss-fuse-full-6.1.0.redhat-139.zip, with hawtio management and is the version supported by openshift.
The location for the drop is as follows:
Documents on Fabric installation on jboss-fuse-full-6.0.0.redhat-024 using the console mode.
Application Container - http://confluence.chnoumis.org/display/INFRA/Fabric+Broker?src=contextnavchildmode
Applying a similar installation using hawtio for fuse-fabric-7.3.0.redhat-139.zip was faster and simplified our fabric management. Do let me know if you require any other details.
If you are going down the OSGI development path then fuse platform gives you an edge. I am using CXF interface with multiple backend application. The business and web service interface bundles linked up with service and reference.
The only major issue I had with CXF was during the addition of org.eclipse.persistence.moxy to enable support for json and xml using a single xsd. It was solved by disabling the default jaxb-impl in fuse. The most annoying part was the enabling of OSGI on jars that are not OSGI compliant.
I have added the document as you had requested. Do take a look at it and let me know if you face any issue. It’s always good to have more people on a platform.