This version includes many new and changed items. Use this article to plan for installing, updating, or migrating the product.
The biggest improvement to
installation is that now you can install one copy of the core files (binary
system files and such) on a machine or partition, then use profiles to
define multiple application server run-time environments -- each with its
own administrative interfaces -- that share the core files. The use of profiles
provides many enhancements for preparing, installing, maintaining, and removing
installations, including a decreased footprint.
Another big change is the introduction of separate installation routines for the application server product, the Web server plug-ins, the IBM HTTP Server, and the Application Client so that you can install only what you need on a particular machine.
Another big change is the removal of the MQ Series integrated JMS from the shipment and installation of WebSphere Application Server. You can use either a separate MQ Series license or the new service integration bus architecture for messaging services. If you set up the integrated JMS under Version 5.0 or Version 5.1, you can continue to use any JMS servers on nodes which have not yet migrated to Version 6 or .
You also now have the ability to incrementally upgrade nodes in a cell. This new feature is discussed in New: Incremental cell upgrade.
Platform support as described in the Supported Hardware and Software Web site. A quick
summary of new platform support is provided in the Support announcement.
![]() |
![]() The installver tool introduced in Version 6.0.2 now enables you to perform checksum calculations to verify installed file sets on all platforms. |
![]() |
![]() |
Query product version information | Version 6.0 continues the ability to query product version information, as described in versionInfo command. |
Support for specific 64-bit platforms | Now you can deploy into an expanded memory space, for consolidating
servers and handling applications with higher memory bandwidth requirements.
Applications developed on 32-bit platforms can be deployed onto 64-bit platforms
without special consideration during application development. The exception
is that applications using Java Native Interface (JNI) code could require
recompilation in the 64-bit environment if they do not start. Supported 64-bit operating systems and processors are formally documented on the Supported Hardware and Software Web site. |
IPv6 support and considerations | This product version introduces selective support for Internet Protocol Version 6 (IPv6). IPv6 is the next evolution in Internet Protocol beyond the IPv4 standard currently in use in most networks today. The key IPv6 enhancement is the expansion of the IP address space from 32 bits to 128 bits, enabling virtually unlimited IP addresses. This addressing capability, along with new functions enabling end-to-end security, improved mobility support, simplified address configuration and management, make IPv6 a critical component in the evolution of e-business and the next generation internet. For details about IPv6 support, see the support document Restrictions for IPv6-only and IPv4/IPv6 mixed-mode dual stack support and IP version considerations for cells. See also the following Web pages:
|
Redesigned launchpad to plan and start installation | A redesigned launch pad on the product disc launches one of the installation programs. See Using the launchpad to start the installation. The launchpad also provides product solution roadmap diagrams to let you decide on the fly what to install where and what to install. Note to zLinux users: Even though the launchpad links are present, the WebSphere Application Server Application Client is not supported on the zLinux platform. See also the TechNote documenting this limitation. |
Install only what you need | New, more granular installation procedures simplify installation
and improve installation reliability. Installation routines exist for the
following components on the product disc.
Separate installation procedures let you install only what you need on a particular machine. |
Installing WebSphere Application Server products | In Version 6.0.x, installing WebSphere Application Server Network Deployment is a two-step process. The first step is using the installation wizard to install a shared set of core product files. The second step is using Profile Creation wizard to create a deployment manager profile, an application server profile, or a custom profile. For more information, see:
|
![]() |
![]() The installation factory provides the ability to:
|
Installing IBM HTTP Server | The installation wizard for IBM HTTP Server is redesigned for Version 6.0.x. At the end of the Web server installation, launch the new Plug-ins installation wizard to configure the IBM HTTP Server and the application server. |
Installing WebSphere Application Client | A client application processes on a distributed client machine and a host WebSphere Application Server system. A client might provide the GUI, but process data on the host, for example. The Application Client Installation wizard installs environments for running client applications on the client machine. Some environments perform all necessary handshaking and protocol. Thin client environments require client applications to have their own protocols for such things as JNDI lookups. See Installing Application Client for WebSphere Application Server. |
The product installation root has changed | The installation root varies by operating system, as before, but now includes IBM in the path. The installation root is the same for all three product editions now -- there is no longer a separate installation root for the Network Deployment product edition. See Directory conventions for more information. Additional directory structure changes are introduced, as described in New: Improved installation and configuration, with profiles. |
Improved installation documentation | New installation documentation on the product disc helps you retrieve relevant information. For an overview of the installation section, see Overview and new features for installing an application serving environment. |
Simplified setup and prerequisites | Redesigned product features simplify operating system setup and reduce prerequisite requirements. For details, see Preparing the operating system for product installation and Hardware and software requirements. |
Smaller footprint | A redesigned installer simplifies the installation of the core product files for WebSphere Application Server products. You do not have to install the core product files multiple times to create multiple stand-alone application servers. Instead, use the new Profile Creation wizard GUI or the wasprofile command to create an application server run-time environment that has its own administrative interface. See Configuring the product after installation for more information. |
Simplified service | The installation program installs the system files (shared binary files), which you do not update until you install a service fix. Creation and configuration of application servers do not change the system files. See Installing maintenance packages for information about using the IBM Update Installer for WebSphere Software to install interim fixes, fix packs, and refresh packs. |
Easier removal and reinstallation | Removal and reinstallation of application server environments is simplified and faster. Application server environments are much easier to install and much easier to uninstall than in previous version. Uninstalling an application server profile does not change the shared system files of WebSphere Application Server Network Deployment. Profile directories retain the logs for reference. Delete them if no longer needed. See Uninstalling the product for more information. |
Better indicators of installation status | Improved logging and status indicators let you easily determine the success or failure of an installation. Improved installation verification tools help you verify that the installation succeeded, as described in Using the installation verification tools. |
Silent installation requires license acceptance | You now must set the License Acceptance property to "true" in the silent installation response file. See responsefile.nd.txt for more information. |
New migration wizard | A new migration wizard collects data for the migration command line tools. The wizard also monitors and reports migration status. Note that the installation program no longer performs the migration. See Using the Migration wizard for additional information. |
Related information
Using the launchpad to start the installation
Creating profiles through the graphical user interface
wasprofile command
Installing IBM HTTP Server
Installing Web server plug-ins
Installing Application Client for WebSphere Application Server
What is new in this release