Bug 1025060

Summary: Deploy to Fuse Service Works?
Product: [Retired] JBoss BPMS Platform 6 Reporter: Bill Kemp <bikemp>
Component: DocumentationAssignee: Eva Majorsinova <emajorsi>
Status: CLOSED DEFERRED QA Contact: Marek Baluch <mbaluch>
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 6.0.0CC: amelicha, brms-docs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 13464, Getting Started Guide-6-Beta-1 Build Date: 28-10-2013 13:46:10 Topic ID: 13681-546567 [Latest]
Last Closed: 2014-01-09 11:04:39 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:

Description Bill Kemp 2013-10-30 21:43:32 UTC
Title: Installation options

Describe the issue:

Documentation says bpms is deployable to FSW. If the EAP deployable zip is unzipped into the FSW directory, it will overwrite the configurations of the FSW deployment in the standalone-xxx.xml files. Works for EAP, but not FSW.


Suggestions for improvement:

Suggest a different installation procedure for installing on FSW.


Additional information:

Comment 2 Eva Majorsinova 2014-01-09 10:59:46 UTC
The deployment on FSW would have to be done with the installer, which is not currently prepared for it. We can compose the procedure when an installer supporting installation on FSW becomes available. Commenting FSW out of relevant guides for the moment.