The following topics are addressed in this section:. The answer file forms the template for silent installation. The file is created when you use the trial mode -n option to start an interactive installation. In trial 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. If you do not include a path to the file, the file is created under the directory from which the installation program is run.
Review the Ready to Install selections and click Install to proceed with trial mode installation and create the answer file. Unless a path to the file was specified in Step 2 , the answer file is created under the directory from which the installation program is run.
The answer file provides a number of system-specific parameters as well as parameters that you selected during trial 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 trial mode installation. Default values were accepted during the installation. Some values in the answer file can be changed if desired. Such editing is strictly optional.
Can be set to true or false. Always set this value to true if you are using the answer file for silent installation. 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.
Verify that the parameters in the answer file are set to the values that you want to use for silent installation. Navigate to the directory that contains the self-extracting installer file and the installation answer file. Ensure that you provide the complete path to the answer file. When the prompt is returned, the silent installation is complete and the installation components are installed on your system.
The following options can be used when you run the installation program from the command line using the self-extracting installation file. If Contributor obtains such knowledge after the Modification is made available as described in Section 3. Contributor represents that, except as disclosed pursuant to Section 3.
You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location such as a relevant directory where a user would be likely to look for such a notice. If You created one or more Modification s You may add your name as a Contributor to the notice described in Exhibit A.
You must also duplicate this License in any documentation for the Source Code where You describe recipients' rights or ownership rights relating to Covered Code.
You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor.
You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer. You may distribute Covered Code in Executable form only if the requirements of Section 3.
The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor.
You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer. You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product.
In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code. If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: a comply with the terms of this License to the maximum extent possible; and b describe the limitations and the code they affect.
Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. Each version will be given a distinguishing version number. Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by Netscape.
No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License. Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach.
All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive. If You initiate litigation by asserting a patent infringement claim excluding declatory judgment actions against Initial Developer or a Contributor the Initial Developer or Contributor against whom You file such action is referred to as "Participant" alleging that:.
If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2. Provides the option to install the full Update Tool and pkg utility at installation time. Each of the installation methods listed in Table also let you choose to install either the GlassFish Server Full Platform or Web Profile distribution.
Table 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.
The Oracle GlassFish Server 3. 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. This section describes how to install Oracle GlassFish Server 3. GlassFish Server is installed by unzipping the file in the installation directory of your choice.
Any configuration changes, such as creating domains, clusters, and server instances, must be made manually after installation. See Table for a list of available ZIP files. GlassFish Server 3. This glassfish3 directory is referred to throughout the GlassFish Server documentation set as as-install-parent.
The guide explains how to perform basic tasks such as starting the server, accessing the Administration Console, and deploying a sample application. Console installation is not supported in Oracle GlassFish Server 3. 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. See Table for a list of available self-extracting bundles. See Installation Command-Line Options for a list of command-line options you can specify here, if desired. Additional setup options are available. See Installation Command-Line Options. If you are installing on a bit Windows system, run the installer with the -j option pointing to a 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 this option for application development purposes or non-production use only.
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.
The default installation directory is referred to as as-install-parent throughout the GlassFish Server documentation. Update Tool is an administrative tool that enables you to install updates and add-on components to an existing GlassFish Server 3.
Update Tool can be installed during GlassFish Server installation or at a later time. 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. 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. 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. 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. Installation information is captured in log files. The names of the files are timestamp -install. Install the GlassFish Server binaries, and then configure a DAS and one or more standalone server instances, clusters, or clustered instances.
You can rerun the GlassFish Server installation wizard at a later time and choose the Configure an Existing Installation option to configure the items. 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. The remainder of this procedure explains the Install and Configure option. Most of these steps also apply to the other options. A progress bar is displayed as the core GlassFish Server components are installed and the default domain is automatically created and started.
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.
Each configuration option displays its own configuration screen. The specific options in each configuration screen are described after this procedure, in Custom Configuration Parameters.
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.
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.
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.
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. This section lists the configuration parameters in the screens displayed for the options in Step 7 in To Perform a Custom Installation. 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.
The default port is The port on which the non-secure HTTP server will listen. Note that the port used for the secure HTTP listener is 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. 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. 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. Alternatively, if you are running on Windows and want to run the uninstaller from the Windows Start menu, you can skip this step and jump ahead to the next step.
The default installation directory is referred to as as-install-parent throughout GlassFish Server documentation. The problem may occur when the Java binaries are not installed through a standard Java SDK installer. This problem does not occur when running the uninstaller from the Windows Start menu.
The workaround for this issue is to explicitly specify the location of the Java binaries when running the GlassFish Server uninstall utility from the command line. For example:. Note - To uninstall in silent non-interactive mode, use the -s option after the file name. Uninstallation information is captured in log files. The names of the files are timestamp -remove.
0コメント