-
1. Re: Application specific configuration
john-liptak Sep 16, 2014 9:11 AM (in response to staleks)1 of 1 people found this helpfulWhat we do is have an operational "starting" configuration file and allow applications to modify it with delivered CLI files.
This allows the changes to the standard to be easily reviewed and a reasonable amount of flexibility. We simply process the files in filesystem order with a find command.
-
2. Re: Application specific configuration
staleks Sep 16, 2014 9:18 AM (in response to john-liptak)First let me thank you for quick answer.
So if I understood you correctly, starting point anyway is standalone that comes as part of EAP distribution. And than there is CLI tool that can execute script file that will change "original" standalone.xml file and modify it to application specific settings, right ?
What happens if you want to upgrade EAP (e.g. from 6.2 to 6.2.4) ? Then administrators would have to install new version, re-run same script file and then deploy my foo.ear, again?
-
3. Re: Application specific configuration
john-liptak Sep 16, 2014 10:13 AM (in response to staleks)1 of 1 people found this helpfulActually, our starting point is a modified standalone.xml file that has things like our JAAS realm, JDBC drivers, and other standard corporate items pre-added.
In our configuration, the CLI scripts are re-run for every installation: dot release of software, upgrade, etc. They are generally quick and allow any machine to take an application with a minimum of fuss.
With the new EAP patching technique, usually the standalone.xml file does not need to be changed. But we always test the upgrade anyway. Major upgrades (like 6.2 to 6.3) we do a re-install.