mirroring 2.0 - tech forum 2009

Mirroring 2.0

Tech Forum 2009

Presentation

» Design goals

» Architecture

» Monitoring Mirroring

» New Functions

» Components and Modules

Design goals

- Better performance

- Higher volume

- More stability

- Reduce impact on site

- Better information and monitoring

- Improved extensibility

Architecture

Change page / file

Change Log

Editor

Change page / file

Source service

Change Log

Start mirroring

Editor

Export, make packages

Change page / file

Source service

Change Log

Target service

Start mirroring

Editor

Site

Export, make packages

Import

Change page / file

Source service Monitoring service

Change Log

Client WMIStart mirroring

Editor

Target service

Site

Export, make packages

Import

Change page / file

Source service Monitoring service

Change Log

Client WMIStart mirroring

Editor

Better performance Target service

Site

Export, make packages

Import

Change page / file

Source service Monitoring service

Change Log

Client WMIStart mirroring

Editor

Higher volume Target service

Site

Export, make packages

Import

Change page / file

Source service Monitoring service

Change Log

Client WMIStart mirroring

Editor

More stability Target service

Site

Export, make packages

Import

Change page / file

Source service Monitoring service

Change Log

Client WMIStart mirroring

Editor

Reduce impact on site Target service

Site

Export, make packages

Import

Change page / file

Source service Monitoring service

Change Log

Client WMIStart mirroring

Editor

Better information Target service

Site

Export, make packages

Import

Change page

Source service Monitoring service

Change log

Client WMIStart mirroring

Editor

Improved extensibility Target service

Site

Export, make packages

Import

Monitoring Mirroring

» Based on WCF

- Publisher / Subscriber

» Embedded loggning (Xml File, Tools to read and parse)

» Online/Offline monitoring

» Monitoring Httpmodule

- Send e-mail on failure

- See Monitoring Data from Source CMS Site

Mirroring & Monitoring Data Flow

CMS(S)

MS(S) MS(T)

MM

Monitoring Mirroring Clients

CMS(T)

MMS Proxy

Log File

XML

MTPMMD

(S) Source(T) TargetMS Mirroring ServiceMMS Mirroring Monitoring ServiceMMD Mirroring Monitoring DataMM Mirroring MonitoringMTP Mirroring transport Protocol

Monitoring Mirroring Data» Contains of

- General Mirroring

• ID, Name

• Source / Destination Info

• Total number of items in package

• …

- Package

• Type of Package

• Size of Data (Sent / Received)

• Time stamp (Sent / Received)

• …

- Status

• State, Exporting, Importing, Transferring, Error

• Processing / Exporting / Importing / Warning / Error Log

New Functions

Enable/Disable mirroring channel

Send Notification/E-mail on failure

Validation Source and target before mirroring starts (by default checks Pagetypes info (number of Properties and Type)

Check system configuration checks…

Send event on Exporting/Importing page

Continue on Error

Keep the packages that could not be mirrored and try them next time

Traceability on mirroring process Online/Offline

Provider based Transport Protocol

Components and Modules (1)

Mirroring Source Service

Based on WCF

Mirroring Transport Protocol

Based on Provider Base (plug-in-able), By default is WCF based.

Mirroring Target Service

Based on WCF

Components and Modules (2)

Monitoring Server

Based On WCF

Monitoring Client

Proxy to Monitoring Server

Monitoring Module

Send E-mail and customer can see the online information

Configuration (1)

Number of pages in export package

Number of files in export package

Number of byte should be send between Source and Target. By default is (4MB)

Which provider should handle transport. By default is based on WCF

Which user credentials should use between Source and Target services

Destination path for storing Export and Import packages

Configuration (2)

Enable/Disable on Channel

Validation on/off on Channel

Continue on error on Channel

E-mail notification on Channel