Installation is an easier, more consistent, and functionally rich experience across platforms, installable components, and types of installations.
The biggest improvement to the installation process is that now you can install one copy of the core files (binary system files and processes) on a machine, then use profiles to define multiple application server runtime environments -- each with its own administrative interfaces -- that share the core files. This improvement provides enhancements for preparing, installing, maintaining, and removing installations, including a decreased disk image footprint.
Another big change is the introduction of separate installation routines for the Application Server product, the Web server, the Web server plug-ins, and the clients so that you can install only what you need on a particular machine.
Platform support is described on the Detailed system requirements page. A quick summary of new platform support is provided in the Support announcement.
Deprecated and removed features describes features that are being replaced or removed in this or future releases.
Simplified setup and prerequisites | Redesigned product features simplify
operating system setup and reduce prerequisites. See Preparing the operating system for product installation and Hardware and software requirements. |
Redesigned launchpad to plan and start installation | A redesigned launchpad on the product disc launches one of the installation programs. The launchpad also provides product solution roadmap diagrams to let you decide what to install, and where. |
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. See Using the installation verification tools. |
Verify installation across all installation packages | The installver tool introduced in Version 6.0.2 enables you to perform checksum calculations to verify installed file sets on all platforms. |
Improved installation documentation | New installation documentation helps
you retrieve relevant information. See Overview and new features for installing an application serving environment. |
Smaller footprint | A redesigned installer simplifies the installation of the core product files. You do not have to install the core product files multiple times to create multiple standalone application servers. Instead, use the Profile Creation wizard GUI or the wasprofile command to create an application server run-time environment that has its own administrative interface. |
Install only what you need | New, more granular installation procedures
simplify installation and improve installation reliability. Installation
routines exist for the following components. Separate installation procedures let you install only what you need on a particular machine. |
Create customized installation packages (CIP) | The installation factory provides
the ability to: See IBM Installation Factory for WebSphere Application Server. |
Support for specific 64-bit platforms | 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. IPv6 client workload can be distributed to back end WAS servers. The proxy server supports IPv6 clients and servers. The new IPv6 network support extends Load Balancer to IPv6 clients, enabling their workload to be distributed to backend WebSphere application servers for increased flexibility. And with proxy server support for IPv6 clients and upstream server connections, you get added network reach and flexibility. See the Edge Component Information Center. |
Changed product installation root | The installation root varies by operating system, as before, but now includes IBM in the path. Additional directory structure changes are introduced as described in What is new for administrators. |
Consider profiles during product installation | 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 runtime 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. Version 6.0.x installs the core product files and a standalone application server in a profile named default. Create a profile after installation at any time using the Profile Creation wizard GUI or the wasprofile command line interface. For more information, see:
|
Silent installation requires license acceptance | You must set the License Acceptance property to "true" in the silent installation response file. |
Query product version information | You can query product version information. See versionInfo command. |
Migration wizard | A migration wizard collects data for the migration command-line tools. It also monitors and reports migration status. The installation program no longer performs the migration. |
Incremental cell upgrade | |
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. |
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 the product. Profile directories retain the logs for reference. Delete them if no longer needed. |
Installing IBM HTTP Server | The installation wizard for IBM HTTP Server has been redesigned. 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. |
MQ Series integrated JMS removed from product installation | WebSphere Application Server no longer
uses MQ Series to support the embedded JMS function contained in the
application server. The MQ Series product is not included any more. You can use either a separate WebSphere MQ 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.0.x. |
Installing the client | The application client installation is no longer a feature under the application server install. A separate application client installation program is delivered on its own disc. See Installing Application Client for WebSphere Application Serverf. |