Extending and Updating GlassFish Server Inside a Closed Network

GlassFish Server might be installed on a machine without an Internet connection. For example, for security reasons, GlassFish Server might be installed behind a restrictive firewall, or it might be installed on a LAN that is physically isolated from other networks. In such situations, neither the graphical Update Tool nor the pkg command-line utility that are included with GlassFish Server can contact a public repository server to download and install updates. Therefore, a local repository server must be configured inside the closed network and the GlassFish Server updates installed from there.

The following topics are addressed here:

Installing the Pre-Installed Toolkit Image inside a closed network

The Pre-Installed Toolkit Image provides the software components that are required to run a local repository server inside a closed network.
Configuring and running a local repository server on a locally accessible host

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

Each GlassFish Server installation that will be updated inside a closed network must be configured to use a local repository server instead of the default public repository servers.
Installing the GlassFish Server updates

The GlassFish Server updates inside the closed network are performed normally, but use the local repository server instead of the public repository servers.

To Install the Pre-Installed Toolkit Image Inside a Closed Network

The Pre-Installed Toolkit Image provides the software components that are required to configure and run a local repository server inside a closed network. Running a local repository server makes it possible for a GlassFish Server installation to obtain packages and updates from within the closed network rather than from the default public GlassFish Server repositories.

Before You Begin

The first three steps of this procedure require access to a machine that is connected to the Internet. This machine must also be able to write to some type of removable medium, such as CD, DVD, USB drive, or flash memory card.
The remaining steps in the procedure are performed on the machines that are inside the closed network, and do not require access to an Internet connection.

In a Web browser on the machine that is connected to the Internet, open the Pre-installed Toolkit Images and Starter Repositories page.
Download the ZIP file that contains the Pre-Installed Toolkit Image that is correct for your server's operating system and save it to the location of your choice.
The ZIP files are named according to operating system and architecture, using the following format:
```
pkg-toolkit-2.3.3-platform-arch.zip
```
For example, the ZIP file for 32–bit Linux operating systems is named:
```
pkg-toolkit-2.3.3-linux-i386.zip
```
Download the correct ZIP file for the operating system and architecture on each of the following machines:
- The machine on which the local repository server will be run
- Each machine on which one or more GlassFish Server installations will be updated inside the closed network
Copy each Pre-Installed Toolkit Image ZIP file to a removable medium that you can physically transport to the machines inside the closed network.
Copy the correct Pre-Installed Toolkit Image ZIP file for each operating system from the removable medium to the directories of your choice on the following machines:
- The machine on which the local repository server will be run
- Each machine on which one or more GlassFish Server installations will be updated inside the closed network
Unzip the Pre-Installed Toolkit Image ZIP file on each machine to which you copied the ZIP file in the preceding step.
The size of the expanded Pre-Installed Toolkit Image ZIP file depends on the operating system:
- On Windows systems, the expanded ZIP file is approximately 11 Mbytes.
- On Linux and Solaris systems, the expanded ZIP file is approximately 13 Mbytes.
(Optional) On each machine to which you copied the Pre-Installed Toolkit Image, verify that the pkg command-line tool is correctly installed.
1. Change to the pkg/bin subdirectory of the directory that contains the unzipped Pre-Installed Toolkit Image.
```
cd toolkit-dir/pkg/bin
```
  toolkit-dir
  
  The directory that contains the unzipped Pre-Installed Toolkit Image.
2. Display the pkg version.
```
./pkg version
```
  Output similar to the following is displayed:
```
1.122.2-38.2791
```

To 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:

You have access to a machine that is connected to the Internet.
The machine that is connected to the Internet can write to some type of removable medium, such as CD, DVD, USB drive, or flash memory card.
The Pre-Installed Toolkit Image has been installed as described in To Install the Pre-Installed Toolkit Image Inside a Closed Network.

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 My Oracle Support Web site.
1. Log in to the My Oracle Support site.
2. Click the Patches & Updates tab.
3. Enter the desired patch number in the Patch Name or Number 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.
Copy each ZIP file that you downloaded from My Oracle Support onto a removable medium that you can physically transport to the local repository server.
Each My Oracle Support ZIP file is approximately 270 Mbytes in size.
Copy each My Oracle Support ZIP file from the removable medium to the local repository server machine.
The directory used for the My Oracle Support 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.
Unzip each My Oracle Support ZIP file that you copied in the preceding step.
The My Oracle Support ZIP files are wrappers that contain a GlassFish Server repository ZIP file, a README file, and a license file. For example, the My Oracle Support 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 My Oracle Support ZIP file.
  For example:
