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.
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.
sptcfgCategory | 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. |
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: |
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: For more information, read Setting up the proxy server and Setting up caching in the proxy server. |
Edge component Load Balancer function that is
associated with the following capabilities: |
Use the Edge component Load Balancer with
Media Access Control (MAC) forwarding in conjunction with one of the
following: For more information, read Setting up the proxy server. |