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. |
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.
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 easily 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 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. |
New customization tool | New in Version 6.1! A workstation-based Profile Management tool is now available as an alternative to the host-based ISPF Customization Dialog. This tool uses the same worksheets and overall customization flow as the Customization Dialog and also provides new function, such as the ability to create a complete Network Deployment cell in one pass including an application server. |
New command line tool | New in Version 6.1.1! The z/OS Profile Management
Command Line tool is an alternative to the z/OS Profile Management
tool launched from the Application Server Toolkit. This tool would
be beneficial for users who want to use the z/OS Profile Management
tool, but do not have a Windows or Linux workstation available. See Configuring with the z/OS Profile Management Command Line tool. |
Improved Customization Dialog menus | The Customization Dialog main menus have been reorganized for clarity. They now show the configuration options more clearly and the product data set panel has been updated to simplify setup. |
Ability to create managed nodes directly | You now can directly configure managed nodes (with a node agent but no application servers) and add them to a Network Deployment cell. Create new application servers in the node using scripting or the administrative console. It is no longer necessary to create a standalone application server (formerly called a base application server) to build a Network Deployment cell. |
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. |
zFS file system option for performance gains | New in Version 6.1! Customization tools allow the customization file system to be created as either an HFS or zFS file system. The zFS file system has significant performance advantages. |
Independent product SDK | The Java Software Development Kit is now shipped, installed and serviced as part of WebSphere® Application Server. There is no longer a separate FMID for the SDK. This makes the WebSphere Application Server for z/OS product independent of any other SDK installed on the same z/OS systems. The shipped SDK resides in app_server_root/java. |
Security enabled by default; installation requires a user ID | New in Version
6.1! Security now is enabled by default at installation time.
|
Launchpad for remote installation | New in Version 6.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. |
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.
|
Multiple installations are possible on the same iSeries server | New in Version 6.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. |
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.
|
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.
|
Create customized installation packages (CIP) | The installation factory provides
the ability to:
|
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 |
Additional directory structure changes are introduced as described in What is new for administrators.
|
Consider profiles during product installation |
Available
profiles include:
For more information, see:
|
Profile enhancements | New in Version 6.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. |
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. See responsefile.nd.txt. |
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. |
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 | You can incrementally upgrade nodes in a cell. |
Removed use of static application environments | The Workload Management dynamic application environment SPE (APAR OW54622, included in z/OS Version 1.5 and above) is a prerequisite for this product running under z/OS Version 1.4. You no longer need to set up or update static application environments in WLM. |
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. |
z/OS Version 1.6 required | Note this change from Version 6.0 to Version 6.1. WebSphere Application Server requires a minimum z/OS level of Version 1 Release 6. Because Version 1 Release 6 always supports WLM application environments, the customization steps and documentation for static application environments have been removed. |
New sample jobs | Note this change from Version 6.0
to Version 6.1. New sample jobs are provided in the SBBOJCL product
data set for: |
LE and SSL data set requirements | Note this change from Version 6.0
to Version 6.1. The customization process assumes that the Language
Environment load module libraries (SCEERUN and SCEERUN2) and the System
SSL load module library (SGSKLOAD or SIEAKNKE) are in the system link
list. This reduces the amount of customer information that must be
provided during customization. If they are not in the link list on the target z/OS system, be sure to follow the customization instructions for adding them to JCL and scripts as appropriate. |
Administrative console port changes | Note this change from Version 6.0
to Version 6.1. The standalone application server now uses a separate
virtual host and HTTP transport chains for the administrative console.
As a result, the default ports for the standalone administrative
console are now the same as for the administrative console in a Network
Deployment cell: |
Java 1.5 SDK included | Note this change from Version 6.0 to Version 6.1. WebSphere Application Server includes IBM 31-bit SDK for z/OS, Java 2 Technology Edition, V5 (5655-N98) See IBM 31-bit SDK for z/OS, V5 - Prerequisites to installing the product for z/OS prerequisites that must be installed to support this level of Java. |
Changes to SBBOLPA | Note this change from Version 6.0 to Version 6.1. The modules that are loaded into common storage during node startup have been merged into a single load module and moved from SBBOLPA to SBBOLOAD. The only module remaining in SBBOLPA is the BBORTS61 CTRACE support module. The BBORTSS5 module, which has been replaced by the BBORTS61 module, is not needed. |
Availability of 64-bit support | Note this change from Version 6.0 to Version 6.1. A new load module library, SBBGLOAD, is shipped in this release; it contains 64-bit product code, which is not currently enabled. The new library must be APF authorized, and it is added to server procedure JCL and scripts during customization. Additional logic is added to the cataloged procedures generated during customization to support 64-bit mode, which is available in Version 6.1.0.4. |
HTTP transport chains replace HTTP transports | Note this change from Version 6.0 to Version 6.1. HTTP transport chains are used at initial customization, in place of the HTTP transports used by default in previous releases. |
Changes to certificate and key ring names | Note this change from Version 6.0 to Version 6.1. The SAF key ring default name and digital certificate names used during customization have been modified to provide better security isolation, and to reduce the number of browser challenges. See Secure Sockets Layer security for WebSphere Application Server for z/OS. |
New configuration file system owner | Note this change from Version 6.0 to Version 6.1. The WebSphere Application Server File System Owner user ID has been added in Websphere Application Server Version 6.1. In earlier versions of the product, the configuration file system was owned by the WebSphere Application Server Administrator user ID. |
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 |
|
Use the administrative console to define Web servers | New in Version 6.1! The standalone application server administrative console can be used to create Web server definitions. The customization job BBOWCFGW has been removed. The Web server definition function has been incorporated into the BBOWWPFA job. |
Flexibility in when to define Web servers | New in Version 6.1! Web servers on non-z/OS systems can be defined during customization (using the customization tools), or after customization (using the administrative clients). |
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. |
New application server address space | Each application server controller now uses a new address space, called the control region adjunct (CRA), to attach to service integration buses for messaging. |
Installing the client |
|
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. |