Stabilized features

Stabilized features

If we are migrating the configuration from an earlier release of WAS, you should be aware of the various features that have been stabilized in this release.
If a feature is listed here as stabilized, IBM does not currently plan to deprecate or remove this capability in a subsequent release of the product; but future investment will be focused on the alternative function listed under Strategic Alternative. You do not need to change any of the existing applications and scripts that use a stabilized function; but you should consider using the strategic alternative for new applications.

Features stabilized in v8.5.5

Category Stabilized Function Strategic Alternative
Proxy components Use of the on-demand router (ODR) for HTTP and Session Initiation Protocol(SIP) The features of the ODR for HTTP are being implemented in the WebSphere Web server plug-in for Apache and IBM HTTP Server (IHS). All new intelligent management features will be implemented in the Web server plug-in rather than in the ODR.
The strategic alternative to the ODR for SIP is the SIP proxy server.
Use of the WebSphere Proxy for HTTP only
The WebSphere Proxy is not being stabilized for SIP.
The features of the WebSphere Proxy are being implemented in the WebSphere Web server plug-in for Apache and IBM HTTP Server (IHS). All new features will be implemented in the Web server plug-in rather than in the WebSphere Proxy.
System administration Intelligent Management support for the following assisted lifecycle middleware server types:

Apache Tomcat

BEA WebLogic

JBoss

External WebSphere application server (application servers that run outside the Intelligent Management cell)

Use wsadmin scripting to manage these middleware server resources.

Features stabilized in v8.5

Category Stabilized Function Strategic Alternative
Application programming model and container support Use of the Common Base Event application-programming interface (API) for problem determination

Classes or Interfaces:

All classes and interfaces from org.eclipse.hyades.logging.* packages

Methods:

Use of CommonBaseEvent or CommonBaseEventLogRecord as a message parm in the following WsJDK14Logger methods:

public void trace(Object message)

public void trace(Object message, Throwable t)

public void debug(Object message)

public void debug(Object message, Throwable t)

public void info(Object message)

public void info(Object message, Throwable t)

public void warn(Object message)

public void warn(Object message, Throwable t)

public void error(Object message)

public void error(Object message, Throwable t)

public void fatal(Object message)

public void fatal(Object message, Throwable t)

Other:

Use of the eventfactory Logger.properties logger extension

CBE-XML-1.0.1 output format for showlog

CBE-1.0.1 output format for HPEL logviewer

Use of the custom property name="com.ibm.ws.logging.zOS.errorLog.format" and value "CBE-XML-1.0.1"

Use of the showlog command on z/OS

None

Features stabilized in Version 8.0

8.0. This table describes the features that are stabilized
Category Stabilized Function Strategic Alternative
Application programming model and container support ActiveX to EJB Bridge Do not use Active X to access EJB.
WebSphere Application Servers V4 Data sources and ConnectionManager Use the WASs Data sources (non-V4) and ConnectionManager.
Use of CommonBaseEventLogRecord for logging Use standard java.util.logging API for logging; and when needed, use High Performance Extensible Logging (HPEL) log and trace facility's LogViewer command to convert log and trace messages into Common Base Event XML.
System administration WebSphere Application Server Reliability, Availability, and Serviceability (RAS) basic logging formatsSystem.out, System.err, trace.log, and activity.log Use the High Performance Extensible Logging (HPEL) log and trace facility to improve logging performance as well as to improve analysis and merging of logs.

Features stabilized in Version 7.0

7.0. This table describes the features that are stabilized
Category Stabilized Function Strategic Alternative
Application programming model and container support EJB entity beans: Container-Managed Persistence (CMP) 1.x and 2.x, and Bean-Managed Persistence (BMP) Use the Java Persistence API (JPA) for new database and other persistence-related operations.
JAX-RPC
The Java Community Process (JCP) is limiting the focus for enhancements to the JAX-RPC runtime for building web services; therefore, WebSphere Application Server will follow suit and limit enhancements.
JAX-WS will become the strategic runtime on which any new enhancements will be focused. The focus to ensure interoperability for the subset of capabilities that map to the JAX-RPC and JAX-WS intersection will be maintained; but all new enhancements related to updating to support new standards will be only in the JAX-WS runtime.
System administration Application server administrative (wsadmin) scripting support for the Jacl language Jython syntax for any new wsadmin scripting.
J2EE resources Support for configuring and using message-driven beans (MDBs) through JMS listener ports Perform the following actions to use JMS activation specifications instead of listener ports:

