Bug 724309 (BRMS-254)

Summary:	Expand the KnowledgeAgent API
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Tihomir Surdilovic <tsurdilo>
Component:	unspecified	Assignee:	Tihomir Surdilovic <tsurdilo>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	5.0.0 GA, 5.1.0 GA, 5.0.1
Target Milestone:	---
Target Release:	5.1.0.ER3
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/BRMS-254
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-04 18:07:37 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Tihomir Surdilovic 2010-02-01 18:48:29 UTC

Date of First Response: 2010-02-01 14:20:48
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/460493
securitylevel_name: Public

In a situations where multiple BRMS versions are deployed in HA environment the current KnowledgeAgent API is not capable to scan multiple locations for rule resources. KnowledgeAgent API should be able to scan multiple locations for the same resource or number of resources and be able to determine which location holds the "latest" version and pick that one up.

Also, If one of the BRMS instances goes down, KnowledgeAgent API should be able to switch to receive resource updates only from the BRMS instance that is still up.

Comment 1 Jaroslaw Kijanowski 2010-02-01 19:20:48 UTC

... and if no BRMS is up for a while, then use the local cache, until a BRMS is up again - then it should switch to it automatically and refresh the local cache.

Comment 2 Jeronimo Ginzburg 2010-02-01 19:33:07 UTC

I think agents following multiple sources is rather complicated. What does it happen if the BRMS instance that is up does not have the latest package version? Instead of it, it would be better that all BRMS instances are aware they are clusterized. When a user builds a new version of a package, the BRMS should send messages to all the other BRMS instances asking to update that package. The fail over between BRMS instances could be provided by any well known HA alternative (like mod_jk).

Comment 3 Tihomir Surdilovic 2010-09-07 19:04:27 UTC

Part of this was implemented through https://jira.jboss.org/browse/JBRULES-2219. I am not sure if rest of the request is still needed but there should be a corresponding Guvnor or JBRules Jira for it first.

Comment 4 Tihomir Surdilovic 2010-09-07 23:23:00 UTC

Link: Added: This issue depends JBRULES-2690

Comment 5 Tihomir Surdilovic 2010-09-07 23:23:47 UTC

Link: Added: This issue depends JBRULES-2219

Comment 6 Tihomir Surdilovic 2010-11-04 18:07:37 UTC

JBRULES-2219 / BRMS-348 resolve this issue as well.