1. Overview of GlassFish Server Administration
Default Settings and Locations
Instructions for Administering GlassFish Server
4. Administering the Virtual Machine for the Java Platform
6. Administering Web Applications
7. Administering the Logging Service
8. Administering the Monitoring Service
9. Writing and Running JavaScript Clients to Monitor GlassFish Server
10. Administering Life Cycle Modules
11. Extending and Updating GlassFish Server
Preconfigured Repositories for GlassFish Server
Oracle GlassFish Server Repositories
Enabling the Oracle GlassFish Server Support Repository
GlassFish Server Open Source Edition Repositories
Tools for Extending and Updating GlassFish Server
To Install an Add-on Component
To Update an Installed Component
To Update All Installed Components in an Image
To Uninstall an Installed Component
To Uninstall and Revert to an Older Version of a Component
Upgrading to Oracle GlassFish Server From GlassFish Server Open Source Edition
To Upgrade to Oracle GlassFish Server by Using Update Tool
To Upgrade to Oracle GlassFish Server by Using the pkg Command
Extending and Updating GlassFish Server Inside a Closed Network
To Install the Pre-Installed Toolkit Image Inside a Closed Network
To Configure a Local Repository Server Inside a Closed Network
Part II Resources and Services Administration
12. Administering Database Connectivity
13. Administering EIS Connectivity
14. Administering Internet Connectivity
15. Administering the Object Request Broker (ORB)
16. Administering the JavaMail Service
17. Administering the Java Message Service (JMS)
18. Administering the Java Naming and Directory Interface (JNDI) Service
19. Administering Transactions
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.
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.
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
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
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.
cd toolkit-dir/pkg/bin
The directory that contains the unzipped Pre-Installed Toolkit Image.
./pkg version
Output similar to the following is displayed:
1.122.2-38.2791
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.
The repository ZIP files for GlassFish Server are distributed as patches through the My Oracle Support Web site.
|
A list of patches appears at the bottom of the page.
Each My Oracle Support ZIP file is approximately 270 Mbytes in size.
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.
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.
For example:
unzip 145093-01
For example:
cd 145093-01
For example:
unzip ogs-3.0.1-repo-linux-i386.zip
cd toolkit-dir/pkg/bin
The directory that contains the unzipped Pre-Installed Toolkit Image.
./pkg.depotd -d repository-dir -p port
The directory that contains the unzipped GlassFish Server repository.
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:
The name of the Pre-Installed Toolkit Image directory.
The GlassFish Server repository directory.
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
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
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
The fully qualified URL for the proxy host.
The port on which the proxy-host listens.
cd 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.
toolkit-dir/pkg/bin/pkg -R as-install set-publisher -Pe -O http://repo-host:port publisher
The directory that contains the unzipped Pre-Installed Toolkit Image.
The path to the directory that contains the GlassFish Server installation that is to be updated.
The name of the server on which the pkg.depotd repository server daemon is running.
The port used for the pkg.depotd daemon, as specified in To Configure a Local Repository Server Inside a Closed Network.
The name of the preconfigured GlassFish Server publisher. For GlassFish Server, use release.glassfish.oracle.com as the publisher.
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:
The GlassFish Server installation directory.
The Pre-Installed Toolkit Image directory.
The host name of the local repository server.
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/
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.
See To Stop a Domain.
cd as-install
Note - The remainder of this procedure must be performed from within the GlassFish Server installation directory.
For detailed instructions on updating or installing GlassFish Server components, see Updating Installed Components.
See To Restart a Domain.