[IBM i]

Installing the product on IBM i operating systems using response files

You can install WebSphere® Application Server Version 8.5 on IBM i operating systems using Installation Manager response files.

Before you begin

Prepare for the installation before using this procedure. See Preparing the operating system for installation on IBM i for more information.

Before you install WebSphere Application Server, ensure that your user profile has *ALLOBJ and *SECADM special authorities.

Install Installation Manager on the system onto which you want to install the product.
  • If you want to use the Installation Manager that comes with this product, perform the following actions:
    1. Obtain the necessary files.
      There are three basic options for obtaining and installing Installation Manager and the product.
      • Access the physical media, and use local installation
        You can access the product repositories on the product media.
        1. Install Installation Manager on your system.

          You can install Installation Manager using the product media, using a file obtained from the Passport Advantage® site, or using a file containing the most current version of Installation Manager from the IBM® Installation Manager download website.

        2. Use Installation Manager to install the product from the product repositories on the media.
      • Download the files from the Passport Advantage site, and use local installation
        Licensed customers with a Passport Advantage ID and password can download the necessary product repositories from the Passport Advantage site.
        1. Download the files from the Passport Advantage site.
        2. Install Installation Manager on your system.

          You can install Installation Manager using the product media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.

        3. Use Installation Manager to install the product from the downloaded repositories.
      • Access the live repositories, and use web-based installation
        If you have a Passport Advantage ID and password, you can install the product from the web-based repositories.
        1. Install Installation Manager on your system.

          You can install Installation Manager using the product media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of Installation Manager from the IBM Installation Manager download website.

        2. Use Installation Manager to install the product from the web-based repository located at
          http://www.ibm.com/software/repositorymanager/com.ibm.websphere.EXPRESS.v85 
          Note: This location does not contain a web page that you can access using a web browser. This is a remote web-based repository location that you must specify in the response file so that the installation can access the files in this repository.

        Whenever possible, you should use the remote web-based repositories so that you are accessing the most up-to-date installation files.

      Note: If you do not have a Passport Advantage ID and password, you must install the product from the product repositories on the media or local repositories.
    2. Install Installation Manager.
      1. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
      2. On a CL command line, run the STRQSH command to start the Qshell command shell.
      3. Make sure that the umask is set to 022.
        To verify the umask setting, issue the following command:
        umask
        To set the umask setting to 022, issue the following command:
        umask 022
      4. Change to the temporary directory where you unpacked the Installation Manager files.
      5. Run the following command in the temporary folder:
        installc -acceptLicense -log log_file_path_and_name
        Notes:
  • If you already have a version of Installation Manager installed on your system and you want to use it to install and maintain the product, obtain the necessary product files.
    There are three basic options for installing the product.
    • Access the physical media, and use local installation

      You can access the product repositories on the product media. Use Installation Manager to install the product from the product repositories on the media.

    • Download the files from the Passport Advantage site, and use local installation
      Licensed customers with a Passport Advantage ID and password can download the necessary product repositories from the Passport Advantage site.
      1. Download the product repositories from the Passport Advantage site.
      2. Use Installation Manager to install the product from the downloaded repositories.
    • Access the live repositories, and use web-based installation
      If you have a Passport Advantage ID and password, you can use Installation Manager to install the product from the web-based repositories. Use Installation Manager to install the product from the web-based repository located at
      http://www.ibm.com/software/repositorymanager/com.ibm.websphere.EXPRESS.v85 
      Note: This location does not contain a web page that you can access using a web browser. This is a remote web-based repository location that you must specify in the response file so that the installation can access the files in this repository.

      Whenever possible, you should use the remote web-based repositories so that you are accessing the most up-to-date installation files.

    Note: If you do not have a Passport Advantage ID and password, you must install the product from the product repositories on the media or local repositories.

