Answered: JRules / IBM ODM BAL question

Thu, 31 Oct 2013 07:45:47 +0000

I solved this by writing the following methods in the source code of the XOM object:

private BigDecimal amount;

public BigDecimal getAmount() {
return amount;
}

public BigDecimal getCeilBasedCalc(int z, int x, int y, BigDecimal n) {
return ( new BigDecimal((z-x) / y ).multiply(n) ).setScale(0, RoundingMode.CEILING);
}

public void calculateBasedOnCeil(int z, int x, int y, BigDecimal n) {
this.amount = ( new BigDecimal((z-x) / y ).multiply(n) ).setScale(0, RoundingMode.CEILING);
}

And then verbalized the above in the BOM.

Answered: The difference between RetePlus, Sequential and Fastpath algorithms in IBM ODM

Thu, 31 Oct 2013 07:30:25 +0000

See the following at IBM InfoCenter for Webspehere Operational Decision Management:

Choosing an execution mode:

http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/index.jsp?topic=%2Fcom.ibm.wodm.dserver.rules.designer.run%2Foptimizing_topics%2Ftpc_opt_choose_execmode.html

RetePlus in simple terms allows objects in working memory (WM) to be inserted/deleted/updated, then evaluated and matched with the conditions on the rules. Any rules that do match get put into an agenda and then fired. If those rules change data in working memory, this could potentially fire more rules whose conditions match the changed objects. The cycle continues until there are no more rules that match the objects in WM.

Sequential pretty much runs through the rules in the specified order, firing off rules whose conditions match the objects then exits. Any changes to data will not be re-evaluated and will not fire further rules.

There is also Fastpath, that sits in between. It uses the condition matching capability of RetePlus (for performance reasons), but does not re-evaluate changed data (so is not cyclical).

Ask Ozar.net - Recent questions and answers in BRMS

Answered: JRules / IBM ODM BAL question

Answered: The difference between RetePlus, Sequential and Fastpath algorithms in IBM ODM