ILOG Rules for .NET on the Microsoft platform creates powerful solutions for the enterprise.

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

6. Architecture 06/02/09 ILOG Internal

7. Rule Solutions for Office Systems Delivering Value to business analysts

10. Problem List 06/02/09 ILOG Internal

11. Rule Studio

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

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

16. Enterprise Management 06/02/09 ILOG Internal Supported Clients Performance Monitor Windows Event Log Services Console Local Application Remote Application RES .NET

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

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

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

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

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

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

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

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

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

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

32. Any Questions 06/02/09 ILOG Internal