I create one fuse project using Jboss developer studio with apache camel spring context..
Currently I am running my project in local machine in internal Jboss-eap of Jboss developer studio. Now i want to deploy my project in application server or container.
Please give me answer of below question :
1) What should i use : fabric8 or osgi?
2) What are the dependency need to add in pom.xml for deployment?
3) I have jboss-fuse-6.1.0.redhat-379 , as per my understanding it is container. For deploy my project in server should i required any application server like jboss-eap?
4) As i am using maven for dependency, should i need to copy my maven local repository to server?
I suggest to read the JBoss Fuse 6.1 documentation - there is a deploying into the container guide
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Deploying_into_the_Container/
As you have JBoss Fuse then its a container by itself, so you do not need JBoss EAP - its two different containers.
You can deploy from the Eclipse editor if you have the Fuse plugins installed (I think they are named integration stack). You can read how to install those plugins at the installation section from this page: http://tools.jboss.org/blog/
Related
I will ultimately be deploying my Vaadin web app to Tomcat servlet container.
In Tomcat, JDBC drivers generally need to be stored outside of the web app, in a separate Tomcat folder. So I do not want to add any JDBC driver as a dependency within my Maven build settings.
In the meantime, while developing I am running the Vaadin 8 or 8.1 web app (created from the vaadin-archetype-application Maven archetype) from within IntelliJ 2017.1 using the Jetty servlet container that is somewhere mysteriously bundled (“embedded”?) within the project.
Where can I store my JDBC driver jar file(s) while developing with IntelliJ-Jetty combo?
This depends on wether you use Tomcat or Jetty as an "old fashioned" appserver, or if you use it as an embedded component in your application. The archetype you have used probably assumes the latter (adds jetty-plugin to pom), while it sounds like you want the first scenario. In that case, just install the driver in the tomcat or jetty instance you want to use, and create a run configuration in IntelliJ for that instance. If you need the driver compile-time, add it to the pom with scope "provided". If you want to just have it available to the jetty-plugin, add it as a dependency for that plugin (inside the plugin definition).
See this related question for more info about including dependencies only for embedded jetty.
We have a specific requirement that only Enterprise Archive (EAR) should be deployed on our application server (Web Logic).
Can spring-boot be used for such type of Enterprise applications?
As spring-boot provide an inbuilt Jetty/Tomcat server, can I use the jar/war to be deployed on Web Logic application server?
Also we have some external dependencies (not from maven central)
which have to be included in the pom. Does that impact spring-boot
configurations?
Of course it can - as Spring itself. You can read about it here http://www.virtual7.de/blog/2016/07/spring-boot-oracle-weblogic-server-12/
Yes, here is the instruction how to do it: http://docs.spring.io/spring-boot/docs/current/reference/html/howto-traditional-deployment.html
It depends what are those dependencies. There could be some conflicts, but any conflict can be resolved somehow :)
Previousally we where using JBOSS 5 and the codehaus plugin (http://mojo.codehaus.org/jboss-maven-plugin) to deploy war to JBOSS. We where using the jboss:hard-depoly maven goal. This goal could be executed even if my JBOSS server was not up
Recently we moved to JBOSS 7, and started using the plugin (http://docs.jboss.org/jbossas/7/plugins/maven/latest/) . we are now using the goal jboss-as:deploy goal. This plugin does not support hard-deploy and jboss must be started to run this goal.
Is there a specfic reason to not support the hard-deploy goal?Simply copying the war file to deployements directory in JBOSS 7 still works and why this goal is not included?
jboss-as plugin uses JBoss Management api to do everything it does. If Jboss AS7 is not up, there will of course be no JBoss Management endpoint handling requests. Having such hard-deploy would imply totally different approach - one would have to define JBoss home and parse its configuration offline. Since this is not in general supported by the plugin, I'd imagine that is the reason hard-deploy goal is not supported as well.
I'm developing a Worklight (v6.0) application. I have added Tomcat server in Eclipse server perspective. With that I have deployed my application, and it is working fine.
I want know, how can we deploy our application in an external apache server? i.e without adding Tomcat server in Eclipse.
You need to have another instance of Apache Tomcat installed on your computer - simply download and extract it somewhere in your hard disk.
You need to then "install" to it the Worklight framework files and prepare databases based on your worklight.properties setup.
Then you need to simply deploy your project's .war file to it (can be found in the bin folder in your Worklight project), followed by deploying your .adapter files and application .wlapp files (also found in the bin folder).
Assuming you are an IBM Worklight customer, then after extracting Tomcat in your HD, you can and should use the IBM Installation Manager and Ant task scripts to handle the rest (deploying Worklight framework, setting up the database, deploying the .war file).
See this topic in the IBM Worklight 6.0 Information Center:
Installing Worklight Server
If you prefer to work manually...:
Deploying a project WAR file and configuring the application server manually
Note that the Worklight framework .jar file is available ONLY to customers of IBM Worklight.
I have an standalone Apache ServiceMix 4.4 application, it works nicely. Now, I want to deploy this application inside a JBoss Application Server 7. I use Maven as project and dependency management tool.
My objective is deploying the application not touching any line of code, only maven POM files. I can add new dependencies, change some versions (minor) and use different tools. I want, as a second objective, integrate all the Apache CXF DOSGi container features into JBoss AS ones seamlessly.
I think it is possible, but I found information for old releases of JBoss and ServiceMix or incomplete guides like this.
Can someone provide more information about that?
EDIT
I have found some issues in JBoss issue tracker:
Initial runtime support for Karaf based products
And some JBoss forum topics:
Migrating osgi bundles running in Karaf to JBoss 7 as OSGI container
I forgot to mention that my application is using Apache Karaf OSGi runtime.
Well Servicemix is "pre-"setup of a Container (Apache Karaf) and lot's of other Apache Projects like ActiveMq and Camel plus some ServiceMix specialties. So why would you want to deploy this setup in another Container?
If you want to do something like this, try to deploy std. Apache Camel, ActiveMQ and CXF and your own app in JBoss.