6.2. Adding a Custom Deploy Directory
EAP by default looks for deployments under the
JBOSS_DIST/jboss-as/server/<instance-name>/deploy directory. However you can configure the server to include custom directories for scanning deployments. To do so, configure the BootstrapProfileFactory MC bean in JBOSS_DIST/jboss-as/server/PROFILE/conf/bootstrap/profile.xml file: add the custom directory to the applicationURIs property of the BootstrapProfileFactory, which defines a list of URLs scanned for applications (refer to Example 6.1, “The /home/me/myapps Directory Defined as Custom Deploy Directory”).
Example 6.1. The /home/me/myapps Directory Defined as Custom Deploy Directory
Important
After modifying the
JBOSS_DIST/jboss-as/server/PROFILE/conf/bootstrap/profile.xml file, you need to restart the server for the changes to take effect.
For performance reasons, adding a new deployment directory to the BootstrapProfileFactory also requires the same URL to be added to the
VFSCache MC bean configuration in JBOSS_DIST/jboss-as/server/PROFILE/conf/bootstrap/vfs.xml (refer to Example 6.2, “The /home/me/myapps Directory Added to VFSCache”).
Example 6.2. The /home/me/myapps Directory Added to VFSCache
Important
Not adding the custom deployment directory to the
VFSCache bean might result in growing disk space usage by the server.