Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1054862

Summary: Cannot install S-RAMP into existing FSW
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Andrej Podhradsky <apodhrad>
Component: InstallerAssignee: Miroslav Sochurek <msochure>
Status: CLOSED UPSTREAM QA Contact: Len DiMaggio <ldimaggi>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: kejohnso, soa-p-jira
Target Milestone: CR2   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:34:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrej Podhradsky 2014-01-17 15:49:56 UTC
Description of problem:
I'm not able to install S-RAMP into an existing FSW. When I try to do this I'm asked for a vault keystore password (which is?). In the end the installation failed with the following error

Generation of key: /home/apodhrad/Temp/fsw/jboss-eap-6.1/standalone/configuration/vault.keystore has failed.

Version-Release number of selected component (if applicable):
CR1

How reproducible:
always

Steps to Reproduce:
1. Install EAP + SwitchYard + RTGov Server using FSW installer
2. Install S-RAMP using S-RAMP installer

Comment 1 Andrej Podhradsky 2014-01-17 16:02:29 UTC
When I try to install S-RAMP into an existing FSW using FSW installer I'm getting the following error

FSW cannot be layered with EAP and FSW

Comment 2 Thomas Hauser 2014-01-17 16:25:56 UTC
Hello Andrej,

The SRAMP installer is meant for use with the products that do not contain SRAMP themselves. So I'm not sure about the use-case you are describing :)

Comment 3 Andrej Podhradsky 2014-01-18 09:58:18 UTC
For example, assume you have FSW without S-RAMP. After some time you want also S-RAMP, how will you install it into your existing FSW?

Btw I see the same issue when I try to install DV into an existing FSW (maybe this is a DV issue).

Comment 4 Thomas Hauser 2014-01-20 16:57:48 UTC
To my knowledge, layering support has been moved to 6.0.1.

Comment 5 Alan Santos 2014-02-24 16:09:56 UTC
Is this a layering question or trying to install S-RAMP into an existing EAP footprint that was created by the FSW installer?

Comment 6 Thomas Hauser 2014-02-25 16:42:00 UTC
This is a layering question with FSW + SRAMP (SRAMP installed through the standalone installer at a later time)

Comment 7 Thomas Hauser 2014-03-05 21:01:44 UTC
The majority of the work for this issue has been completed in a branch on the fsw-installer and the sramp-installer repo. Changes must also be made to the zip assemblies for 6.1.0 in order for the layering to be possible. Note: one can also install SRAMP first, and then install FSW overtop of that with no issues (the installations are equivalent.)

Changes:
a) The SAML keystore generated by the first installation is reused in the second.
b) The vault created in the first installation is reused in the second.
c) The user created in the first FSW installation can be reused as well. The user is not able to create a user that would overwrite the first user created (this would break the first installation)
d) The script 'rt-gov-add-governance-conf.cli' has been divided in order to conditionally apply the /subsystem=messaging:new() command.
e) The jbpmDS datasource creation is only run in the first installation, since the second installation can use the same one.
f) A JDBC driver defined in the first installation can be used by the second.

Remaining items:
a) Security-manager modifications must be made conditional, to avoid appending the required JAVA_OPTS to the file twice. See https://bugzilla.redhat.com/show_bug.cgi?id=1054853

Comment 8 Thomas Hauser 2014-08-07 15:25:25 UTC
Bug 1054853 has been set to MODIFIED, so this bug is set to MODIFIED also.

Comment 12 Red Hat Bugzilla 2025-02-10 03:34:52 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.