How to deploy a web application manually in wildfly9?

Question

How to deploy a web application manually in wildfly9?

Navigation

#1 by (2 votes)

1

I have already deployed a web application manually in tomcat, I know it is not a complete container, but now I would like to deploy manually in wildfly9. I would like to deploy the web application manually in wildflyjá because I already tried to run by netbeans but I did not get it says the port is already being used and such. I've tried several tutorials, but it's all sort of old. If it is possible to deploy manually in wildfly, how should I proceed to do a deployment test using a helloworld application that I deployed in tomcat webapp to wheel on wildfly? What should I modify within the WEB-INF directory? Need to change anything in the standalone.xml file inside the wildfly directory?

Have I read the tomcat webapp is there something similar on wildfly?

To access an application running in tomcat, just open the browser and type localhost: 8080 / HelloWorld / index.html and do the same on wildfly?

java wildfly

asked by anonymous 02.04.2016 / 17:12

1 answer

Location container docker on host What would be equivalent to these two properties of persistence.xml in hibernate?

score 2 · Answer 1

If it is possible to deploy manually in wildfly, how should I proceed to do a deployment test using a helloworld application that I deployed in tomcat webapp to wheel on wildfly?

Yes it is possible. If you are using a standalone instance, you just need to include the artifact to be deployed in standalone/deployments , along with a placemark to deploy (if auto deploy does not is enabled). So if your artifact is called HelloWorld.war , also include an empty file named HelloWorld.war.dodeploy ( touch HelloWorld.war.dodeploy)

You can check detailed documentation here: Application deployment

It is also possible to deploy the web admin console, so after booting the server, go to http://localhost:9990 , enter username and password (you must create before using the add-user.bat or add-user.sh scripts), < Deployments button, Add button and choose the type and artifact to deploy:

Thenjustfollowthesteps...

WhatshouldImodifywithintheWEB-INFdirectory?Needtochangesomethinginthestandalone.xmlfileinsidethewildflydirectory?

Idonotknow,doyou?Youdependonsomethingprovidedbythecontainer,suchasdatasources,customsystemproperties,threadpool,socketbindings,etc.?Ifnot,justchangethedeployment-scanner(subsystemdeployment-scanner)tosomethinglikethis:

<subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0">
    <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" 
        runtime-failure-causes-rollback="${jboss.deployment.scanner.rollback.on.failure:false}" 
        scan-interval="5000" auto-deploy-zipped="true" auto-deploy-exploded="false" />
</subsystem>

This will cause% (%) to be set to war to be deployed, but not already decompressed applications (for this, change deployments to auto-deploy-exploded ).

Most things can be configured by the web console as well, such as system properties, socket bindings, datasources, mail sessions logs, etc.

Have I read the tomcat webapp is there something similar on wildfly?

Yes, as stated above is by default the directory true in deployments .

To access an application running in tomcat, just open the browser and type localhost: 8080 / HelloWorld / index.html and do the same on wildfly?

If standalone is the context of the deployed application and is using default WildFly settings, yes, that alone will suffice.

All of the above can be done by CLI, so consider reading about it: CLI Recipes

In case of problems, be more specific in your doubt:)