1 / 11

Enterprise Integration Project Proof of Concept I Review Daryl Shing December 5 th , 2006

Enterprise Integration Project Proof of Concept I Review Daryl Shing December 5 th , 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.

nohemi
Télécharger la présentation

Enterprise Integration Project Proof of Concept I Review Daryl Shing December 5 th , 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Integration ProjectProof of Concept I ReviewDaryl ShingDecember 5th, 2006 1

  2. 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 2

  3. Overall Integration Conceptual Architecture Design/Build Operation/Admin Internal/External User: AJAX Client (GI) Web Client Application Browser Administrator • Monitoring • Deployment • Operation Ctrl • Security Designer • IDE • Schema • Process Definition • Event • Test cases Presentation Layer: Web Server Portal Hawk • Monitoring • Rules Engine • Recovery Business Process Layer: Business Works Process Engine XML Canon • Version Control Common Services • Notification • Auditing • Scheduling • Exception • Transformation • Validation • Meta Data • WSDL Business Logic Layer: Application Server Legacy System Business Works Application Layer: EMS (JMS)/RV • Transportation MIS NMMS CS MMS EMS 3

  4. 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 TIBCO Operator UI Source Systems (MMS, CRR, etc..) Lodestar System Integration Layer Bill Determinant Pre-Processor Integration Layer Integration Layer Staging 4

  5. Logical Process Flow Extract Errors Validation Errors Process Errors Verify Errors Export Errors Created Extracted Validated Processed Verified Exported All Extracts Successfully Completed For Market All Extracts Successfully Validated For Market All Bill Determinants Created For Market All Bill Determinants Verified For Market All Bill Determinants Exported For Market 5

  6. POC Screens 6

  7. POC Screens 7

  8. Process Orchestration 8

  9. 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 RV Messaging Bus Integration Server Messaging Server Hawk Business Works Hawk JMS Rules Rules Rules Rules OS OS 9

  10. 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 Requirements Design Dev. Test Demo Requirements Design Dev. Test Demo Requirements Design Dev. Test Demo Requirements Design Dev. Test Demo Requirements Design Dev. Test Demo 10

  11. Questions 11

More Related