Installation is an easier, more consistent, and functionally rich experience across platforms, installable components, and types of installations.
New in Version 6.1! indicates new features or changes implemented at the Version 6.1 level. Unmarked items are Version 6.0 improvements that apply also to Version 6.1, which should interest anyone migrating to Version 6.1 from Version 5.x. |
Platform support is described on the Detailed system requirements page.
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. |
Separate installer for the Update Installer | New in Version 6.1! A separate installer is used to install the Update Installer. At the end of the installation, launch the Update Installer to apply maintenance. |
Improved installation documentation | New installation documentation helps
you retrieve relevant information. See Overview and new features for installing an application serving environment. |
Automatic UID/GID selection | The Customization Dialog and Profile Management Tool allow you the option of having RACF choose unused UID and GID values for user IDs and groups created during the customization process. This applies to 6.1.0.9 and above. |
Security enabled by default; installation requires a user ID | New in Version
6.1! Security now is enabled by default at installation time. For a silent or graphical installation to succeed, you must either provide a user ID and password or disable security. |
Perform non-root installations | New in Version 6.1! Non-root
installations are supported by all WebSphere Application Server installation
packages in both silent and interactive mode for full installation
and removal, incremental feature installations, and edition updates.
In particular, root access is not required to install and evaluate
IBM HTTP Server. The user who owns the currently installed files is
the only user who can perform subsequent installation and update operations
on that installation. Many installation operations are not permitted
unless the installer also owns the file sets.
|
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 Management tool GUI or the manageprofiles 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. |
Installation factory enhancements | New in Version 6.1! The installation
factory creates a customized, distributable installation image tailored
to your specific needs. Now, while in connected mode, you can create
the installation packages on one operating system and distribute them
to another system. For example, you can create a customized installation package (CIP) for Windows from your Linux system. Support is also expanded to 64-bit platforms. Linux for zSeries continues to be supported only in command-line mode. |
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.1 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 Management tool GUI or the manageprofiles command line interface. For more information, see:
|
Simpler command-line installation | New in Version 6.1! The standard ISMP option format (-W option=value and –P option=value) is being replaced with an -OPT option that takes “sub-options” whose names are simpler and more meaningful, and less subject to change from one release to another. The same options are used in the command-line invocation of the wizard and in the silent-installation parameters in the response files. |
Silent installation requires license acceptance | You must set the License Acceptance property to "true" in the silent installation response file. |
Tivoli License Compliance Manager | New in Version 6.1! This product
is enabled for management with IBM Tivoli License Compliance Manager.
Tivoli software meets today's business requirements for software license
management and asset tracking. For more information about Tivoli License Compliance Manager, see http://www.ibm.com/software/tivoli/products/license-mgr/. |
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. See Using the Migration wizard to migrate product configurations. |
Robust product migration support | New in Version 6.1! To protect
your investment defining and tuning your configuration, a number of
migration paths are supported among versions and editions. The overall
migration is easier and more seamless because many of the migration
tools can be integrated into your installation scripts. You can choose
from a variety of tools, including: |
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. Now you can leave profiles installed when uninstalling the product and its core product files. |
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. |
When you install IBM HTTP Server, its plug-in is installed | New in Version 6.1! The IBM HTTP Server installation now includes the Web server plug-in for IBM HTTP Server, eliminating an extra step. You can enter information in just one place when setting up the Web server environment. |
Separate installer for Web server plug-ins | New in Version 6.1! The separate plug-ins installer installs the Web server plug-ins on a machine on which WebSphere Application Server is not installed, without incurring the overhead of running the WebSphere Application Server installation. |
Configure the Web server more easily | New in Version 6.1! New convenience scripts have been added to the installation package, enabling you to configure another instance of the Web server post-installation. Version 6.0 required running the Plug-ins installer again in order to accomplish this. |
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.1. |
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. |
More usability in selecting application clients to install | New in Version 6.1! J2EE clients and pluggable clients are no longer exclusive features placed on the same feature panel. They are separate setup types that have separate feature panels. |
Improved update installer for Application Server Toolkit | New in Version 6.1! In Version 6, Application Server Toolkit used the Eclipse Update Manager to retrieve and apply maintenance. In Version 6.1, it uses the Rational Product Updater (RPU), which is built on top of the Update Manager. RPU is able to update the JRE that is bundled with the toolkit, whereas Update Manager knew only how to update Eclipse plug-ins. RPU runs as a separate process from the code it updates, whereas Update Manager runs within the toolkit itself. |