Stabilized features of WebSphere Application Server traditional
If you are migrating your configuration from an earlier release of WebSphere® Application Server traditional, you should be aware of the various features that have been stabilized in this release.
Features stabilized in Version 9
Category | Stabilized Function | Strategic Alternative |
---|---|---|
Java Persistence API | OpenJPA/WSJPA | EclipseLink JPA persistence provider |
Mediation flow in service integration | Service integration For more information, 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 Version 8.5.5
Category | Stabilized Function | Strategic Alternative |
---|---|---|
Application programming model and container support | Service Component Architecture (SCA) programming model | Update your applications to use different programming models. The
programming models that you use vary depending on how you previously incorporated SCA in your
application. If you used SCA to create modular applications, consider using OSGi instead. For more information, see Developing OSGi applications. If you used SCA for binding, consolidate the ways in which your 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 Implementing JAX-RS web applications. To minimize the duplication of binding level implementation, structure your application to use shared code. If you want to continue to use SCA as part of your long-term strategy, consider hosting your 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 WebSphere Application Server, 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 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. Read Intelligent Management for web servers overview 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 web servers overview for more information. |
|
System administration | Intelligent Management support for the following assisted lifecycle middleware
server types:
|
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 Version 8.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 |
None |
Features 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
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: |
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
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: 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. |