Stabilized features of WAS traditional

Stabilized features of WAS traditional

If we are migrating the configuration from an earlier release of WebSphere Application Server traditional, we 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. We do not need to change any of our existing applications and scripts that use a stabilized function; but we should consider using the strategic alternative for new applications.

Features stabilized in v9

Category Stabilized Function Strategic Alternative
Java Persistence API OpenJPA/WSJPA EclipseLink JPA persistence provider
Mediation flow in service integration Service integration
See Mediation handlers and mediation handler lists
IBM Integration Bus
Web applications Application extension registry None
JSON4J Consider using Java API for JSON Processing (JSON-P).
XML applications XSLT 2.0, XPath 2.0, XQuery 1.0 and the IBM XML APIs that support these standards. Consider using the Java API for XML Processing (JAXP) when your XML processing needs would be satisfied by capability available in XSLT 1.0 and/or XPath 1.0. See the API documentation for the javax.xml.transform and javax.xml.xpath packages in the Java SDK for more information.

Features stabilized in v8.5.5

Category Stabilized Function Strategic Alternative
Application programming model and container support Service Component Architecture (SCA) programming model Update the applications to use different programming models. The programming models that we use vary depending on how we previously incorporated SCA in the application.
If we used SCA to create modular applications, consider using OSGi instead. See Develop OSGi applications.

If we used SCA for binding, consolidate the ways in which the application is exposed to a few standards, such as Java API for RESTful Web Services (JAX-RS) or Java Message Service (JMS). For example, use JAX-RS for application bindings; for more information, see Implement JAX-RS web applications. To minimize the duplication of binding level implementation, structure the application to use shared code.

To continue to use SCA as part of our long-term strategy, consider hosting the applications on IBM Business Process Manager.

Java Platform, Enterprise Edition resources JDBCProvider configuration templates for all DataDirect JDBC drivers No strategic alternative is necessary. Although the DataDirect JDBC drivers will no longer be certified with WAS, their use will continue to be fully supported as detailed in the Other Configurations section of the IBM Support Statement.
Proxy components Use of the on-demand router (ODR) for HTTP and 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.

Read Intelligent Management for IHS web servers for more information.

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.
Read Intelligent Management for IHS web servers for more information.

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.
Messaging WS-Notification Use SOAP over Java Message Service (SOAP/JMS) for publish subscribe messaging model.
Web Services Quality of service (QoS) WS-Reliable Messaging Use SOAP over Java Message Service (SOAP/JMS) transport protocol for communicating request and response messages.

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 v8.0

Category Stabilized Function Strategic Alternative
Application programming model and container support ActiveX to Enterprise JavaBeans (EJB) Bridge Do not use Active X to access EJB.
WASs 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 WAS Reliability, Availability, and Serviceability (RAS) basic logging formats-System.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 v7.0

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)

Deprecated feature: This function was deprecated in v9.0.depfeat
Use the Java Persistence API (JPA) for new database and other persistence-related operations.
Java API for XML-based RPC (JAX-RPC)
The Java Community Process (JCP) is limiting the focus for enhancements to the JAX-RPC runtime for building web services; therefore, WAS will follow suit and limit enhancements.

Deprecated feature: This function was deprecated in v9.0.depfeat
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 Use 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 a JMS activation specification can be defined at a wider scope than a listener-port definition (which is restricted to server scope), we 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 Bean to use the pause and resume operations on the Message Endpoint MBean instead.

Features stabilized in v6.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:

WAS ND proxy server
IBM HTTP Server plug-in in WAS ND

For more information, read Set up the proxy server and Set up caching in the proxy server.

Edge component Load Balancer function 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:

WAS ND proxy server
IBM HTTP Server plug-in in WAS ND

For more information, read Set up the proxy server.

Deprecated, stabilized, and removed features of WAS traditional
Deprecated features of WAS traditional
Removed features of WAS traditional

Category	Stabilized Function	Strategic Alternative
Java Persistence API	OpenJPA/WSJPA	EclipseLink JPA persistence provider
Mediation flow in service integration	Service integration See Mediation handlers and mediation handler lists	IBM Integration Bus
Web applications	Application extension registry	None
Web applications	JSON4J	Consider using Java API for JSON Processing (JSON-P).
XML applications	XSLT 2.0, XPath 2.0, XQuery 1.0 and the IBM XML APIs that support these standards.	Consider using the Java API for XML Processing (JAXP) when your XML processing needs would be satisfied by capability available in XSLT 1.0 and/or XPath 1.0. See the API documentation for the javax.xml.transform and javax.xml.xpath packages in the Java SDK for more information.

Category	Stabilized Function	Strategic Alternative
Application programming model and container support	Service Component Architecture (SCA) programming model	Update the applications to use different programming models. The programming models that we use vary depending on how we previously incorporated SCA in the application. If we used SCA to create modular applications, consider using OSGi instead. See Develop OSGi applications. If we used SCA for binding, consolidate the ways in which the application is exposed to a few standards, such as Java API for RESTful Web Services (JAX-RS) or Java Message Service (JMS). For example, use JAX-RS for application bindings; for more information, see Implement JAX-RS web applications. To minimize the duplication of binding level implementation, structure the application to use shared code. To continue to use SCA as part of our long-term strategy, consider hosting the applications on IBM Business Process Manager.
Java Platform, Enterprise Edition resources	JDBCProvider configuration templates for all DataDirect JDBC drivers	No strategic alternative is necessary. Although the DataDirect JDBC drivers will no longer be certified with WAS, their use will continue to be fully supported as detailed in the Other Configurations section of the IBM Support Statement.
Proxy components	Use of the on-demand router (ODR) for HTTP and 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. Read Intelligent Management for IHS web servers for more information.
Proxy components	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. Read Intelligent Management for IHS web servers for more information.
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.
Messaging	WS-Notification	Use SOAP over Java Message Service (SOAP/JMS) for publish subscribe messaging model.
Web Services Quality of service (QoS)	WS-Reliable Messaging	Use SOAP over Java Message Service (SOAP/JMS) transport protocol for communicating request and response messages.

Category	Stabilized Function	Strategic Alternative
Application programming model and container support	ActiveX to Enterprise JavaBeans (EJB) Bridge	Do not use Active X to access EJB.
	WASs 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	WAS Reliability, Availability, and Serviceability (RAS) basic logging formats-System.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) Deprecated feature: This function was deprecated in v9.0.depfeat	Use the Java Persistence API (JPA) for new database and other persistence-related operations.
Application programming model and container support	Java API for XML-based RPC (JAX-RPC) The Java Community Process (JCP) is limiting the focus for enhancements to the JAX-RPC runtime for building web services; therefore, WAS will follow suit and limit enhancements. Deprecated feature: This function was deprecated in v9.0.depfeat	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	Use 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 a JMS activation specification can be defined at a wider scope than a listener-port definition (which is restricted to server scope), we 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 Bean to use the pause and resume operations on the Message Endpoint MBean instead.