[AIX Solaris HP-UX Linux Windows]

Installing the product on distributed operating systems using the GUI

You can use the Installation Manager GUI to install WebSphere® Application Server Version 8.5.

Before you begin

Prepare your system as described in Installing Installation Manager and preparing to install the product.

About this task

Tip: By default, Installation Manager saves earlier versions of a package to roll back to if you experience issues later. When Installation Manager rolls back a package to a previous version, the current version of the files are uninstalled and the earlier versions are reinstalled. If you choose not to save the files for rollback, you can prevent the files from being saved or delete them after they are saved. To set your rollback preferences, perform the following actions before installing a package:
  1. Launch Installation Manager.
  2. Open the Rollback preferences window by selecting File > Preferences > Files for Rollback.
  3. Select or clear the Save files for rollback option to save or to stop saving a copy of files that are required to roll back packages on your computer.

    You can remove any files that have already been saved by clicking Delete Saved Files. If you delete the files and you need to roll back a package later, you must connect to a repository or insert the media to obtain the required files for the previous version of the package.

  4. Click OK to save your rollback preferences.
For more information on setting your Installation Manager preferences, see the IBM® Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center.

Procedure

  1. Start Installation Manager.
    [AIX][HP-UX][Linux][Solaris] Tip: You can start Installation Manager in group mode with the ./IBMIM command.
  2. Click Install.
    Note: If you are prompted to authenticate, use the IBM ID and password that you registered with on the program website.

    Installation Manager searches its defined repositories for available packages.

  3. Perform the following actions.
    1. Select IBM WebSphere Application Server Network Deployment and the appropriate version.
      Note: If you are installing the trial version of this product, select IBM WebSphere Application Server Network Deployment Trial and the appropriate version.

      If you already have the product installed on a WebSphere Application Server installation on your system, a message displays indicating that the product is already installed. To create another installation of the product in another location, click Continue.

      Tip: If the Search service repositories during installation and updates option is selected on the Installation Manager Repository preference page and you are connected to the Internet, you can click Check for Other Versions and Extensions to search for updates in the default update repositories for the selected packages. In this case, you do not need to add the specific service-repository URL to the Installation Manager Repository preference page.
    2. Select the fixes to install.

      Any recommended fixes are selected by default.

      If there are recommended fixes, you can select the option to show only recommended fixes and hide non-recommended fixes.

    3. Click Next.
    Note: Installation Manager might prompt you to update to the latest level of Installation Manager when it connects to the repository. Update to the newer version before you continue if you are prompted to do so. Read the IBM Installation Manager Version 1.6 Information Center or the IBM Installation Manager Version 1.5 Information Center for information about automatic updates.
  4. Accept the terms in the license agreements, and click Next.
  5. Specify the installation root directory for the product binaries, which are also referred to as the core product files or system files.
    The panel also displays the shared resources directory and disk-space information.
    Note: The first time that you install a package using Installation Manager, specify the shared resources directory. The shared resources directory is where installation artifacts are located that can be used by one or more package groups. Use your largest drive for this installation. You cannot change the directory location until after you uninstall all packages.
    Restrictions:
    • Deleting the default target location and leaving an installation-directory field empty prevents you from continuing.
    • Do not use symbolic links as the destination directory.

      Symbolic links are not supported.

    • Do not use a semicolon in the directory name.

      WebSphere Application Server cannot install properly if the target directory includes a semicolon.

      [Windows] A semicolon is the character used to construct the class path on Windows systems.

    • [Windows] The maximum path length on the Windows Server 2008, Windows Vista, and Windows 7 operating systems is 60 characters.
  6. Click Next.
  7. Select the languages for which translated content should be installed.

    English is always selected.

  8. Click Next.
  9. Select the features that you want to install.
    Choose from the following features:
    • IBM WebSphere Application Server Network Deployment
      [8.5.5.0 or later]
      • WebSphere Application Server Full Profile
        Note: You must select this feature.
        • EJBDeploy tool for pre-EJB 3.0 modules

          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.

          Tip: 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.
          Tip: You can run the Installation Manager later to modify this installation and add or remove this feature.
        • Standalone thin clients, resource adapters, and embeddable containers

          IBM thin clients and resource adapters provide a set of clients and resource adapters for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An embeddable container runs in a standalone Java Platform, Standard Edition environment. For example, you can use the embeddable EJB container to run enterprise beans outside the application server.

          • Standalone thin clients and resource adapters

            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

            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.

          Tip: You can run the Installation Manager later to modify this installation and add or remove these features.
        • Sample applications

          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.

          Tip: You can run the Installation Manager later to modify this installation and add or remove this feature.
      • [AIX][Linux][Solaris][Windows] IBM WebSphere SDK Java Technology Edition Version 6.0

        This option allows you to choose between a 32-bit and 64-bit Software Development Kit.

        Notes:
        • This option displays only if you are installing on a 64-bit system.
        • This does not apply to Solaris x86 64-bit systems.
        • You must select one of the two options.
        • If IBM WebSphere SDK Java Technology Edition Version 7.0 is being installed, its bit selection will be set to match this selection.
        • You cannot modify this installation later and change this selection.
      • WebSphere Application Server Full Profile
        Selecting 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

          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.

          Tip: 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.
          Tip: You can run the Installation Manager later to modify this installation and add or remove this feature.
        • Standalone thin clients, resource adapters, and embeddable containers

          IBM thin clients and resource adapters provide a set of clients and resource adapters for a variety of technologies, such as JAX-WS, JAX-RPC, JAX-RS, XML, EJB, JPA, JMS, and more. An embeddable container runs in a standalone Java Platform, Standard Edition environment. For example, you can use the embeddable EJB container to run enterprise beans outside the application server.

          • Standalone thin clients and resource adapters

            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

            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.

          Tip: You can run the Installation Manager later to modify this installation and add or remove these features.
        • Sample applications

          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.

          Tip: You can run the Installation Manager later to modify this installation and add or remove this feature.
      • WebSphere Application Server Liberty Profile

        Selecting 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 great 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.

      • [AIX][Linux][Solaris][Windows] IBM Software Development Kit

        This option allows you to choose between a 32-bit and 64-bit Software Development Kit.

        Notes:
        • This option displays only if you are installing on a 64-bit system.
        • This does not apply to Solaris x86 64-bit systems.
        • You must select one of the two options.
        • If IBM WebSphere SDK Java Technology Edition Version 7.0 is being installed, its bit selection will be set to match this selection.
        • You cannot modify this installation later and change this selection.
      Restrictions:
      • You must select WebSphere Application Server Full Profile, WebSphere Application Server Liberty Profile, or both.
      • You cannot use the Installation Manager modify, update, or rollback functions to modify this installation later and add or remove WebSphere Application Server Full Profile or WebSphere Application Server Liberty Profile. You can use these functions to add or remove the subfeatures of WebSphere Application Server Full Profile later.
      • You cannot upgrade from a trial or Express edition later and add or remove WebSphere Application Server Full Profile or WebSphere Application Server Liberty Profile.
  10. Click Next.
  11. Review the summary information, and click Install.
    • If the installation is successful, the program displays a message indicating that installation is successful.
      Note: The program might also display important post-installation instructions as well.
    • If the installation is not successful, click View Log File to troubleshoot the problem.
  12. Select which tool you want to start when this installation is finished.
    • Select Profile Management Tool to create a profile if you want to open the full Profile Management Tool and create a new profile when this installation is finished.
    • Select Profile Management Tool to create an application server profile for a development environment if you want to create an application server profile with settings appropriate for a development environment when this installation is finished.
      Note: The development settings are appropriate for a development environment where frequent application updates are performed and system resources are at a minimum. Do not use the development settings for production servers.
    • Select None if you do not want to create a new profile when this installation is finished.
    Restriction: The option to launch the Profile Management Tool is only available when a version of WebSphere Application Server containing the Profile Management Tool is installed.
  13. Click Finish.
  14. Click File > Exit to close Installation Manager.

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 Profile Management Tool or the manageprofiles command.

Tip: Installation Manager optionally can search for updates to itself whenever the Install Packages, Modify Packages, or Update Packages page is opened from the Start page as well as when clicking Check for Other Versions and Extensions on the Install Packages page. To enable this option, perform the following actions:
  1. Start Installation Manager.
  2. In the top menu, click File > Preferences.
  3. Select Updates.
  4. Select Search for Installation Manager updates.
  5. Click Apply.
  6. Click OK.

Do not enable this option if you do not have access to the service repository.

Task topic    

Terms and conditions for information centers | Feedback

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