What is new for installers

What is new for installers

+

Search Tips | Advanced Search

This topic highlights what is new or changed in v6.x for users who plan to install, upgrade, or migrate the product, including coexistence and interoperability concerns.
The biggest improvement to installation is that now install one copy of the core files (binary system files and such) 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 has many positive ramifications 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, the Web server plug-ins, and the clients so that install only what we need on a particular machine.
You also now have the ability to incrementally upgrade nodes in a cell. This new feature is discussed in New: Incremental cell upgrade.

Support for specific 64-bit platforms Now one 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 site

IPv6 support and considerations
This product version introduces selective support for Internet Protocol V6 (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:

Security evaluations for IBM products
IPv6 enablement at IBM - Overview
IPv6 enablement at IBM - Products

Redesigned launch pad to plan and start installation A redesigned launch pad on the product CD launches one of the installation programs. The launch pad also provides product solution roadmap diagrams to let you decide on the fly what to install where.
Note to zLinux users: Even though the launch pad links are present, the WAS Application Client is not supported on the zLinux platform. See also the TechNote documenting this limitation.

Install only what we need
New, more granular installation procedures simplify installation and improve installation reliability. Installation routines exist for the following components on the product disc.

WebSphere Application Server products
IBM HTTP Server
Web Server plug-ins
Application clients

Separate installation procedures for the IBM HTTP Server product and for the Web server plug-ins let you install only what we need on a particular machine.

Installing WAS products In v6.x, installing WAS 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 the new Profile creation wizard to create a deployment manager profile, an application server profile, or a custom profile.
For more information, see:

Using the Profile creation wizard
wasprofile command

Installing IBM HTTP Server The installation wizard for IBM HTTP Server is redesigned for v6.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 WAS clients A client application processes on a distributed client machine and a host WAS system. A client might provide the GUI, but process data on the host, for example. The Clients 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.
The installation root is now:

For AIX: /usr/IBM/WebSphere/AppServer
For Linux and UNIX: /opt/IBM/WebSphere/AppServer
For Windows: C:\Program Files\IBM\WebSphere\AppServer

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 WAS products. You do not have to install the core product files multiple times to create multiple standalone application servers. Instead, use the new Profile creation wizard to create an application server runtime environment that has its own administrative interface.
See Configuring the product after installation.

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.
The Applying service topic describes how to use 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 V5. Uninstalling an application server does not change the shared system files of the base WAS product.
In V5, some scenarios required uninstalling all traces of the product to produce a clean machine, which then allowed you to reinstall the product. In v6.x, that is a thing of the past. Application servers uninstall cleanly, almost effortlessly.
See Uninstalling the product.

Better indicators of installation status
Improved logging and status indicators let you easily determine the success or failure of an installation.

Silent installation requires license acceptance
You now must set the License Acceptance property to "true" in the silent installation response file. The property is silentInstallLicenseAcceptance.value. 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 Tasks

Using the launchpad to start the installation
Using the Profile creation wizard
Installing IBM HTTP Server
Installing Web server plug-ins
Installing Application Client for WebSphere Application Server

Related Information

wasprofile command
What is new in this release

Support for specific 64-bit platforms	Now one 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 site

IPv6 support and considerations	This product version introduces selective support for Internet Protocol V6 (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: Security evaluations for IBM products IPv6 enablement at IBM - Overview IPv6 enablement at IBM - Products

Redesigned launch pad to plan and start installation	A redesigned launch pad on the product CD launches one of the installation programs. The launch pad also provides product solution roadmap diagrams to let you decide on the fly what to install where. Note to zLinux users: Even though the launch pad links are present, the WAS Application Client is not supported on the zLinux platform. See also the TechNote documenting this limitation.

Install only what we need	New, more granular installation procedures simplify installation and improve installation reliability. Installation routines exist for the following components on the product disc. WebSphere Application Server products IBM HTTP Server Web Server plug-ins Application clients Separate installation procedures for the IBM HTTP Server product and for the Web server plug-ins let you install only what we need on a particular machine.

Installing WAS products	In v6.x, installing WAS 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 the new Profile creation wizard to create a deployment manager profile, an application server profile, or a custom profile. For more information, see: Using the Profile creation wizard wasprofile command

Installing IBM HTTP Server	The installation wizard for IBM HTTP Server is redesigned for v6.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 WAS clients	A client application processes on a distributed client machine and a host WAS system. A client might provide the GUI, but process data on the host, for example. The Clients 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. The installation root is now: For AIX: /usr/IBM/WebSphere/AppServer For Linux and UNIX: /opt/IBM/WebSphere/AppServer For Windows: C:\Program Files\IBM\WebSphere\AppServer 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 WAS products. You do not have to install the core product files multiple times to create multiple standalone application servers. Instead, use the new Profile creation wizard to create an application server runtime environment that has its own administrative interface. See Configuring the product after installation.

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. The Applying service topic describes how to use 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 V5. Uninstalling an application server does not change the shared system files of the base WAS product. In V5, some scenarios required uninstalling all traces of the product to produce a clean machine, which then allowed you to reinstall the product. In v6.x, that is a thing of the past. Application servers uninstall cleanly, almost effortlessly. See Uninstalling the product.

Better indicators of installation status	Improved logging and status indicators let you easily determine the success or failure of an installation.

Silent installation requires license acceptance	You now must set the License Acceptance property to "true" in the silent installation response file. The property is silentInstallLicenseAcceptance.value. 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.