4.3. Deploying Configuration Files
- New login configuration, in
- New JMX console users, in
conf/directory for the application server.
The bundle must contain all of the files that are expected to be in the
conf/props/ subdirectories, not just the two new files that the administrator wants to use. Additionally, the
manageRootDir parameter in the recipe must be set to
false so that all of the existing configuration files in the root directory,
conf/, are preserved.
As with deploying a web app, the intent is to add new content, not to replace existing content. Setting
manageRootDir=false only preserves files outside the bundle deployment. However, because there are two subdirectories defined in the bundle, JBoss ON will manage all of the content in those subdirectories. This means:
- The recipe has to have
manageRootDir=falseset for the bundle to preserve the other files in the
- Any files in the subdirectories of the bundle —
conf/props/— will be overwritten when the bundle is deployed. The provisioning process can ignore files in the root directory, but it always manages (meaning, updates, adds, or deletes) files in any subdirectories identified in the bundle so that they match the content of the bundle.
- Existing files in the
conf/props/subdirectories must be included in the bundle distribution.
/opt/bundle/. Then, an Ant post-install task can be defined in the recipe that copies the configuration files from the root directory into the application server's