Management Security Enhancements Administration of IBM HTTP Server from WebSphere Admin Console Support for (pre-OASIS) WS-Security 1.0 Support for Web Services Resource Framework and WS-BusinessActivity (WS-BA) Support for JSR160 JMX Remote Connections (From IBM Agents Only) Administrative Console Jython Command Assistance Enhanced scripting. This version started the deprecation process for the Jacl syntax. 64-bit servants and a new Apache-based IBM HTTP Server for z/OS Support for the EJB 3.0 technology and support for some webservices standards were provided by the EJB feature pack and the webservices feature packs, respectively. These function in these feature packs has been folded into the main product in version 7. Functions in the webservices feature pack include: Asynchronous programming model (Limited functional support) Multiple Payload structures StAX (Streaming API for XML) WS-RM (Limited functional support) Support for (OASIS specified) WS-Security 1.0. WS-Addressing (Limited functional support) JAX-B support Policy Set (Limited functional support) Secured thin client (Limited functional support) SOAP (protocol) Message Transmission Optimization Mechanism (MTOM) Supports CGI and CORBA Version 6.0 This version was released on December 31, 2004. It is a Java EE 1.4 compliant application server. Security enhancements include support for JACC 1.0 and (pre-OASIS) WS-Security 1.0. Support for Java Standard Edition 1.4 Many programming model extensions previously found in WebSphere Application Server V5.0 Enterprise Edition were moved out of enterprise and into Express and Base. These APIs included application profile, startup beans, the scheduler, and async beans. The JMS engine, now called "WebSphere Platform Messaging," was rewritten in 100% Java and its functionality greatly enhanced. (WebSphere MQ is still supported as the JMS provider and is interoperable with WebSphere Platform Messaging.) The clustering was rewritten to use the high availability manager. This manages all singletons in the WebSphere environment and can provide hot recovery for those singletons. WebSphere was modified so that a shared file system can be used to store transaction logs and this meant that any cluster member with that shared file system mounted can hot recover in-doubt XA transactions with no external HA software. The Deployment Manager's role was eliminated from all clustering runtime operations. It's only required for centralized JMX admin and config changes. Now supports running mixed version cells (V5 to V6) in production. WebSphere Application Server for z/OS Provides the same core functionality as Network Deployment, since it shares a common programming model, but still contains the platform advantages such as: z/OS Workload Manager for prioritized