Creating the Installation Configuration File (Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Installation Guide)

Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Installation Guide

Creating the Installation Configuration File

The installation configuration file is created when you use the savestate option with the setup command to start a interactive installation. During the interactive installation, your input is collected and stored in the configuration file you specified. This forms the template for silent installation, which you can use later to install the product on one or more machines. If needed, you can modify the installation configuration file.

The following topics are addressed:

Syntax for Creating the Installation Configuration File

The syntax for creating an installation configuration file is as follows:

For the graphical method:

./bundle_filename -savestate filename

For the command-line method:

./bundle_filename -console -savestate filename

Refer to Installation Methods for more detailed information.

An installation configuration file looks similar to the following example.

Example 1–1 Example Installation Configuration File

# 
# Wizard Statefile created: Tue Aug 10 11:33:59 PDT 2004 
# Wizard path: /var/tmp/sjsasAAA5ZaaaR/appserv.class 
# 
# Install Wizard Statefile section for J2EE 1.4 SDK 
# [STATE_BEGIN J2EE 1.4 SDK 6684bbcb8d348bf04952a1c7a625e26689a21146] 
defaultInstallDirectory = /home/xyz/SUNWappserver 
currentInstallDirectory = /opt/tmp 
SELECTED_COMPONENTS = Domain Admin Server#Node Agent#PointBase Server 4.8# 
USE_BUNDLED_JDK = FALSE 
JDK_LOCATION = /usr/j2se 
WEBSERVER_INSTALL_DIR = 
PLUGIN_TYPE = 
INST_ASADMIN_USERNAME = admin 
INST_ASADMIN_PASSWORD = nklquxpcopmkjkjarvqzvanqzva 
INST_MASTER_PASSWORD = npohjtiehancyynoucqzva123 
INST_ASADMIN_PORT = 4849 
INST_ASWEB_PORT = 8080 
INST_HTTPS_PORT = 8181 
STORE_ADMIN_AUTH = FALSE 
ADMIN_PASSWORD_ENCRYPTED = TRUE 
INST_JMS_PORT = 7676 
INST_ORB_PORT = 3700 
INST_ORB_SSL_PORT = 3820 
INST_ORB_MUTUALAUTH_PORT = 3920 
INST_JMX_PORT = 8686 
INST_POINTBASE_PORT = 9092 
INST_DAS_HOSTNAME = localhost 
CREATE_SAMPLES_DOMAIN = FALSE 
CREATE_DESKTOP_SHORTCUT = FALSE 
UPDATE_PATH = FALSE 
[STATE_DONE J2EE 1.4 SDK 6684bbcb8d348bf04952a1c7a625e26689a21146]

Modifying the Installation Configuration File

You can modify the installation configuration file by editing the variables and values described in Table 1–3.

Table 1–3 Installation Configuration File Variables


Variable Name	Valid Values (if applicable)	Content	Comments
`defaultInstallDirectory`		Default installation directory path
`currentInstallDirectory`		Selected installation directory path	You can specify an environment variable which will be resolved at runtime. First set/export `SUN_APPSVR_HOME`. Solaris OS example: `export SUN_APPSVR_HOME=/myname/myinstallation`. In the installation configuration file, provide the environment variable as the installation directory. For example: `currentInstallDirectory = $SUN_APPSVR_HOME$`/`myappsvr`
`SELECTED_COMPONENTS`		List of product components selected for installation	Modification is not recommended.
`USE_BUNDLED_JDK`	TRUE FALSE	Whether to install JDK bundled with the product	If this value is set to FALSE, the J2SE path referenced by `JDK_LOCATION` is used.
`PLUGIN_TYPE`	Sun ONE Web Server, Microsoft IIS Web Server (Windows only), Apache HTTP Server
`JDK_LOCATION`		JDK path	Preinstalled JDK path, relevant only if `USE_BUNDLED_J2SE` is set to FALSE.
`WEBSERVER_INSTALL_DIR`		Selected web server instance directory path	Relevant only if the Load Balancer Plug-in component is selected for installation.
`INST_ASADMIN_USERNAME`		Administrator user name for initial domain
`INST_ASADMIN_PASSWORD`		Administrator password for initial Domain Administration Server	This entry is obfuscated by default. See also description of `ADMIN_PASSWORD_ENCRYPTED` variable.
`INST_MASTER_PASSWORD`		SSL certificate database password for asadmin operations such as Domain Administration Server startup and Node Agent startup	This entry is obfuscated by default. See also description of `ADMIN_PASSWORD_ENCRYPTED` variable.
`INST_ASADMIN_PORT`	0 - 65535	Administration server port number for initial Domain Administration Server
`INST_ASWEB_PORT`	0 - 65535	Server port number for initial Domain Administration Server instance
`INST_HTTPS_PORT`	0 - 65535
`STORE_ADMIN_AUTH`	TRUE FALSE
`ADMIN_PASSWORD_ENCRYPTED`	TRUE FALSE	Obfuscated admin password flag	In initial statefile created by product installer this flag is set to TRUE, since the admin password value is obfuscated for security reasons. To override the value for admin password, enter values of `INST_ASADMIN_PASSWORD` and `INST_MASTER_PASSWORD` in clear text and set this flag to FALSE to enable silent installation to process it correctly.
`INST_JMS_PORT`	0 - 65535	JMS port number for initial Domain Administration Server
`INST_ORB_PORT`	0 - 65535	ORB port number for initial Domain Administration Server
`INST_ORB_SSL_PORT`	0 - 65535	Secure ORB port number for initial Domain Administration Server
`INST_ORB_MUTUALAUTH_PORT`	0 - 65535	Mutual authentication ORB port number for initial Domain Administration Server
`INST_JMX_PORT`	0 - 65535	JMX port number for initial Domain Administration Server
`INST_POINTBASE_PORT`	0 - 65535	PointBase server port number
`CREATE_SAMPLES_DOMAIN`	TRUE FALSE	Whether to create additional samples server domain.	This value is disregarded because Application Server Enterprise Edition does not support this feature.
`INST_DAS_HOSTNAME`		Name of the Domain Administration Server to be used to administer the server.
`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.
`USE_BUNDLED_JDK`	TRUE FALSE	Whether to install and use bundled J2SE	If this value is set to FALSE, the J2SE path referenced by `JDK_LOCATION` is used.

Note –

You cannot reuse the configuration file created for one distribution on other distributions, editions, or versions of the Application Server software.

To view the results of the silent installation, refer to the log file.