AEDGE® and Plug-ins

  • Utilize the Eclipse Rich Client Platform concept of Plug-ins
  • AEDGE® Core: a collection of core Plug-ins (agent framework, pub/sub, data models, etc.)
  • AEDGE® Extensions: reusable components (visualization, algorithms, agents)
  • AEDGE® Application: a collection of plug-ins that may extend AEDGE® plug-ins with product-specific functionality
  • Together with AEDGE® Core and Extension Plug-ins, the Application plug-ins form the bundled run-time
  • AEDGE:Web is a collection web based facilities and frameworks.

AEDGE:Web® Technology Stack

AEDGE Core and Plug-ins

  • Based on the Eclipse Rich Client Platform concept of Plug-ins
  • Core package: base functionality, pub-sub communications, agent framework
  • Bundled Plug-ins provide many reusable functions (maps, algorithms, agents)
  • Application Plug-ins extend the base for product- specific functionality

AEDGE:Search

  • A federated search engine and text analytics platform
  • Capable of accessing content across enterprise data sources and information repositories
  • Current research towards „enterprise people search‟ – providing unified views for entities across data sources

AEDGE API

  • Strong use of coding standards
  • Well documented, published APIs for each release

Development use AEDGE binaries

  • 21CSI internal product developers use AEDGE as an SDK
    • Just like an external developer would
    • Internal checks and balances for well designed interfaces
  • Two types of regular AEDGE releases
    • Major releases – Every 6 months
      • May not be fully compatible with previous releases
      • AEDGE team supports two previous iterations
    • Minor releases – Every three weeks
      • Guaranteed to be compatible with major release

AEDGE and SOA

    AEDGE is a distributed application environment
    • Abstracts communication layer from Application developers
    • Promotes modular business logic for independent components
  • AEDGE provides Publish/Subscribe services

    • Topic based messaging
    • Publishers and subscribers are independent of each other
    • Scalability built into Agent Environment
    • Using standard underlying comms protocols (e.g. JMS)
  • Provide mechanisms to syndicate services

    • Take data from an application and produces a service
    • Reads from multiple services to produce data the application needs, in the format the application needs

    AEDGE 1.0+ Tiers