+

Search Tips   |   Advanced Search

 

What is new for installers

 

Simplified setup and prerequisites Redesigned product features simplify operating system setup and reduce prerequisites.
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 determine the success or failure of an installation.
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 V6.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.
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.7 and above.

Security enabled by default; installation requires a user ID New in V6.1! Security now is enabled by default at installation time.

For a silent or graphical installation to succeed, either provide a user ID and password or disable security.

Perform non-root installations New in V6.1! Non-root installations are supported by all WAS 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.

[Windows] Non-root support includes non-administrator group installations on supported Windows operating systems.

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 stand alone appservers. Instead, use the Profile Management tool GUI or the manageprofiles command to create an appserver run-time environment that has its own administrative interface.
Install only what we need New, more granular installation procedures simplify installation and improve installation reliability. Installation routines exist for the following components.

  • WAS products
  • IBM HTTP Server
  • Web Server plug-ins
  • Application clients
  • Update Installer

Separate installation procedures let you install only what we need on a particular machine.

Installation factory enhancements New in V6.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:

  • Choose Eclipse-based GUI or CLI

  • Create a “custom refresh,” which is an ISMP-based installation package at any given level of maintenance, such as 6.0.2.1 plus interim fixes

  • Prune unwanted features from the custom installation package

  • Use the custom install package to do a full scratch installation as well as update an existing installation (slip install)

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 code could require recompilation in the 64-bit environment if they do not start.
IPv6 support and considerations

WAS version introduces selective support for 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 appservers for increased flexibility. And with proxy server support for IPv6 clients and upstream server connections, you get added network reach and flexibility.

Changed product installation root

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 ND product edition.

Additional directory structure changes are introduced as described in What is new for administrators.

 

Introducing "profiles"

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 appserver 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.

Installing the product 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 to create a deployment manager profile, an appserver profile, or a custom profile.

Optionally create a profile during installation to have a working environment.

Create a profile after installation at any time using the Profile Management tool GUI or the manageprofiles command line interface. Available profiles include:

  • Cell, which includes a deployment manager and a federated appserver

  • Deployment manager, which provides centralized management of appservers

  • Application server, which can stand alone or run as part of the deployment manager cell

  • Custom, which must be federated and then customized through the deployment manager

For more information, see:

Profile enhancements

New in V6.1! Now you can create a cell (deployment manager and a federated node) in a single pass during the installation, or in a single use of the Profile Management tool. The tool also offers typical and advanced paths. The typical path expedites your creation of a profile by requesting only mandatory parameters, such as the profile type and core security settings. You have additional options during profile creation, such as whether to deploy the samples.

 

Silent and command line installations

Simpler command line installation

New in V6.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

Set the License Acceptance property to "true" in the silent installation response file.

 

Migration, upgrade, and change management

Tivoli License Compliance Manager New in V6.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.
Query product version information

You can query product version information.

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.
Product migration support New in V6.1! To protect your investment defining and tuning the 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:

  • GUI based migration on the same machine using the migration wizard

  • Command based migration on the same machine using the migration scripts

  • Command based migration across different machines using the migration scripts

  • Command based migration for OS update using the migration scripts

  • Command based application migration for client resources

Incremental cell upgrade You can incrementally upgrade nodes in a cell.
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 appservers do not change the system files.
Easier removal and reinstallation

Removal and reinstallation of appserver environments is simplified and faster. Application server environments are much easier to install and much easier to uninstall than in previous version. Uninstalling an appserver 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.

 

Web serving capability

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 appserver.
When you install IBM HTTP Server, its plug-in is installed New in V6.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 V6.1! The separate plug-ins installer installs the Web server plug-ins on a machine on which WAS is not installed, without incurring the overhead of running the WAS installation.
Configure the Web server more easily

New in V6.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.

 

Installable components in the integrated platform

MQ Series integrated JMS removed from product installation WAS no longer uses MQ Series to support the embedded JMS function contained in the appserver. 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 V5.0 or V5.1, you can continue to use any JMS servers on nodes which have not yet migrated to V6.1.

Installing the client The application client installation is no longer a feature under the appserver install. A separate application client installation program is delivered on its own disc.
More usability in selecting application clients to install New in V6.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 (AST)

New in V6.1! In V6, Application Server Toolkit (AST) used the Eclipse Update Manager to retrieve and apply maintenance. In V6.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 AST, 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 AST itself.

See also




Sub-topics

IPv6 support

 

Related information

Use the launchpad to start the installation
Create profiles through the graphical user interface
manageprofiles command
Install IBM HTTP Server
Install Web server plug-ins
Install Application Client for WAS
What is new in this release