```
unzip 145093-01
```
2. Change to the directory that was created when the My Oracle Support 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
```
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 11-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

To Configure a GlassFish Server Installation to Use a Local Repository Server Inside a Closed Network

Each GlassFish Server installation that will be updated inside a closed network must be configured to use a local repository server instead of the default public repository servers.

Before You Begin

This procedure must be completed on each GlassFish Server installation on which updates will be performed inside the closed network.

Ensure that the following conditions are met:

The Pre-Installed Toolkit Image is installed on each machine on which one or more GlassFish Server installations will be upgraded, as described in To Install the Pre-Installed Toolkit Image Inside a Closed Network
The local repository server is configured, as described in To Configure a Local Repository Server Inside a Closed Network

Set the http_proxy environment variable for the local repository server, if necessary.
This step is required if a proxy is needed to access the local repository from within the closed network.
```
export http_proxy=proxy-host:port
```
proxy-host

The fully qualified URL for the proxy host.

port

The port on which the proxy-host listens.
Change to the GlassFish Server installation directory.
```
cd as-install
```
as-install

The path to the directory that contains the GlassFish Server installation that is to be updated.

Note - The remainder of this procedure must be performed from within the GlassFish Server installation directory.
Use the pkg command in the Pre-Installed Image Toolkit installation directory to tell the GlassFish Server installation to use the local repository server.
```
toolkit-dir/pkg/bin/pkg -R as-install set-publisher -Pe -O http://repo-host:port publisher
```
toolkit-dir

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

as-install

The path to the directory that contains the GlassFish Server installation that is to be updated.

repo-host

The name of the server on which the pkg.depotd repository server daemon is running.

port

The port used for the pkg.depotd daemon, as specified in To Configure a Local Repository Server Inside a Closed Network.

publisher

The name of the preconfigured GlassFish Server publisher. For GlassFish Server, use release.glassfish.oracle.com as the publisher.
(Optional) Verify that the local GlassFish Server repository is configured correctly.
```
toolkit-dir/pkg/bin/pkg publisher
```
The name of the of the local server repository and publisher should be listed, as shown in the following example.

Example 11-2 Configuring the pkg Command to Use a Local Repository

This example configures a GlassFish Server installation to use a local repository server. The following parameters are used:

/opt/glassfish: The GlassFish Server installation directory.
/opt/toolkit: The Pre-Installed Toolkit Image directory.
repohost: The host name of the local repository server.
30000: The port number used by the repository server.

/opt/toolkit/pkg/bin/pkg -R /opt/glassfish set-publisher -P --enable \ -O http://repohost:30000 release.glassfish.oracle.com
# /opt/toolkit/pkg/bin/pkg publisher
PUBLISHER                             TYPE     STATUS   URI
release.glassfish.oracle.com (preferred)  origin   online   http://repohost:30000/

To Install Updates From a Local Repository

After configuring a GlassFish Server installation to use a local repository server, as described in the previous procedures in this section, GlassFish Server updates inside a closed network are performed normally. The only difference is that the GlassFish Server installation being updated inside the closed network will use a local repository server instead of the public repository servers.

Perform the following procedure on each GlassFish Server installation that will be updated.

Before You Begin

Ensure that each GlassFish Server installation that will be updated is configured to use the local repository server, as described in To Configure a GlassFish Server Installation to Use a Local Repository Server Inside a Closed Network.

Stop GlassFish Server.
See To Stop a Domain.
Change to the GlassFish Server installation directory.
```
cd as-install
```
Note - The remainder of this procedure must be performed from within the GlassFish Server installation directory.
Use either the graphical Update Tool or the pkg command-line utility to perform the desired updates.
For detailed instructions on updating or installing GlassFish Server components, see Updating Installed Components.
Start GlassFish Server.
See To Restart a Domain.

Skip Navigation Links
Exit Print View
	Oracle GlassFish Server 3.1 Administration Guide