-
1. Re: Redhat JBOSS Fuse Deployment on different box
ffang Apr 24, 2014 7:58 PM (in response to rvashishth)Hi,
Not necessarily.
If you don't have local maven repo on the machine that has all necessary artifacts, the FUSE will download necessary artifacts for you automatically over internet, though it need internet connection available and it takes time to do this provisioning.
Freeman
-
2. Re: Redhat JBOSS Fuse Deployment on different box
davsclaus Apr 25, 2014 1:19 AM (in response to rvashishth)You can upload your war file to the built-in maven repo in JBoss Fuse. Or use the mvn fabric8:deploy goal to deploy your maven project that has the WAR file.
Some details here
- http://fabric8.io/#/site/book/doc/index.md?chapter=mavenPlugin_md
- http://fabric8.io/#/site/book/doc/index.md?chapter=mavenProxy_md
-
3. Re: Redhat JBOSS Fuse Deployment on different box
rvashishth Apr 25, 2014 2:34 AM (in response to ffang)So for this I have to use some repository tools i.e. artifactory as we use in our development environment. But as a standard practice we don't use any repository management tools on our production environment, we need to have a standalone bundle to be deployed in our production system i.e. war file for portal server, zip file for mule esb. I am looking for some docs around what is the best practice on Fuse for production environments.
-
4. Re: Redhat JBOSS Fuse Deployment on different box
davsclaus Apr 25, 2014 4:03 AM (in response to rvashishth)It depends. If you do not use fabric, then you can install your WAR on any box using
osgi:install
And that command support mvn, http, and file url handlers, so you can load the war from the file system or over a http. Or from a mvn repo.
-
5. Re: Redhat JBOSS Fuse Deployment on different box
davsclaus Apr 26, 2014 4:48 AM (in response to davsclaus)See also this thread