enterprise integration project 1 enterprise integration project proof of concept i review daryl...

1 Enterprise Integration Project

Enterprise Integration Project

Proof of Concept I Review

Daryl Shing

December 5th, 2006


The Goal of Proof of Concept I

• Perform a complete RUP Iteration within the EIP team.• Develop iteration one of the core integration approach.• Develop iteration one of the MMS to Settlements and Billing

integration (subset of billing determinants).• Develop iteration one of the Common Services.• Establish the Development Environment.

Requirements Design Development Test Demo


Overall Integration Conceptual Architecture

Application Layer:

Operation/Admin

MMS EMS

Business Logic Layer:

Design/Build

Designer•IDE•Schema•Process Definition•Event•Test cases

Business Process Layer:

Presentation Layer:

Portal

Application Server

Legacy System

BusinessWorks

Web Server

BusinessWorks

Process Engine

AJAX Client (GI) Internal/External User:

Web Client Application

CSNMMS

XML Canon•Version Control

EMS (JMS)/RV•Transportation

CommonServices•Notification•Auditing•Scheduling•Exception•Transformation•Validation•Meta Data•WSDL

Hawk•Monitoring•Rules Engine•Recovery

Administrator•Monitoring•Deployment•Operation Ctrl•Security

Browser

MIS


Settlement Integration Conceptual Architecture

• Interface requirements and a high degree of complexity dictated that an interface application that uses a staging approach was required to “bridge the gap” between MMS/CRR and Settlements

SourceSystems

(MMS, CRR, etc..)

LodestarSystemBill

DeterminantPre-Processor

Operator UI TIBCO

Integration

Layer

IntegrationLayer

Staging

Integration

Layer


Logical Process Flow

Created Extracted Validated Processed Verified Exported

All ExtractsSuccessfullyCompletedFor Market

All ExtractsSuccessfully

ValidatedFor Market

All BillDeterminants

CreatedFor Market


VerifiedFor Market


ExportedFor Market

ExtractErrors

ValidationErrors

ProcessErrors

VerifyErrors

ExportErrors


POC Screens


Process Orchestration


Monitoring & Management

• High availability with distributed architecture

• Monitors run time integration components (TIBCO, DBs, web-servers, HW/OS)

• Proactive event driven custom rules (shutdown/restart, send email/SMS alerts)

• Integrates with enterprise monitoring tools (i.e. HP OpenView) via SNMP

Integration Server

HawkHawk

RV Messaging Bus

Business WorksBusiness Works

Messaging Server

HawkHawk JMSJMS

OS OS

RulesRulesRulesRules RulesRulesRulesRules


Next Steps

• The next Iteration of the MMS to Settlements integration is being planned.

• Six iterations covering most of the major systems will be completed between now and March 31st, 2007.

• The team is incorporating lessons learned from POC I.

Requirements Design Dev. Test Demo







Questions

enterprise integration project 1 enterprise integration project proof of concept i review daryl...

Documents