Hello Jason,
Please refer to the following blog
http://blogs.sun.com/theaquarium/entry/writing_addons_as_update_center
Based on requirement, your UC module can be of any of the following type:
ARCHIVE (
http://javaee-updates.java.sun.com/beta/modules/grails/0_1/grails-0_1.nbm)
APPLICATION (
http://javaee-updates.java.sun.com/beta/modules/woodstock/4_1/woodstock-4_1.nbm)
ADDON_INSTALLER (
http://javaee-updates.java.sun.com/beta/modules/ssg/1_0_2/ssg-1_0_2.nbm)
ADDON_CONFIGURATOR (
http://javaee-updates.java.sun.com/beta/modules/portlet_container/portlet_container-2_0b.nbm)
Please download and see the respective module type for its structure/content. ARCHIVE type is unzipped under GlassFish installroot as it is preserving the zipped directory structure. APPLICATION type module get deployed on GlassFish on installation. ADDON_INSTALLER and ADDON_CONFIGURATOR type can be used in case of more complex installation and configuration requirements. For more information on addons, please refer to following links-
https://updatecenter.dev.java.net/addon/javadoc/api/com/sun/appserv/addons/Installer.html
https://updatecenter.dev.java.net/addon/javadoc/api/com/sun/appserv/addons/package-summary.html
Also, you need to provide three html description pages for your module. Attaching the example files.
Thanks
--
Rajeshwar Patil - (408) 276-4407 - Sun Microsystems, Inc.
----- Original Message -----
From: Jason Lee <jason_at_steeplesoft.com>
Date: Wednesday, May 28, 2008 9:06 am
Subject: How to make an Update Center module
To: admin_at_glassfish.dev.java.net
> Rajiv asked I could make a UC module for Scales (see link below),
> which was
> already on my to do list, but, given his inquiry, I've bumped it up.
> :) At
> any rate, I'm trying to find some documentation on how to go about
> that, and
> all I've found so far is this
>
> http://weblogs.java.net/blog/manveen/archive/2007/06/creating_a_glas_1.html
>
> and Alexis' entry here
>
> http://blogs.sun.com/alexismp/entry/using_the_glassfish_update_center
>
> Neither of these, though, show the detailed mechanics of going about
> building the module, so I'm going to describe how I *think* this should
> work, and, hopefully, someone can correct my errors and/or fill in some
> holes.
>
> Since I am wanting to install an addon library, I'll need to set the
> Module-Type to ADDON_INSTALLER, and implement
> com.sun.appserv.addons.Installer. It's here that things get a little
> vague. In my implementation class, the UC will call my install()
> method and
> pass in an InstallationContext, from which I'll get a File that points
> to
> the installation directory. Using that File, I'll copy the required files
> required by Scales. Everything OK so far? :)
>
> The question, then, is how do these modules usually work? That is,
> what is
> the recommended practice. Do I bundle the JARs in the module archive?
> Do I
> download them from the internet? Is there a third option I'm missing?
>
> Is there an expert around to field questions on this?
>
> Thanks! :)
>
> --
> Jason Lee, SCJP
> Software Architect -- Objectstream, Inc.
> Mojarra and Mojarra Scales Dev Team
> https://mojarra.dev.java.net
> https://scales.dev.java.net
> http://blogs.steeplesoft.com