- Why would someone install into an existing AS7? Is there a
benefit?
This is main to support rpm installations. See this wiki page for some more info on the
rpm requirement:
https://docs.jboss.org/author/display/RHQ/Deploying+Via+AS7+Extension+Mod...
The point is - you should be able to install AS7 via rpm, then you can install RHQ's
rpm (in theory, the RHQ rpm would install AS7 rpm as a dependency). Our install scripts
are now such that with little tweaking, we should be able to get RHQ rpms working in the
future. That's the real reason behind this.
Would a non-dedicated RHQ server be recommended?
We always recommend/require that RHQ be installed in its own AS server instance.
- A simple install requires only a few settings:
Minimally, if the user really has to edit the properties file, those
few
settings should be grouped together at the top and well documented in
the file. We may want different sections for different DB vendors,
with all the typical presets (maybe it's like this already, I haven't
looked).
We can look into reorganizing that file with better comments.
But I'd rather see interactive command line scripts that walk
users
through simple installs, perhaps one for new server and one for
upgrade. Scripts that perform the various helpful things that the
GUI used to do.
This was proposed here:
https://docs.jboss.org/author/display/RHQ/Deploying+Via+AS7+Extension+Mod...
but for now, it was decided that building out a full blown, console-based user interface
for the installer that does much of what the old GUI insatller did was too much work for
now. We can look into this in the future. If we were to do this, we'd have to ensure
it supported i18n, too.