Procedure

  1. Optional: If the repository requires a username and password, create a keyring file to access this repository.

    For more information on creating a keyring file for Installation Manager, read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

    Tip: When creating a keyring file, append /repository.config at the end of the repository URL location if the imutilsc command is unable to find the URL that is specified.
    Note: Starting in Installation Manager Version 1.6.2, the -keyring and -password options that have been used to access credentials in a keyring file are deprecated. When you use Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.

    There is no migration path from keyring files to storage files because of the differences in the file structures. You must create a storage file to replace a keyring file.

    For more information on using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the Installation Manager Version 1.6 Information Center.

  2. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
  3. On a CL command line, run the STRQSH command to start the Qshell command shell.
  4. Make sure that the umask is set to 022.
    To verify the umask setting, issue the following command:
    umask
    To set the umask setting to 022, issue the following command:
    umask 022
  5. Use a response file to install the product.
    Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the product. For example:
    ./imcl -acceptLicense 
      input $HOME/WASFiles/temp/install_response_file.xml 
      -log $HOME/WASFiles/temp/install_log.xml 
      -keyring $HOME/WASFiles/temp/im.keyring
    Notes:
    • The relevant terms and conditions, notices, and other information are provided in the license-agreement files in the lafiles or product_name/lafiles subdirectory of the installation image or repository for this product.
    • /QIBM/ProdData/InstallationManager is the default installation location for Installation Manager files on IBM i systems.
    • The program might write important post-installation instructions to standard output.

    Read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center for more information.

Example

The following is an example of a response file for installing the product with no optional features into the /QIBM/ProdData/WebSphere/AppServer/V85/EXPRESS directory using a web-based repository located at http://www.ibm.com/software/repositorymanager/com.ibm.websphere.EXPRESS.v85.
<?xml version="1.0" encoding="UTF-8"?>
<agent-input>
<server>
  <repository location='http://www.ibm.com/software/repositorymanager/com.ibm.websphere.EXPRESS.v85'/>
</server>
<profile id='IBM WebSphere Application Server V8.5' installLocation='/QIBM/ProdData/WebSphere/AppServer/V85/EXPRESS'>
  <data key='eclipseLocation' value='/QIBM/ProdData/WebSphere/AppServer/V85/EXPRESS'/>
  <data key='was.install.os400.profile.location' value='/QIBM/UserData/WebSphere/AppServer/V85/EXPRESS'/>
  <data key='user.import.profile' value='false'/>
  <data key='cic.selector.nl' value='en, fr, it, zh, ro, ru, zh_TW, de, ja, pl, es, cs, hu, ko, pt_BR'/>
</profile>
<install modify='false'>
  <offering profile='IBM WebSphere Application Server V8.5' 
    features='core.feature' id='com.ibm.websphere.EXPRESS.v85'/>
</install>
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' 
  value='/QIBM/UserData/InstallationManager/IMShared'/>
<preference name='com.ibm.cic.common.core.preferences.connectTimeout' value='30'/>
<preference name='com.ibm.cic.common.core.preferences.readTimeout' value='30'/>
<preference name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount' value='0'/>
<preference name='offering.service.repositories.areUsed' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication' value='false'/>
<preference name='http.ntlm.auth.kind' value='NTLM'/>
<preference name='http.ntlm.auth.enableIntegrated.win32' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/>
<preference name='com.ibm.cic.common.core.preferences.keepFetchedFiles' value='false'/>
<preference name='PassportAdvantageIsEnabled' value='false'/>
<preference name='com.ibm.cic.common.core.preferences.searchForUpdates' value='false'/>
</agent-input>
Tips:
  • Make sure that the repository location points to the web-based or local product repository. For example:
    <repository location='https://downloads.mycorp.com:8080/WAS_85_repository'/>
  • The following line from the example specifies the default value of the profile location for IBM i:
    <data key='was.install.os400.profile.location' value='/QIBM/UserData/WebSphere/AppServer/V85/EXPRESS'/>
    To override this default location, specify a different location
  • The following line from the example specifies the default value of the shared resources directory for IBM i:
    <preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='/QIBM/UserData/InstallationManager/IMShared'/>
    To override this default location, specify a different location
    Note: There is only one shared resources directory for Installation Manager. If there has been an installation on the system in the past, it will use that shared resources directory and not the one specified in the response file.
  • To disable remote searches for updates in the response file, set the following preferences to false:
    • offering.service.repositories.areUsed

      Used for searching remote repositories for updates to installed offerings

    • com.ibm.cic.common.core.preferences.searchForUpdates

      Used for searching for updates to Installation Manager

    For example:
    <preference value='false' name='offering.service.repositories.areUsed'/>
    <preference value='false' name='com.ibm.cic.common.core.preferences.searchForUpdates'/>
    You can find more details on silent preference keys in the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.
  • To install more than one instance of an offering, you must make the profile ID of each additional instance unique. For example:
    <offering profile='IBM WebSphere Application Server V8.5 - Another User's WAS EXPRESS' 
        features='core.feature' id='com.ibm.websphere.EXPRESS.v85'/>
    This must be changed in both places that specify the profile ID in the response file.
