3 0 Webinar

Slide 1: Rules for .NET 3.0 and Managed Execution ILOG Product Marketing

Slide 2: Rules for .NET 3.0 Why do organizations value a BRMS? 2 04/18/08 ILOG Internal

Slide 3: Rules for .NET 3.0 SOA and IT Alignment 3 04/18/08 ILOG Internal

Slide 4: Rules for .NET 3.0 ILOG and Microsoft Partnerships  Gold Certified Partner  Business Process Alliance (BPA) (New)  VSIP Member  Windows Vista Server 2008 Early Access Program (EAP)  Office Business Application (OBA) Member http://www.microsoft.com/ilog/ 4 04/18/08 ILOG Internal

Slide 5: Rules for .NET 3.0  Microsoft Centricity 5 04/18/08 ILOG Internal

Slide 6: Architecture 6 04/18/08 ILOG Internal

Slide 7: Rule Solutions for Office Systems Delivering Value to business analysts

Slide 8: RSO  Business Analysts can access, review, modify or create their business policies using Microsoft Office Word and Excel. Word Document including ILOG Business Rules 8 04/18/08 ILOG Internal

Slide 9: Rule Solutions for Office System  Full Integration with Office 2007  Free-text editing in Word  Expansion of decision table capabilities in Excel  SharePoint updates  SharePoint deployment 9 04/18/08 ILOG Internal

Slide 10: Problem List 10 04/18/08 ILOG Internal

Slide 11: Rule Studio

Slide 12: Rule Studio: RES deployment Rule Studio for .NET RES .NET Straightforward deployment from MS Visual Studio to the new RES execution component

Slide 13: RES.NET Out-of-the-Box SOA

Slide 14: RES.NET Take-away  RES.NET is an SOA enabler  Shared decisions and complete encapsulation of business logic  Web Service invocation with WCF based on standards  Improved Business and IT alignment  Completes the BRMS offering  Scalability  Access control  Management  Alignment with Microsoft’s ecosystem  First BRMS on the market with native WCF services, WMI events and MMC 3.0 in a single package.

Slide 15: RES Console  Integrated in MMC  RuleApp  Creation / retirement  Deployment  Backup  Logs and trace  Log file / Windows event log  E-mail  Database ..  Performance monitoring  WCF counters  ILOG counters (Ruleset The RES Console based on MMC level) 15 04/18/08 ILOG Internal

Slide 16: Enterprise Management Supported Clients Performance Monitor Remote Application Windows Event Log RES .NET Services Console Local Application 16 04/18/08 ILOG Internal

Slide 17: RES.NET Features RES and the Microsoft Solution Stack Microsoft Windows Server 2003 Clients RES Console (MMC) Windows Communication Foundation (WCF) Console (MS Build) Windows Service IIS/ASP.NET IIS/ASP.NET IIS/ASP.NET IIS/ASP.NET Rule Studio (Visual Studio) SharePoint (No Integration) Services Management (Private API) Execution (Public API) Persistence (Private API) Enterprise ADO.NET Trace API WMI WCF Logging API Cluster Event Logs Data Access PerfMon LDAP Synchronization SQL Active Future (Post Trinity) Server Directory

Slide 18: RES and Windows Server 2003 RES and the Microsoft Solution Stack Microsoft Windows Server 2003 • Establishes the foundation • Integration for services • Integration for better management • Integration for lower cost of ownership • Positioned for Vista support in 2008

Slide 19: WCF Support RES and the Microsoft Solution Stack Windows Communication Foundation (WCF) Windows Service IIS/ASP.NET IIS/ASP.NET IIS/ASP.NET IIS/ASP.NET Enterprise Services with WCF • True services architecture • Protocol independence (SOAP, RPC, MQ) • Clustering Support • Integrated Security • “Contract First” Model for API • Extensible Service Model

Slide 20: WCF Clients RES and the Microsoft Solution Stack Clients RES Console (MMC) Windows Communication Foundation (WCF) Console (MS Build) Windows Service IIS/ASP.NET IIS/ASP.NET IIS/ASP.NET IIS/ASP.NET Rule Studio (Visual Studio) Other Service Re-Use Model • Clients support service integration • Common APIs promote BRMS touch points

Slide 21: Public API RES and the Microsoft Solution Stack Services Management (Private API) Execution (Public API) Persistence (Private API) Public API Execution • Stateless execution • Parameter support

