Try OpenEdge Now
skip to main content
Configuring third-party Web applications : Page contributions for a third-party Web application

Page contributions for a third-party Web application

OpenEdge Management provides hooks, located in predefined locations, which allow a third-party Web application to add user interface elements to every page. In this release, only a limited set of hooks are provided, for example, main menu and footers in the OpenEdge Management console.
To register these hooks and to inject a custom PageContributor class into OpenEdge Management, a registration mechanism is provided for third-party Web applications. During execution of every page, the methods in the page contributor instance are invoked at specific points.
Note: A third-party Web application must implement its own PageContributor class in order to work with OpenEdge Management.
OpenEdge Management implements specific callbacks for the page contributor to the following locations in the management console:
*Page header — To inject script and style.
*Main menu — To add a functional menu to the main menu bar.
*Footer menu — To add new entries to the footer.
*Options page — To add new entries to the Options page.
The extension mechanism provides the following configuration entry points to register extensions in OpenEdge Management:
*Extension name — The name of the extension.
*Extension class path — Extends the default behavior of OpenEdge Management.
*Extension initializer class — For startup, state, and shutdown of the extension.
*Standard file layout — The location of the configuration file of the extension.
*Standard Java interfaces — Supports the above entry points.
*Dashboard entry point class — Adds top-level pages.
*Configuration entry point class — Adds entries to the Options page in the management console.
*User login entry point page — Allow user logins to open the Dashboard page or any other page defined by the plugin.
* Behavior of OpenEdge Management
* Registering a contributor