Punit & others:
Our guidelines were relatively simple. If a chunk of business logic was
"complex" and/or "dynamic", it was a candidate for a rules implementation.
By "complex", I really mean tricky to implement in procedural code and somewhat
simpler to implement in a rules engine. I'm not a rules expert -- not even
close. However, logic that uses pattern matching to create results sets and
further operates on those sets is a clear example of a solution that can be
implemented much more simply using rules technology.
By "dynamic", I'm referring to business logic that could change frequently as
our business partners refined their classification models and work distribution
algorithms.
Regarding business analysts writing rules:
The next phase of our project will incorporate a new tool from Blaze (known as
Innovator) that allows for rule development and deployment by non-IT personnel.
It amounts to a framework that allows IT to limit the freedom of the rule
developer to a defined set of operations. It includes the notion of rule
templates. Looks promising.
Hope this helps.
-Tom
-----Original Message-----
From: punit malik <[EMAIL PROTECTED]>
Sent: Thursday, May 04, 2000 3:03 PM
To: [EMAIL PROTECTED]
Subject: Re: EJB + ILOG JRules?
Tom,
Can you please share what motivated you to move business logic to rules
layer.
Can a business analyst write a rule without needing to code. If not what
does it buys?
punit
>From: Tom Larson <[EMAIL PROTECTED]>
>Reply-To: A mailing list for Enterprise JavaBeans development
><[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: EJB + ILOG JRules?
>Date: Thu, 4 May 2000 15:16:03 -0400
>
>We just completed a significant proof-of-concept/prototype that did exactly
>this, but used the Advisor Rules Server (ARS) from Blaze Software (as
>opposed to
>ILOG).
>
>Our experience was very favorable. ARS maps easily to java classes and
>interfaces and it is VERY fast. Their next major release will have much
>tighter
>integration with WebLogic Server -- but even in its current form, building
>that
>bridge was relatively simple. We're planning the project to produce the
>production version of what we prototyped. That solution will absolutely
>include
>ARS.
>
>Tom Larson
>Capital One Services, Inc.
>[EMAIL PROTECTED]
>
>-----Original Message-----
>From: Paul Perevalov <[EMAIL PROTECTED]>
>Sent: Thursday, May 04, 2000 10:40 AM
>To: [EMAIL PROTECTED]
>Subject: EJB + ILOG JRules?
>
>
>Hi,
>
>We are trying to move business logic of our application to separate layer
>using rules engine from ILOG (Jrules).
>Does somebody try this before?
>
>Thanks
>
>Paul Perevalov
>eDocFlow.com
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
