WAS 6.1 New Features and Functions Updated
------------------------------------------
•Multiple installations of any WAS 6.1 edition are now allowed. Just specify a unique installation directory and default profile location.
•The products require Java* Developer Kit (JDK) 5.0 to install and run.
•By default, the ND installer creates a deployment manager profile and a federated node profile, which are part of the deployment manager cell.
•Administrative security is enabled by default when you install. You only need to specify the user name and password to use administrative security when installing, and the default profile is created with administrative security enabled.
•Portlet programming model.
•Installation factory to create customized installation packages (CIPs) from the installation image for a version or release of a WebSphere software product with applicable maintenance packages.
•High-availability (HA), scalability and Web services improvements.
•Ability to run your application server using either of the two supported i5/OS JDK 5 JVMs.
•Ability to install with CDs or DVDs.
•6.1 has a new way of configuring SSL
•6.1 is 64 bit enabled for better performance
•6.1 has a partitioned "profile" architecture that gives more flexibility for backups and updates
•6.1 come with better Admin Console - 6.1 now features a standalone thin admin client that can be used to administer application servers remotely.
•The IBM HTTP Server can also now be managed from the admin console.
•6.1 includes WebSphere Identity Manager (WIM)
•6.1 introduced SIP support (Session Initiation Protocol) - This is a key technology for IP Telephony like VOIP, IPTV, Internet chat etc.
•6.1 has small footprint of Portlet container
•It has future support for EJB 3.0 (Enterprise Java Beans)
•RAD 7 works with 6.1 not lower than RAD7
•For WAS 6.1, the TPV is running under the deployment manager, so it is recommended to get a more powerful server due to the PMI and GUI.
•In 6.1, it is recommended to code your own java client to get the PMI reading or install ITCAM.
•There is no problem found with 6.0 and 6.1 co-existing in the same cell, the same Node or machine.
•The JSR 168 portlet-programming model is supported - meaning portlets can be accessed like servlets via a URL without a full portal server. It is JSR 168 compliant.
•Integration (Service) between WebSphere MQ for z/OS and the default-messaging provider in WebSphere Application Server has been enhanced in Version 6.1, enabling you to add a queue manager or queue sharing group as a member of a service integration bus.
•The IBM Support Assistant is now bundled with WebSphere Application Server V6.1 for more effective and faster self-help and problem reporting. (PMR) submission
•Java Server Faces (JSF) support has been enhanced for you to easily build web applications
•Edge Components like Dynamic Cache Support, Cache identification and management capabilities has been enhanced.
•6.1 supports IPv6 at the node level; both IPv4 and IPv6 nodes can be federated into the same cluster. A node can also be configured in "dual mode" to support both protocols.
•The Packaging structure is supplied with only platform specific images
•In 6.1 - WebSphere Application Server can now be installed by a non-root user -In 6.0 IHS require root
•Application Server Toolkit (AST) in V6.1 reaches a key milestone because it includes a J2EE perspective and a Web perspective, Eclipse 3.1, and Version 1.0 of the Eclipse Web Tools Platform (WTP).
• In 6.1 AST is a complete J2EE development environment, thus you can use it to construct, debug, and deploy new applications directly to WebSphere Application Server V6.1.
•Web Services has been enhanced for better performance - e.g SAAJ changes, SOAP/JMS, WS-I BSP(Basic Security Profile 1.0) and W3C WS-Addressing.
