Personal tools
You are here: Home Developer Infrastructure Teams Architecture Kepler Extension Points

Kepler Extension Points and APIs

This page lists the various APIs and extension points that are available to Kepler module developers and actor developers.

Kepler modules and Actors have access to several frameworks that make it easier to develop a module or actor that integrates into the Kepler system.  These extension points are listed here, with details on how to use them and call their respective APIs.


  • Configuration System
    • The ConfigurationManager is a stand-alone configuration system meant to provide an easy-to-use API for classes within a module to both get and set configuration properties.  Each module can control its own properties, but other modules can overwrite those properties or add to them for their own needs.
  • Menu System
    • Description of adding menus and context menus to Kepler.
  • Event-State
    • The Event-State extension point allows modules to create Events which can be published by one module and monitored by the same or independent modules.  It is an implementation of the Observer pattern and allows inter-module communication without strong compile-time dependencies between modules.
  • ViewPane and TabPane GUI Extension Points
    • This page explains how to extend the Kepler graphical user interface using the ViewPane and TabPane extension points.
  • PreferencesTab Extension Point
    • The PreferencesTab extension point allows modules to provide users the ability to set module specific preferences from a common frame within Kepler.
  • KAREntryHandler Extension Point
    • The KAREntryHandler extension point in the core module allows other modules to contribute files to Kepler ARchives (KARs).
  • Authentication Framework
    • The Authentication Framework provides a common, centralized system for actors to request authentication and authorization credentials for operations that need them, such as data access or remote job execution.


Kepler uses Ptolemy II as Kepler's execution engine, for information about developing actors, see the Ptolemy II design document, especially Volume1, Designing Actors.
Document Actions