Installation is an easier, more consistent, and functionally rich experience across platforms, installable components, and types of installations.
The biggest improvement
to the installation process is that now you can install one copy of
the core files (binary system files and processes) 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 improvement provides enhancements for preparing,
installing, maintaining, and removing installations, including a decreased
disk image 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 you can install only what you need on a particular machine.
Platform support is described on the Detailed system requirements page. A quick summary of new platform support is provided in the Support announcement.
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.
|
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. |
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. |
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. |
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 Creation wizard GUI or the wasprofile 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.
|
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 |
You must create a profile to have a working environment.
Available
profiles include:
For more information, see:
|
Silent installation requires license acceptance | You must set the License Acceptance
property to "true" in the silent installation response file. See responsefile.nd.txt. |
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. |
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. Profile directories retain the logs for reference. Delete them if no longer needed. |
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. |
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.0.x. |
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. |
Included code for clients in the product HFS | Additional downloadable clients and plug-ins are now installed in the product HFS. |
Enlarged product HFS | Because of the addition of client code, the product HFS has grown significantly. If you have a 3390-3 DASD device, you will no longer be able to house the entire product HFS on a single DASD volume. The Program Directory contains instructions for creating a secondary product HFS to hold the downloadable clients and plug-ins. |
Installing the client |
|