JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1 Add-On Component Development Guide
search filter icon
search icon

Document Information


1.   Introduction to the Development Environment for GlassFish Server Add-On Components

2.  Writing HK2 Components

3.  Extending the Administration Console

Administration Console Architecture

Implementing a Console Provider

About Administration Console Templates

About Integration Points

Specifying the ID of an Add-On Component

Adding Functionality to the Administration Console

Adding a Node to the Navigation Tree

Creating a JavaServer Faces Page for Your Node

Adding Tabs to a Page

Creating JavaServer Faces Pages for Your Tabs

Adding a Task to the Common Tasks Page

Creating a JavaServer Faces Page for Your Task

Adding a Task Group to the Common Tasks Page

Creating a JavaServer Faces Page for Your Task Group

Adding Content to a Page

Creating a JavaServer Faces Page for Your Page Content

Adding a Page to the Administration Console

Adding Internationalization Support

Changing the Theme or Brand of the Administration Console

Creating an Integration Point Type

To Create an Integration Point Type

4.  Extending the asadmin Utility

5.  Adding Monitoring Capabilities

6.  Adding Configuration Data for a Component

7.  Adding Container Capabilities

8.  Creating a Session Persistence Module

9.  Packaging, Integrating, and Delivering an Add-On Component

A.  Integration Point Reference


Creating an Integration Point Type

If your add-on component provides new content that you would like other people to extend, you may define your own integration point types. For example, if you add a new page that provides tabs of monitoring information, you might want to allow others to add their own tabs to complement your default tabs. This feature enables your page to behave like the existing Administration Console pages that you or others can extend.

To Create an Integration Point Type

  1. Decide on the name of your integration point type.

    The integration point type must be a unique identifier. You might use the package name of your integration point, with a meaningful name appended to the end, as in the following example:
  2. After you have an integration point ID, use handlers to insert the integration point implementation(s).

    Include code like the following below the place in your JavaServer Faces page where you would like to enable others to add their integration point implementations:


    Change clientId:of:root to match the clientId of the outermost component in which you want others to be able to add their content (in this example, the tab set is the most likely choice). Also include your integration point ID in place of If you omit the root argument to includeIntegrations, all components on the entire page can be used for the parentId of the integration points.

  3. To enable others to use this integration point, document it at the GlassFish Integration Point wiki page.

    Document the integration point only if your content is publicly available.

    You or others can now provide an integration point that will be integrated into this page.

See Also

For more information, see the JSFTemplating API documentation.