Red Hat Bugzilla – Bug 996278
Feature request - Can the installer point to an EAP .zip in addition to, or rather than, point to the directory of an EAP installation
Last modified: 2014-09-04 10:27:17 EDT
Description of problem:
This will make installations much easier for users.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
There are a few problems I see with this feature:
a) What constitutes a valid EAP.zip? We can read the entire zip and check it against some kind of file or entry list, I suppose.
b) This given zip could then be extracted, but there would need to be additions to the UI (and likely IzPack itself) in order for this to work.
Generally to get this to work would take changing IzPack itself, which I would like to avoid doing this close to release time.
As mentioned in this document: https://docspace.corp.redhat.com/docs/DOC-147383 we now include EAP 6.1.0 in the installer.
Supported install directories:
a) Completely blank:
- The installer will lay down a new EAP installation
b) Existing directory with no jboss-eap-6.1 subdirectory:
- Same as a)
c) Existing directory with existing jboss-eap-6.1 subdirectory:
- If product.conf exists and contains slot=eap, continue
- If layers.conf does not exist, continue
- If either standalone.sh + standalone.xml OR domain.sh + domain.xml + host.xml exist, continue
- Install everything else excluding EAP.
If any of the above conditions aren't met, the user will get an error, as the given directory is assumed to be a modified (non-stock) EAP install. The user will have to use a different directory to install in this case.
Changing this bz to a feature request to be reconsidered after beta.
Is there any way to support users who have a different/newer EAP .zip file and want to install EAP from this zip and FSW/SOA6 from its installer jar in a single action.
Definitely will not be present in ER7.