Installing the product using silent installation refers to using a file to supply installation options without user interaction. To configure the installation, change the options in the response file before you issue the installation command. Silent installation mode does not accept interactive installation options. To specify non-default options during a silent installation, you must use the response file. To install silently, you must accept the license agreement in the agreement option.
Verify that the required disk space is available.
In order to install the feature pack you must first install
WebSphere Application Server. See Installing Feature Pack for EJB 3.0 on distributed operating systems for
more information.
In order to install the feature pack you must first
install WebSphere Application Server. See Installing Feature Pack for EJB 3.0 on IBM i for
more information.
Do not use the default response file that is shipped on the product disk to install the product because the value of the silentInstallLicenseAcceptance option is false. Copy the file to change the value to true.
The sample options response file is named responsefile.EJB3.txt for the feature pack.
The file is in the EJB3 directory of the downloaded installation image.
Installing a new installation of a feature pack with the response file creates an operational environment by default. The installer program:
Response file parameters
Set values for the following options:
Option | Description |
---|---|
-OPT silentInstallLicenseAcceptance="true" | Accept the enclosed license agreement. |
-OPT installLocation=app_server_root | Set app_server_root to the root directory of your application server product. |
-OPT disableNonBlockingPrereqChecking="true" | Notifies the installer to continue with the installation and log the warnings even though the prerequisite checking has failed. You have to specify "true" if your application server is below the level of maintenance required by the feature pack. In that case the feature pack will install any included application server maintenance packages. |
-OPT allowNonRootSilentInstall="true" | You must uncomment this line if you are installing the product with a non-root or non-administrator ID. |
-OPT fixpackLocation | Optional. Specifies the location of any application server fix packs to be applied to the application server. This option is unnecessary if the required application server fix pack is located in the default install_image/maintenance/fix_packs directory. The installer will also ignore this option if the application server already meets or exceeds the level of maintenance required by the feature pack. |
-OPT fepFixpackLocation | Optional. Specifies the location of any feature pack fix packs to be applied to the feature pack. The installer will ignore this option if the application server is below the level of maintenance required by the feature pack. Make sure that the level of your application server matches or exceeds the level of the feature pack installer. |
Edit the version of the file that ships with the feature pack. The following example is not guaranteed to be an accurate representation of the file that ships with the product.
################################################################################# # # WebSphere Application Server V6.1 EJB 3.0 options file # # This options file runs the installation wizard in silent mode. This lets the # options file author specify installation settings without having to run the # wizard in graphical mode. To use this options file for silent mode execution, # use the following command line arguments when running the wizard: # # -options "responsefile.EJB3.txt" -silent # # Read the documentation for information on changing the value for each option. # Enclose all values within a single pair of double quotes. ################################################################################ ################################################################################ # Installation options and values ################################################################################ # # License Acceptance # # By changing the silentInstallLicenseAcceptance property in this response file # to "true", you agree that you have reviewed and agree to the terms of the # IBM International Program License Agreement accompanying this program, which # is located at IMAGE_ROOT/was.primary.pak/repository/legal/lafiles. If you # do not agree to these terms, do not change the value or otherwise download, # install, copy, access, or use the program and promptly return the program # and proof of entitlement to the party from whom you acquired it to obtain # a refund of the amount you paid. # # Valid values for silentInstallLicenseAcceptance: # true - Accepts the license and product installation will occur. # false - Declines the license and product installation will not occur. # -OPT silentInstallLicenseAcceptance="false" # # If no install occurs, a log file is created in the temporary directory area # of the user account that performed the installation (<user_area>\ejb3logs\). # ################################################################################ # Custom Install Package (CIP) Special Parameters # # This custom installation may include maintenance files, profile customization # files, and other additional customization files. Maintenance files update an # existing installation to the version level contained in the Customized # Installation Package. Profile customization files enable new profiles to be # created that are customized. Any additional customization files contained # in this customized installation are always installed. # # By using the one of following options, you can choose whether to install # maintenance only, or maintenance files and profile customization at install time. # # Valid Options: # maintenanceOnly - Install maintenance updates contained in # this installation. If the CIP contains # profile customizations, they will NOT be # installed. # customizationAndMaintenance - Install maintenance updates and profile # customization files. # # -OPT if_cip_modifyexistinginstall="maintenanceOnly" # ################################################################################ # # Custom Install Package (CIP) Install Type Settings # # The installType option designates the type of installation that will be # performed. # # The default installType option is to install a new copy of Feature Pack. # # If you want to install CIP on an existing installation, (e.g. apply # maintenance and/or profile customizations), set set the 'installType' # option to 'addFeature'. This will notify the installer that you are doing # an update install. # # Valid Values: # installNew - default value, installs a new copy. # addFeature - updates an existing installation with a Custom Install # Package with maintenance and/or profile customizations. # -OPT installType="installNew" # ######################################################################################### # # # Non-Root Installation Limitations # # This option indicates whether you accept the limitations associated with # installing as a non-root user. The following installation actions cannot be # performed with installing as a non-root or non-administrative user. # - Creation of a Windows or Linux service for WebSphere Application Server. # - Native registration with the operating system. # - Port conflicts may occur with other installations of WebSphere # Application Server that are not registered with the operating system. # # Valid values for allowNonRootSilentInstallation: # true - Accepts the limitations. Will install the product. # false - Do not accept the limitations. Install will not occur. # # Uncomment the following option only if you are installing as a non-root user. # # -OPT allowNonRootSilentInstall="true" # ################################################################################ # # Prerequisite Checking # # The installer checks the system for prerequisites by default. # # Uncomment the following option to notify the installer to continue with # the installation and log the warnings even though prerequisite checking # of the operating system failed. # # -OPT disableOSPrereqChecking="true" # # Uncomment the following option to notify the installer to continue with # the installation and log the warnings even though prerequisite checking # failed. You must uncomment this option to install the application server # fix pack that is specified with the fixpackLocation parameter, or in # the default fix pack location in the EJB3\maintenance\fix_packs directory. # # -OPT disableNonBlockingPrereqChecking="true" # ################################################################################ # # Installation Location # # Specify a valid directory path to an installed version of WAS6.1 # Only Windows operating systems support spaces in the installation location # and must be enclose in double-quotes as shown below. # Additionally, the maximum path length is 60 characters for Windows systems. # # Uncomment the appropriate option for your operating system. # # If you are installing as a non-root user on Unix or non-administrator on # Windows, be sure you have write permission for the install location chosen. # Also, be sure to include the appropriate value for <user_home>. # # AIX Default Install Location: # -OPT installLocation="/usr/IBM/WebSphere/AppServer" # AIX Default Non-Root Install Location: # -OPT installLocation="<user_home>/IBM/WebSphere/AppServer" # # HP-UX, Linux or Solaris Default Install Location: # -OPT installLocation="/opt/IBM/WebSphere/AppServer" # HP-UX, Solaris or Linux Default Non-Root Install Location: # -OPT installLocation="<user_home>/IBM/WebSphere/AppServer" # # i5OS Default Install Location: # -OPT installLocation="/QIBM/IBM/WebSphere/AppServer/V61/<productOffering>" # # Windows Default Install Location: # -OPT installLocation="C:\Program Files\IBM\WebSphere\AppServer" # Windows Default Non-Administrator Install Location: # -OPT installLocation="C:\IBM\WebSphere\AppServer" # ################################################################################ # # WebSphere Application Server Fix Pack Location # # The fix pack's default location is located in the base of the install image. # If the fix pack has been moved, or you would like to install a specific fix pack # from another location, specify the full path including the fix pack's filename # here. You may also specify the full path to the new location where the fix pack # is located. Otherwise leave this option commented out. # # You must uncomment the disableNonBlockingPrereqChecking option to install the # application server fix pack that is specified with the fixpackLocation parameter, # # -OPT fixpackLocation="<fix_pack_location>" # ################################################################################ # # JDK Fix Pack Location # # The jdk fixpack's default location is located in the base of the install image. # If the jdk fixpack has been moved, or you would like to install a specific jdk fix # pack from another location, specify the full path including the jdk fix pack's # filename here. You may also specify the full path to the new location where the # jdk fix pack is located. Otherwise leave this option commented out. # # -OPT jdkFixpackLocation="<fix_pack_location>" # ################################################################################ # # Feature Pack Fix Pack Location # # Use this option to specify the full path including the feature pack fix pack's # filename here. # # -OPT fepFixpackLocation="<fix_pack_location>" # ################################################################################ # # Create a new augmented profile for Existing V6.1 Installation # # Valid Values for createProfile: # true - create a new profile # false - do not create a new profile # # Please note: # When creating a deploymentManager, or standAlone profile # the profiles will be augmented automatically. # # Also note: If you are applying the Feature Pack on a Base or Express # installation, you may only create a "standAlone" profile. # # -OPT createProfile="true" # # Indicate the type of profile you would like to create. # # Valid Values: # deploymentManager - a profile will be created with a deployment manager. # - This profiles is not available for base/express installations # standAlone - a profile will be created with a stand alone Application # server. # none - a profile will not be created during installation. # # This option is required if you select to create a profile. # # -OPT profileType="standAlone" # ################################################################################ # # Administrative Security # # Valid profile types: deployment manager, and stand alone # # Valid values for PROF_enableAdminSecurity: # true - Administrative security is enabled during installation. # false - Administrative security is not enabled during installation. # # Enabling administrative security during installation is recommended. # To configure administrative security, an administrative user name and # password must be specified. Additionally, if the Application Server # Samples are installed, a password is also required for the Samples user. # # Valid values for adminUserName: a character string # Valid values for adminPassword: a character string # Valid values for samplesPassword: a character string # # Do not use the following special characters for names or passwords: # / \ * , : ; = + ? | < > & % ' " [ ] > # $ ^ { } # Note: a period (.) is not valid if it is the first character. # -OPT PROF_enableAdminSecurity="true" -OPT PROF_adminUserName= -OPT PROF_adminPassword= #-OPT PROF_samplesPassword= # ################################################################################ # # Trace Control Output # # Valid Values for traceFormat: # text - output file saved in plain text format only. # XML - output file saved in standard Java logging XML format only. # # Trace output is saved as both text and XML files by default, but it can be # restricted to only one output format. # # The amount of trace information captured can be controlled. All informational # messages, warnings, and severe warnings are output to a trace file by default. # # Valid values for traceLevel: # OFF - No trace file is produced. # SEVERE - Only severe errors are output to a trace file. # WARNING - Non-fatal exceptions and warnings are added to trace file. # INFO - Informational messages are added to the trace file. # CONFIG - Configuration related messages are added to the trace file. # FINE - Trace all public method calls. # FINER - Trace all non-public method calls except getters and setters. # FINEST - Trace all methods, entry and exit parameters, and return values. # # -OPT traceFormat= # -OPT traceLevel="INFO" # ################################################################################ # Profile creation options and values ################################################################################ # In this section, the options and valid values for creating all of the # supported profile types are described. Following this descriptive section, # each profile type is listed with all of the options necessary to create it # with its default values. # ################################################################################ # # Profile Settings # # Valid profile types: deployment manager and stand alone # # Valid values for PROF_profilePath: An empty directory path, such as # <app_server_root>/profiles/<profile_name> # # Specify a valid directory to contain the files for the run-time environment, # such as, commands, configuration files, and log files. # The user account that runs the installation must have proper permissions. # The directory must be empty and have adequate disk available. # On Windows systems, the total path length cannot exceed 80 characters. # # Valid values for PROF_profileName: a unique character sting # # Assign a name to the profile. Because creation of a cell creates two # profiles, options exists to assign separate names to the deployment # manager and application server profiles. # # Do not use the following special characters for profile names: # / \ * , : ; = + ? | < > & % ' " [ ] > # $ ^ { } # Note: a period (.) is not valid if it is the first character. # # Valid values for PROF_isDefault: # true - make this profile the default profile for the installation. # false - retain the current default profile for the installation. # # The first profile created for an installation is designated the default. # Only one profile can be designated the default profile for an installation. # Commands that are executed from the <app_server_root>/bin/ directory that # do not specify a profile to run against are run against the default profile. # ############################################################################### # # Node, Host, and Cell Names # # Valid profile types: deployment manager and stand alone # # Valid values for PROF_hostName: a character string # Valid values for PROF_nodeName: a character string # Valid values for PROF_appServerNodeName: a character string # Valid values for PROF_cellName: a character string # # Do not use the following special characters for node, host or cell names: # / \ * , : ; = + ? | < > & % ' " [ ] > # $ ^ { } # Note: a period (.) is not valid if it is the first character. # # The node name is for administration by a deployment manager. Each node name # within a cell must be unique. # # The host name is the domain name system (DNS) name (short or long) or # the IP address of this computer. If using IPv6, then specify the IP address. # # The cell name is a logical name for a group of nodes administered by # a deployment manger. # # Creation of the cell profile type creates two separate nodes, therefore # options exists to assign separate names to the deployment manager and # application server nodes. However, because both nodes are in the same cell # and on the same host, those names are specified only once. # ############################## # # Development Server Template # # Valid profile type: stand alone # # Valid values for PROF_isDeveloperServer: # true - create the application server with developer settings. # # The application server process created in the stand alone application server # profile can be configured with settings that are optimized for development. # The development template reduces startup time and allows the server to run # on less powerful hardware. Do not use this option for production servers. # ############################################################################### # # Optional Application Deployment # # Valid profile types: deployment manager, and stand alone # # Valid values for PROF_omitAction: # deployAdminConsole - do not deploy the administrative console # defaultAppDeployAndConfig - do not deploy the default application # samplesInstallAndConfig - do not deploy the sample applications # # The administrative console, default application, and Application Server # Sample applications can be optionally deployed to supported profiles types. # Use the omitAction option to prevent the specified applications from # being deployed to the new profile. # # The administrative console is a Web-based console for managing application # servers. The administrative console is deployable to stand alone application # servers and deployment managers, including the deployment manager created # with the cell set of profiles. Deploying the administrative console # is strongly recommended. # # The default application contains the Snoop, Hello, and HitCount servlets. # The default application is deployable to the application server in the # stand alone application server profile and the application server profile # created with the cell set of profiles. # # The sample applications are not recommended for deployment to production # Application Server environments. Deploy the sample applications to exercise # the application server and evaluate the latest technological advancements. # The sample applications are deployable to the application server in the # stand alone application server profile and the application server profile # created with the cell set of profiles. # ############################################################################### # # Port Value Assignment and Validation # # Valid profile types: deployment manager, stand alone # # Valid values for PROF_defaultPorts: # true - use the default port values for WebSphere Application Server. # Valid values for PROF_startingPort: # a positive integer port value, within the valid port range # Valid values for PROF_nodeStartingPort: # a positive integer port value, within the valid port range # Valid values for PROF_portsFile: # a fully qualified path to a valid ports property file # Valid values for PROF_nodePortsFile: # a fully qualified path to a valid ports property file # # There are three ways to assign port values, choose only one option. # Consult the Information Center for lists of the ports that each profile # type uses and the default values assigned to each port. # # Use PROF_defaultPorts to assign the set of default port values assigned # to the selected profile type. When creating a custom profile, the default # set of port values will be assigned during the federation process. # Therefore, this option is not supported for custom profiles. # # Alternatively, use PROF_startingPort to assign a block of ports to the # profile. Port values will be assigned incrementally as required to assign # a unique value to each port in the selected profile type. This option # is not supported for creating custom profile. Include the # PROF_nodeStartingPorts option when creating a cell set of profiles. # # Otherwise, use PROF_portsFile to assign your own specific port values # to each port that is needed for the selected profile type. This option # is supported for custom profiles when federating to a deployment manager. # Include the PROF_nodePortsFile option when creating a cell set of profiles. # # Valid values for PROF_validatePorts: # true - validates that each port value is unique and is not in use. # false - no validation of port values # # The validatePorts option is set to false by default. The validatePorts # option verifies whether the port values to be used are assigned to other # profiles and whether the ports are actively in use by other applications. # If a port conflict is detected, then validation fails and the profile # will not be created. This option is not supported for custom profiles. # ############################################################################### # # Windows Service Creation # # Valid profile types: deployment manager, and stand alone # # Valid values for PROF_winserviceCheck: # true - run as Windows service. # false - do not run as Windows service. # # Specify whether to run the deployment manager or application server as a # Windows service. For the cell set of profiles, a service is created only # for the deployment manager. A service cannot be created when installing # as a non-administrative user. # # Valid values for PROF_winserviceAccountType: # localsystem - run this service as the Local System account # specifieduser - run this service as a specified user account # Valid values for PROF_winserviceUserName: # a user account that already exists on the Windows system that has # the permission to log on as a service # Valid values for PROF_winservicePassword: # the password for the specified user account # Valid values for PROF_winserviceStartupType: # manual - the windows service must be started and stopped manually. # automatic - the windows service will start automatically after reboot. # disabled - the windows service is disabled. # # Choose whether to run the service as Local System or a specified user. # When specifying a user account also include the password for the user. # By default, the service startup type is set to automatic. # ############################## # # Linux Service Creation # # Valid values for PROF_enableService: # true - run as a Linux service. # false - do not run as a Linux service. # Valid values for PROF_serviceUserName: # a user account that already exists on the Linux system # # Specify whether to run the deployment manager or application server as a # Linux service. For the cell set of profiles, a service is created only # for the deployment manager. A service can be created only when installing # as a root user. # ############################################################################### # # Web Server Definition # # Valid profile types: stand alone # # Valid values for PROF_webServerCheck: # true - enable the creation of a Web server definition. # false - do not create a Web server definition. # # A Web server definition is not created by default. # If a Web server is used to route requests for dynamic content from the # application server, then you may want to create a Web server definition. # Web server definitions also may be created from the administrative console # or using a script that is generated during Web server plug-in installation. # # Valid values for PROF_webServerType (case sensitive): # IHS - IBM HTTP Server # HTTPSERVER_ZOS - IBM HTTP Server for Z/OS # APACHE - Apache Web servers # DOMINO - Lotus Domino Web servers # IIS - Microsoft Internet Information Services # SUNJAVASYSTEM - Sun Web servers # Valid values for PROF_webServerOS: # aix, hpux, linux, os390, os400, solaris, windows # Valid values for PROF_webServerName: a character string # Valid values for PROF_webServerHostName: DNS host name or IP Address # Valid values for PROF_webServerPort: a HTTP port number # Valid values for PROF_webServerPluginPath: directory path to plug-in # Valid values for PROF_webServerInstallPath: directory path to Web server # # To create a Web server definition, specify the type of Web server and its # operating system. The Web server name is used to identify the specified # Web server in the administrative console. Also provide the DNS host name # or IP address of the Web server, its primary communication port # (default 80), and the complete directory path to the Web server plug-ins. # Additionally, if the Web server is IHS, then provide the complete # directory path to where it is installed. # # Do not use the following special characters for Web server names: # / \ * , : ; = + ? | < > & % ' " [ ] > # $ ^ { } # Note: a period (.) is not valid if it is the first character. # ############################################################################### ################################################################################ # Uncomment the following when creating a stand alone application server profile. ################################################################################ # ## Profile Settings # -OPT PROF_profilePath= # -OPT PROF_profileName= # -OPT PROF_isDefault="true" ## Node, Host, and Cell Names # -OPT PROF_hostName= # -OPT PROF_nodeName= # -OPT PROF_cellName= # -OPT PROF_isDeveloperServer="false" ## Optional Application Deployment # -OPT PROF_omitAction="samplesInstallAndConfig" ## Port Value Assignment and Validation # -OPT PROF_defaultPorts="true" # -OPT PROF_startingPort= # -OPT PROF_portsFile= # -OPT PROF_validatePorts="true" ## Windows Service Creation # -OPT PROF_winserviceCheck="true" # -OPT PROF_winserviceAccountType= # -OPT PROF_winserviceUserName= # -OPT PROF_winservicePassword= # -OPT PROF_winserviceStartupType="automatic" ## Linux Service Creation # -OPT PROF_enableService="true" # -OPT PROF_serviceUserName= ## Web Server Definition # -OPT PROF_webServerCheck="false" # -OPT PROF_webServerType= # -OPT PROF_webServerOS= # -OPT PROF_webServerName= # -OPT PROF_webServerHostname= # -OPT PROF_webServerPort=80 # -OPT PROF_webServerInstallPath= # -OPT PROF_webServerPluginPath= # ################################################################################ # Uncomment the following to create a deployment manager profile. ################################################################################ # ## Profile Settings # -OPT PROF_profilePath= # -OPT PROF_profileName= # -OPT PROF_isDefault="true" ## Node, Host, and Cell Names # -OPT PROF_hostName= # -OPT PROF_nodeName= # -OPT PROF_cellName= ## Optional Application Deployment # -OPT PROF_omitAction= ## Port Value Assignment and Validation # -OPT PROF_defaultPorts="true" # -OPT PROF_startingPort= # -OPT PROF_portsFile= # -OPT PROF_validatePorts="true" ## Windows Service Creation # -OPT PROF_winserviceCheck="true" # -OPT PROF_winserviceAccountType="localsystem" # -OPT PROF_winserviceUserName= # -OPT PROF_winservicePassword= # -OPT PROF_winserviceStartupType="automatic" ## Linux Service Creation # -OPT PROF_enableService="true" # -OPT PROF_serviceUserName= # ################################################################################ # Profile Augmentation on existing Profiles ################################################################################ # # Augmenting profiles # # To Augment an existing profile you must provide the information you would if # you were to call -augment option from the command line (minus the -augment command) # # - If your template path contains spaces(Windows Only), then enclose the path # with 'SINGLE' quotations # # - you can augment multiple profiles at once, by copying the line below # multiple times. # # Augment options are # -profileName: replace <profilename> with an existing profile name # -templatepath: replace WAS_HOME with the absolute path to the # current WAS home directory (same as installLocation) # ## For Augmenting a deployment manager profile # -OPT PROF_augment="-profileName <profilename> -templatePath WAS_HOME/profileTemplates/EJB3/dmgr.ejb3fep" # ## For Augmenting an Application Server profile # -OPT PROF_augment="-profileName <profilename> -templatePath WAS_HOME/profileTemplates/EJB3/default.ejb3fep" # ##################################################################################
See the install command for
more information about installation types and
profile types.