[jboss-rpm] Using RPM packaged JBoss AS in different location by different user

Marek Goldmann mgoldman at redhat.com
Fri Apr 13 16:46:19 EDT 2012



On 04/13/2012 07:12 PM, Carlo de Wolf wrote:
> On 04/13/2012 07:07 PM, Juan Hernandez wrote:
>> The original jboss-as configuration files are marked as
>> %config(noreplace), so they will be updated during "yum update" only if
>> the user didn't do any change since the initial installation. The
>> installation process of ovirt-engine does such changes (it edits
>> standalone.xml). This means that the update of jboss-as will never
>> update those files.
>>
>> Instead of that I think that the ovirt-engine configuration files should
>> go in /etc/ovirt-engine/jboss-as (and symlinked to
>> /usr/share/ovirt-engine/standalone/configuration). These configuration
>> files should be part of the ovirt-engine RPM and untouched during the
>> installation, so they are updated when ovirt-engine is updated with "yum
>> update", unless the end-user decides to manually modify them.
>>
>> (If at all possible I would use jboss-as system properties instead of
>> symlinks. Are there such system properties in AS7?)
>
> Right. No symlinks out or into /etc/ovirt-engine. That makes no sense.
> We'll just patch AS (if necessary) until it does work. :-)

We need to expose all available dir properties to the standalone.sh script:

	https://docs.jboss.org/author/display/AS71/Command+line+parameters

Then we'll be able to do it without symlinks.

--Marek



More information about the jboss-rpm mailing list