Posted on

Deploying applications using the Autodeploy folder

Oracle Weblogic Auto-deployment can be useful when performing development and continuous integration tests.

When the WebLogic Server instance is running in development mode, applications and modules in the autodeploy folder are automatically deployed. The folder which is used for autodeployment is WL_HOME>/user_projects/domains/domain/autodeploy

Due to Windows’ file locking limitations, if an application is exploded, all the modules within the application must also be exploded too. In other words, you cannot use auto-deployment with an exploded application or module that contains a JAR file.

Triggering redeployment (or undeployment) of an archived application is pretty easy: just replace the archive with the new one to trigger redeployment or delete it in order to undeploy the application.

Triggering redeployment of an exploded application is a bit more complex due to OS file locking limitations. In order to trigger redeployment, you need to update the timestamp (in Unix you can just use the touchcommand) of a marker file namedREDEPLOY.

The only thing you need to pay attention is the location where WebLogic server looks for the REDEPLOY marker files: The following table will assist you:

Application type

Location of REDEPLOY file

Enterprise Application

META-INF top-level directory

Web Application

WEB-INF directory

EJB Application

META-INF top-level directory

Application Server Comparison

As for Oracle WLS, also JBoss EAP 6 by default uses a marker file to trigger redeployment of an exploded application. Just the name changes: for JBoss users it’s application-name.dodeploy and needs to be placed in the deployments folder of your standalone server.