Deliver WildFly with default deployment - deployment

WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final):
I am searching for a possibility to trigger the deployment of my Java EE application (packed as EAR file), without starting the WildFly server or using the deployment-scanner.
Is it possible to add the ear file to a configuration file, so that the server start the deployment of my application at the first time the server starts?

The server has to be started to deploy anything. You can use offline CLI to deploy the content. This wouldn't actually process the deployment until the server has been restarted.

Related

How to avoid deployment at each reboot JBoss EAP 7.2 server?

Every time I start jboss EAP 7.2.0 server (standalone), my ear file present in the "standalone\deployments" folder is deployed. Is it possible to avoid deployment at each reboot of the server?
Have a look at the documentation
So earfilename.ear.skipdeploy should do the trick.
Also if you undeploy the application a earfilename.ear.undeployed file is created. As long as this file exists the application won't be deployed.

Weblogic 12c deployment shared library not picked while deploying to managed server

Application is a EAR file
Shared Library where the third party jar are bundled and deployed to managed server as shared library.
weblogic-application.xml file where library ref to shared library is made and present in EAR file(META-INF folder).
Shared libraries are deployed to managed server as target and is successful.
while deploying the EAR file, the selection of EAR from console deployment results in ClassNotFoundException of the class present in shared library even though the reference is made in weblogic-application.xml.
Note that if the Library deployment is targeted to Admin Server and Managed Server the deployment of EAR file is successful without any exception.
Single Admin Server deployment is working fine without any issues for the same setup.
Deployment is expecting the JAR is classpath of admin server while deploying to managed server. is this an intended behavior ?
Is there any setup configuration we are missing here ? Correct me if there is any steps gone wrong.
Update : we did the same deployment with ant script using wldeploy and no errors are encountered and application is deployed successfully.
This was a known issue in a previous version of weblogic. Maybe it is still not fixed.
CR282367
While using the WebLogic Administration Console with applications or EJBs deployed on a Managed Server that depend on a deployed library, you may encounter a java.lang.NoClassDefFoundError
Workaround:
The WebLogic Server Administration Console needs access to any shared library deployments so that Java data types and annotations can be processed. Therefore, all shared library deployments should always be targeted to the Administration Server in addition to any Managed Servers or clusters.
https://docs.oracle.com/cd/E11035_01/wls100/issues/known_resolved.html

Run jboss 7.1 as service in domain mode in windows environment

I run the Jboss 7.1 as a service, but when I deploy the war through console it got deployed in data folder inside standalone folder.
To run Jboss 7.1 as service I refered to this link
It seems that Jboss getting started in standalone mode when I run it as a service.
Just an assumption, but have you tried replacing the run.bat properly with domain.bat rather than standalone.bat (the latter is shown in the post you followed)?

How to deploy war using CLI to individual instance than deploying to ha-server-group for jboss 6.0 eap?

Jboss version= 6.0 EAP
Need your inputs around Jboss deployment, currently we were deploying custom war files using jboss cli command like deploy custom.war --server-groups=ha-server-group
We have a requirement to deploy custom war into individual jboss servers (ha-server-1,ha-server-2) rather server group name.
Do we have any jboss cli commands which can be used for deploying war file into individual server….?.
Sorry to say but in Domain mode we cant deploy application on specific server which is part of the server-group.
If you deploy application on server group then it will be get deployed on all servers which are part of that server-group.In EAP 6 Domain mode, we can deploy application on server-group only.
If you want to deploy application on specific server instance then you can create new server group.

Deploy JBOSS FUSE 6 as service on application server

I want to deploy JBoss FUSE as war or in any other way on application server (Tomcat for example). In documentation for the old version (3.5) of FUSE there was described a simple way for doing that by running special maven project from examples folder.
But for later releases I just can't find any information about possibility of doing that. I thought that deploying ESB as a service on application server is standard way of working with it, but I only found tutorials for installing FUSE as standalone instance or system service.
I would like to know how can I deploy it or why I can't do this if thats the case.
This is no longer supported. JBoss Fuse 6.x is a standalone application that has its own container (based on Apache Karaf).
The current 6.x release requires running on top of Apache Karaf.
Though we have plans to make Fuse (that would be Fuse Fabric) container agnostic so you in the
future would be able to run Fuse on JBoss AS, Tomcat, Karaf, Standalone, in the cloud, etc. Though we focus on JBoss AS, Tomcat, and Karaf as the main containers at first we aim to support.