There are two ways to go about automatically deploying an app.
This article describes how to deploy the app by placing an EAR, WAR, JAR, or SAR to the appropriate monitoredDeployableApps subdirectory. Refer to this article for the steps on how to deploy an app by placing a properties file to the monitoredDeployableApps/deploymentProperties directory.
A significant advantage to adding a properties file to the deploymentProperties directory is that you have more control at your disposal, such as being able to easily define the application name, mapping the application to a virtual host, and defining the context root of the application in the properties file.
By default, WebSphere is not setup to automatically deploy an app. Follow these steps to setup WebSphere to automatically deploy an app, which will also create the monitoredDeployableApps directory and subdirectories.
Add an EAR, WAR, JAR, or SAR to the appropriate monitoredDeployableApps subdirectory
Placing an EAR, WAR, JAR or SAR file in the subdirectory will automatically deploy the app to the server or cluster. The app should be in the was_home/profiles/your_profile/installedApps/ directory. The date and time listed should correlate to the date and time that the app was deployed.
~]# ll was_home/profiles/your_profile/installedApps/ drwxrwxr-x 4 root root 4096 May 1 07:49 your_app_name.ear
You can now check if the application was successfully deployed.
When an app is automatically deployed, the app may not be automatically mapped to certain resources (virtual host, modules, JNDI, et cetera).
Removing the EAR, WAR, JAR or SAR file will automatically undeploy the app. The SystemOut.log can be checked to ensure the app was undeployed.
CWLDD0007I: Event id 123456789. Start of processing. Event type: Deleted, File path: /path/to/example.properties