Slide 22: Management and Persistence RES Management and Persistence Services (Private API) Rule Studio Share Point Enterprise MMC Console MS Build Management (Future) Persistence Service Management Service Publish/Update Ruleset Archives Data is passed Meta Data to this service Disable Ruleset for storage. Remove Ruleset The service notifies WMI of a WMI Service repository change. Events WMI notifies the execution service. It will update it’s pool.

Slide 23: Execution RES Execution Service (Public API) .NET Client Execution Service Interface Singleton ResponseObject Execute(RequestObject) Pool zed hroni Sync Get Engine/Ruleset Instance Persistence Service Data is passed Pass In Parameters d from the ize management on Archives service to this Engine.Execute() hr Persistence API service for Metadata nc storage Sy Process Out Parameters WMI Service Return Valid ResponseObject Events Return Engine/Ruleset WMI Notifications The execution service uses an observer to listens for This is vertical sequence diagram that shows a simple events that inform it about changes to the archives. The order of execution for the service. It also demonstrates service will then call the persistence service to update the the fundamentals of it’s interactions with the pool in a pool as needed. multi-threaded environment.

Slide 24: Sub Systems RES and the Microsoft Solution Stack Enterprise ADO.NET Trace API WMI WCF Logging API Cluster Event Logs Data Access PerfMon LDAP Synchronization Future (Post Trinity) SQL Active Server Directory Enterprise Foundation • Enterprise logging with event log support • Provider based RDBM support • Real-time tracing and performance monitoring • Cluster synchronization with meta data • Active Directory support day one • Support for MS SQL Server 2005 and Express

Slide 25: .NET Architecture RES Execution Architecture Microsoft .NET 3.0 ASP.NET Binding (SOAP) In Process (Named Pipes) Windows Communication Foundation (WCF) WCF Execute Interface Rule Flow Rule Set Rete Plus Parameters FastPath Hot Updates Rule Engine/Rule Set Pool WMI Observer (Singleton) AppDomain AppDomain AppDomain AppDomain XOM XOM XOM XOM File System Assembly Assembly Assembly Assembly

Slide 26: Single Server RES Physical Architecture: Single Server Microsoft Windows 2003 Server Windows Services IIS / ASP.Net Management Persistence Execution File WMI Event SQL Local System Service Logs Server Directory

Slide 27: Dual Server RES Physical Architecture: Dual Server Management Server Management Persistence WCF Binding TCP/IP File WMI Event SQL Directory System Service Logs Server SQL Server TCP/IP DCOM TCP/IP SOAP over HTTP(S) WMI Client IIS / ASP.Net Execution File Event System Logs Execution Server

Slide 28: Basic Cluster RES Physical Architecture: Basic Cluster Management Server Management Persistence WCF Binding TCP/IP File WMI Event SQL Local System Service Logs Server Directory SQL Server TCP/IP DCOM TCP/IP SOAP over HTTP(S) Standard IIS Load WMI Client IIS / ASP.Net Execution Balancing File Event System Logs Execution Server

Slide 29: Topology Rules for .NET Distributed Topology Management Server TCP/IP Port Z TCP/IP Port X Management LDAP Active Directory SQL Persistence TCP/IP Port Y Directory Server WMI Service Database Server Enterprise Management Clients DCOM TCP/IP MMC Console MS Build Execution Rule Studio Execution Server WebDAV HTTP(s) Share Point HTTP(s) HTTP(s) Client Application Collaboration Server Firewall Windows Server Internal Zone DMZ

Slide 30: E-Commerce View Potential Firewall Touch Points: Model 1 Management Server TCP/IP Port Z TCP/IP Port X Management LDAP Active Directory SQL Persistence TCP/IP Port Y Directory Server WMI Service Database Server Enterprise Management Clients rely on a (Optional) single port to the Clients DCOM TCP/IP management MMC Console service. Some management tools may MS Build require DCOM if Execution they are used Rule Studio from the Internal Zone. Execution Server WebDAV HTTP(s) Share Point HTTP(s) HTTP(s) Client Application Collaboration Server Firewall Windows Server Internal Zone DMZ

Slide 31: Typical View Potential Firewall Touch Points: Model 2 LDAP Active Directory Management Server Client Application TCP/IP Port X Directory Server Management Windows Server Persistence TCP/IP Port Y Enterprise WMI Service Management Clients HTTP(s) MMC Console DCOM TCP/IP MS Build Execution TCP/IP Port Z Rule Studio Execution Server SQL WebDAV HTTP(s) Share Point HTTP(s) Database Server Collaboration Server Firewall Internal Zone DMZ

Slide 32: Any Questions 32 04/18/08 ILOG Internal