top of page


Public·12 membres

How To Install Glassfish [NEW]

Before installing Oracle GlassFish Server 3.1.2, ensure that your system meets the requirements listed in "Hardware and Software Requirements" in Oracle GlassFish Server Release Notes. If necessary, download and install the required JDK software. Problems are likely to arise if you attempt to install on a platform that is not supported or on a system that in some other way does not meet release requirements. Also see "Known Issues" in Oracle GlassFish Server Release Notes for known issues related to installation.

How to install Glassfish

You are receiving a copy of the Javassist (Java Programming Assistant) Library in source form at -GA/javassist-3.14.0-GA-sources.jar and in object code form in the jar file glassfish/modules/weld-osgi-bundle.jar included with the distribution. The terms of the Oracle license do NOT apply to the Javassist (Java Programming Assistant) program; it is licensed under the following license, separately from the Oracle programs you receive. If you do not wish to install this program, you may choose to not proceed with the installation of Oracle GlassFish Server.

0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.

a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.

Before performing any GlassFish Server installation, ensure that your environment adheres to the JDK guidelines in "Paths and Environment Settings for the JDK Software" in Oracle GlassFish Server Release Notes.

Each of the installation methods listed in Table 1-1 also let you choose to install either the GlassFish Server Full Platform or Web Profile distribution. Table 1-2 lists the features available in each of these two distributions. Note that some of these features are value-adds, and are not required by the Java 6 EE specification.

Regardless of whether you choose the Full Platform or Web Profile distribution, you can add or removed packages after installation by using the Update Tool or pkg utility. See "Extending and Updating GlassFish Server" in Oracle GlassFish Server Administration Guide for more information.

The Plug-in is shipped as a ZIP bundle that you install after installing and configuring GlassFish Server and your desired Web server. The Plug-in is installed by means of a graphical Load Balancer Configurator that helps you configure your Web server and GlassFish Server to work together.

See "Configuring Web Servers for HTTP Load Balancing" in Oracle GlassFish Server High Availability Administration Guide for instructions on installing the HTTP Load Balancer Plug-in and performing the configuration steps required to make the Plug-in work with your Web server.

This section describes how to install Oracle GlassFish Server 3.1.2 using the multi-platform ZIP file. GlassFish Server is installed by unzipping the file in the installation directory of your choice.

It is not possible to specify any GlassFish Server configuration options during a ZIP file installation. Any configuration changes, such as creating domains, clusters, and server instances, must be made manually after installation. If you prefer to make such changes during the GlassFish Server installation process, or if you prefer to use the GUI-based installation wizard, follow the instructions in Installing GlassFish Server From a Self-Extracting Bundle.

GlassFish Server 3.1.2 is extracted into a new glassfish3 directory under your current directory. This glassfish3 directory is referred to throughout the GlassFish Server documentation set as as-install-parent.

This section describes how to install Oracle GlassFish Server 3.1.2 software using one of the self-extracting installation bundles. Running any of the self-extracting bundles automatically launches the GUI-based GlassFish Server installation wizard.

When launching the self-extracting installer from the command-line, it possible to specify several command-line options that may be useful to you. See Installation Command-Line Options for more information.

Depending on your user privileges and the version of Windows you are running, it may be necessary to run the installer as Administrator. In particular, if you will be configuring the domain as a Service as part of a Custom Installation (see next step) or after the installation, then you should run the installer as Administrator.

Choose the option if you are deploying GlassFish Server in a production environment. This option provides several installation choices, which are described in detail later in this guide, in To Perform a Custom Installation.

Update Tool is an administrative tool that enables you to install updates and add-on components to an existing GlassFish Server 3.1.2 installation. Update Tool can be installed during GlassFish Server installation or at a later time. For more information about Update Tool, see "Update Tool" in Oracle GlassFish Server Administration Guide.

If you choose to cancel the installation at this point, no GlassFish Server files will be installed, but the directory you specified for as-install-parent will remain. This directory can be deleted manually.

Installation information is captured in log files. The names of the files are timestamp-install.log and timestamp-install-summary.html. On Solaris, Linux, and Mac OS X systems, these files are generated by default in the /tmp directory. On Windows systems, these files are generated in the %TEMP% directory.

Install only the GlassFish Server binaries, without configuring a DAS or any server instances or clusters. You can rerun the GlassFish Server installation wizard at a later time and choose the Configure an Existing Installation option to configure the items.

Configure a DAS, standalone server instances, clusters, or clustered instances for an existing GlassFish Server 3.1.2 installation. Note that this option is not for upgrading from an older version of GlassFish Server. For instructions on upgrading from a version of GlassFish Server prior to 3.1.2, see the Oracle GlassFish Server Upgrade Guide.

À propos

Bienvenue sur le groupe ! Vous pouvez contacter d'autres mem...
Page de groupe: Groups_SingleGroup
bottom of page