WebSphere® Application Server Version 8.0 is the first full version to be installed and maintained by IBM® Installation Manager rather than by the ISMP-based programs that are used to install and maintain previous versions. You do not use the same response files that are used with WebSphere Application Server Version 7.0 or earlier to silently install, update, roll back, or uninstall Version 8.0 and later; you must use response files that are based on Installation Manager to silently install, update, roll back, or uninstall Version 8.0 and later.
Function performed | Example of Version 7 ISMP-based installation response-file usage | Example of Version 8 installation and configuration usage |
---|---|---|
Silent installation using minimum response-file contents |
-OPT silentInstallLicenseAcceptance="true" -OPT installType="installNew" -OPT profileType="none" -OPT feature="noFeature" -OPT PROF_enableAdminSecurity="false" -OPT installLocation="/opt/IBM/WebSphere/AppServer"options in the response file |
<agent-input> <server> <repository location="http://www.ibm.com/software/repositorymanager/V8WASBASETrial" /> </server> <install modify='false'> <offering id='com.ibm.websphere.BASETRIAL.v80' profile='IBM WebSphere Application Server Trial V8.0' features='core.feature,com.ibm.sdk.6_32bit' installFixes='none'/> </install> <profile id='IBM WebSphere Application Server Trial V8.0' installLocation='/opt/IBM/WebSphere/AppServer'> <data key='eclipseLocation' value='/opt/IBM/WebSphere/AppServer'/> <data key='user.import.profile' value='false'/> <data key='cic.selector.nl' value='en'/> </profile> <preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='/var/ibm/InstallationManager'/> </agent-input>in the response file |
Install using a silent-installation response file |
-options "responsefile.txt" -silentparameter in the install command |
input response_file_path_and_nameparameter in the imcl command |
Install as a non-root user or non-administrator |
-OPT allowNonRootSilentInstall="true"option in the response file |
Not applicable to Version 8.0 installation |
Accept license |
-OPT silentInstallLicenseAcceptance="true"option in the response file |
-acceptLicenseparameter in the imcll command |
Use a keyring file for authenticating with secure repositories |
Not applicable to Version 7.0 installation |
-keyring path_and_name_of_keyring_file -password passwordparameter in the imcl command |
Continue installation even if prerequisite checking of the operating system does not pass |
-OPT disableOSPrereqChecking="true"option in the response file |
To bypass operating-system prerequisite checking, add disableOSPrereqChecking=true to the config.ini file in IM_install_root/eclipse/configuration. |
Verify that user account running the installation has proper file permissions to perform the installation |
-OPT checkFilePermissions="true"option in the response file |
Not applicable to Version 8.0 installation |
Install a new copy of the product |
-OPT installType="installNew" -OPT feature="feature"options in the response file, where the value for feature is noFeature, samplesSelected, languagepack.console.all, and languagepack.server.all; multiple features can be installed by having a separate line in the response file for each feature to install |
<install modify='false'> <offering id='offering_id' profile='profile_id' features='comma_separated_features' installFixes='install_fixes'/> </install> <profile id='profile_id' installLocation='installation_location'> <data key='eclipseLocation' value='eclipseLocation'/> <data key='user.import.profile' value='false'/> <data key='cic.selector.nl' value='comma_separated_languages'/> </profile>in the response file, where the |
Upgrade a trial edition to a licensed edition, or upgrade the Express edition |
-OPT installType="upgrade"option in the response file |
Not applicable to Version 8.0 installation |
Add a new feature to an existing installation of the product |
-OPT installType="addFeature" -OPT feature="feature"options in the response file, where the value for feature is noFeature, samplesSelected, languagepack.console.all, or languagepack.server.all; multiple features can be installed by having a separate line in the response file for each feature to install |
<install modify='true'> <offering id='offering_id' profile='profile_id' features='comma_separated_features'/> </install> <profile id='profile_id' installLocation='installation_location'> <data key='eclipseLocation' value='eclipseLocation'/> <data key='user.import.profile' value='false'/> <data key='cic.selector.nl' value='comma_separated_languages'/> </profile>in the response file, where the |
Remove a feature from an existing installation of the product |
<uninstall modify='true'> <offering id='offering_id' profile='profile_id' features='comma_separated_features'/> </uninstall> <profile id='profile_id' installLocation='installation_location'> <data key='eclipseLocation' value='eclipseLocation'/> <data key='user.import.profile' value='false'/> <data key='cic.selector.nl' value='comma_separated_languages'/> </profile>in the response file, where the |
|
Specify the location in the file system in which to install the product files |
-OPT installLocation="installation_location"option in the response file |
<profile id='profile_id' installLocation='installation_location'> </profile>in the response file |
Specify log file and trace options |
-OPT traceFormat=trace_format -OPT traceLevel=trace_leveloptions in the response file, where the
|
-log log_file_path_and_nameparameter in the imcl command |
Specify the setting and preferences to use and whether to persist setting and preferences |
Not applicable to Version 7.0 installation |
<agent-input clean="true" temporary="true"> . . . </agent-input>All contents of the response file must be included within the agent-input attribute. |
Specify where the installable files are located |
Not applicable to Version 7.0 installation |
<server> <repository location="repository_location" /> </server>in the response file |
Specify preference for keeping or removing downloaded files |
Not applicable to Version 7.0 installation |
<preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/>in the response file |
Specify location to store downloaded and shared files |
Not applicable to Version 7.0 installation |
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='shared_location'/>in the response file |
The remaining entries in this table are profile-creation options that are no longer applicable to installation response files in Version 8 because server profiles are not created during the installation process; instead, server profiles are created using the Profile Management Tool or manageprofiles command after installation |
||
Create a specified server profile during installation |
-OPT profileType="profile_type"option in the response file, where the value for profile_type is cell, management, standAlone, custom, secureProxy, or none |
-templatePath template_pathparameter in the manageprofiles -create command, where the value for template_path is app_server_root/profileTemplates/default or app_server_root/profileTemplates/management |
Specify the type of management profile to create |
-OPT PROF_serverType="server_type"option in the response file, where the value for server_type is DEPLOYMENT_MANAGER, JOB_MANAGER, or ADMIN_AGENT; this option is used only with the management profile type |
-serverType server_typeparameter in the manageprofiles -create command, where the value for server_type is DEPLOYMENT_MANAGER, JOB_MANAGER, or ADMIN_AGENT; this option is used only with a management profile type |
Specify the location in the file system to create the profile |
-OPT PROF_profilePath="directory_path"option in the response file |
-profilePath directory_pathparameter in the manageprofiles -create command |
Specify the profile being created as the default profile among all profiles associated with a given installation of the product |
-OPT PROF_isDefault="true"option in the response file |
-isDefaultparameter in the manageprofiles -create command |
Specify the name of the profile being created |
-OPT PROF_profileName="profile_name"option in the response file; used with all profiles except the cell type -OPT PROF_dmgrProfileName="profile_name" -OPT PROF_appServerProfileName="profile_name"options in the response file; used only with the cell profile type |
-profileName profile_nameparameter in the manageprofiles -create command |
Specifies the host name |
-OPT PROF_hostName="host_name"option in the response file |
-hostName host_nameparameter in the manageprofiles -create command |
Specify the node name |
-OPT PROF_nodeName="node_name"option in the response file; used for all profile types; in the case of a cell, the name is assigned to the deployment manager -OPT PROF_appServerNodeName="node_name"option in the response file; used only with the cell profile type to assign the node name to the application server profile |
-nodeName node_nameparameter in the manageprofiles -create command |
Specify the cell name |
-OPT PROF_cellName="cell_name"option in the response file |
-cellName cell_nameparameter in the manageprofiles -create command |
Specify the server name |
-OPT PROF_serverName="server_name" |
-serverName server_nameparameter in the manageprofiles -create command |
Configure the performance-tuning setting for developer environment |
-OPT PROF_isDeveloperServer="true | false"option in the response file; used only with the standalone profile type |
-isDeveloperServerparameter in the manageprofiles -create command; only valid for the default profile template -applyPerfTuningSetting perf_tuning_optionparameter in the manageprofiles -create command, where the value for perf_tuning_option is standard, production, or development; only valid for the default profile template Note: If
you specify both the -isDeveloperServer and -applyPerfTuningSetting
parameters, depending on the option selected for -applyPerfTuningSetting,
-applyPerfTuningSetting might override -isDeveloperServer
|
Optional configuration action used to prevent applications from being deployed into a profile even through the binary files for the application are installed with the product |
-OPT PROF_omitAction="omit_action"option in the response file, where the value for omit_action is deployAdminConsole, defaultAppDeployAndConfig, or samplesInstallAndConfig; multiple configuration actions can be omitted by having a separate line in the response file for each action to skip |
-omitAction feature1 feature2... featureNparameter in the manageprofiles -create command, where the values for the omitted features are deployAdminConsole, defaultAppDeployAndConfig, and samplesInstallAndConfig |
Enable administrative security in the server profile |
-OPT PROF_enableAdminSecurity="true" -OPT PROF_adminUserName="user_name" -OPT PROF_adminPassword="password" -OPT PROF_samplesPassword="sample_passwordoptions in the response file |
-enableAdminSecurity true | false -adminUserName user_name -adminPassword passwordparameters in the manageprofiles -create command |
Assign port values |
-OPT PROF_defaultPorts="true"or -OPT PROF_startingPort="starting_port" -OPT PROF_nodeStartingPort="node_starting_port"or -OPT PROF_portsFile="port_file" -OPT PROF_nodePortsFile="node_port_file"options in the response file; PROF_nodeStartingPort and PROF_nodePortsFile are used only with the cell profile type |
-defaultPorts -nodeDefaultPortsor -startingPort starting_port -NodeStartingPort node_starting_portor -portsFile port_file -nodePortsFile node_port_fileparameters in the manageprofiles -create command; -nodeStartingPort and -nodePortsFile are used only with the cell profile type |
Validate the port values for conflicts |
-OPT PROF_validatePorts="true | false"option in the response file; if the value is true and a port conflict is detected, validation fails and the profile is not created |
-validatePortsparameter in the manageprofiles -create command; if the parameter is specified and a port conflict is detected, validation fails and the profile is not created |
Create a service to run the server (Optional, Windows and Linux only) |
-OPT PROF_winserviceCheck="true | false" -OPT PROF_winserviceAccountType="account_type" -OPT PROF_winserviceUserName="user_name" -OPT PROF_winservicePassword="password" -OPT PROF_winserviceStartupType="startup_type"options in the response file; where the value for account_type is localsystem or specifieduser and the value for startup_type is automatic, manual, or disabled; used for Windows Service creation only -OPT PROF_enableService="true | false" -OPT PROF_serviceUserName="service_user_name"options in the response file; used for Linux Service creation only |
-winserviceCheck true | false -winserviceAccountType account_type -winserviceUserName user_name -winservicePassword password -winserviceStartupType startup_typeparameters in the manageprofiles -create command; where the value for account_type is localsystem or specifieduser and the value for startup_type is automatic, manual, or disabled; used for Windows Service creation only -enableService true | false -serviceUserName service_user_nameparameters in the manageprofiles -create command; used for Linux Service creation only |
Create a web server definition (optional) |
-OPT PROF_webServerCheck="true | false" -OPT PROF_webServerType="webserver_type" -OPT PROF_webServerOS="webserver_OS" -OPT PROF_webServerName="webserver_name" -OPT PROF_webServerHostname="webserver_host" -OPT PROF_webServerPort="webserver_port" -OPT PROF_webServerPluginPath="plugin_path" -OPT PROF_webServerInstallPath="webserver_path"options in the response file; where the |
-webServerCheck true | false -webServerType webserver_type -webServerOS webserver_OS -webServerName webserver_name -webServerHostname webserver_host -webServerPort webserver_port -webServerPluginPath plugin_path -webServerInstallPath webserver_pathparameters in the manageprofiles -create command; where the |
Create or import a security certificate |
-OPT PROF_keyStorePassword="keystore_password" -OPT PROF_personalCertDN="personal_cert_domain" -OPT PROF_personalCertValidityPeriod="personal_validity_period" -OPT PROF_signingCertDN="sign_cert_domain" -OPT PROF_signingCertValidityPeriod="sign_cert_validity_period"or -OPT PROF_keyStorePassword="keystore_password" -OPT PROF_importPersonalCertKS="personal_cert_keystore" -OPT PROF_importPersonalCertKSType="personal_cert_keystore_type" -OPT PROF_importPersonalCertKSPassword="personal_cert_keystore_password" -OPT PROF_importPersonalCertKSAlias="personal_cert_keystore_alias" -OPT PROF_importSigningCertKS="sign_cert_keystore" -OPT PROF_importSigningCertKSType="sign_cert_keystore_type" -OPT PROF_importSigningCertKSPassword="sign_cert_keystore_password" -OPT PROF_importSigningCertKSAlias="sign_cert_keystore_alias"options in the response file |
-keyStorePassword keystore_password -personalCertDN personal_cert_domain -personalCertValidityPeriod personal_validity_period -signingCertDN sign_cert_domain -signingCertValidityPeriod sign_cert_validity_periodor -keyStorePassword keystore_password -importPersonalCertKS personal_cert_keystore -importPersonalCertKSType personal_cert_keystore_type -importPersonalCertKSPassword personal_cert_keystore_password -importPersonalCertKSAlias personal_cert_keystore_alias -importSigningCertKS sign_cert_keystore -importSigningCertKSType sign_cert_keystore_type -importSigningCertKSPassword sign_cert_keystore_password -importSigningCertKSAlias sign_cert_keystore_aliasparameters in the manageprofiles -create command |