Here are some examples of changes that you could make to manipulate this response file to perform alternative actions.
  • To alter the location of the installation, simply change the installation location. For example:
    Replace
    <profile id='IBM WebSphere Application Server V8.5' installLocation='/QIBM/ProdData/WebSphere/AppServer/V85/EXPRESS'>
    with
    <profile id='IBM WebSphere Application Server V8.5' installLocation='/home/user/IBM/Websphere/AppServer/V85/Server'>
  • To install from a local repository instead of the live remote repository, replace the repository location. For example:
    Replace
    <repository location='http://www.ibm.com/software/repositorymanager/com.ibm.websphere.EXPRESS.v85'/>
    with
    <repository location='/home/user/repositories/WAS85/local-repositories'/>
  • To add the optional features, add each desired feature in the offering as an entry in a comma-separated list.
    In the following list, the offering IDs to be used in the response files are enclosed in parentheses:
    [8.5.5.0 or later]
    • WebSphere Application Server full profile (core.feature)
      • EJBDeploy tool for pre-EJB 3.0 modules (ejbdeploy)

        This option installs the EJBDeploy tool for pre-EJB 3.0 modules.

        Before you deploy applications on the server, you must run the EJBDeploy tool on applications that contain EJB modules that are based on specifications prior to EJB 3.0. Running the EJBDeploy tool generates deployment code for enterprise beans in the application. Beginning with the EJB 3.0 specification, the EJBDeploy tool is no longer required because WebSphere Application Server uses a new feature called JITDeploy, which automatically generates code when the application starts.

        Note: Unexpected errors might occur if applications that are provided with IBM WebSphere Application Server, such as the samples, require the optional EJBDeploy tool for pre-EJB 3.0 modules but the feature is not installed. If you deploy and use applications that might require pre-EJB 3.0 modules, include the optional EJBDeploy feature in all WebSphere Application Server installations that will be used by servers running the pre-EJB 3.0 applications.
      • Standalone thin clients, resource adapters, and embeddable containers
        • Standalone thin clients and resource adapters (thinclient)

          This option installs the IBM standalone thin clients and resource adapters.

          IBM thin clients provide a set of clients for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. IBM resource adapters provide the resource adapters for JMS.

        • Embeddable EJB container (embeddablecontainer)

          This option installs the embeddable EJB container.

          The embeddable EJB Container is a Java Archive (JAR) file that you can use to run enterprise beans in a standalone Java Platform, Standard Edition environment. You can run enterprise beans using this embeddable container outside the application server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used for unit testing enterprise beans business logic.

      • Sample applications (samples)

        This option installs the sample applications for learning and demonstration environments.

        The samples include both source code files and integrated enterprise applications that demonstrate some of the latest Java (TM) Platform, Enterprise Edition (Java EE) and WebSphere technologies. The samples are recommended for installation to learning and demonstration environments, such as development environments. However, they are not recommended for installation to production application server environments.

    • WebSphere Application Server full profile (core.feature)
      Installing this application-server feature gives you the traditional standards-based Java Platform, Enterprise Edition (Java EE) compliant application foundation, offering broad programming model choice and low total cost of ownership through high performance and high manageability.
      • EJBDeploy tool for pre-EJB 3.0 modules (ejbdeploy)

        This option installs the EJBDeploy tool for pre-EJB 3.0 modules.

        Before you deploy applications on the server, you must run the EJBDeploy tool on applications that contain EJB modules that are based on specifications prior to EJB 3.0. Running the EJBDeploy tool generates deployment code for enterprise beans in the application. Beginning with the EJB 3.0 specification, the EJBDeploy tool is no longer required because WebSphere Application Server uses a new feature called JITDeploy, which automatically generates code when the application starts.

        Note: Unexpected errors might occur if applications that are provided with IBM WebSphere Application Server, such as the samples, require the optional EJBDeploy tool for pre-EJB 3.0 modules but the feature is not installed. If you deploy and use applications that might require pre-EJB 3.0 modules, include the optional EJBDeploy feature in all WebSphere Application Server installations that will be used by servers running the pre-EJB 3.0 applications.
      • Standalone thin clients, resource adapters, and embeddable containers
        • Standalone thin clients and resource adapters (thinclient)

          This option installs the IBM standalone thin clients and resource adapters.

          IBM thin clients provide a set of clients for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. IBM resource adapters provide the resource adapters for JMS.

        • Embeddable EJB container (embeddablecontainer)

          This option installs the embeddable EJB container.

          The embeddable EJB Container is a Java Archive (JAR) file that you can use to run enterprise beans in a standalone Java Platform, Standard Edition environment. You can run enterprise beans using this embeddable container outside the application server. The embeddable EJB container is a part of the EJB 3.1 specification and is primarily used for unit testing enterprise beans business logic.

      • Sample applications (samples)

        This option installs the sample applications for learning and demonstration environments.

        The samples include both source code files and integrated enterprise applications that demonstrate some of the latest Java (TM) Platform, Enterprise Edition (Java EE) and WebSphere technologies. The samples are recommended for installation to learning and demonstration environments, such as development environments. However, they are not recommended for installation to production application server environments.

    • WebSphere Application Server Liberty profile (liberty)

      Installing this application-server feature gives you a lightweight profile of the application server along with a simplified configuration approach for the development environment. Its fast restart times, small size, and ease of use make it a good option for building web applications that do not require the full JEE environment of traditional enterprise application server profiles. The Liberty profile also can be used in production; and because it is a dynamic configuration, the application server provisions only the features required by the running applications.

    Notes:
    • The features samples, thinclient, embeddablecontainer, and ejbdeploy are subfeatures of core.feature.
    • If no features are specified, the default features (core.feature, ejbdeploy, thinclient, and embeddablecontainer) are installed. To install only the features that you want, specify the list of features explicitly.
    • You must install core.feature (full WebSphere Application Server profile), liberty (Liberty profile), or both.
    • You cannot use the Installation Manager modify, update, or rollback functions to modify this installation later and add or remove core.feature (full WebSphere Application Server profile) or liberty (Liberty profile). You can use these functions to add or remove the ejbdeploy, thinclient, embeddablecontainer, or samples subfeature of core.feature later.
    For example, to install the samples:
    Replace
    <offering profile='IBM WebSphere Application Server V8.5' 
      features='core.feature' id='com.ibm.websphere.EXPRESS.v85'/>
    with
    <offering profile='IBM WebSphere Application Server V8.5' 
      features='core.feature,samples' id='com.ibm.websphere.EXPRESS.v85'/>
