Stabilized features

Network Deployment (Distributed operating systems), v8.0 > Reference > Developer best practices

Stabilized features

If you 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.

This topic is about configuration migration, such as migrating dmgrs and federated nodes in a network deployment environment. The Application Migration Toolkit for WAS provides support for migrating applications from previous versions of WAS to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit. 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 your existing applications and scripts that use a stabilized function; but you should consider using the strategic alternative for new applications.
With WAS v8 you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh. See the information about using HPEL to troubleshoot applications for more information on using HPEL.New feature:

Features stabilized in v8.0

Features stabilized in v8.0. This table describes the features that are stabilized in v8.0.

Category Stabilized Function Strategic Alternative
Application programming model and container support ActiveX to 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

Features stabilized in Version 7.0. This table describes the features that are 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) 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, WAS will follow suit and limit enhancements.
Java API for XML Web Services (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 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 v6.1

Features stabilized in v6.1. This table describes the features that are stabilized in v6.1

Category Stabilized Function Strategic Alternative
Edge component 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 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:

WAS ND proxy server

IBM HTTP Server plug-in in WAS ND

For more information, read Set up the proxy server.

Related

Deprecated features
Removed features
Deprecated, stabilized, and removed features

+
Search Tips | Advanced Search

Category	Stabilized Function	Strategic Alternative
Application programming model and container support	ActiveX to 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)	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, WAS will follow suit and limit enhancements.	Java API for XML Web Services (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 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.