Comments on: COBOL Lives! In the business rules space at least http://jtonedm.com/2008/02/20/cobol-lives-in-the-business-rules-space-at-least/ James Taylor on Everything Decision Management Sun, 21 Mar 2010 19:03:55 -0700 http://wordpress.org/?v=2.9.2 hourly 1 By: IBM and ILOG - Java, COBOL AND .Net » JT on EDM http://jtonedm.com/2008/02/20/cobol-lives-in-the-business-rules-space-at-least/comment-page-1/#comment-13090 IBM and ILOG - Java, COBOL AND .Net » JT on EDM Fri, 23 Jan 2009 21:01:58 +0000 http://jtonedm.com/2008/02/20/cobol-lives-in-the-business-rules-space-at-least/#comment-13090 [...] has been moving beyond its Java roots ILOG has a COBOL version of its BRMS as well as a sophisticated .Net product with some very nifty integration with Microsoft [...] [...] has been moving beyond its Java roots ILOG has a COBOL version of its BRMS as well as a sophisticated .Net product with some very nifty integration with Microsoft [...]

]]> By: First Look - ILOG and Relativity for legacy modernization » Smart (Enough Systems, the blog) http://jtonedm.com/2008/02/20/cobol-lives-in-the-business-rules-space-at-least/comment-page-1/#comment-10595 First Look - ILOG and Relativity for legacy modernization » Smart (Enough Systems, the blog) Mon, 21 Jul 2008 16:10:13 +0000 http://jtonedm.com/2008/02/20/cobol-lives-in-the-business-rules-space-at-least/#comment-10595 [...] The initial integration with ILOG’s product takes this vocabulary across as well as copybooks etc. This would allow new rules to be authored using the same object model and vocabulary as that established in the model in Relativity. At present the candidate rules remain in the Relativity environment and are not moved into the ILOG repository but these candidate rules and some elements of ruleflow are next on the integration roadmap (though no date has been announced yet). In addition Relativity is working on decision tables and decision trees and the companies expect this to help with integration as many trees and tables should come across more or less wholesale. The current integration is with JRule and takes advantage of some of the features in Rules for COBOL (which I blogged about before). [...] [...] The initial integration with ILOG’s product takes this vocabulary across as well as copybooks etc. This would allow new rules to be authored using the same object model and vocabulary as that established in the model in Relativity. At present the candidate rules remain in the Relativity environment and are not moved into the ILOG repository but these candidate rules and some elements of ruleflow are next on the integration roadmap (though no date has been announced yet). In addition Relativity is working on decision tables and decision trees and the companies expect this to help with integration as many trees and tables should come across more or less wholesale. The current integration is with JRule and takes advantage of some of the features in Rules for COBOL (which I blogged about before). [...]

]]> By: COBOL živi! | Dan u životu kompanije http://jtonedm.com/2008/02/20/cobol-lives-in-the-business-rules-space-at-least/comment-page-1/#comment-7808 COBOL živi! | Dan u životu kompanije Mon, 25 Feb 2008 05:40:53 +0000 http://jtonedm.com/2008/02/20/cobol-lives-in-the-business-rules-space-at-least/#comment-7808 [...] COBOL živi!!! Bar u upravljanju poslovnim procesima :). [...] [...] COBOL živi!!! Bar u upravljanju poslovnim procesima :) . [...]

]]> By: Paul Haley http://jtonedm.com/2008/02/20/cobol-lives-in-the-business-rules-space-at-least/comment-page-1/#comment-7577 Paul Haley Fri, 22 Feb 2008 13:08:56 +0000 http://jtonedm.com/2008/02/20/cobol-lives-in-the-business-rules-space-at-least/#comment-7577 How do you compare sequential rule execution to the alternatives and why FI/Ilog offer both? Are there limitations on inference, scalability, and dynamic deployment that should be more widely understood? How do you compare sequential rule execution to the alternatives and why FI/Ilog offer both?

Are there limitations on inference, scalability, and dynamic deployment that should be more widely understood?

]]>