Tip: If no features are specified, the default features (core.feature, ejbdeploy, thinclient, and embeddablecontainer) are installed. To install only the features that you want, specify the list of features explicitly.

What to do next

You can create a standalone application server profile or a management profile with an administrative agent server using the manageprofiles command.

The following is an example of using the manageprofiles command to create a default standalone application server profile. This example is based on the following assumptions:
  • The samples feature is installed.
  • Security is to be enabled.
  • The system host name is myhost.abc.com.
  • The appserver_install_root is /QIBM/ProdData/WebSphere/AppServer/V85/EXPRESS.
  • The user_data_root is /QIBM/UserData/WebSphere/AppServer/V85/EXPRESS.
  • The administrative user name is wasadmin.
  • The password is password.
Default standalone application server:
manageprofiles -create
  -portsFile /QIBM/ProdData/WebSphere/AppServer/V85/EXPRESS/profileTemplates/default/actions/portsUpdate/portdef.props
  -serverName server1
  -nodeName myhost
  -hostName myhost.abc.com
  -cellName myhost 
  -adminUserName wasadmin
  -adminPassword password
  -templatePath /QIBM/ProdData/WebSphere/AppServer/V85/EXPRESS/profileTemplates/default
  -enableAdminSecurity true
  -profileName default
Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 09:50 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-express-iseries&topic=tins_installation_is_silent
File name: tins_installation_is_silent.html