3 0 Webinar
Upcoming SlideShare
Loading in...5
×
 

3 0 Webinar

on

  • 1,748 views

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

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

Statistics

Views

Total Views
1,748
Views on SlideShare
1,744
Embed Views
4

Actions

Likes
0
Downloads
28
Comments
0

2 Embeds 4

http://stage.ilog.com 3
http://www.slideshare.net 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

3 0 Webinar 3 0 Webinar Presentation Transcript

  • Rules for .NET 3.0 and Managed Execution ILOG Product Marketing
  • Rules for .NET 3.0
    • Why do organizations value a BRMS?
    06/02/09 ILOG Internal
  • Rules for .NET 3.0
    • SOA and IT Alignment
    06/02/09 ILOG Internal
  • Rules for .NET 3.0
    • ILOG and Microsoft Partnerships
    06/02/09 ILOG Internal
    • 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/
  • Rules for .NET 3.0
    • Microsoft Centricity
    06/02/09 ILOG Internal
  • Architecture 06/02/09 ILOG Internal
  • Rule Solutions for Office Systems Delivering Value to business analysts
  • RSO
    • Business Analysts can access, review, modify or create their business policies using Microsoft Office Word and Excel.
    06/02/09 ILOG Internal Word Document including ILOG Business Rules
  • 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
    06/02/09 ILOG Internal
  • Problem List 06/02/09 ILOG Internal
  • Rule Studio
  • Rule Studio: RES deployment Straightforward deployment from MS Visual Studio to the new RES execution component Rule Studio for .NET RES .NET
  • RES.NET Out-of-the-Box SOA
  • 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.
  • 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 level)
    06/02/09 ILOG Internal The RES Console based on MMC
  • Enterprise Management 06/02/09 ILOG Internal Supported Clients Performance Monitor Windows Event Log Services Console Local Application Remote Application RES .NET
  • 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)
  • 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
  • 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
  • WCF Clients RES and the Microsoft Solution Stack
    • Service Re-Use Model
      • Clients support service integration
      • Common APIs promote BRMS touch points
    Windows Communication Foundation (WCF) Windows Service IIS/ASP.NET IIS/ASP.NET IIS/ASP.NET IIS/ASP.NET RES Console (MMC) Console (MS Build) Rule Studio (Visual Studio) Other Clients
  • Public API RES and the Microsoft Solution Stack
    • Public API
      • Execution
        • Stateless execution
        • Parameter support
    Services Management (Private API) Persistence (Private API) Execution (Public API)
  • 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)
  • 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
  • Sub Systems RES and the Microsoft Solution Stack
    • 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
    Enterprise Logging API Trace API WMI Event Logs PerfMon Cluster Synchronization SQL Server ADO.NET Data Access WCF LDAP Active Directory Future (Post Trinity)
  • .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
  • 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
  • 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
  • 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
  • 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)
  • 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.
  • 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)
  • Any Questions 06/02/09 ILOG Internal