Application specific configuration

[staleks]

Hi all,

I must admit that I am new to JBoss EAP and therefore for some of you this question might sound strange.

After some time of work, I've developed foo.ear file that I want to deploy to JBoss EAP 6.2.4

What I've did so far, in process of testing, all the necessary properties for my foo application, I declared as system-properties in standalone.xml file. Further more all necessary dataSources are part of standalone.xml.

There are other application specific stuff that maybe it is not logical to assume to be part of standalone.xml, but rather some other configuration file, since that is specific to my application.

Now we come to the problem! As I am not in control of server, and I will never be (deployment of this application will be lead by TechOps guys), TechOps don't want to pollute standalone.xml file.They want to keep it clean as much as possible. And they are right. I understand their motives.

I need somehow to define properties like those system-properties and/or dataSources that I already was defining in standalone.xml configuration file. I guess there is a way that I can have foo.xml or similar that will hold specific stuff just for my application.

Can someone help me regarding this?

Thank You

[john-liptak]

What 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.

[staleks]

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?

[john-liptak]

Actually, 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.