Java SE 7 Archive Downloads. Go to the Oracle Java Archive page. Thank you for downloading this release of the Java TM Platform, Standard Edition Development Kit (JDK TM).The JDK is a development environment for building applications, applets, and components using the Java programming language. Default Plug-in NPRuntime Script Plug-in Library for Java(TM) Deploy Shockwave Flash 10.0 r45 iTunes Detector Plug-in GEPlugin Windows Presentation Foundation (WPF) plug-in for Mozilla browsers Google Update Adobe PDF Plug-In For Firefox and Netscape The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages.
- Download the Java plug-in from this server and install it manually (Internet Explorer 11) Download the Java plug-in from this server and install it. To install the Java Plugin follow these steps: Exit Firefox.
- Java Plug In free download - DJ Java Decompiler, Java Runtime Environment (JRE) (64-Bit), Java Launcher, and many more programs.
- To install the Java plug-in files, you must copy the Java plug-in files to the appropriate folders on the AR System server. The following section describes the prerequisites and steps to manually install the Java plug-in files.
vSphere Integrated Containers provides a plug-in for the HTML5 vSphere Client on vCenter Server 6.5 and 6.7. The HTML5 plug-in allows you to to deploy and interact with virtual container hosts (VCHs) directly in the vSphere Client.
vSphere Integrated Containers also provides a basic informational plug-in for the Flex-based vSphere Web Client on vCenter Server 6.0.
For information about the Flex-based vSphere Web Client and the HTML5 vSphere Client, see Introduction to the vSphere Client in the vSphere documentation.
IMPORTANT: If you installed a version of vSphere Integrated Containers that pre-dates 1.4.3, you must install the plug-in manually. You can manually deploy the plug-in on a vCenter Server instance that runs on Windows, or on a vCenter Server Appliance.
If you installed vSphere Integrated Containers 1.4.3 or later, by default the plug-in is installed automatically with no user action required. If you deselected the option to install the plug-in when you deployed the vSphere Integrated Containers appliance, you can subsequently install the plug-in by reinitializing the appliance. For information, see Reinitialize the vSphere Integrated Containers Appliance.
IMPORTANT: If you use vSphere 6.7 update 1 or later, you must use vSphere Integrated Containers 1.4.3 or later. Due to significant changes in the HTML5 vSphere Client in version 6.7 update 1, previous versions of the vSphere Integrated Containers plug-in for the vSphere Client might not work with that version. Only version 1.4.3 and later releases have been verified with vSphere 6.7 update 1.
This chapter provides instructions for installing the Sun Java System Application Server software.The following topics are discussed:
You can download GlassFish Application Server from https://glassfish.dev.java.net/public/downloadsindex.html.The GlassFish v2 distribution includes the Application Server software, the Sun Java System MessageQueue 4.1, Java DB, and ant 1.6.5. You can run GlassFish on Solaris SPARC,Solaris x86, Linux, Windows, and Mac OS.
Application Server 9.1 product distribution is available as: ApplicationServer 9.1 with HADB and Application Server 9.1 without HADB. The standalone Application Server 9.1is available at http://www.sun.com/download.
Application Server 9.1 without HADB includes the load balancing plug-in,Java DB, and Sun Java System Message Queue 4.1. Application Server 9.1 with HADBincludes the load balancing plug-in, Java SE Development Kit (JDK) 5, JavaDB, Sun Java System Message Queue 4.1, and HADB.
The Java ES 5 Update 1 distribution includes a Application Server 9.1 distributionas an optional download. This distribution includes HADB in addition to theload balancing plug-in, Java Development Kit (JDK) 5, Java DB, and the Sun Java System MessageQueue 4.1.
Application Server 9.1 is also part of the Java EE SDK and the Java ApplicationPlatform SDK. You can download these distributions from http://java.sun.com/javaee/downloads/index.jsp.
You can download the latest version of Sun Java System Access ManagerPolicy Agent 2.2 from http://www.sun.com/download.For more information on how the Access Manager Policy Agent works with the Application Server 9.1,see Sun Java System Access Manager Policy Agent 2.2 Guide for Sun Java SystemApplication Server 9.0/9.1 on docs.sun.com.
This section provides instructions for installing GlassFish v2 distributionand for installing the load balancing plug-in for GlassFish v2. This distributiondoes not support upgrades or patching.
To Install GlassFish Application Server
Before You Begin
Get JDK (Java SE Developerment Kit) 5 or higher from http://java.sun.com/javase/, if you are using Solaris,Linux, or Windows..
If you are using Mac OS X, you need to download JDK 5 (supported onMac OS X 1.4 or later) from http://www.apple.com/support/downloads/java2se50release3.html andmake JDK 5 the default JVM.
- Download the GlassFish v2 distribution https://glassfish.dev.java.net/public/downloadsindex.html.
- Set the environment variable JAVA_HOME to pointto the directory in which JDK 5 is installed.
- Run the following command:java -Xmx256m-jar <filename>.jar
- Set ANT_HOME to point to the ant 1.6.5 installation,which is at <downloaded-dir>/glassfish/lib/ant directory.
- Navigate to the glassfish directory:cd glassfish
- If you do not want clustering capabilities, run the followingcommand:ant -f setup.xml
- If you want to use GlassFish with clustering, change the commandto:ant -f setup-cluster.xml
To Install the Load Balancing Plug-in (standalone)
Use the procedures in this section if the load balancing plug-in isnot part of the Application Server distribution you are using. If you are usingthe Sun Java System Application Server 9.1 (bundle with HADB), see To Install Application Server 9.1 with HADB forinstructions for installing the load balancing plug-in.
The load balancing plug-in is not currently bundled with the GlassFishv2Application Server. If you want load balancing capabilities, you can downloadthe load balancing plug-in from the following locations:
- Solaris (SPARC): http://download.java.net/javaee5/external/SunOS/aslb/jars/
- Solaris (x86): http://download.java.net/javaee5/external/SunOS_X86/aslb/jars/
- Linux: http://download.java.net/javaee5/external/Linux/aslb/jars/
- Windows: http://download.java.net/javaee5/external/WINNT/aslb/jars/
- Mac OS: http://download.java.net/javaee5/external/Darwin/aslb/jars/
- Before you install the load balancer plug-in, ensure that youhave installed a supported web server. For a list of supported web servers,see WebServers in Sun Java System ApplicationServer 9.1 Release Notes.
- Create the lbplugin directory within <glassfish_install_dir>/lib.
- Unjar this file in the lbplugin directory.Run the following command: jar -xvf <lbplugin>.jar.
- Unzip the following two files: SUNWaslb.zip and SUNWaspx.zip in the same directory. Delete the zip files.
- Change permissions on all shared libraries within lbplugin directory.Run the following command: chmod -R 755 ${glassfish.home}/lib/lbplugin/lib.
- Create a configuration for the load balancer. See Settingup Load Balancing in Sun Java System ApplicationServer 9.1 Quick Start Guide.
- Restart the Web Server after creating a configuration for theload balancer.
Next Steps
You need to configure Web Server for load balancing. For detailed instructionson manually configuring Web Server for load balancing, see ConfiguringSun Java System Web Server in Sun JavaSystem Application Server 9.1 High Availability Administration Guide.
If you are using the Sun Java System Application Server 9.1 distributed asan optional download with the Java Enterprise System 5 Update 1 (Java ES 5Update 1) release, use the following procedure:
- Install Sun Java System Application Server 9.1. For instructionson how to install Application Server 9.1, see Installing Application Server 9.1.
- After the installation is complete, start the domain.On Solaris or Linux, Application Server 9.1 installer detects earlier versionsof Application Server or other Java ES Components installed in native package formatand automatically performs the upgrade of the binaries.
- Start the Java ES 5 Update 1 installation.
The Java ES Update 1 installer could report that conflict were detectedin Application Server components. Ignore these conflict messages and proceedwith the installation.
Java ES 5 Update 1 installer validates the Application Server installationand then installs the selected Java ES components.
Note – Application Server 9.1 is not supported with Java ES 5 and needsthe Java ES 5 Update 1 Portal Server. Portal Server for Java ES 5 Update 1is not supported on Windows.
If you run into problems with usingthe Portal Server database while using Application Server 9.1 with Java ES5 Update 1 Portal Server, see the Portal Database Not Found After Java DBRestart in the Java ES 5 Update 1 Installation Guide.
To Perform a Cleanup after Partial Installation
This procedure describes how to perform a cleanup on your machine aftera partial, failed installation of the package-based Application Server 9.1distribution. You can use this procedure for preparing your machine for installingApplication Server.
- Remove the partly installed Application Server by running thefollowing commands:On Solaris:cd /var/sadm/pkgls -ltrpkgrm <Application Server packages>On Linux:rpm -qa|grep -i sunrpm -e <Application Server rpm>
- If you have removed packages manually, you need to delete thecorrespondent entries from the productregistry file ordelete the productregistry file.The locationof productregistry file: /var/sadm/install directoryon Solaris, /var/tmp/ directory on Linux.
- Kill any running Application Server processes.
- Remove the Application Server installation directory.
To Configure Registry Server with Application Server9.1
Before You Begin
If you are using Application Server 9.1 with Java ES 5 Update 1, youneed to install Registry Server manually from the Java ES 5 Update 1 distributiondirectory from <JavaES_ditribution_dir>/<OS>/Products/registry-svr/Packages directory.
The following procedure describes how to Configure Registry Server fromJava ES 5 Update 1 to work with Application Server 9.1.
- Run the following command:cd <registry_server_install_dir>/installOn Solaris, <registry_server_install_dir> is /opt/SUNWsrvc-registry, by default.On Linux, the default install location is /opt/sun/srvc-registry.
- Run the following command:<Ant-base_dir>/ant -f build-install.xml -Dinstall.properties=./install.propertiesinstallWhere <Ant-base_dir> is /usr/sfw/bin on Solaris and /opt/sun/share/bin onLinux.
- Run the following command:<Ant-base_dir>/ant -f build-install.xml appserver.deploy.as9
- Run the following command:<Ant-base_dir>/ant -f build-install.xml appserver.domain.stop
- Run the following command:<Ant-base_dir>/ant -f build-install.xml appserver.domain.start
If you are using the Sun Java System Application Server 9.1 file-based installation,use one of the following procedures:
To Install Application Server 9.1 without HADB
Before You Begin
Use this procedure if you are using the Sun Java System Application Server file—basedinstaller. Verify that your system meets the requirements specified in Hardwareand Software Requirements in Sun JavaSystem Application Server 9.1 Release Notes.
Solaris and Linux installations support both root and non-root userinstallations. Users of Windows installations should have Power User or Administratoraccess. If you areinstalling as a non-root user on Solaris or Linux, you must have read-writeaccess to the following directories:
- The installation directory you select
- The home directory of the installation user
- The /var/tmp directory
- The /tmp directory
- The web server installation directory and the web server instancedirectory, if applicable.
- Navigate to the directory where you downloaded the distributionfile.
- If you have downloaded a .bin file, change the permission of thedistribution file so that you have execute access:chmod+xdistribution_filename
- Run the installation program.
- If you are installing from a .bin file, use the following commandto run the installation program :./distribution_filenameUse the -console option to run the installation program in command-line mode.
- If you are installing from a .zip file, unzip the file, navigateto the extracted folder, and run the following command:./setupUse the -console option to run theinstallation program in command-line mode.
- If you are installing from an .exe file on Windows, double-clickthe file.
- Specify the directory where you want to install the software oraccept the default installation directory.
- Choose toinstall JDK 5 or use a pre-installed JDK 5.
- In the Administration Configuration page (or when prompted atthe command line), enter the following:
- Admin User Name – Name of the user who administers theserver.
- Password – Admin user’s password to access theAdmin Server (8-character minimum).
- Master Password — The master password (8-character minimum).
- Admin Port – Administration port number for initialserver instance. The default value is 4848.
- HTTP Port- Port number to access the default server instance. You need to providethis value only if you had selected to install DAS.
- HTTPSPort - Secure port number to access the default server instance. You needto provide this value only if you had selected to install DAS.
- Note – The installation program automatically detects ports in use andsuggests unused ports for the default settings.The default ports are:
- Administration Server - The default is 4848
- HTTP server - The default is 8080
- HTTPS sever - The default is 8181
In addition, five other ports are automatically assigned. You can changethe automatically assigned values after installation using the Admin Console.The default ports assigned are:- Sun Java System Message Queue - The default is7676
- IIOP- The default is 3700 for IIOP, and 3820 and 3890 for IIOP/SSL
- JMX- The default is 8686
If these default port numbers are in use, the installation program assignsrandom port numbers from the dynamic port range. This number may not be thenext available port number.
- In the Installation Options page, select the options that youwant. Installation Options are:
- Register Application Server: Select this option to registeryour installation of Application Server.
- Upgrade from Previous Version: Select this option to upgradefrom configuration data from an earlier installation of Application Server.
- Enable Updatecenter Client: Select this option to enable Updatecenterto check for available updates and collect system data.
If you are running the installer in command-line mode, you needto run the asupgrade command manually. - On the Ready to Install page, click Install Now.Note –To create a Windows service, the sc.exe utilitymust be available on the system. Windows 2000 users may need to install theWindows 2000 Resource Kit to get this utility. For other supported Windowsversions, the utility is included in the operating system.
- After the installation completes, set the PATH environmentvariable to include the Application Server install-dir/bin directory.
- Verify the installation by following the procedures in the Sun Java System ApplicationServer 9.1 Quick Start Guide, located in install-dir/docs/QuickStart.html or on docs.sun.com.If you haveproblems with your installation, see the known issues and limitations in Installation in Sun Java System Application Server 9.1 Release Notes.
See Also
The Application Server 9.1 bundle without HADB does not include theload balancing plug-in. You can download and install the load balancing plug-inseparately. For instructions, see To Install the Load Balancing Plug-in (standalone).
To Install Application Server 9.1 with HADB
Before You Begin
Use this procedure if you are using the Sun Java System Application Server file—basedinstaller. Verify that your system meets the requirements specified in Hardwareand Software Requirements in Sun JavaSystem Application Server 9.1 Release Notes.
Solaris and Linux installations support both root and non-root userinstallations. Users of Windows installations should have Power User or Administratoraccess. If you areinstalling as a non-root user on Solaris or Linux, you must have read-writeaccess to the following directories:
- The installation directory you select
- The home directory of the installation user
- The /var/tmp directory
- The /tmp directory
- The web server installation directory and the web server instancedirectory, if applicable.
- Navigate to the directory where you downloaded the distributionfile.
- If you have downloaded a .bin file, change the permission of thedistribution file so that you have execute access:chmod+xdistribution_filename
- Run the installation program.
- If you are installing from a .bin file, use the following commandto run the installation program :./distribution_filenameUse the -console option to run the installation program in command-line mode.
- If you are installing from a .zip file, unzip the file, navigateto the extracted folder, and run the following command:./setupUse the -console option to run theinstallation program in command-line mode.
- If you are installing from an .exe file on Windows, double-clickthe file.
- Specify the directory where you want to install the software oraccept the default installation directory.
- Select the components to install. If you are using a ApplicationServer bundle without HADB, you will not see this screen.The following components are available for installation:
- NodeAgent – All machines that contain application server instances shouldhave a node agent installed.
- High Availability Database Server -This component stores sessioninformation so requests can be failed over if you are using the load balancingplug-in.
- LoadBalancing Plug-in - Install the load balancing plug-in on the machine wherea web server is installed. If you do not already have a web server installedon the machine where you are installing the load balancing plug-in, you cannotcontinue to install the load balancer plug-in. Supported web servers are Sun Java System Web Server 6.1 and above (including 7.0), Apache 2.0.x, andIIS 5.0 and above.
- Domain Administration Server and Administration Tool - The DomainAdministration Server (DAS) acts as a central repository for applicationsand configuration information for server instances, even if the instancesare located on a remote machine. It includes graphical and command-line administrationtools.
- Command Line Administration Tool Only - Install the CommandLine Administration tool on machines which do not contain a DAS, but fromwhich you want to communicate with the DAS or a node agent. For example, installthe command-line administration tool on machines from which you plan to remotelyadminister the Application Server using the command-line administration tools.
- No Administration Tools - Use this option when installingcomponents on a machine that already contains the administration tools, oron which no administration tools are required. For example, when installingthe load balancing plug-in on a machine with a web server, but no ApplicationServer, no Application Server administration tools are required.
- SampleApplications - Samples come with the source, schema, Ant build scripts, andEAR files. Any existing data associated with the database-related samplesis available in the included Java DB database.
Before you run incremental installation of Application Server9.1 components, ensure that server processes are stopped if Domain AdministrationServer or Node Agent component is pre-installed on the machine - Choose toinstall JDK 5 or use a pre-installed JDK 5.
- If you selected the load balancing plug-in component:
- Select the Web Server you have installed. Ensure that you haveinstalled a supported web server. For a list of supported web servers, see Web Servers in Sun Java System Application Server 9.1 Release Notes.
- If you have Sun Java System Web Server, provide the install-dir andthe instance-dir. If you have Apache web server or IIS, provide the install-dir.
- If you have created a DAS certificate for the Apache web server, automatically import the certificate by providing the Certificate file location.The Certificate file location is the location of the DAS certificatefile. Ensure that you provide the path to certificate file inclusive of thename of the certificate file.Automatic import of DAS certificateis supported only for Apache web server. If you are using Apache web server,install Application Server without the load balancing plug-in. After installingApplication Server, create and export a DAS certificate by using the certutil utility, and run the Application Server installer again to installthe load balancing plug-in. For instructions on how to create and export DAScertificate for Apache web server, see Chapter 4, Configuring Web Serversfor Load Balancing, in Sun Java SystemApplication Server 9.1 High Availability Administration GuideIf you are using Sun Java System Web Server or IIS, you will need tomanually import the DAS certificate. You need to install load balancer withouta DAS certificate. After installing the load balancing plug-in, you can createa DAS certificate and manually import it. For instructions, see Chapter 4, ConfiguringWeb Servers for Load Balancing, in SunJava System Application Server 9.1 High Availability Administration Guide.
- If you are installing the load balancing plug-in on Web Server7.0, the installer displays the Sun Java System Web Server 7.0 informationpage. Enter the following:
- Web Server Administrator User - Name of the user who administersthe web server.
- Web ServerAdministrator Password - Password to access the Web Server administrationserver.
- WebServer Host Name - Name of the web server host.
- WebServer Administration Port - Port number to access the Web Server administrationserver. The default port is 8989.
- Ensure that you enter valid values for these fields relatedto Web Server 7.0 administration server. The installer does not validate thesevalues.
- After you install load balancing plug-in on Windows for SunJava Systems Web Server 7.0, you need to reboot the machine, so that the installerupdates the system PATH environment variable to add the path to the plug-inlibraries.
The Installation Summary page is displayed indicating the installationstatus. - In the Administration Configuration page (or when prompted atthe command line), enter the following:
- Admin User Name – Name of the user who administers theserver.
- Password – Admin user’s password to access theAdmin Server (8-character minimum).
- Master Password — The master password (8-character minimum).
- Admin Port – Administration port number for initialserver instance. The default value is 4848.
- HTTP Port- Port number to access the default server instance. You need to providethis value only if you had selected to install DAS.
- HTTPSPort - Secure port number to access the default server instance. You needto provide this value only if you had selected to install DAS.
- Node agent name — A name for the node agent. You needto provide this value only if you had selected the Node Agent option.
- Note – The installation program automatically detects ports in use andsuggests unused ports for the default settings.The default ports are:
- Administration Server - The default is 4848
- HTTP server - The default is 8080
- HTTPS sever - The default is 8181
In addition, five other ports are automatically assigned. You can changethe automatically assigned values after installation using the Admin Console.The default ports assigned are:- Sun Java System Message Queue - The default is7676
- IIOP- The default is 3700 for IIOP, and 3820 and 3890 for IIOP/SSL
- JMX- The default is 8686
If these default port numbers are in use, the installation program assignsrandom port numbers from the dynamic port range. This number may not be thenext available port number.
- In the Installation Options page, select the options that youwant. Installation Options are:
- Register Application Server: Select this option to registeryour installation of Application Server.
- Upgrade from Previous Version: Select this option to upgradefrom configuration data from an earlier installation of Application Server.
- Enable Updatecenter Client: Select this option to enable Updatecenterto check for available updates and collect system data.
If you are running the installer in command-line mode, you needto run the asupgrade command manually. - On the Ready to Install page, click Install Now.Note –To create a Windows service, the sc.exe utilitymust be available on the system. Windows 2000 users may need to install theWindows 2000 Resource Kit to get this utility. For other supported Windowsversions, the utility is included in the operating system.
- After the installation completes, set the PATH environmentvariable to include the Application Server install-dir/bin directory.
- Verify the installation by following the procedures in the Sun Java System ApplicationServer 9.1 Quick Start Guide, located in install-dir/docs/QuickStart.html or on docs.sun.com.If you haveproblems with your installation, see the known issues and limitations in Installation in Sun Java System Application Server 9.1 Release Notes.
Next Steps
If you have installed load balancing plug-in, you need to configureWeb Server for load balancing. For detailed instructions on configuring WebServer for load balancing, see Chapter4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server 9.1 High Availability AdministrationGuide.
To Install Application Server 9.1 in Silent Mode
You can use this procedure only with the Sun Java System ApplicationServer 9.1 installer. GlassFish v2 does not offer Silent Mode installation.Silent mode installation is non-interactive. You cannot use the Silent Modeif you are installing the load balancing plug-in on Web Server 7.0. You mustfirst provide a configuration file for information that the installer needs.The following topics are discussed:
Creating the Installation Configuration File
The installation configuration file is created when you use the savestate option when starting an interactive installation. During the interactiveinstallation, your input is collected and stored in the configuration fileyou specified. This file forms the template for silent installation, whichyou can use later to install the product on one or more machines. If needed,you can modify the installation configuration file.
On Solaris and Linux, for the graphical interface the syntax is:
./distribution_filename-savestateconfiguration_filename
On Solaris and Linux, for the command-line interface, the syntax is:
./distribution_filename-console -savestateconfiguration_filename
To create the installation configuration file on the Windows platform,start the installation program from the command line. Change to the directorywhere the executable file resides. For the graphical method the syntax is:
distribution_filename-savestateconfiguration_filename
On Windows, for the command-line method, the syntax is:
distribution_filename-console -savestateconfiguration_filename.
Note – If you do not include a path to the installation configurationfile, the file is created in the directory where you are running the installationprogram.
Example 1–1 Installation Configuration File Example
The following example shows an installation configuration file createdby running the installation program with the savestate option.
Modifying the Installation Configuration File
You can modify the installation configuration file by editing the variablesand values described in the following table. This table has four columns showingvariable names, valid values (if applicable), contents, and comments.
![Download The Java Plug-in From This Server And Install It Manually Mac Download The Java Plug-in From This Server And Install It Manually Mac](/uploads/1/1/7/7/117767845/321876328.png)
Download The Java Plug-in From This Server And Install It Manually Mac Catalina
Variable Name | Valid Values (If Applicable) | Content | Comments |
---|---|---|---|
Build ID | The string of characters following the distribution in the STATE_BEGINand STATE_END sections. This value is automatically generated. | No need to alter this value unless installing a different distributionfile than the one that produced the configuration file. To find the buildID, enter distribution_filename -id at the commandprompt. | |
defaultInstallDirectory | Default installation directory path. | ||
currentInstallDirectory | Selected absolute installation directory path. | ||
JDK_LOCATION | Selected JDK installation directory path. | This entry is needed only for distributions that do not contain a bundledJDK. | |
INST_ASADMIN_USERNAME | Administrator user name for initial server instance. | ||
INST_MASTER_PASSWORD | SSL certificate database password for asadmin operations. | This entry is obfuscated by default. See also: ADMIN_PASSWORD_ENCRYPTED. | |
INST_ASADMIN_PASSWORD | Administrator password for initial server instance. | This entry is obfuscated by default. See also:ADMIN_PASSWORD_ENCRYPTED. | |
INST_ASADMIN_PORT | 0 - 65535 | Administration server port number for initial server instance. | Default value is 4848. |
INST_ASWEB_PORT | 0 - 65535 | HTTP port number for initial server instance. | Default value is 8080. |
INST_HTTPS_PORT | 0 - 65535 | HTTPS port number for initial server instance. | Default value is 8081. |
STORE_ADMIN_AUTH | TRUE, FALSE | Whether to create admin authentication user preference file. | |
ADMIN_PASSWORD_ENCRYPTED | TRUE, FALSE | Obfuscated admin password flag. | In the initial statefile created by the product installer, this flagis set to TRUE, since the admin password value is obfuscated for securityreasons. To override the value for admin password, enter INST_ASADMIN_PASSWORD value in clear text and set this flag to FALSE to enable silentinstallation to process it correctly. |
INST_JMS_PORT | 0 - 65535 | JMS port number for initial server instance. | If the configuration file does not include this entry, default valueof 7676 is used. |
INST_ORB_PORT | 0 - 65535 | ORB port number for initial server instance. | If the configuration file does not include this entry, default valueof 3700 is used. |
INST_ORB_SSL_PORT | 0 - 65535 | Secure ORB port number for initial server instance. | If the configuration file does not include this entry, default valueof 3820 is used. |
INST_ORB_MUTUALAUTH_PORT | 0 - 65535 | Mutual authentication ORB port number for initial server instance. | If the configuration file does not include this entry, default valueof 3920 is used. |
INST_JMX_PORT | 0 - 65535 | JMX port number for initial server instance. | If the configuration file does not include this entry, default valueof 8686 is used. |
CREATE_DESKTOP_SHORTCUT | TRUE, FALSE | Whether to create autodeploy folder desktop shortcut. | Valid for Windows platforms only and is disregarded otherwise. |
UPDATE_PATH | TRUE, FALSE | Whether to update PATH environment variable to include Application Server bin directory. | Valid only for Windows platforms and is disregarded otherwise. If this entry is not present, default value of FALSE is used. |
CREATE_WINDOWS_SERVICE | TRUE, FALSE | Whether to create the server as a Windows service. | Valid for Windows platforms only and is disregarded otherwise. |
SELECTED_ADDONS | JBI | Add-ons selected for installation. If no add-ons are selected, the valueis blank. | Valid for Java EE SDK SOA Starter Kit Preview installations only andis disregarded otherwise. |
CREATE_DAS | TRUE, FALSE | Creates a DAS if set to TRUE. The default domain is named domain1 andis created under default domain-root-dir. | Equivalent to selecting 'Domain Administration Server' component incomponent selection panel. |
CREATE_NA | TRUE, FALSE | Creates a node agent if set to TRUE. The default node agent would benamed agent1 and is created under default node agents root. | Equivalent to selecting 'Application Server Node Agent' component incomponent selection panel. |
WEBSERVER_INSTALL_DIR | A valid, read-writable directory location. | Installation directory of a supported Web server. | Used only when the load balancing plug-in component is selected forinstallation. |
WEBSERVER_INSTANCE_DIR | A valid read-writable directory location. | Instance directory of selected web server where the load balancing plug-inwill be configured. | Used when load balancing plug-in component is selected to be installedon Sun Java System Web Server. Not applicable for other web servers. |
PLUGIN_TYPE | Sun ONE Web Server, Apache HTTP Server,or Microsoft IIS Web Server. | Type of web server on which the load balancing plug-in will be installed/configured. | Used only when the load balancing plug-in component is selected forinstallation. |
PLUGIN_CERTIFICATE_FILE | A valid path to a certificate file. | Used only when Apache HTTP Server is selected for load balancing plug-ininstallation. Not supported or is ignored for other web servers. |
Using the Installation Configuration File to Installin Silent Mode
After creating the configuration file, use it to install Application Server insilent mode as many times as needed. Use the following procedure:
To Install in Silent Mode
- Review the installation configuration file and verify that itcontains the values to use for your silent installation.
- Copy your installation configuration file to each machine whereyou plan to install the software.
- Copy the Application Server distribution file to each machine whereyou plan to install the software.
- Navigate to the directory where you copied the distribution fileand your installation configuration file.
- Start silent installation at the command line using one of thefollowing command formats:
- On Solaris or Linux:./distribution_filename-silentconfiguration_filename
- On Windows:distribution_filename-silentconfiguration_filename
The installation program reads the specified configuration_filename, checks for adequate disk space, then installs the productbased on the data in configuration_filename.When the prompt is returned, the silent installation is complete andthe installation components are installed on your systems. - Start the Application Server software by using the instructions inthe Sun Java System ApplicationServer 9.1 Administration Guide.
You can install Application Server on local or global zones.
Consider the following before you install Application Server on a Solariszone:
Application Server and MQ bundled with Solaris 10
Application Server and Message Queue components are bundled and pre-installedas part of Solaris 10. These packages are installed under /usr directory.
Global zone installation:
- Before installing, make sure you remove the version of applicationserver that is bundled in Solaris 10. Refer the Java ES installation guidefor instructions.
- If Application Server 8.2 has been installed through JavaES 5 Update 1, it is automatically upgraded by the Application Server installationalong with shared components. Refer to Java ES Update 1 Installation Planningguide for information about shared components
Sparse zone installation:
- If global zone has a version of application server bundledin Solaris, remove this application server installation. Refer to Java ES5 Update 1 Installation guide for instructions on how to uninstall this applicationserver installation.
- If there is a version of Application Server 8.2 installedthrough Java ES 5 Update 1, it is automatically upgraded to Application 9.1installation along with shared components. Refer to Java ES Update 1 InstallationPlanning guide for information about shared components.
- The version of Message Queue (MQ) that is bundled as partof Java ES 5 Update 1 is 3.7 UR1 and the one bundled with Application Server9.1 is 4.1.If you do not have MQ installed or if you have a versionof MQ lower than 4.1 on the global zone, the Application Server 9.1 installer(running on sparse local zone) will not be able to automatically install orupgrade MQ on global zone. Before you run the Application Server 9.1 installerin sparse local zone, you need to download Message Queue 4.1 standalone package-basedinstallation from and install it in global zone. Alternatively, youcan install Sample Applications from Application Server 9.1 installer, whichwill install MQ 4.1 in global zone or upgrade the existing MQ in global zone.
- If global zone has a version of application server installedthrough Java ES or through Application Server 9.1 installation, they are setnot to propagate to local zones. You can have another copy of the installationin sparse zone. If a sparse zone already has an application server installationthrough Java ES, you can upgrade that version.
Installations on whole root local zones are much simpler because allcomponents of Application Server (including shared components, MQ, HADB) canbe installed and they do not interfere with packages in other global and sparsezones.
Download The Java Plug-in From This Server And Install It Manually Macos
Propagation Levels of Components Installed ThroughJava ES 5 Update 1
The propagation levels of components installed through ApplicationServer 9.1 installation (with Java ES 5 Update 1) are:
Download The Java Plug-in From This Server And Install It Manually Macbook Pro
- Bundled Application Server packages have propagation set to TRUE to all zones.
- Application Server packages that are part of Java ES Update1 and Application Server 9.1 installation do not propagate to local zones.
- Message Queue and shared components that are part of JavaES Update 1 and Application Server 9.1 installation are set to propagate toall zones from the global zone.
- HADB packages are not set to propagate to local zones.