Screencast – installing a GlassFish company-internal repository

The GlassFish Update Center is a really severely underused feature of the product (IMO). Of course you can install GlassFish and simply ignore the update center and not use it to install updates, 3rd party frameworks, your own packages or upcoming patches but that would be ignoring one of the unique features of the product.

This new screencast shows how to setup a GlassFish Update Center repository behind your company’s firewall. It shows access to (which replaced sunsolve) to grab the content of the repository, setting up an internal server (a Publisher), and updating existing GlassFish installs to use it or installing new app servers from this repo.

The offline version is here (75 MB).

The screencast scenario is largely based on this Extending and Updating GlassFish Server Inside a Closed Network documentation (for GlassFish 3.0.1) and you may also find Upgrading to Oracle GlassFish Server From GlassFish Server Open Source Edition to be useful. Finally, the blog about support from Oracle mentioned at the end of the screencast is here.

Author: alexismp

Google Developer Relations in Paris.

4 thoughts on “Screencast – installing a GlassFish company-internal repository”

  1. Important modules are too old, like jsf or grizzly.
    Commonly used modules like OSGi spring framework are not available and are not strightforward to install, and don’t work if deployed in a war.
    Besides, module installation or upgrade usually fails.
    It’s not a surprise the underuse of the update tool.

  2. I forgot to comment on Grizzly – it’s really at the heart of GlassFish so it’s hard to update without doing a full release. Even 3.1 will not ship with 2.0.
    For JSF, yes, we need to get better at releasing updates using the UC!

Comments are closed.

%d bloggers like this: