What is new for installers

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.

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.

Improved ease of use

Simplified setup and prerequisites Redesigned product features simplify operating system setup and reduce prerequisites.

See Preparing the base operating system and Hardware and software requirements on z/OS.

Better indicators of installation status Improved logging and status indicators let you easily determine the success or failure of an installation.
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.

See Using the Profile Management Tool.

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.

Improved capabilities

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.

See What is new for security specialists.

Changed product installation root

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

The default product directory in Version 6.1 is /usr/lpp/zWebSphere/V6R1. The default product directory in Version 6.0 is /usr/lpp/zWebSphere/V6R0.

See Directory conventions.

Migration, upgrade, and change management

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.

Incremental cell upgrade

You can incrementally upgrade nodes in a cell.

See What is new for administrators.

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:
  • Creating z/OS log streams for the error log and transaction XA partner log
  • Created a scheduler database in DB2
The jobs include comments for customization, and replace the corresponding panels in the Customization Dialog.
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:
  • 9060 (non-SSL)
  • 9443 (SSL)
Ports 9080 and 9043 continue to be the default HTTP ports for ordinary applications in a standalone application server.
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.

See Managing application servers.

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.

See Configuring transport chains.

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.

Web serving capability

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

New in Version 6.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.

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

Installable components in the integrated platform

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

Application server clients and plug-in code no longer are shipped in the product hierarchical file system. Instead, they are provided among the installation discs. An additional HFS for client and plug-in code no longer is required.

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.



Related information
What is new in this release
Installing the product and additional software
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=welc_newinstaller
File name: welc_newinstaller.html