SOA Governance Summit – Copenhagen 2007, October 2nd Service Registries Are Not Sufficient! Aligning Business and IT Goals using a Business Rule Management System and CentraSite Daniel Selman Product Manager, ILOG

Presentation Title | Date | Page 2 About ILOG Founded 1987 Publicly traded on NASDAQ and Euronext Over 2,500 customers Over 420 ISV/OEM partners Recognized market leader in business rules, optimization and visualization

Presentation Title | Date | Page 3 The Challenge Data Services ¬Easy to implement, easy to reuse ¬E.g. retrieving customer data from a single database Infrastructure Services ¬Challenging to implement, easy to reuse ¬E.g. coordinating a business process across multiple systems Decision Services ¬Hard to implement, complex to reuse, expensive to maintain ¬E.g. credit scoring, pricing, eligibility, up-sell, discounting…

Presentation Title | Date | Page 4 Understanding Transparent Decision Services? Business rules are expressed in a form accessible to their business stakeholders. Tracability from the decision service to the business rules. Service-oriented interface to a high- level business decision. Metric and reporting to drive reuse decisions.

Presentation Title | Date | Page 5 Transparent Rules are statements of business policy accessible to business owners ¬Not cryptic code! ¬Largely self-documenting ¬Reusable

Presentation Title | Date | Page 6 Role-appropriate Editors

Presentation Title | Date | Page 7 Transparent Decision Service Lifecycle 1.Define Transparent Decision Services signature (architect) 2.Implement business rules (business analyst or policy manager) 3.Deploy RuleApp (developer or business analyst) 4.RuleApp exposed as Web Service (administrator) 5.Publish Web Service definition to CentraSite (architect) 6.Publish service metadata to CentraSite (architect) 7.Query CentraSite Repository (architect 2 ) 8.Reuse Transparent Decision Service (architect 2 )

Presentation Title | Date | Page 8 Storing Transparent Decision Services in CentraSite Use the CentraSite Registry to manage Transparent Decision Services

Presentation Title | Date | Page 9 Looking at the Details of a Transparent Decision Service Use the Rule Details tab to access the business rules report for the Transparent Decision Service

Presentation Title | Date | Page 10 Technical Alignment: ILOG JRules and CentraSite 1.Architectural: JMX, Eclipse, Tomcat/J2EE, BIRT, repository 2.Core capabilities within JRules 1.Eclipse-based tools to model and implement rule-based services 2.Web Services without developer intervention or code deployment 3.Tracability from deployed rules to the business rules repository 4.Business rules reports for publication to CentraSite repository 5.Runtime statistics on usage of Transparent Decision Services 6.APIs to publish deployed service metadata to CentraSite

SOA Governance Summit – Copenhagen 2007, October 2nd Thank You!