The installation configuration file is created when you use the savestate option with the setup command to start an 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:
You cannot use the silent installation procedure to install the load balancing plugin on Web Server 7.0.
To create an installation configuration file on Solaris or Linux:
Navigate to the location of the installation file.
Create the configuration file. For the graphical method, the syntax for creating the configuration file is: ./distribution-filename -savestate configuration-filename
For the command-line method, the syntax is: ./distribution-filename -console -savestate configuration-filename
If you do not include a path to the installation configuration file, the file is created in the directory where you are running the installation program. You must have write permissions for the directory where the installation configuration file is created, otherwise the installer will not be able to create the installation configuration file after the installation is complete.
To create the installation configuration file on the Windows platform, start the installation program from the command line. Change to the directory where the installation file resides.
For the graphical method the syntax is: distribution-filename -savestate configuration-filename
For the command-line method, the syntax is: distribution-filename -console -savestate configuration-filename.
If you do not include a path to the installation configuration file, the file is created in the directory where you are running the installation program.
# # Wizard Statefile created: Tue Mar 28 16:37:05 PST 2006 # Wizard path: /var/tmp/sjsasAAAH7aarp/appserv.class # # # Install Wizard Statefile section for J2EE 1.4 SDK # # [STATE_BEGIN J2EE 1.4 SDK 2860414c861c7b95a1287502663618e16472fc40] defaultInstallDirectory = /SUNWappserver currentInstallDirectory = /export/SUNWappserver SELECTED_COMPONENTS = Domain Admin Server#Node Agent#High Availability Database Administration Client#Sample Applications# USE_BUNDLED_JDK = TRUE JDK_LOCATION = /usr/j2se WEBSERVER_INSTALL_DIR = PLUGIN_TYPE = INST_ASADMIN_USERNAME = admin INST_ASADMIN_PASSWORD = ngvismlhimdgfgqrrkqzvanqzva INST_MASTER_PASSWORD = nwgxqgvrqhmeusidvuqzvanqzva 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_DAS_HOSTNAME = localhost INST_ASADMIN_USERNAME = admin INST_ASADMIN_PASSWORD = ngvismlhimdgfgqrrkqzvanqzva INST_ASADMIN_PORT = 4849 INST_MASTER_PASSWORD = nwgxqgvrqhmeusidvuqzvanqzva CREATE_SAMPLES_DOMAIN = FALSE CREATE_DESKTOP_SHORTCUT = FALSE UPDATE_PATH = FALSE [STATE_DONE J2EE 1.4 SDK 2860414c861c7b95a1287502663618e16472fc40]