3 0 webinar

Post on 18-Dec-2014

1.325 Views

Category:

Economy & Finance

3 Downloads

Preview:

Click to see full reader

DESCRIPTION

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

TRANSCRIPT

Rules for .NET 3.0 and Managed Execution

ILOG Product Marketing

04/10/23 ILOG Internal 2

Rules for .NET 3.0

Why do organizations value a BRMS?

04/10/23 ILOG Internal 3

Rules for .NET 3.0

SOA and IT Alignment

04/10/23 ILOG Internal 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/

04/10/23 ILOG Internal 5

Rules for .NET 3.0

Microsoft Centricity

04/10/23 ILOG Internal 6

Architecture

Rule Solutions for Office Systems

Delivering Value to business analysts

04/10/23 ILOG Internal 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

04/10/23 ILOG Internal 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

04/10/23 ILOG Internal 10

Problem List

Rule Studio

Rule Studio: RES deployment

Rule Studio for .NET

RES .NET

Straightforward deployment from MS Visual Studio to the new RES execution component

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.

04/10/23 ILOG Internal 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

level) The RES Console based on MMC

04/10/23 ILOG Internal 16

Supported Clients

Performance Monitor

Windows Event Log

Services Console

Enterprise Management

RES .NET

Local Application

Remote Application

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 PerfMonCluster

Synchronization

IIS/ASP.NETIIS/ASP.NETIIS/ASP.NET

SQLServer

RES Console (MMC)

Console (MS Build)

Rule Studio (Visual Studio)

ADO.NET

Data Access

WCF

LDAP

ActiveDirectory

SharePoint (No Integration)

Clients

Future (Post Trinity)

RES.NET Features

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

RES and Windows Server 2003

RES and the Microsoft Solution Stack

Windows Communication Foundation (WCF)

Windows Service IIS/ASP.NETIIS/ASP.NETIIS/ASP.NETIIS/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 Support

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.NETIIS/ASP.NETIIS/ASP.NETIIS/ASP.NET

RES Console (MMC)

Console (MS Build)

Rule Studio (Visual Studio)

Other

Clients

WCF Clients

RES and the Microsoft Solution Stack

Public API

Execution• Stateless execution• Parameter support

Services

Management (Private API)

Persistence (Private API)

Execution (Public API)

Public API

RES Management and Persistence Services (Private API)

Persistence Service

WMI Service

ArchivesMeta 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)

Management and Persistence

RES Execution Service (Public API)

Execution Service Interface

Get Engine/Ruleset Instance

SingletonPool

ResponseObject Execute(RequestObject)

Pass In Parameters

Engine.Execute()

Process Out Parameters

Return Valid ResponseObject

Return Engine/Ruleset

Synchronized

Synch

roni

zed

WMI Notifications

Persistence Service

WMI Service

ArchivesMetadata

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

Execution

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 PerfMonCluster

Synchronization

SQLServer

ADO.NET

Data Access

WCF

LDAP

ActiveDirectory

Sub Systems

Future (Post Trinity)

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)

XOMAssembly

AppDomain

XOMAssembly

AppDomain

XOMAssembly

AppDomain

XOMAssembly

AppDomain

Hot Updates

File System

Rete Plus

FastPathRule Set

.NET Architecture

RES Physical Architecture: Single Server

Microsoft Windows 2003 Server

IIS / ASP.Net

Windows Services

FileSystem

SQLServer

LocalDirectory

Management Persistence

Execution

EventLogs

WMIService

Single Server

RES Physical Architecture: Dual Server

FileSystem

SQLServer

Directory

Management Persistence

EventLogs

WMIService

IIS / ASP.Net

FileSystem

Execution

EventLogs

SOAP over HTTP(S)WMI Client

DCOM TCP/IP SQL Server TCP/IP

WCF Binding TCP/IP

Management Server

Execution Server

Dual Server

RES Physical Architecture: Basic Cluster

FileSystem

SQLServer

LocalDirectory

Management Persistence

EventLogs

WMIService

DCOM TCP/IP SQL Server TCP/IP

WCF Binding TCP/IP

IIS / ASP.Net

FileSystem

Execution

EventLogs

SOAP over HTTP(S)Standard IIS LoadBalancing

WMI Client

Management Server

Execution Server

Basic Cluster

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

Clie

nts

HTTP(s)

DMZ Internal Zone

Client Application

Windows Server

HTTP(s)

Topology

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

Clie

nts

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.

E-Commerce 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

Clie

nts

HTTP(s)

DMZ Internal Zone

Client Application

Windows Server

HTTP(s)

Typical View

04/10/23 ILOG Internal 32

Any Questions

top related