Version 3.5 of the java-based, J2EE compatible business rules engine ILog has been announced today. ILOG JRules 3.5 will replace static business logic program code in an application with XML business rules, which can be easily updated, changed, shipped across the Internet and executed on trading partners' systems, etc.

Press Release:
--------------------------
PARIS and MOUNTAIN VIEW, Calif., May 29 /PRNewswire/ -- ILOG (Nasdaq: ILOG; NM France: SICOVAM: 006673) today announced the first step towards enabling business rule exchange over the web with the new ILOG JRules(TM) 3.5. The industry's first XML-centric business rule engine, ILOG JRules 3.5 will make it possible for business rules, representing business policy, to be dynamic and reusable in a standard format. XML-centric means that XML is the primary input/output method versus just another standard that is supported. ILOG JRules 3.5 can also deliver reduced deployment time and cost, and faster performance for applications that need to exchange XML data. This is particularly important for XML applications, which are known for having a high performance overhead, impacting system response time.

XML is fast becoming the standard for automating data exchange between business systems via the web, since it is simpler to use, more flexible and less expensive to implement compared with the electronic data interchange (EDI) format. However, XML on its own can only deal with data (like information from a database) and, while it can be used to provide some context, XML does not tell people who receive the data how to use it or what others might know about it. ILOG JRules 3.5 will address this by allowing business policy and knowledge about the data to travel with XML documents between applications. For example, XML would handle details of a customer profile, while business rules would handle customer preferences.

With the use of XML content increasing, improving XML processing performance is a major issue for companies doing business online, since the overhead associated with XML mapping can impact system performance. Since ILOG JRules 3.5 directly processes XML, performance is much better than competitors' offerings which use Java or proprietary software to map to XML objects. For developers, being XML-centric means development time and cost are reduced, since developers don't have to write additional code to access XML data, nor do they have to invest in additional software to do the parsing and translation of Java objects into XML.

Because ILOG JRules 3.5 has been completely re-architected to leverage XML data, it is more robust, efficient and generally suitable for XML applications than competitors products that have added XML support as an afterthought.

Business Rule Exchange Means Knowledge Becomes Portable

As the first step in the creation of a Business Rule Exchange, ILOG JRules 3.5 will replace static business logic program code in an application with XML business rules, which can be easily updated, changed, shipped across the Internet and executed on trading partners' systems, for example.

The availability of an XML-centric product will have an impact on a wide range of applications, including:


    -- In a trade exchange setting, business rules can be created in XML for
       affecting purchase requisitions, shipment dates, etc., so that
       companies can identify possible partners and suppliers instantly.
    -- For customer relationship management (CRM) applications, XML-centric
       business rules allow customer preferences to be defined that "travels"
       over the web with customer data.
    -- In enterprise application integration (EAI) applications, business
       rules can be used to determine how information, which is stored in
       disparate applications, needs to be manipulated and routed as part of a
       larger business process.


Business Rules for Business People Extends to XML

ILOG was the first to bring business rules for business people by offering a customizable business action language that allows business rules to be created in the language of a business or industry. ILOG JRules 3.5 continues this tradition of allowing non-programmers with more knowledge of customer needs to change the business rules that govern the application.

ILOG JRules 3.5 uses the full power of the ILOG business rule language to monitor and react to XML objects. This allows business people and others to construct business rules as usual using ILOG's Rule Builder environment.

ILOG JRules is fully Enterprise Java Bean (EJB)-compliant, which enables it to be easily embedded directly into a Java 2 Enterprise Edition (J2EE) environment. Many other business rule engines don't have this ability.

The product is also very lightweight with a footprint of just 300 Kilobytes. It is also extremely high performance. Recent benchmark tests show ILOG business rule engines can fire up to 18,000 rules per second.

Pricing and Availability:

ILOG JRules 3.5 is available immediately for HP-UX, Red Hat Linux, Sun Solaris and Windows NT/2000. Pricing starts at $10,000 for a development license.

About ILOG

Dually headquartered in Paris and Mountain View, Calif., ILOG is the world's leading supplier of C++ and Java software components. ILOG's embeddable optimization, visualization and business rules software components dramatically shorten development times for enterprise software applications in the supply chain, telecommunications, transportation and financial services industries. In addition to optimization applications where ILOG enjoys significant market share, the company is taking an active role in the e-business software-components market. Visit www.ilog.com for additional information.