Bug 1040067 - Seeding Startup time.
Summary: Seeding Startup time.
Keywords:
Status: MODIFIED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Installer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Miroslav Sochurek
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-10 16:17 UTC by Nick Cross
Modified: 2019-02-22 22:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Enhancement

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nick Cross 2013-12-10 16:17:26 UTC 
Currently the installer has to start up an entire server to do the s-ramp seeding. This means any other wars (e.g. dtgov) will be started as well due to the .dodeploy files (to trigger startup of exploded wars). 

If these other dodeploy files were moved/renamed/etc temporarily by the installer so only s-ramp was started for the seeding this might make the installation quicker.
Comment 2 Thomas Hauser 2014-01-07 21:35:27 UTC 
Work for this feature has been completed and resides in a branch in the installer repo. It is not slated for inclusion in the FSW ga, however.
Comment 3 Thomas Hauser 2014-02-19 21:32:33 UTC 
The feature branch has been merged into installer-commons.
Note You need to log in before you can comment on or make changes to this bug.