[IBM i]

Installing the product on IBM i operating systems using the command line

You can install WebSphere® Application Server Version 8.5 using the Installation Manager command line.

Before you begin

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

Important: Before installing WebSphere Application Server Version 8, you must read the license agreement that you can find with the product files. Signify your acceptance of the license agreement by specifying -acceptLicense in the command as described below.
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.ND.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 for the value of the -repositories parameter so that the imcl command can access the files in this repository to install the product.

        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. Choose three separate locations for Installation Manager's binaries, runtime data (agent data), and shared data locations.
    3. Install Installation Manager using the Installation Manager command line.
      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 location containing the Installation Manager installation files, and run the following command:
        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.ND.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 for the value of the -repositories parameter so that the imcl command can access the files in this repository to install the product.

      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. Choose three separate locations for the product's binaries, runtime data (agent data), and shared data locations.
  3. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
  4. On a CL command line, run the STRQSH command to start the Qshell command shell.
  5. 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
  6. Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager.
  7. Use the imcl command to install the product.
    ./imcl install com.ibm.websphere.ND.v85_offering_version,optional_feature_ID
      -repositories source_repository 
      -installationDirectory installation_directory 
      -sharedResourcesDirectory shared_directory
      -accessRights access_mode
      -preferences preference_key=value
      -properties property_key=value
      -keyring keyring_file -password password
      -acceptLicense
    Tips:
    • 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.
    • You can install a list of features that are separated by commas.
      In the following list, the feature IDs 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.
    • The offering_version, which optionally can be attached to the offering ID with an underscore, is a specific version of the offering to install (8.5.0.20110503_0200 for example).
      • If offering_version is not specified, the latest version of the offering and all interim fixes for that version are installed.
      • If offering_version is specified, the specified version of the offering and no interim fixes for that version are installed.
      The offering version can be found attached to the end of the offering ID with an underscore when you run the following command against the repository:
      ./imcl listAvailablePackages -repositories source_repository
    • You can also specify none, recommended or all with the -installFixes argument to indicate which interim fixes you want installed with the offering.
      • If the offering version is not specified, the -installFixes option defaults to all.
      • If the offering version is specified, the -installFixes option defaults to none.
    • For initial installations, it is a good practice to specify the user_data_root; otherwise, the default value for the user_data_root, /QIBM/UserData/WebSphere/AppServer/V85/ND, is used. Use the was.install.os400.profile.location property to specify the user_data_root. If the user_data_root is to be /QIBM/UserData/WebSphere/AppServer/V85/ND, for example, specify -properties was.install.os400.profile.location=/QIBM/UserData/WebSphere/AppServer/V85/ND on the imcl installation command.
    • The program might write important post-installation instructions to standard output.

    For more information on using the imcl command to install the product, see the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

Example

Here is an example of using the imcl command to install Websphere Application Server:
./imcl install com.ibm.websphere.ND.v85
  -repositories https://downloads.mycorp.com:8080/WAS_85_repository
  -installationDirectory /QIBM/ProdData/WebSphere/AppServer/V85/ND
  -properties was.install.os400.profile.location=/QIBM/UserData/WebSphere/AppServer/V85/ND
  -sharedResourcesDirectory /QIBM/UserData/InstallationManager/IMShared
  -keyring $HOME/WASFiles/temp/im.keyring
  -acceptLicense

What to do next

You can create a standalone application server profile, management profile, managed (custom) profile, cell profile, or secure proxy profile using the manageprofiles command.

The following are examples of using the manageprofiles command to create a default standalone application server profile and a default cell profile. These examples are 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/ND.
  • The user_data_root is /QIBM/UserData/WebSphere/AppServer/V85/ND.
  • The administrative user name is wasadmin.
  • The password is password.
Default standalone application server:
manageprofiles -create
  -portsFile /QIBM/ProdData/WebSphere/AppServer/V85/ND/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/ND/profileTemplates/default
  -enableAdminSecurity true
  -profileName default
Default cell profile:
  1. Create the deployment manager portion of the default cell profile:
    manageprofiles -create 
      -appServerNodeName myhost
      -portsFile /QIBM/ProdData/WebSphere/AppServer/V85/ND/profileTemplates/cell/dmgr/actions/portsUpdate/portdef.props
      -nodeName myhostManager
      -nodeProfilePath /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/default
      -nodePortsFile /QIBM/ProdData/WebSphere/AppServer/V85/ND/profileTemplates/cell/dmgr/actions/portsUpdate/nodeportdef.props
      -hostName myhost.abc.com 
      -cellName myhostNetwork
      -adminUserName wasadmin
      -adminPassword password
      -templatePath /QIBM/ProdData/WebSphere/AppServer/V85/ND/profileTemplates/cell/dmgr
      -enableAdminSecurity true
      -profileName dmgr
  2. Create the application server portion of the cell profile:
    manageprofiles -create
      -appServerNodeName myhost
      -portsFile /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/dmgr/properties/portdef.props
      -dmgrProfilePath /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/dmgr
      -serverName server1 
      -nodeName myhostManager
      -nodePortsFile /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/dmgr/properties/nodeportdef.props
      -hostName myhost.abc.com
      -cellName myhostNetwork
      -adminUserName wasadmin
      -adminPassword password
      -isDefault
      -templatePath /QIBM/ProdData/WebSphere/AppServer/V85/ND/profileTemplates/cell/default 
      -enableAdminSecurity true 
      -profileName default 
Task topic    

Terms and conditions for information centers | Feedback

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