Create a JMS activation specification to replace the listener port.

Modify the configuration of the application's Message Driven Bean listener bindings to use the activation specification instead of the listener port.

Because an JMS activation specification can be defined at a wider scope than a listener-port definition (which is restricted to server scope), you might be able to replace multiple listener-port definitions with a single activation specification.

Update any administrative scripts that define or administer listener ports to define or administer JMS activation specifications instead.

Update any administrative scripts that use the stop or start operations of the ListenerPort MBean to use the pause and resume operations on the Message Endpoint MBean instead.

Features stabilized in Version 6.1

Category Stabilized Function Strategic Alternative
Edge components Edge component Caching Proxy function Use the Edge component Load Balancer with Media Access Control (MAC) forwarding in conjunction with one of the following:

WebSphere Application Server Network Deployment proxy server

IBM HTTP Server plug-in in WebSphere Application Server Network Deployment

For more information, read Proxy server setup and Set up caching in the proxy server.
Edge component Load Balancer function that is associated with the following capabilities:

Content-based routing (CBR) component

Site Selector component

Cisco CSS Controller component

Nortel Alteon Controller component

Generic routing encapsulation (GRE)

Network address translation (NAT) forwarding method

CBR forwarding method

Remote administration

Rules-based load balancing

Wide-area load balancing

Mutual high availability

Simple Network Management Protocol (SNMP) subagent support

User Datagram Protocol (UDP) support

Use the Edge component Load Balancer with Media Access Control (MAC) forwarding in conjunction with one of the following:

WebSphere Application Server Network Deployment proxy server

IBM HTTP Server plug-in in WebSphere Application Server Network Deployment

For more information, read Proxy server setup.

Deprecated, stabilized, superseded, and removed features
Deprecated features
(v8550) Superseded features
Removed features

Category	Stabilized Function	Strategic Alternative
Application programming model and container support	ActiveX to EJB Bridge	Do not use Active X to access EJB.
WebSphere Application Servers V4 Data sources and ConnectionManager	Use the WASs Data sources (non-V4) and ConnectionManager.
Use of CommonBaseEventLogRecord for logging	Use standard java.util.logging API for logging; and when needed, use High Performance Extensible Logging (HPEL) log and trace facility's LogViewer command to convert log and trace messages into Common Base Event XML.
System administration	WebSphere Application Server Reliability, Availability, and Serviceability (RAS) basic logging formatsSystem.out, System.err, trace.log, and activity.log	Use the High Performance Extensible Logging (HPEL) log and trace facility to improve logging performance as well as to improve analysis and merging of logs.

Category	Stabilized Function	Strategic Alternative
Application programming model and container support	EJB entity beans: Container-Managed Persistence (CMP) 1.x and 2.x, and Bean-Managed Persistence (BMP)	Use the Java Persistence API (JPA) for new database and other persistence-related operations.
JAX-RPC The Java Community Process (JCP) is limiting the focus for enhancements to the JAX-RPC runtime for building web services; therefore, WebSphere Application Server will follow suit and limit enhancements.	JAX-WS will become the strategic runtime on which any new enhancements will be focused. The focus to ensure interoperability for the subset of capabilities that map to the JAX-RPC and JAX-WS intersection will be maintained; but all new enhancements related to updating to support new standards will be only in the JAX-WS runtime.
System administration	Application server administrative (wsadmin) scripting support for the Jacl language	Jython syntax for any new wsadmin scripting.
J2EE resources	Support for configuring and using message-driven beans (MDBs) through JMS listener ports	Perform the following actions to use JMS activation specifications instead of listener ports: Create a JMS activation specification to replace the listener port. Modify the configuration of the application's Message Driven Bean listener bindings to use the activation specification instead of the listener port. Because an JMS activation specification can be defined at a wider scope than a listener-port definition (which is restricted to server scope), you might be able to replace multiple listener-port definitions with a single activation specification. Update any administrative scripts that define or administer listener ports to define or administer JMS activation specifications instead. Update any administrative scripts that use the stop or start operations of the ListenerPort MBean to use the pause and resume operations on the Message Endpoint MBean instead.