Installation is an easier, more consistent, and functionally rich experience across platforms, installable components, and types of installations.
| New in V6.1! indicates new features or changes implemented at the V6.1 level. Unmarked items are V6.0 improvements that apply also to V6.1, which should interest anyone migrating to V6.1 from V5.x. |
Now you can install the product more than once on your system to a location of your choice. Previous versions of the product installed the product to a fixed location and did not allow multiple installations of the product.
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 installation and iSeries 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 easily determine the success or failure of an installation. |
| 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. 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 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. welc_See Installing WebSphere Application Server from your iSeries server. |
| Launchpad for remote installation |
New in V6.1! A launchpad now is available when installing remotely onto an iSeries server from a Windows workstation. The launchpad does not run locally on an iSeries server. |
| Multiple installations are possible on the same iSeries server |
New in V6.1! You can install more than one copy of the product on an iSeries server. Previously, you could install only one copy because the installation location was fixed. This version allows more than one copy and supports user-specified installation locations. |
| 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 partition. For your convenience, the Web server plug-ins also are still included with the Application Server product. If you are running your application server and Web server on the same iSeries server, you do not need to install the Web server plug-ins. |
| 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. Support is expanded to i5/OS, although only in command line mode. |
| Changed product installation root |
Additional directory structure changes are introduced as described in What is new for administrators. Multiple installations are supported now. The installer enables you to specify the installation location and the user data location when installing. |
| Consider profiles during product installation |
You can install the product multiple times on a single system by specifying a different installation and user data destination. The deployment manager provides centralized management of its group of application servers, referred to as a cell. You can add, or federate, an application server into the deployment manager cell, or remove a federated application server to restore it as a stand-alone application server. Several profile types are available. Optionally create a profile during installation to have a working environment. Available profiles include:
For more information, see:
|
| 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. |
| 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. 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. |
| Robust product migration support | New in V6.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:
See Migrating and coexisting. |
| 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 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. |
| 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 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 V6.1! You can use the configureOS400WebServerDefinition script and the manageprofiles script to configure multiple IBM HTTP Server for iSeries or Domino Web Server for iSeries instances for use with WebSphere 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 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 application server 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. |