1 / 102

V615 CeBS 1.x - Detailed Architecture

V615 CeBS 1.x - Detailed Architecture. Reed Shilts reed.shilts@sybase.com. Onion Model - Same Topics in More and More Depth What Is CeBS? Architecture Overview Overall, UI, Business Objects, EAI Connectivity Architecture & Implementation Details UI: goto V616 - “UI Framework”

giles
Télécharger la présentation

V615 CeBS 1.x - Detailed Architecture

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. V615CeBS 1.x - Detailed Architecture • Reed Shilts • reed.shilts@sybase.com

  2. Onion Model - Same Topics in More and More Depth What Is CeBS? Architecture Overview Overall, UI, Business Objects, EAI Connectivity Architecture & Implementation Details UI: goto V616 - “UI Framework” Framework Support, Business Object Layer, etc A Vertical In Detail Topics

  3. CeBS Communications eBusiness Solution Pronounced: See-Biz

  4. What Is CeBS “Open Framework For Customer Self Service for use by Telecommunication Carriers and Resellers” • Telco Business Process Aware • Framework - More Than An Application • Application - More Than a Framework • Useful Working Reference Implementation (Sample) • Works “Right Out Of The Box”

  5. Goals of CeBS • Designed to be customized • EAI to Legacy Systems • Integration with Data Warehousing for Mining • Security Security Security • Enable Collaboration • Useful Working Reference Implementation (Sample) • Works “Right Out Of The Box”

  6. Reference Implementation(sample) SybTel • The fictitious telecommunications provider. • This provides the web front end for legacy systems… • The source code is provided. • English, Spanish, and Chinese

  7. User View of the Reference Implementation

  8. CeBS 1.x Implementation • J2EE Application Using • Apache / iPlanet - Web Server • EAServer - JSP (presentation) • EAServer - EJB (business logic) • EAServer - EAI (connectors & listeners) • ASE - local customer database • ASE-IQ - data warehouse

  9. CeBS Implementation • Framework for Snap-ins • All the “framework” work is finished • Table Driven Configuration using XML “Glue” • Authentication & Authorization • Not industry specific • Role Based Security • Vertical Business-Centric • Telco industry specific

  10. CeBS Implementation - Framework Framework for Snap-Ins with built in… • User Management, Authentication, and Authorization • HTML Based UI Framework (MVC Pattern) • Business Object Dispatcher Pattern • EAI Dispatcher Pattern • EAI Listener Pattern • Fine Grained Feature Licensing • Uniform N-Tier Logging Throughout • Administration and Monitoring Tools

  11. CeBS Implementation - Open Architecture • Designed to be Extended • Designed to be Customized • ALL of the Sample JSP sources are shipped • Fully Documented APIs & XML for: • In-Bound - business object dispatcher • Out-Bound - BOS (EAI) dispatcher • Business and Data Access Objects • Connector, EJB, JSP, other Configuration • Extensive docs to EXTEND the existing application.

  12. CeBS 1.x Architecture Overview

  13. Architecture - 10,000 Foot View HTTPS HTML WML SOAP User Interface Layer Public API Dispatcher Pattern User Mgmt & Authorization Trouble Ticket Bill View Bill Analysis Shopping Cart Product Catalog Order Entry Message Center Retailer Info Etc... EAI Dispatcher Pattern EAI Listeners EAI Connectors

  14. Simplified Activity DiagramShowing Overall Control Flow User Interface Public API Business Objects EAI Dispatcher & Adapters

  15. Control Flow Overview -User Submits RequestServlets Translate to XML Request

  16. Business Object Dispatcher (BOD)Validates the XML Request

  17. BOD Forwards to Correct EJB

  18. BOD Forwards to Correct EJB…Work Happens…

  19. EJB Forwards to BOS Dispatcher

  20. BOS Dispatcher EnQueues Request

  21. Later - DeQueue and Send to Connector - which Sends to BSS

  22. Later….Listener Receives Asynch Message…

  23. Listener Sends to BODJust like Any Other Request…

  24. Architecture OverviewUser Interface Layer HTML, JSPs, & Servlets

  25. Context…. User Interface Public API Business Objects EAI Dispatcher & Adapters

  26. UI Layer - Philosophy • Provide a “Reference Implementation”. • Programmable by HTML Designers. • Details are hidden in servlets which look like HTML tags. • Allow 3rd Party Tag Libraries. • Enable I18N and L10N (even a Chinese sample!) • Not Just HTML - Future plans for WAP, Voice, … • Not Just ‘User’ - Future plans for WebServices (SOAP)

  27. UI Layer - OverviewModel - View - Controller JSPs Tags Action Engine Data Beans Actions Business Object Dispatcher (BOD) “Gateway to EJBs”

  28. UI Layer - Extending • Adding A New Vertical System • Write JSPs (using our tags) LIKE HTML • Write “Actions” (for MVC) • Add the mapping to ONE XML file • Done

  29. UI LayerFramework Details Refer to: V616 “CeBS UI Framework Overview” Time: 3:30 pm Date: Thursday Location:

  30. Architecture OverviewBusiness Object Layer EJB Logic

  31. Context…. User Interface Public API Business Objects EAI Dispatcher & Adapters

  32. BO Layer - Overview • Delegation Pattern, Factory Pattern • Easy To Extend • “Customer Information Database” (CID) • Local cache for Performance and Uniform View • Company, User, Account Mapping • Order, Product, Trouble Ticket History linked to BOS • XML throughout • Sharing between Verticals

  33. BO Layer - Overview • BO Dispatcher (BOD) - only point of entry • Converts XML to a binary tree (JDOM) • Layer of User Level Security Access Authorization • Table Driven for easy customization • Stateless Session Beans Throughout • Where the Business Logic Happens • Access to database (CID) • When Processed - forward to BOS Dispatcher • Some Entity Beans - Complex database relationships

  34. BO Layer - Extending • All Business Logic can be “SubClassed” • The Custom EJB can subclass or even delegate to our EJBs. • The Database CAN be Extended • Samples Provided

  35. BO Layer - Extending Adding A New Vertical System • Write your own EJBs or extend ours • Write a “task” for the BOD • Add the mapping to ONE XML file • Done • Bill Analysis Is PROOF - Implemented by B.I. Division

  36. Architecture OverviewBack Office System (BOS) Adapter Layer Back Office Integration

  37. Context…. User Interface Public API Business Objects EAI Dispatcher & Adapters

  38. BOS Layer - Overview • Generic – Talks to multiple BSS • Decoupled – from rest of CeBS • XML based Messages • Delegation Pattern, Factory Pattern • Easy To Extend • Table Driven and Table Configured • Base Classes Provided • Numerous Samples Provided

  39. BOS Layer - Overview • Synchronous • “Real Time Usage” Query • Seldom Used - Doesn’t Scale • Asynchronous • Typical UseTrue Real Time Response Typically Not Needed... • Store and Forward Queue • Any Technology - JMS, MQ, TIBCO, CORBA, JDBC…

  40. What are adapters • Critical integration software for communication between CeBS and existing backoffice systems • Connectors are responsible outbound messages • Listeners are responsible for inbound messages • Connectors and Listeners are collectively called adapters

  41. BOS Layer - Extending • Base Classes Provided • Samples Provided (JMS, MQ, TIBCO, Calculus Opera™, Ericsson Progressor™, ‘Synthetic’ BSS) • Write your connector • Write your Listener • Add the mappings to TWO XML files • Done

  42. CeBS Architecture Details

  43. CeBS Architecture DetailsTopics • User Interface • Support Subsystems in the Framework • Business Object Dispatcher (BOD) • Business Objects • Back Office Dispatcher (BOSD) • Security • Trouble Ticket Vertical in Detail

  44. CeBS Typical Activity Flow...New Trouble Ticket • Business Process Vertical • User Action - Create/Edit a Trouble TicketUI (JSP)  Data Beans & Action  BOD  BOD Task  EJB  BOSD  Connector  BOS • Process Notification (Asynch from BOS)BOS  Listener  BOD  PNTask  EJB

  45. CeBS Architecture DetailsUser Interface Layer

  46. CeBS User Interface Layer Refer to: V616 “CeBS UI Framework Overview” Time: 3:30 pm Date: Thursday Location:

  47. CeBS Architecture DetailsSupport Subsystems in the Framework

  48. Support Subsystems(horizontal) • Customer Information Database (CID) • Database and other helpers • Security • Customer Portfolio • Session Management • User Management • Message Center

  49. Support Subsystems(horizontal) • BOD Dispatcher - Outside World Access Point (incoming) • BOS Dispatcher - Telco BSS Access Point (outgoing) • System Management • All are EJBs or Service Components or Simple Classes, Available to All Callers

  50. CeBS Architecture DetailsBusiness Object Dispatcher (BOD) Gateway To The EJBs Only External API

More Related