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

Bug 947313

Summary:	BPEL engine didn't start unless we deployed a bpel sample first
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Ryan Zhang <rzhang>
Component:	BPEL Integration	Assignee:	Gary Brown <gbrown>
Status:	CLOSED DUPLICATE	QA Contact:	lvaskova
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	atangrin, gbrown, jsedlace, ncross, soa-p-jira
Target Milestone:	DR3
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:	2013-10-31 15:57:33 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 Ryan Zhang 2013-04-02 06:38:53 UTC

Description of problem:
After discussed with Jeff yu, this is somewhat a design issue.
BPEL engine is deployed with switchyard but it won't start until an bpel application is deployed. 

Jeff also think that it is somewhat an issue . So I track this problem here.
Hopefully we can fix it next riftsaw release or so.

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


How reproducible:
bpel-console can't start without deployed an bpel samples

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Gary Brown 2013-04-02 08:55:20 UTC

The decision to not start the BPEL engine until a process was deployed is based on a request from Keith Babo (switchyard lead), which I felt was sensible, as there is no point in starting up the engine if there are no switchyard apps going to use it.

Therefore first approach should be to see whether the problem can be addressed in a different way - e.g. if the BPEL engine has not been started, then simply display no information in the console, and don't allow any actions to be performed. Or alternatively display a message stating that BPEL is not available on this node and log them out :)

Comment 2 Jeff Yu 2013-04-02 13:05:26 UTC

I like Gary's idea. I can check the Engine on the authentication step. So if the engine is not started, I'll prompt the user in the login page. :-)

Comment 3 Ryan Zhang 2013-04-03 02:43:27 UTC

This sounds good to me too.

Comment 4 JBoss JIRA Server 2013-04-08 07:46:43 UTC

Jeff Yu <cyu> updated the status of jira RIFTSAW-532 to Resolved

Comment 5 Nick Cross 2013-04-22 20:45:27 UTC

Applied patch from Jeff:

 6a66542f0b3b81787b3776561700f68a5026828a - BZ947313/RIFTSAW-532: Update version to 2.4.3-1
 8e26aa87dd708f582c7518ecf4958cd03489158a - BZ947313/RIFTSAW-532: prompt user information on console when BPEL engine is not started.

Comment 6 Jiri Sedlacek 2013-05-14 13:48:36 UTC

The fix is verified in DR4, but I don't think this is the best solution we can provide to customers. They may want the browse the console even if they didn't deploy any process yet.

Comment 7 JBoss JIRA Server 2013-06-07 14:06:08 UTC

Gary Brown <gary> updated the status of jira RIFTSAW-532 to Closed

Comment 11 Jiri Sedlacek 2013-10-11 09:49:21 UTC

Gary, there should be some useful information for user shown why BPEL engine is not started and what to do to start it. Now user who sees it for the first time don't know what to do.

Comment 12 Gary Brown 2013-10-31 15:57:33 UTC

Closing this issue, as the duplicate issue will result in the user being logged into the console, even if BPEL process hasn't been deployed.

*** This bug has been marked as a duplicate of bug 1012019 ***