A very good question, and one I think very important to the Drools community. There is no doubt in my mind that Drools provides significant functionality that can address this question, but it is up to us as the user community to come up with specific use cases/stories that challenge the current framework and work out how to best use the functionality provided.<div>
<br></div><div>Looking at your options I would say that 2) is getting close, although for very complex organizations, there is no reason why you can&#39;t have multiple repositories. This may be more for organizational/political reasons. I think a run time rule agent does not care from which repository it gets it&#39;s rules, it is just a URL. </div>
<div><br></div><div>Option 1 - well it is just not scalable and will suffer from the usual infrastructure/deployment issues. There is no way I would attempt this. </div><div><br></div><div>The key question is how you structure your packages in whatever repository. Let&#39;s assume 80% of rules are common across all BUs, but each BU has variants.  Yes you could have a single ruleset/package with the variants included, but I suspect this will get sticky in time, particularly with changes and date effective rules.</div>
<div><br></div><div>So can you split this across multiple rulesets, again difficult for long term management. One of the initial issues is how to share a common fact model across multiple packages in the BRMS - it&#39;s on the do list for BRMS/Guvnor, and how do you manage versions across multiple versions!</div>
<div><br></div><div>As to your option 3, I don&#39;t think it will work. Nice in theory but will end up as a bottleneck. BU&#39;s need to control their rules and provide a capability to deliver functionality to market within their timeframes. Again a difficult problem and you need to analyze the scenarios, who needs to do what when.</div>
<div><br></div><div>Rather than ask a generic question, I would suggest you consider your problem space and post some concrete use cases that will engage the broader community. I&#39;m going to be looking at this problem area closely in the near future and it would be good to hear from others of the specific problems that the dev community can focus on to help solve our problems.</div>
<div><br></div><div><br><div class="gmail_quote">2009/8/11 Sumant Kumar <span dir="ltr">&lt;<a href="mailto:amulboy@yahoo.com">amulboy@yahoo.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><div><div>Can any body suggest the way to oraganize and share rules for mutiple business lines with each having multiple apps</div><div>Basically I am looking at Business Rule management , development and deployment best practices across the organization taking into consideration all Business Units that needs Rule based apps<span class="Apple-style-span" style="font-family: arial; font-size: small; "> </span></div>
</div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><div><div></div>
<div><br></div><div><br></div><div>option 1) Have one run time deployment (Expert engine) for all these apps with large memory.</div><div><br></div><div>option 2) Have one BRMS/Repository for all the rules in the enterprise across the business lines and then a sperate run-time for each app/business unit ?</div>
<div><br></div><div>If we assign a package for entire rules in a Business unit or BU_App can we have permissions around package so that certain project teams can work on
 those packages but not others.</div><div><br></div><div>Option 3) Should one team be responsible for all the rules in an enterprise ( across BUs ) and provide decision services to the corresponding apps in each BU ?</div>
<div><br></div><div><br></div><div>Any references on web is great!!</div></div><div></div></div><br>

      </div><br>_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
<br></blockquote></div><br></div>