Oracle GlassFish Server 3.0.1 Administration Guide

ProcedureTo Configure a Local Repository Server Inside a Closed Network

A local repository server makes it possible for a GlassFish Server installation to obtain packages and updates from within a closed network, rather than from the default public repository servers.

Before You Begin

Ensure that the following conditions are met:

  1. In a Web browser on the machine that is connected to the Internet, download the ZIP file that contains the GlassFish Server repository for the operating system on which GlassFish Server is running.

    The repository ZIP files for GlassFish Server are distributed as patches through the SunSolve Web site.

    1. Log in to the SunSolve site.

    2. Navigate to the Patch Finder page.

    3. Enter the desired patch number in the Patch ID field and then click Search.

      Operating System 

      Patch ID 

      sunos-sparc 

      145091 

      sunos-i386 

      145092 

      linux-i386 

      145093 

      windows-i386 

      145094 

      mac-universal 

      145095 

      A list of patches appears at the bottom of the page.

    4. Download the ZIP file for the latest version of the desired patch.

  2. Copy each ZIP file that you downloaded from SunSolve onto a removable medium that you can physically transport to the local repository server.

    Each SunSolve ZIP file is approximately 270 Mbytes in size.

  3. Copy each SunSolve ZIP file from the removable medium to the local repository server machine.

    The directory used for the SunSolve ZIP files should be different than the directory in which the Pre-Installed Toolkit Image was copied, as described in To Install the Pre-Installed Toolkit Image Inside a Closed Network.

  4. Unzip each SunSolve ZIP file that you copied in the preceding step.

    The SunSolve ZIP files are wrappers that contain a GlassFish Server repository ZIP file, a README file, and a license file. For example, the SunSolve ZIP file for Linux contains the following files:


    LEGAL_LICENSE.TXT
    README.145093-01
    ogs-3.0.1-repo-linux-i386.zip

    In this example, the GlassFish Server repository ZIP file is named ogs-3.0.1-repo-linux-i386.zip.

    1. Unzip the SunSolve ZIP file.

      For example:


      unzip 145093-01
      
    2. Change to the directory that was created when the SunSolve ZIP file was unzipped.

      For example:


      cd 145093-01
      
    3. Unzip the GlassFish Server repository ZIP file.

      For example:


      unzip ogs-3.0.1-repo-linux-i386.zip
      
  5. On the local repository server machine, start the repository server daemon.

    1. Change to the Pre-Installed Toolkit Image pkg/bin directory.


      cd toolkit-dir/pkg/bin
      
      toolkit-dir

      The directory that contains the unzipped Pre-Installed Toolkit Image.

    2. Start the pkg.depotd daemon.


      ./pkg.depotd -d repository-dir -p port
      
      repository-dir

      The directory that contains the unzipped GlassFish Server repository.

      port

      Your choice of port number for requests to the repository server. The default is 80.

    Several startup messages are displayed as the repository daemon initializes, as shown in the following example.


Example 10–1 Starting a Local Repository Daemon

This example starts the pkg.depotd daemon using the following parameters:

/opt/toolkit

The name of the Pre-Installed Toolkit Image directory.

/opt/145093-01/linux-i386/

The GlassFish Server repository directory.

30000

The port number used by the local repository daemon.


./pkg.depotd -d /opt/145093-01/linux-i386/ -p 30000
[ Jun 15 08:06:38 ] ENGINE Listening for SIGHUP.
[ Jun 15 08:06:38 ] ENGINE Listening for SIGTERM.
[ Jun 15 08:06:38 ] ENGINE Listening for SIGUSR1.
[ Jun 15 08:06:38 ] ENGINE Bus STARTING
[ Jun 15 08:06:38 ] ENGINE Started monitor thread '_TimeoutMonitor'.
[ Jun 15 08:06:38 ] ENGINE Serving on 0.0.0.0:30000
[ Jun 15 08:06:38 ] ENGINE Bus STARTED