<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: First Look - ILOG and Relativity for legacy modernization</title>
	<atom:link href="http://jtonedm.com/2008/07/21/first-look-ilog-and-relativity-for-legacy-modernization/feed/" rel="self" type="application/rss+xml" />
	<link>http://jtonedm.com/2008/07/21/first-look-ilog-and-relativity-for-legacy-modernization/</link>
	<description>James Taylor on Enterprise Decision Management</description>
	<pubDate>Mon, 01 Dec 2008 21:55:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Mannes Neuer</title>
		<link>http://jtonedm.com/2008/07/21/first-look-ilog-and-relativity-for-legacy-modernization/#comment-10596</link>
		<dc:creator>Mannes Neuer</dc:creator>
		<pubDate>Mon, 21 Jul 2008 19:40:21 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=506#comment-10596</guid>
		<description>Hi, I am the Product Manager from the Relativity side and would like to thank James for this informative post on this topic which is generating a great deal of market interest.
I would like to flesh out one of the points  mentioned in it, regarding assistance we can potentiallyÂ provide to a rule  author in ILOG and the last paragraph statement: "there is also no work so far on how a user of the rules  environment would be able to access artifacts managed in Relativity to help them  write the rules correctly".
It is true that the current integration level  does not include a hyperlink (or similar reference) back from the ILOG authoring  environment to the underlying legacy declarations and usages. However, a  developer with JRules and Relativity Modernization Workbench (RMW) open side by  side, can query RMW for the use of any common term both in the application  sources and the Relativity candidate business rules. In addition, quick analysis  will uncover upstream data and control flow dependencies. This result will help  inform the author on legacy behavior to consider when authoring the new Rule in  JRules.
As we continue to enhance the integration between our respective tools, I will be happy to continue and inform this community on our progress.
</description>
		<content:encoded><![CDATA[<p>Hi, I am the Product Manager from the Relativity side and would like to thank James for this informative post on this topic which is generating a great deal of market interest.<br />
I would like to flesh out one of the points  mentioned in it, regarding assistance we can potentiallyÂ provide to a rule  author in ILOG and the last paragraph statement: &#8220;there is also no work so far on how a user of the rules  environment would be able to access artifacts managed in Relativity to help them  write the rules correctly&#8221;.<br />
It is true that the current integration level  does not include a hyperlink (or similar reference) back from the ILOG authoring  environment to the underlying legacy declarations and usages. However, a  developer with JRules and Relativity Modernization Workbench (RMW) open side by  side, can query RMW for the use of any common term both in the application  sources and the Relativity candidate business rules. In addition, quick analysis  will uncover upstream data and control flow dependencies. This result will help  inform the author on legacy behavior to consider when authoring the new Rule in  JRules.<br />
As we continue to enhance the integration between our respective tools, I will be happy to continue and inform this community on our progress.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
