Stabilized features

If you are migrating your configuration from an earlier release of WebSphere® Application Server, you should be aware of the various features that have been stabilized in this release.

Supported configurations Supported configurations:

This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.

sptcfg
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.
New feature New feature: This topic references one or more of the application server log files. Beginning in WebSphere Application Server Version 8.0 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 the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.newfeat

Features stabilized in Version 8.0

Table 1. Features stabilized in Version 8.0. This table describes the features that are stabilized in Version 8.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.
WebSphere Application Servers V4 Data sources and ConnectionManager Use the WebSphere Application Servers 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 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 Version 7.0

Table 2. Features stabilized in Version 7.0. This table describes the features that are stabilized in Version 7.0.
Category Stabilized Function Strategic Alternative
Application programming model and container support Enterprise JavaBeans (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.
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, WebSphere Application Server 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.



Related reference
Deprecated features
Removed features
Deprecated, stabilized, and removed features
Reference topic Reference topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 6:15:55 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-dist&topic=rmig_stabfeat
File name: rmig_stabfeat.html