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

Attention: Starting in version 8.5.5.11, the default versions of Java are Java SE 6 or Java SE 8. As such, you can accept the default and install either Java SE 6 or Java SE 8 as the version of Java SE contained in the /java and /java64 directories in WebSphere Application Server and used by default during server and node configuration. Java 8 is the recommended Java SDK because it provides the latest features and security updates. You can continue to use Java SE 6, but no service can be provided after the end of support in April 2018, which might expose your environment to security risks.

Java SE 7 and Java SE 7.1 (not available for Solaris and HP) are also viable options for installing on WebSphere Application Server version 8.5.5.11.

The bit level of Java SE 7.0 is based on the bit level selected during the initial installation of WebSphere Application Server. If a 32-bit WebSphere Application Server is installed, then only the 32-bit Java SE 7.0 can be installed. If a 64-bit WebSphere Application Server is installed, then only the 64-bit Java SE 7.0 can be installed.
Installing the optional Java SE 7.0 or Java SE 7.1 does not imply that profiles can take advantage of this new version of Java. The managesdk command can be used to switch Java or the WebSphere Application Server administrative console (wsadmin) can be used to make the switch.

[8.5.5.14 or later] Starting in version 8.5.5.14, Java SE 8 is the default Java. When updating to 8.5.5.14, any existing profile that uses Java SDK 6 is replaced by Java SDK 8. You can continue to use Java SDK Java Technology Edition Version 7.0 and Version 7.1, but no service can be provided after the end of support in July 2022, which could expose your environment to security risks.

For more information on Java SE 6, 7, and 7.1 end of service, see Java SE 6, 7, and 7.1 end of service in WebSphere Application Server V8.5.

The com.ibm.websphere.IBMJAVA.v80 offering will be deprecated, and no fix packs or interim fixes will be provided for this offering after March 2020. If this offering is installed with WebSphere Application Server Version 8.5.5 after March 2020, uninstall it and switch to the default Java SE 8 SDK provided by the WebSphere Application Server package in the same package group. With the default Java SE 8 SDK, you continue receiving Java SE 8 SDK support, including security updates.

[8.5.5.18 or later] Starting in version 8.5.5.18 for Linux on POWER8 Little Endian (LE), the default versions of Java are Java SE 7.1 or Java SE 8. As such, you can accept the default and install either Java SE 7.1 or Java SE 8 as the version of Java SE contained in the /java directory in WebSphere Application Server and used by default during server and node configuration. Java 8 is the recommended Java SDK because it provides the latest features and security updates. You can continue to use Java SE 7.1, but no service can be provided after the end of support in July 2022, which might expose your environment to security risks.

You can use the user.wasjava=java8 property only with new installations of the product for Linux on POWER8 LE. The user.wasjava=java8 property does not work for product upgrades through fix packs for Linux on POWER8 LE.

[8.5.5.19 or later] Starting in version 8.5.5.19 for Linux on POWER8 Little Endian (LE), the default version of Java is Java SE 8. As such, you can accept the default and install Java SE 8 as the version of Java SE contained in the /java directory in WebSphere Application Server and used by default during server and node configuration. You can continue to use Java SE 7.1 by installing IBM WebSphere Java SDK Version 7.1, but no service can be provided after the end of support in July 2022, which might expose your environment to security risks.

The user.wasjava=java8 property is not required for installing and updating to version 8.5.5.19 for Linux on POWER8 LE.

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

Supported configurations: Installation on the K-UX 2.1 operating system is supported in silent mode only. You must have IBM® Installation Manager Version 1.7.3.1 to install the product on the K-UX 2.1 operating system.

Supported configurations: To install the product on Linux on POWER® Little Endian (LE) systems, you must have IBM Installation Manager Version 1.8.0 or later.

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:

Launch Installation Manager.
Open the Rollback preferences window by selecting File > Preferences > Files for Rollback.
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.
Click OK to save your rollback preferences.

For more information on setting your Installation Manager preferences, see the IBM Installation Manager documentation.

Procedure

Start Installation Manager.
Tip: You can start Installation Manager in group mode with the ./IBMIM command.
- Group mode allows multiple users to use a single instance of IBM Installation Manager to manage software packages.
- For more information on using group mode, read the Group mode road maps in the IBM Installation Manager documentation.
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.
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 documentation for information about automatic updates.
Accept the terms in the license agreements, and click Next.
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.
  
  A semicolon is the character used to construct the class path on Windows systems.
- The maximum path length on the Windows Server 2008, Windows Vista, and Windows 7 operating systems is 60 characters.
Click Next.
Select the languages for which translated content should be installed.

English is always selected.
Click Next.
Select the features that you want to install.
Choose from the following features:
- IBM WebSphere Application Server Network Deployment
  - 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 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.
    
    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.
    
    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 any of these features.
  - IBM WebSphere SDK Java Technology Edition
    This option is only available on 64-bit systems.
Click Next.
The default Java SDK is Java SE 8. Support for using Java SE 6 ends in April 2018. To use Java SE 6 as the default SDK, select the box. If you do not check the box, the default Java SE 8 is used. Click Next.

Note: Continuing to use Java SE 6 is not recommended.

Note: To use a 64-bit Java SDK, you must select the 64-bit Java SDK in the feature panel.
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.
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.
Click Finish.
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:

Start Installation Manager.
In the menu, click File > Preferences.
Select Updates.
Select Search for Installation Manager updates.
Click Apply.
Click OK.

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