1 / 23

Architecture Overview NexJ Systems Inc.

Architecture Overview NexJ Systems Inc. NexJ Systems Inc. People-centric Enterprise Business Solutions. Corporate & Investment Banking Institutional Sales & Trading Commercial & Small Business Banking. Private Client Services Insurance Agency Asset Management / Mutual Fund Wholesaling.

tejana
Download Presentation

Architecture Overview NexJ Systems Inc.

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. Architecture OverviewNexJ Systems Inc.

  2. NexJ Systems Inc. • People-centric Enterprise Business Solutions • Corporate & Investment Banking • Institutional Sales & Trading • Commercial & Small Business Banking • Private Client Services • Insurance Agency • Asset Management / Mutual Fund Wholesaling • Designed for enterprise CRM customers with integration and unique business requirements

  3. Working for Change Waterloo Institute for Health Informatics Research at the University of Waterloo Draw together academic, government, technology, and health care system players Examine, research, discuss, and publish findings on opportunities in health informatics Canadian Association for People-Centred Health Not-for-profit advocacy foundation Promote collaborative patient-centric health care Promote Canadian health technology Publishing Journey to Wellness: Informed People-Centred Healthcare by Dr. Vaughan Glover

  4. Product Timeline • 2003: NexJ Architectural Vision white paper created • 2004: Core engineering team starts building framework • 2005: Application Developers start creating applications with framework • 2006: Early Beta at charter customers and start to bring product to market • 2007: Win major accounts in Wealth Management: • Wachovia – 35,000 users • Investors Group – 5000 users • Assante Asset Management – 2000 users • 2008: Initial Architectural Vision essentially delivered; start planning next generation architecture

  5. Next Generation Vision • Open source core server components as part of OHT • Domain Model Layer • Integration Layer • Persistence Layer • MySQL Datasource Adapter • JBoss Container Support • Studio Editor for open sourced components • Layer commercialized product offerings on top • BI Models and Analytics • Support for separate OLTP and BI models and application stacks that are kept in real time sync • Enhanced Reporting including scheduled batch, and on screen interactive reporting • “Deep Functional Stacks” • Decoupling of objects in business model to allow just using objects of interest • Storing data related to each type of decoupled objects in independent data sources • Support for Federated searching across data sources • Enhanced Studio • Enhanced Editors • Interactive Debugger Support

  6. Architectural Goals • Simple Deployment • Scalable and reliable using commodity hardware • Run on variety of open source & common enterprise software platforms • Extensible and Flexible • Model logical business layer separately from technical implementation • Easily enable powerful, complex customizations • Easy to Integrate • Powerful integration layer that can be coupled to the business layer • Integrate with a wide variety of legacy and modern platforms • Easy to Upgrade • Allow multiple code streams and versions • Allow customization without changing base/core code Revisiting First Principles

  7. Achieving the Goals • Repository Based Architecture • Repository editor used to design the solution • Server and Client Frameworks use metadata to drive behaviour • J2EE Server Framework • Isolates business objects from data sources • Workflow and Rules Engine enables complex business processes • Integration layer supports rich integration capabilities • Specialized Client Framework per platform • Manages user interface, communication, data caching and security • Client independent scripting • Optimizes data transfer for minimizing round trips and data traffic volume Design Once, Run Anywhere

  8. NexJ Enterprise Application Framework Define your CRM applications Deliver on any platform Connect your existing data and applications Partners

  9. Java Rich Web Flat Web Portal Mobile/Handheld Clients Designer Applications Portlets Presentation Layer Screens Web Links/Sites External Painter Forms 3rd Party / Existing UI Scripting Navigation Business Model Accounts Clients Companies Business Model Relationships Entities Reports Roles Rules Business Logic Workflows Schemas Persistence Mapping Environments Connections Data Sources Db Data Storage FileSystem Archive Grid NexJ Enterprise Application Environment External Integration XML Web Services Data Transformations Messaging Protocols

  10. Repository Based Architecture Repository editor used to design and customize the system Repository management tools enable development, upgrade and deployment lifecycles Choose a fully functional vertical repository Server and Client frameworks use repository metadata to drive behaviour Repository Metadata Drives your System

  11. Business Domain Model Fully functional dynamic OOP system Powerful event driven model Extensive scripting capability Support for Aspects Workflow and Rules engine allow description of complex business logic Persistence Mapping layer isolates Domain Model from physical data sources Platform for Enterprise Solutions

  12. Integration – Message Definition Easily create complex messages Import from XSD Link messages together to create compound message Support for enumerations and type constraints Formats supported: XML / SOAP Text delimited HL7 2 and 3 Object coupled VCard / iCalendar Zip / Compressed

  13. Integration – Transformation Create complex message transformations Provides full script access to domain model classes, events and rules Initializer and Finalizer support Transform between formats e.g. File Based CSV -> XML SOAP Messages

  14. Integration – Services Channel Adapters for: HTTP, File System (FTP), UDP, Message Queues, SMTP, MAPI Channels can be bound to one or more Services Content Based Routing via: script and dispatch steps Interface bindings Try / Catch for intelligent error handling Synchronous and asynchronous invocation of other services. Transaction support WSDL Publishing

  15. Workflow Rich visual editor based on UML Activity diagrams Tightly coupled to domain model Supports: Conditional branching Wait states and timers Forks and Parallel processes Work Queues with automated and manual pulling from queues Integration to domain model events Nested Workflows Used for: Definition of complex non-procedural business processes without writing code Service Orchestration Managing long running processes

  16. Key Benefits • Scalable and Reliable • Easy to Customize • Easy to Upgrade • Easy to Deploy • Domain Model Portability • Intelligent Integration Layer

  17. Scalable and Reliable • Stateless NexJ Server • Allows the system to linearly scale and maximize the use of hardware • Extensive Database Tuning Capability • Persistence mappings can easily be modified to take tune performance based on customer specific data demographics • The NexJ Framework contains hooks providing the capability to modify and specialize SQL for tuning purposes if required • Use of J2EE technology • Leverage extensive horizontal scalability and fault tolerance that comes with the J2EE platform • Highly Scalable • Recently certified under a load of over 35,000 users, and maintained sub-second response times while processing over 100,000 transactions per minute. • The application tier exhibited linear scalability across CPU-cores and physical servers.

  18. Easy to Customize • Metadata repository is stored in XML files on the hard disk • Source Code Management integration of Eclipse is used to manage these files: • Provides mutli-developer support • Provides versioning and branching • Repository are organized into a Hierarchy • Customization of a base repository are done in a child without requiring any changes to the base. • Child repositories can be separately versioned • Base repository can advance without impact to children based on older versions.

  19. Easy to Upgrade • Child repository customization are kept distinct from base repository functionality • The definition of XML in the meta files of the repository has been designed to minimize collisions between developers and versions • XML element based 3-way difference logic makes it easy to merge • Database independent DB schema definition and upgrade definitions make it easier to track schema changes and generate upgrade DDL.

  20. Easy to Deploy • One button deploy automatically configures JBoss or Websphere and deploys to the server cluster • Client frameworks automatically download and install on first connection to server • The functionality definition in the repository is server and client agnostic • No special servers for specific client types or business functions are required

  21. Security Domain Model & applications don’t change! Domain Model Roles Rules Business Logic Workflows LHIN I LHIN 2 Hospital B Hospital E Hospital C… Pharmacy Radiology Hospital A Hospital F… Hospital D Physicians Pathology Pathology … Patients Radiology Medications Hospitals Lab Services Lab Services Lab Services Allied Health Allied Health Allied Health Pharmacy Pathology Pharmacy Pharmacy Pharmacy Radiology Radiology Pathology Pathology … … … Lab Services Pharmacy … Radiology Radiology Lab Services … … Lab Services PACS/ Image Archive Allied Health Pathology Clinical PACS/ Image Archive Lab Lab Clinical PACS/ Image Archive Lab Clinical Lab Lab Clinical Clinical Clinical Lab Meditech CernerMcKessonMysis… PACS/ Image Archive PACS/ Image Archive PACS/ Image Archive Meditech CernerMcKesson Domain Model Portability ScreenHideBox timer

  22. Security Domain Model & applications don’t change! Domain Model Roles Rules Business Logic Workflows LHIN 2 Hospital E Radiology Hospital F… Hospital D Physicians Pathology Pathology … Patients Medications Hospitals Lab Services Allied Health Pharmacy Pharmacy … Lab Services Pharmacy Radiology Radiology … … Lab Services PACS/ Image Archive Allied Health Pathology Clinical Lab Lab Clinical Clinical Lab Meditech CernerMcKessonMysis… PACS/ Image Archive PACS/ Image Archive Domain Model Portability Consistent Domain Model across multiple disparate systems and environments timer HideBox . . .

  23. Intelligent Integration Layer • Message Normalization between formats and dialects of the same format • i.e. HL7 v3 element contents differ between implementations • Translation services for ontologies • Add business logic for regional level policies to the layer to make enforcement easier and consistent measurement of metrics more reliable • i.e. wait time measurement in Ontario • Embed business logic for global services in the layer • i.e. EMPI processing • Allow less complex messages and smaller payloads • ability to late bind to rich content at message delivery time using built in business logic and the persistence layer

More Related