This chapter provides instructions for installing Oracle GlassFish Server 3.1.2 software on Solaris, Linux, Mac OS X, and Windows systems.
The following topics are addressed here:
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.
On Solaris, Linux, and Windows systems, JDK software is available from the Java SE downloads page.
For Mac OS X systems, GlassFish Server uses the JDK that is part of the Macintosh operating system. If necessary, obtain the required JDK version from the Mac OS X Updates site.
You are receiving a copy of the Javassist (Java Programming Assistant) Library in source form at http://repo1.maven.org/maven2/org/javassist/javassist/3.14.0-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.
GNU LESSER GENERAL PUBLIC LICENSE Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.
To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.
Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs.
When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.
We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.
For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.
Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
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.
1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine- readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:
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.
7. You may place library facilities that are a work based on the Library side-by- side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above. b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.
11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Libraries If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License). To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. one line to give the library's name and an idea of what it does. Copyright (C) year name of author This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Also add information on how to contact you by electronic and paper mail. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker. signature of Ty Coon, 1 April 1990 Ty Coon, President of Vice That's all there is to it!
The following topics are addressed here:
Installation files for Oracle GlassFish Server 3.1.2 are available from the GlassFish Server Downloads page.
Table 1-1 lists the various Oracle GlassFish Server installation methods. The table also provides links to installation instructions for each method.
Note:
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.
Table 1-1 GlassFish Server 3.1.2 Installation Methods
| Installation Method | Installation Instructions |
|---|---|
|
Multi-platform ZIP file |
|
|
Solaris, Linux, Mac OS, UNIX, or Windows self-extracting bundle in graphical mode |
|
|
Solaris, Linux, Mac OS, UNIX, or Windows self-extracting bundle in silent mode |
Each of the installation methods listed in Table 1-1 also let you choose between installing the Full Platform or the Web Profile. These two distributions are explained in the next section.
There are two general sets of questions you should consider when deciding which GlassFish Server 3.1.2 installation method to use.
The relative features and strengths of the GlassFish Server ZIP packages and self-extracting bundles are listed below.
ZIP Package
Is simpler to install, but provides no configuration options during the installation
Any additional configurations must be performed manually, after installation
Includes Update Tool and pkg utility installer stubs, which can be used to install those utilities after GlassFish Server installation
If uninstallation is desired, product must be uninstalled manually
Product downloads are roughly 25%-30% larger than the analogous self-extracting bundles
Self-Extracting Bundle
Provides a GUI-based installation wizard with many configuration options
The installation wizard can be used again after the initial installation to perform additional configuration tasks
Can be used to perform Silent Mode installation, which is useful for performing consistent script-based installations on multiple server machines
Provides the option to install the full Update Tool and pkg utility at installation time
If uninstallation is required, a GUI-based uninstaller is provided
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.
Table 1-2 GlassFish Server Full Profile and Web Profile Features
| Feature | Full Platform | Web Profile |
|---|---|---|
|
Java Platform, Enterprise Edition 6 |
X |
X |
|
EJB 3.1 Lite (Support for Local Container only) |
X |
X |
|
JTS/JTA 1.1 ** |
X |
X |
|
OSGi-based microkernel |
X |
X |
|
Java Web Technologies (Servlet 3.0, JSP 2.2, JSF 2.0, JSTL 1.2, EL 2.2) |
X |
X |
|
Grizzly/Comet |
X |
X |
|
JPA 2.0, (EclipseLink), JDBC Connection Pooling |
X |
X |
|
JDBC 4.0 |
X |
X |
|
JavaDB 10.5.3 |
X |
X |
|
Web Administration Console and CLI |
X |
X |
|
Rapid Redeployment (Maintain session state on application redeploy) |
X |
X |
|
OMG CORBA APIs 3.0 |
X |
X |
|
Debugging Support for Other Languages 1.0 |
X |
X |
|
Common Annotations for Java 1.1 |
X |
X |
|
Dependency Injection for Java 1.0 |
X |
X |
|
Managed Beans 1.0 |
X |
X |
|
Interceptors 1.1 |
X |
X |
|
Contexts and Dependency Injection for Java 1.0 (CDI, ex-Web Beans) |
X |
X |
|
Bean Validation 1.0 |
X |
X |
|
JAX-RS 1.1 (Jersey) |
X |
X |
|
EJB 3.1 Full API (Support for Remote Container) |
X |
- |
|
Java EE Connector Architecture 1.6 |
X |
- |
|
JAX-WS 2.2 |
X |
- |
|
JAXB 2.2 |
X |
- |
|
Implementing Java Web Services 1.3 |
X |
- |
|
Web Services Metadata for the Java Platform 2.1 |
X |
- |
|
JMS 1.1 |
X |
- |
|
JavaMail 1.4 |
X |
- |
|
JACC 1.4 |
X |
- |
|
Java Authentication Service Provider Interface for Containers 1.1 |
X |
- |
|
Java EE Application Deployment 1.2 |
X |
- |
|
J2EE Management 1.1 |
X |
- |
|
JAX-RPC 1.1 |
X |
- |
|
JAXR 1.0 |
X |
- |
|
CORBA 3.0.0 |
X |
* |
|
Metro |
X |
- |
* The Full Java EE Platform contains the complete CORBA package. The OMG CORBA v3.0 APIs are available in the Java EE Web Profile.
** Transaction propagation not supported.
Note:
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 Oracle GlassFish Server 3.1.2 multi-platform ZIP files are compatible with Solaris, Linux, Mac OS, UNIX, and Windows operating systems. See GlassFish Server Download Locations for a list of download locations.
Table 1-3 lists the available ZIP file downloads.
Note:
In all cases, the *-ml.zip bundles in the table are multilingual versions of the product.
The Oracle GlassFish Server 3.1.2 self-extracting bundles are platform-specific, and are available for Solaris, Linux, Mac OS, UNIX, and Windows operating systems. See GlassFish Server Download Locations for a list of download locations.
Table 1-4 lists the available self-extracting bundles.
Note:
In all cases, the *-ml.* bundles in the table are multilingual versions of the product.
Table 1-4 GlassFish Server Self-extracting Bundles
| Self-Extracting Bundle | Description |
|---|---|
ogs-3.1.2-unix.sh ogs-3.1.2-windows.exe ogs-3.1.2-unix-ml.sh ogs-3.1.2-windows-ml.exe |
Full Platform distribution of Oracle GlassFish Server for Solaris, Linux, and Mac OS X systems ( |
ogs-3.1.2-web-unix.sh ogs-3.1.2-web-windows.exe ogs-3.1.2-web-unix-ml.sh ogs-3.1.2-web-windows-ml.exe |
Web Profile distribution of Oracle GlassFish Server for Solaris, Linux, and Mac OS X systems ( |
The HTTP Load Balancer Plug-in for Oracle GlassFish Server 3.1.2 provides high availability load balancing features for GlassFish Server.
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.
Note:
The Load Balancer Plug-in is only available to customers who are using Oracle GlassFish Server 3.1.2. The Plug-in is not available for GlassFish Server Open Source Edition.
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.
Note:
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.
Ensure that your system meets the requirements listed in "Hardware and Software Requirements" in Oracle GlassFish Server Release Notes.
Also see "Known Issues" in Oracle GlassFish Server Release Notes for known issues related to installation.
Download the desired GlassFish Server 3.1.2 ZIP file.
See GlassFish Server Download Locations for a list of download locations. See Table 1-3 for a list of available ZIP files.
Change to the directory where you downloaded the ZIP file.
Unzip the file.
Solaris, Linux, and Mac OS X systems:
unzip zip-file-name
zip-file-name is the name of the file that you downloaded.
For example:
unzip ogs-3.1.2.zip
Windows systems:
Unzip using your favorite file compression utility.
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.
Start GlassFish Server using the instructions in the Oracle GlassFish Server Quick Start Guide.
The guide explains how to perform basic tasks such as starting the server, accessing the Administration Console, and deploying a sample application.
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.
The following topics are addressed here:
Note:
Console installation is not supported in Oracle GlassFish Server 3.1.2. Silent mode installation is available, however. For more information, see Performing a Silent Mode Installation.
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.
Ensure that your system meets the requirements listed in "Hardware and Software Requirements" in Oracle GlassFish Server Release Notes.
See "Known Issues" in Oracle GlassFish Server Release Notes for known issues related to installation.
Download the desired GlassFish Server 3.1.2 bundle.
See GlassFish Server Download Locations for a list of download locations. See Table 1-4 for a list of available self-extracting bundles.
Change to the directory where you downloaded the self-extracting file.
Start the installer.
Solaris, Linux, and Mac OS X systems:
If necessary, grant execute permissions to the self-extracting file:
chmod +x ./self-extracting-file-name
self-extracting-file-name is the name of the self-extracting file that you downloaded.
At the command prompt, type:
sh ./self-extracting-file-name
For example, start the installer by typing the following:
sh ./ogs-3.1.2-unix.sh
See Installation Command-Line Options for a list of command-line options you can specify here, if desired.
Windows systems:
Double-click the executable .exe installation file.
For example, double-click:
ogs-3.1.2-windows.exe
On Windows you can also start the installer by typing the file name at the command prompt.
Note:
Additional setup options are available. See Installation Command-Line Options.
If you are installing on a 64-bit Windows system, run the installer with the -j option pointing to a 64-bit JDK.
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.
After starting the installer, the Introduction page is displayed. Use the Next button to move through the installation process.
Choose the Installation Type
Typical Installation
Choose this option for application development purposes or non-production use only. This option installs the GlassFish Server binaries and creates a DAS.
Custom Installation
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.
The remainder of this procedure describes the steps in the Typical Installation path. If you are performing a Custom Installation, skip the remainder of this procedure and jump instead to To Perform a Custom Installation.
Specify where to install GlassFish Server.
The default installation directories are as follows:
Solaris, Linux, and Mac OS X systems
user-home-directory/glassfish3
Windows systems
SystemDrive\glassfish3
Make sure the directory you specify is empty before installing the product.
The default installation directory is referred to as as-install-parent throughout the GlassFish Server documentation.
Specify whether to install and enable Update Tool.
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 are not installing Update Tool, deselect the Install Update Tool check box.
If you are installing Update Tool and your system accesses the Internet through a proxy, specify the proxy host and proxy port.
If you are installing Update Tool and do not require the automatic notifications of available updates after installation, deselect the Enable Update Tool check box.
Note:
Update Tool differs from Upgrade Tool, which is used to migrate the configuration and deployed applications from an earlier version of GlassFish Server to the current version. For more information about Upgrade Tool, see the Oracle GlassFish Server Upgrade Guide.
Review the Ready To Install selections and click Install to proceed with the installation.
A progress bar is displayed as the core GlassFish Server components are installed.
Note:
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.
Review the Domain Info options.
Tailor the default values displayed to suit your needs and then click Next to proceed.
Note:
To secure your domain, you should provide a password for the admin user.
Review the Config Results page and click Next to proceed.
Tip:
The configuration results panel presents the recently executed commands in the center section and this is selectable text. The text can be copied on to a script for future automated runs of such commands.
Review the Summary page and click Exit to exit the installer.
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.
Register your GlassFish Server product.
Follow the instructions on the registration screen to complete the registration process.
Familiarize yourself with the instructions in the Oracle GlassFish Server Quick Start Guide. The guide explains how to perform basic tasks such as starting the server, accessing the Administration Console, and deploying a sample application.
This procedure builds upon the instructions provided for the Typical Installation path in To Install GlassFish Server Using the Self-Extracting File.
Complete the steps in To Install GlassFish Server Using the Self-Extracting File.
Choose the kind of Custom Installation you want to perform.
Install and Configure
Install the GlassFish Server binaries, and then configure a DAS and one or more standalone server instances, clusters, or clustered instances.
Install Only
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 an Existing Installation
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.
The remainder of this procedure explains the Install and Configure option. Most of these steps also apply to the other options.
Specify where to install GlassFish Server.
The default installation directories are as follows:
Solaris, Linux, and Mac OS X systems
user-home-directory/glassfish3
Windows systems
SystemDrive\glassfish3
Make sure the directory you specify is empty before installing the product.
The default installation directory is referred to as as-install-parent throughout the GlassFish Server documentation.
Specify the path to the JDK to be used with the installation.
Use a JDK installation detected by the installer or specify the path for a different JDK.
JDK 6 is required. See Installation Requirements for more information.
Note:
This JDK page is not presented for Mac OS X installations. The installation uses the value in the JAVA_HOME environment variable.
Specify whether to install Update Tool.
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 are not installing Update Tool, deselect the Install Update Tool check box.
If you are installing Update Tool and your system accesses the Internet through a proxy, specify the proxy host and proxy port.
If you are installing Update Tool and do not require the automatic notifications of available updates after installation, deselect the Enable Update Tool check box.
Note:
Update Tool differs from Upgrade Tool, which is used to migrate the configuration and deployed applications from an earlier version of GlassFish Server to the current version. For more information about Upgrade Tool, see the Oracle GlassFish Server Upgrade Guide.
Review the Ready To Install selections and click Install to proceed with the installation.
A progress bar is displayed as the core GlassFish Server components are installed and the default domain is automatically created and started.
Note:
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.
When the core installation has completed, the installer displays the Configuration page.
Configure GlassFish Server components.
The general procedure for configuring server components involves the following substeps:
Choose a component configuration option:
Create a Domain Administration Server (DAS). At least one DAS must be created and running before you can configure any other components. The parameters in the Configuration screen for this option are described in Parameters for the Create a server domain Option.
Create a standalone GlassFish Server instance. The parameters in the Configuration screen for this option are described in Parameters for the Create a standalone server instance Option.
Create a new cluster or a clustered server instance in a new or existing a cluster. The parameters in the Configuration screen for this option are described in Parameters for the Create a clustered server instance Option.
Skip any additional component configuration and proceed immediately to the final steps of the installation and configuration wizard.
When configuring a new or previously unconfigured GlassFish Server installation you must choose the first option, Create a server domain, before proceeding with any of the other options. Once at least one server domain has been created, you can choose any of the other options in any order you wish, including creating additional domains.
Configure the selected component.
Each configuration option displays its own configuration screen. The specific options in each configuration screen are described after this procedure, in Custom Configuration Parameters.
Choose how you want to proceed.
After configuring any one of the available options, a Configuration Results screen is displayed. In addition to displaying the configuration results, three buttons are displayed:
Cancel the configuration and exit the installation wizard. Note that the core GlassFish Server components will already be installed at this point, as well as any configurations that may have been configured during this step or during another installation. To remove the core GlassFish Server components and any configurations, follow the instructions in Uninstalling GlassFish Server 3.1.2
Return to the Configuration page so you can configure another item.
Complete the configuration option and continue to the final steps of the installation and configuration wizard. Note that this label becomes "Exit" if this is a Custom Installation and the "Configure Existing Installation" option is selected.
Tip:
The configuration results panel presents the recently executed command in the center section. This is selectable text, and it can be copied to a script for future automated runs of such commands.
When you have configured all the components you want and then clicked the Next button, the final configuration option is performed and a Summary screen is displayed.
Click Exit to exit the installation and configuration wizard.
A web browser is displayed so you can register your GlassFish Server product.
Register your GlassFish Server product.
Follow the instructions on the registration screen to complete the registration process.
If you are done with the installation at this point, it is recommended that you familiarize yourself with the instructions in the Oracle GlassFish Server Quick Start Guide. The guide explains how to perform basic tasks such as starting the server, accessing the Administration Console, and deploying a sample application.
This section lists the configuration parameters in the screens displayed for the options in Step 7 in To Perform a Custom Installation.
Parameters for the Create a standalone server instance Option
Parameters for the Create a clustered server instance Option
The following are the parameters displayed in the Configuration screen when you choose the Create a server domain option in Step 7 in To Perform a Custom Installation. This option enables you to create a Domain Administration Server (DAS)
The unique domain name to use for the DAS. The default name is domain1.
The port on which the GlassFish Server Admin Console will listen. The default port is 4848.
The port on which the non-secure HTTP server will listen. The default port is 8080. Note that the port used for the secure HTTP listener is 8181.
The user name for administrative access to the GlassFish Server Admin Console.
The password for administrative access to the GlassFish Server Admin Console. You can leave this parameter empty to enable unauthenticated logins to the Admin Console, but make sure that the Username field has "admin" as the input value. Specifying a password is highly recommended if you are installing GlassFish Server in a production environment.
Reenter the password to verify your typing.
Specify whether an operating system service will be created for the DAS. The service will be started when the operating system is booted.
If a service is not created here, the DAS can be started manually using the asadmin start-domain subcommand.
Note:
The Create Operating System Service option is not available on Mac OS X systems. Also note that on Unix or Linux systems, you must run the installer as superuser or root if you want to create a system service for the domain.
Specify the name for the DAS operating system service. The default name is domain1Service. This parameter is only required if the Create Operating System service parameter is enabled.
Start the domain as soon as it is created. This option is enabled by default. Note that is necessary for the DAS to be running before you can configure any server instances or clusters. If you choose to not start the domain at this time, you can start it manually later using the asadmin start-domain subcommand.
Note:
Ensure that this option is enabled if you plan on performing more configurations during this installation procedure. The DAS must be running in order to create any server instances or clusters.
The following are the parameters displayed in the Configuration screen when you choose the Create a standalone server instance option in step 7 in To Perform a Custom Installation. This option enables you to create a standalone GlassFish Server instance.
Note:
The DAS for the domain in which the standalone server instance will be created must be running with the specified name and at the specified port before configuring a standalone server instance. See the Parameters for the Create a server domain Option for instructions.
The unique name to use for the standalone GlassFish Server instance. If the name is already in use, an error will be generated when the configuration is performed. The default name is instance1.
The name of the physical host on which the DAS is running. The default name is localhost.
The administration port on which the DAS is running. The default port is 4848.
The following are the parameters displayed in the Configuration screen when you choose the Create a clustered server instance option in Step 7 in To Perform a Custom Installation. This option enables you to create a new cluster or a clustered server instance in a new or existing a cluster.
Note:
The DAS for the domain in which the standalone server instance will be created must be running with the specified name and at the specified port before configuring a cluster or clustered server instance. See the Parameters for the Create a server domain Option for instructions.
The unique name to use for the clustered GlassFish Server instance. If the name is already in use, an error will be generated when the configuration is performed. The default name is instance1.
The name of the physical host on which the DAS is running. The default name is localhost.
The administration port on which the DAS is running. The default port is 4848.
Specify whether a new cluster will be created at this time. The default is to leave this option disabled. If left disabled, the cluster specified in the Cluster Name field, below, must already exist.
Ensure that this option is enabled if the cluster in which you want to create the clustered server instance does not yet exist.
Ensure that this option is disabled if the cluster in which you want to create the clustered server existence already exists.
The unique name to use for the cluster. If the name is already in use, an error will be generated when the configuration is performed. The default name is c1.
The name of the DAS in which the cluster will run. The default name is domain1.
This section describes how to install Oracle GlassFish Server 3.1.2 using silent mode installation. Silent mode is a non-interactive installation based on user-defined parameters captured in an answer file. The answer file can be used later to install GlassFish Server on one or more systems.
Note:
It is only possible to perform a silent installation using the Typical Installation path described in To Install GlassFish Server Using the Self-Extracting File. It is not possible to perform a silent installation using the more complex Custom Installation path described in To Perform a Custom Installation.
The following topics are addressed here:
The answer file forms the template for silent installation. The file is created when you use the dry-run (-n) option to start an interactive installation. In dry-run mode, actual installation does not take place.
During the interactive installation you can accept the default values presented or you can change them. Your input is collected and stored in the answer file, which is then used to install GlassFish Server. You can use the answer file as it is or you can modify the file before using it.
The installation wizard is used to create the answer file. Actual installation does not take place.
Remember that it is only possible to perform a silent installation using the Typical Installation path described in To Install GlassFish Server Using the Self-Extracting File. It is not possible to perform a silent installation using the more complex Custom Installation path described in To Perform a Custom Installation.
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.
Ensure that your system meets the requirements listed in "Hardware and Software Requirements" in Oracle GlassFish Server Release Notes.
See "Known Issues" in Oracle GlassFish Server Release Notes for known issues related to installation.
Download the desired GlassFish Server 3.1.2 bundle.
See GlassFish Server Download Locations for a list of download locations. See Table 1-4 for a list of available self-extracting bundles.
Change to the directory where you downloaded the self-extracting file.
Start the installer in dry-run mode.
Solaris, Linux, and Mac OS X systems:
If necessary, grant execute permissions to the self-extracting file:
chmod +x ./self-extracting-file-name
self-extracting-file-name is the name of the self-extracting file that you downloaded.
At the command prompt, type:
self-extracting-file-name -n answer-file
answer-file is the name of the answer file you want to generate. If you do not include a path to the answer file, the file is created under the directory from which the installation program is run.
For example, start the installer in dry-run mode by typing the following:
ogs-3.1.2-unix.sh -n 312-answer
See Installation Command-Line Options for a list of command-line options you can specify here, if desired.
Windows systems:
Open a Windows Command Prompt shell with Administrative privileges.
At the command prompt, type:
self-extracting-file-name -n answer-file
answer-file is the name of the answer file you want to generate. If you do not include a path to the answer file, the file is created under the directory from which the installation program is run.
For example, start the installer in dry-run mode by typing the following:
ogs-3.1.2-windows.exe -n 312-answer
See Installation Command-Line Options for a list of command-line options you can specify here, if desired.
Note:
Additional setup options are available. See Installation Command-Line Options.
If you are installing on a 64-bit Windows system, run the installer with the -j option pointing to a 64-bit JDK.
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.
After starting the installer, the Introduction page is displayed. Use the Next button to move through the installation process.
Choose Typical Installation in the Installation Type screen.
It is not possible to use the Custom Installation path when generating an answer file for silent-mode installation.
Specify where to install GlassFish Server.
The default installation directories are as follows:
Solaris, Linux, and Mac OS X systems
user-home-directory/glassfish3
Windows systems
SystemDrive\glassfish3
Make sure the directory you specify is empty before installing the product.
The default installation directory is referred to as as-install-parent throughout the GlassFish Server documentation.
Specify whether to install and enable Update Tool.
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 are not installing Update Tool, deselect the Install Update Tool check box.
If you are installing Update Tool and your system accesses the Internet through a proxy, specify the proxy host and proxy port.
If you are installing Update Tool and do not require the automatic notifications of available updates after installation, deselect the Enable Update Tool check box.
Note:
Update Tool differs from Upgrade Tool, which is used to migrate the configuration and deployed applications from an earlier version of GlassFish Server to the current version. For more information about Upgrade Tool, see the Oracle GlassFish Server Upgrade Guide.
Review the Ready To Install selections and click Install to proceed with the installation.
A progress bar is displayed as the answer file is created and an empty as-install-parent directory is created.
Tip:
The configuration results panel presents the recently executed command in the center section and this is a selectable text. The text can be copied on to a script for future automated runs of such commands.
Review the summary page and click Exit to exit the installer.
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.
Proceed to the instructions in Reviewing the Installation Answer File.
The answer file generated using the procedure described in Creating the Installation Answer File provides a number of system-specific parameters as well as parameters that you selected during dry-run mode installation. Values for some parameters can be edited as described in To Edit the Answer File.
The following example shows the contents of an answer file that was created during a dry-run mode installation. All default values were accepted during the installation.
Note:
The following example contains a complete answer file, where most of the parameters are not used in GlassFish Server 3.1.2. For an answer file template that contains only the elements required to perform a typical installation, see the Example 1-2.
Example 1-1 Example Answer File
#openInstaller Dry Run Answer File. This File can be used as input to the openInstaller engine using the -a option. #Sun Jan 16 16:56:14 EST 2011 InstallType.Option.INSTALL_AND_CONFIG=INSTALL_AND_CONFIG UpdateTool.Configuration.PROXY_PORT= SOAccountCreation.accountinfo.FIRSTNAME= ClusteredInstance.Configuration.CLUSTER_NAME=c1 Domain.Configuration.ADMIN_PASSWORD_REENTER= StandaloneInstance.Configuration.SERVER_HOST_NAME=localhost RegistrationOptions.regoptions.USE_EXISTINGACCT=USE_EXISTINGACCT Domain.Configuration.ADMIN_PASSWORD= UpdateTool.Configuration.BOOTSTRAP_UPDATETOOL=true RegistrationOptions.regoptions.USERNAME= StandaloneInstance.Configuration.INSTANCE_NAME=instance1 ClusteredInstance.Configuration.INSTANCE_NAME=instance1 SOAccountCreation.accountinfo.EMAIL= ClusteredInstance.Configuration.SERVER_ADMIN_PORT=4848 Domain.Configuration.CREATE_SERVICE=false ClusteredInstance.Configuration.CREATE_CLUSTER=false InstallUserType.Option.ADVANCED_USER=ADVANCED_USER UpdateTool.Configuration.ALLOW_UPDATE_CHECK=true SOAccountCreation.accountinfo.LASTNAME= RegistrationOptions.regoptions.CREATE_NEWACCT=CREATE_NEWACCT JDKSelection.directory.HIDDEN_JDK= SOAccountCreation.accountinfo.PASSWORD= ConfigType.Option.CREATE_CLUSTEREDINSTANCE=CREATE_CLUSTEREDINSTANCE JDKSelection.directory.JDK_LIST= ClusteredInstance.Configuration.SERVER_HOST_NAME=localhost SOAccountCreation.accountinfo.REENTERPASSWORD= JDKSelection.directory.JDK_TYPED_IN_CHOICE=false UpdateTool.Configuration.PROXY_HOST= InstallType.Option.INSTALL_ONLY=INSTALL_ONLY ConfigType.Option.CREATE_STANDALONEINSTANCE=CREATE_STANDALONEINSTANCE Domain.Configuration.HTTP_PORT=8080 RegistrationOptions.regoptions.SKIP_REGISTRATION=SKIP_REGISTRATION Domain.Configuration.SERVICE_NAME=domain1Service ConfigType.Option.NO_CONFIGURATION=NO_CONFIGURATION Domain.Configuration.ADMIN_USER=admin JDKSelection.directory.JDK_FROM_LIST_CHOICE=false RegistrationOptions.regoptions.USERPASSWORD= SOAccountCreation.accountinfo.COUNTRY= InstallHome.directory.INSTALL_HOME=C\:\\glassfish3 Domain.Configuration.ADMIN_PORT=4848 SOAccountCreation.accountinfo.COMPANYNAME= InstallUserType.Option.BASIC_USER=BASIC_USER ConfigType.Option.CREATE_DOMAIN=CREATE_DOMAIN InstallType.Option.CONFIG_ONLY=CONFIG_ONLY Domain.Configuration.START_SERVER=false Domain.Configuration.DOMAIN_NAME=domain1 ClusteredInstance.Configuration.DOMAIN_NAME=domain1 JDKSelection.directory.JDK_TYPE_IN= StandaloneInstance.Configuration.SERVER_ADMIN_PORT=4848 SOAccountCreation.accountinfo.COUNTRY_DROP_DOWN= RegistrationOptions.regoptions.DUMMY_PROP=
Example 1-2 Answer File Template for GlassFish Server 3.1.2
#openInstaller Dry Run Answer File. This File can be used as input to the openInstaller engine using the -a option. Domain.Configuration.ADMIN_PASSWORD= Domain.Configuration.ADMIN_PASSWORD_REENTER= Domain.Configuration.ADMIN_PORT=4848 Domain.Configuration.ADMIN_USER=admin Domain.Configuration.DOMAIN_NAME=domain1 Domain.Configuration.HTTP_PORT=8080 InstallHome.directory.INSTALL_HOME=C\:\\glassfish3 UpdateTool.Configuration.ALLOW_UPDATE_CHECK=true UpdateTool.Configuration.BOOTSTRAP_UPDATETOOL=true UpdateTool.Configuration.PROXY_HOST= UpdateTool.Configuration.PROXY_PORT=8888
Some values in the answer file can be changed if desired. Such editing is strictly optional.
Create the answer file as described in To Create the Installation Answer File.
Review the answer file.
Review the values that will be used for silent installation.
Edit the answer file.
Only the following default values can be changed:
InstallHome.directory.INSTALL_HOME=as-install-parentProvide another directory name for GlassFish Server 3.1.2 installation files.
Domain.Configuration.ADMIN_PASSWORD=Provide a password for access to the Administration Console. This password is case sensitive.
Domain.Configuration.ADMIN_PASSWORD_REENTER=Provide the password confirmation for Administration Console. Make sure that this matches the value for Domain.Configuration.ADMIN_PASSWORD.
Domain.Configuration.ADMIN_PORT=4848Assign another port number to the Administration Console.
Domain.Configuration.ADMIN_USER=adminProvide another user name for the administrator. This name is case sensitive.
Domain.Configuration.HTTP_Port=8080Assign another port number to HTTP connections.
UpdateTool.Configuration.ALLOW_UPDATE_CHECK=trueChange value to false if you do not want Update Tool notifications.
UpdateTool.Configuration.BOOTSTRAP_UPDATE=trueChange value to false if you do not want to install the standalone Update Tool.
UpdateTool.Configuration.PROXY_HOST=Assign a name to the proxy host.
UpdateTool.Configuration.PROXY_PORT=Assign a port number to the proxy host.
Note:
Parameters not listed are system specific. Do not change system-specific parameters. Doing so will cause problems with the installation program.
The non-interactive installation program reads the specified answer file, checks for adequate disk space, and installs GlassFish Server based on the data in the answer file.
Create the answer file as described in To Create the Installation Answer File. Verify that the parameters in the answer file are set to the values that you want to use for silent installation, as described in Reviewing the Installation Answer File.
Answer files generated using the GlassFish Server 3.1.2 installer are not backward-compatible with earlier versions of GlassFish Server including version 3.1.2.
Navigate to the directory that contains the self-extracting installer file and the installation answer file.
From the command line, type:
self-extracting-file-name -a answer-file -s
self-extracting-file-name is the name of the file that you downloaded during Creating the Installation Answer File.
-a answer-fileThe name of the answer file that was generated according to the instructions in Creating the Installation Answer File. Ensure that you provide the complete path to the answer file.
-sRuns the installer in silent mode.
For example:
ogs-3.1.2-unix.sh -a 312-answer -s
When the prompt is returned, the silent installation is complete and the installation components are installed on your system.
Familiarize yourself with the instructions in the Oracle GlassFish Server Quick Start Guide. The guide explains how to perform basic tasks such as starting the server, accessing the Administration Console, and deploying a sample application.
The following options can be used when you run the installation program from the command line using the self-extracting installation file (.sh or .exe). Specify the desired options after typing the installation file name at the command prompt.
For example:
ogs-3.1.2-unix.sh -a 312-answer -l log-directory -s
The options are as follows:
-a answer-fileRun the installation program in silent mode using the answer file specified. Use this option with the -s option.
-l log-directoryWrite log information to this directory.
-qSet logging level to WARNING.
-vRuns the installation program in verbose mode, which can be useful for troubleshooting. Also sets the logging level to FINEST.
-sRun the installation program in silent mode.
-j javahomeUse this directory for the JDK software installation.
-n answer-fileRun the installation program in trial mode to generate the answer file for silent mode installation.
-h or -helpDisplay the help message listing these options.