Bug 1105448

Summary:	Default installation too complicated.
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Marek Baluch <mbaluch>
Component:	Installer	Assignee:	Thomas Hauser <thauser>
Status:	CLOSED NOTABUG	QA Contact:	Tomas Livora <tlivora>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.2	CC:	kverlaen, mrietvel, rrajasek
Target Milestone:	CR1
Target Release:	6.0.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-13 15:53:13 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 Marek Baluch 2014-06-06 07:17:25 UTC

*** Description of problem:
The default installation path (only by clicking next, next, ...) is currently too complicated. It requires 5 distinct passwords to be entered.

Could we move somtehing to advanced settings? E.g. 'Configure JMS SSL keystores' screen which is saying that only some JMS messages require this setting.

Comment 1 Thomas Hauser 2014-06-06 14:15:49 UTC

Moving panels around is not a difficult task. The JMS SSL keystores was placed where it currently is because I was told that it should always be displayed (not optional). Do we want to make the JMS SSL keystores generation one of the 'advanced settings'?

Comment 2 Marek Baluch 2014-06-06 17:31:08 UTC

Looks like that the presence of a JMS SSL keystore may be mandatory for the JMS interface to function properly - in which case it will probably be better to leave the screen where it is. 

Let's see what Marco thinks about the idea.

Comment 3 Thomas Hauser 2014-06-10 19:25:50 UTC

Blocked by the needinfo flag;

Comment 5 Kris Verlaenen 2014-06-13 15:29:39 UTC

This part of the installer is required for the Remote API through JMS to work.  I would consider this a required step.  If we make it optional I would expect a lot of questions on how to configure it later (in case you skipped it in the installer) and on the JMS remote API not working (not realizing they skipped this in the installer).

Comment 6 Thomas Hauser 2014-06-13 15:53:13 UTC

We will keep the panel in the same location as it is now, based upon comments above.