Deprecated features

For programming models that use Java™ EE 5 and later, use the IBM WebSphere Application Server Developer Tools for Eclipse.

To modify the bindings and extensions deployment descriptors for Java EE programming models prior to Java EE 5, use the WebSphere administrative console when you install your application. For more information, see Installing enterprise application files with the console.

Migrate your Enterprise JavaBean (EJB) modules to EJB 3.0 or later. For EJB 3.0 and later modules use Just-In-Time (JIT) deployment to dynamically generate deployment code.

There are no replacements for the editors for the ibm-webservices-bnd.xml and Programming Model Extensions deployment descriptors.

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 Configuring 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.

• WebSphere Application Server Network Deployment proxy server
• IBM HTTP Server plug-in in WebSphere Application Server Network Deployment

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

In IBM HTTP Server, CRL support is enabled with the SSLCRLHostname and SSLCRLUserid directives. CRL support is also controlled by the CRLDistributionPoint extension in TLS certificates.

TLS specifications now favor OCSP, which is enabled with the SSLOCSPEnable and SSLOCSPResponderURL directives. In TLS certificates, OCSP support is controlled by the AuthorityInformationAccess extension.

For more information, see SSL certificate revocation list and Online Certificate Status Protocol.

If you use the proxy server separately from WebSphere Application Server, use IBM HTTP Server and the WebSphere Web Server Plug-in with Intelligent Management or on demand router.

For more information about intermediary services, see Selecting a front end for your WebSphere Application Server topology.

When you migrate the graphics service, you can use the open source Apache Batik project to convert images.

• Optimizer
• WebDAV extension
• Map Conversion
• Dojo Diagrammer

Read Servlet security methods.

Read Migrating from WebSphere Virtual Enterprise.

• Sybase Adaptive Server Enterprise (ASE) 12.5.X
• Sybase jConnect 5.5

• Sybase Adaptive Server Enterprise (ASE) 15.X
• Sybase jConnect 6.05 or jConnect 7.0

For information about how to migrate to the JSF 2.0 MyFaces implementation, see JavaServer Faces migration

• -component

  Do not use this argument. It now performs no action.

• -maintenancePackageID

  This argument now performs an action that is equivalent to -offeringID. Use -offeringID.

• -componentDetail

  Do not use this argument. It now performs no action.

• -components

  Do not use this argument. It now performs no action.

• -maintenancePackageDetail

  This argument now performs an action that is equivalent to -fixpackDetail plus -ifixDetail. Use -fixpackDetail and -ifixDetail.

• -maintenancePackages

  This argument now performs an action that is equivalent to -fixpacks plus -ifixes. Use -fixpacks and -ifixes.

• public WASComponent getInstalledComponentByName(String componentName)

  This method now returns a null object.

• public WASComponent[] getInstalledComponentList()

  This method now returns an empty list.

• public boolean isComponentInstalled(String componentName)

  This method now returns as false.

• public WASMaintenancePackage[] getHistoryMaintenancePackageList()

  This method is replaced by public IMEvent[] getHistoryEventList().

• public WASMaintenancePackage getInstalledMaintenancePackageByID(String mpID)

  This method is replaced by public IMOffering getInstalledOfferingByID(String productID).

• public WASMaintenancePackage[] getInstalledMaintenancePackageList()

  This method is replaced by public IMOffering[] getInstalledOfferingList().

• public boolean isMaintenancePackageInstalled(String ID)

  This method is replaced by public boolean isThisProductInstalled(String id).

• com.ibm.websphere.product.metadata.WASComponent

  Do not use this class. All public methods in this class now return either null objects or empty lists.

• com.ibm.websphere.product.metadata.WASComponentUpdate

  Do not use this class. All public methods in this class now return either null objects or empty lists.

• com.ibm.websphere.product.metadata.WASMaintenancePackage

  Do not use this class.

• com.ibm.websphere.product.WASProductException

  Do not use this class. Use the com.ibm.websphere.product.WASDirectoryException class.

• com.ibm.websphere.product.history.WASHistoryException

  Do not use this class. Use the com.ibm.websphere.product.WASDirectoryException class.

• com.ibm.websphere.product.WASProduct.

  Do not use this class. Use the com.ibm.websphere.product.WASDirectory class.

• com.ibm.websphere.product.history.WASHistory

  Do not use this class. Use the com.ibm.websphere.product.WASDirectory class.

• createTargetGroup
• deleteTargetGroup
• addMemberToTargetGroup
• deleteMemberFromTargetGroup
• queryTargetGroups
• getTargetGroupMembers
• getTargetGroupInfo
• modifyTargetGroupInfo

• cleanupTarget
• queryTargets
• getTargetProperties
• modifyTargetProperties
• getTargetKeys

• SystemOut.log file when your system is configured to use basic log and trace mode
• High Performance Extensible Logging (HPEL) LogViewer command when your system is configured to use HPEL log and trace mode

  Configure your servers to use HPEL log and trace mode and use the HPEL API if you need to be able to merge log file content from multiple servers. Use the HPEL log and trace mode and use the HPEL LogViewer command if you need to be able to render log content in Common Base Event XML format.

For more information, read JTA support.

For more information, read JTA support.

Instead of using getNativeConnection, use the Java Database Connectivity (JDBC) 4.0 wrapper pattern.

Instead of WSConnection client information, use JDBC 4.0 client-information APIs.

Instead of com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn), use the com.ibm.websphere.rsadapter.WSCallHelper.setConnectionError (Object conn, boolean logEvent) method. The new method provides a boolean parameter that allows you to control whether or not connection error events are logged to system out.

Instead of WSCallHelper.call, use standard Java reflections APIs.

If you are using the ORACLE_HELPER, switch to the Oracle 11g JDBC driver and use the ORACLE_11G_HELPER instead.

Rather than specifying session manager properties as system or web container custom properties, use session-manager custom properties.

• javax.xml.ws.wsaddressing.W3CEndpointReference
• com.ibm.websphere.wsaddressing.jaxws21.SubmissionEndpointReference
• com.ibm.websphere.wsaddressing.jaxws21.EndpointReferenceConverter

AdminTask.listSIBJMSQueues()

If you are using disablePK54589=true, you can replace it with isConnectionSharingBasedOnCurrentState=false.

The default in Version 7.0 is to create new servers to run in 64–bit addressing mode; however, servers that are migrate to Version 7.0 from an earlier release can still be configured to run in 31–bit mode.

For more information, read Switching between 64 and 31 bit modes.

For more information, read Core group transports.

• Use the -busSecurity flag instead of the -secure flag.
• Replace usages of the listInheritSenderForTopic, listInheritReceiverForTopic, and listInheritDefaultsForDestination commands with the isInheritSenderForTopic, isInheritReceiverForTopic, and isInheritDefaultsForDestinaton commands respectively.
• Remove any usage of the -interEngineAuthenticationAlias option on the createSIBus and modifySIBus commands.

For more information, read ServerManagement command group for the AdminTask object

• IDS rather than SECUREWAY, IDS4, IDS51, or IDS6
• DOMINO rather than DOMINO5, DOMINO6, or DOMINO65
• AD rather than AD2000 or AD2003

For more information, read SOAP over JMS protocol and SOAP over Java Message Service .

public final void
  setDatabaseDefaultIsolationLevel  
  (int helperDefaultLevel, 
  int cusDefinedWasDefaultIsoLevel) 

Replace all uses of the com.ibm.websphere.sib.mediation.messagecontext.SIMediationBean MessageContext interface with an equivalent interface. WebSphere Application Server does not provide an implementation of this interface.

The channel framework provides the TransportChannelService message bean, which is more flexible and has more methods than the current web container transport-related methods.

1. Ensure that any JMS Server messaging providers that are hosted on WebSphere Application Server Version 5.1 application servers are moved onto Version 6.0 or later application servers. This task is handled automatically when you migrate a Version 5.x server to Version 6.0 or later.
2. Change all JMS resource definitions to use the new Version 6 default messaging provider instead of the Version 5 default messaging provider.

Use the z/OS Migration Management Tool to generate migration definitions. For information on using the z/OS Migration Management Tool, read the Using the z/OS Migration Management Tool to create and manage migration definitions topic.

For new configurations, use the Derby datastore helpers and types instead of the Cloudscape datastore helpers.

For more information, read Data source minimum required settings, by vendor.

When this function is removed, however, all custom Object Request Broker (ORB) properties that you specified for it will be ignored. The custom ORB properties of interest are com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.*.

For more information, read Object Request Broker custom properties.

The deprecated mapping file supported specifying multiple transaction classes per row. This allowed the creation of an artificial round-robin work-dispatch effect. Although the XML file pointed to by wlm_classification_file does not support specifying multiple transaction classes per row, you can better achieve this same effect by using zWLM's round-robin option. Select this option by specifying wlm_stateful_session_placement_on=1.

For information on using this property, read TCP transport channel custom properties

In a subsequent version of WebSphere Application Server for z/OS, a new configuration mechanism will be provided that will allow you to choose a different SSL server certificate to be used for the SSL handshake depending on the server IP address of the socket connection. This new administrative mechanism will replace the current file format of the file pointed to by the protocol_http_cert_mapping_file variable.

Read the Java Servlet 2.4 Specification, which is available for download at http://jcp.org/aboutJava/communityprocess/final/jsr154/, for information on how sendRedirect should behave.

Starting with the Java Servlet 2.3 specification, javax.servlet.filter classes give you the capability to intercept requests and examine responses. They also allow provide chaining functionality as well as functionality for embellishing or truncating responses.

Read Transactional high availability for information on configuring the high availability manager to perform transaction recovery.

For more information, read Lightweight Third Party Authentication.

For more information, read JVM Tool Interface (JVMTI).

For more information, read JVM Tool Interface (JVMTI).

For more information, read Converting log files to use IBM unique Message IDs.

• Logging facility

  Logging facility used for logging Java primitives and complex objects to named loggers; configurable with predefined filtering levels, Logging Agent and file sinks, and output formats through an API, Eclipse plug-in manifest, or Eclipse preference panel

• Logging agent

  XML-based messaging agent used in conjunction with the IBM Agent Controller to write log and trace XML records to a logging service remotely attachable through an API or Test and Performance Tools Platform (TPTP), formally Hyades, Eclipse workbench

• Problem determination artifacts and messages

  Original implementation of the Manageability (M12) Model Problem Determination Architecture Version 1.5 and Problem Determination Artifacts Common Data Model specification used for capturing and encoding log and trace data

• Distributed correlator service (DCS)

  Distributed correlator service that is used for instrumenting correlation identifiers for correlating log and trace data across one or more hosts

• Java client bindings

  Java client bindings used to communicate with the IBM Agent Controller to launch local and remote processes, attach to running processes, and monitor active agents in a secure client environment

• Logging facility

  Replacement: Java Logging APIs in Java Version 1.4.0+; Logging Agent support for the Java Logging APIs provided in TPTP and Common Logging (com.ibm.etools.common.logging/logging.jar)

• Logging agent

  Replacement: TPTP Logging Agent (org.eclipse.hyades.logging.core/hlcore.jar)

• Problem determination artifacts and messages

  Replacement: Common Base Event Version 1.0.1 specification and TPTP implementation (org.eclipse.hyades.logging.core/hlcbe101.jar)

• Distributed correlator service (DCS)

  Replacement: TPTP Correlation Service (org.eclipse.hyades.execution.correlation/hcorrelation.jar)

• Java client bindings

  Replacement: TPTP Java Client Bindings (org.eclipse.hyades.execution/hexl.jar)

tsx tag            JSTL tag

tsx:repeat         c:forEach
tsx:dbconnect      sql:setDataSource
tsx:dbquery        sql:query
tsx:getProperty    Use standard EL syntax; c:out
                   value="${book.title}" for example, 
                   where book is the current index in 
                   the result set
tsx:userid         Use the user attribute of the
                   setDataSource tag
tsx:passwd         Use the password attribute of
                   the setDataSource tag
tsx:dbmodify       sql:update

Use the equivalent function in the java.util.logging package (JSR47).

• getPoolContents and getAllPoolContents are replaced with showPoolContents and showAllPoolContents.
• ConnectionManager interface is replaced with J2EE Connector Architecture 1.5 LazyAssociatableConnectionManager interface.
• ConnectionEventListener interface is replaced with J2EE Connector Architecture 1.5 LazyEnlistableConnectionManager interface.

For container-managed authentication aliases, specify the container-managed credentials in the resource binding information for the application.

javax.servlet.filters maintain all of the functionality of MIME filters. javax.servlet.filters are standard APIs, and are supported by all compliant application servers.

Refer to the Servlet 2.3 specification or Servlet filtering for more information.

• public WASProductInfo getWASProductInfo(String id)
• public boolean isThisProductInstalled(String id)
• public WASProductInfo[] getWASProductInfoInstances()
• public String getWasLocation()

Read Enterprise application settings for additional details.

WSS 1.0 is only supported in J2EE 1.4 applications. Therefore, you need to migrate applications to J2EE 1.4 first. The next step is to use Application Server Toolkit or Rational Application Developer tooling to reconfigure WSS for the migrated application. There is no automatic migration of WSS in this release of Application Server Toolkit or Rational Application Developer tooling for Version 6.0; the migration has to be done manually.

The following SPI has also been deprecated:

Finally, the Java Authentication and Authorization Service (JAAS) LoginModule implementation needs to be migrated to the new programming model for JAAS LoginModule in Version 6.0.

Plan over time to replace your existing filters with a combination of JAX-RPC handlers and service integration bus mediations.

• Microsoft SQL Server 2000 Driver for JDBC
• SequeLink JDBC driver for Microsoft SQL Server

For information on the ORB service for Java technology, read Managing Object Request Brokers.

• are included as part of IHS Version 1.3.x packages, you do not need to take any action to migrate those modules.
• are supplied by a third party (including other IBM products), you need to obtain IHS/Apache 2 versions of these modules from the third party.
• have been customized or are inhouse, you need to port these modules to the new IHS/Apache 2 API.

This functionality will continue to exist in WebSphere Application Server Version 5.1 and succeeding releases until Version 6.0. If debugging JSP files, you might have to restart the application server during JavaScript debugging sessions.

public Object createTaskInfo(Class 
  taskInfoInterface) throws TaskInfoInvalid;

BeanTaskInfo ti = (BeanTaskInfo) 
  Scheduler.createTaskInfo(BeanTaskInfo.class);

For more information on the usage (tools and runtime) of the J2EE Connector Architecture read Accessing data using Java EE Connector Architecture connectors.

• The RunAs Subject is the Subject used for outbound requests.
• The Caller subject is the Subject that represents the authenticated caller for the current request.
• The methods to use to get the runAs and caller subjects are as follows:
    com.ibm.websphere.security.auth.WSSubject.getRunAsSubject()
  and
    com.ibm.websphere.security.auth.WSSubject.getCallerSubject()
  respectively.

For more information, read Lightweight Third Party Authentication.

If you currently use the DB2390DataStoreHelper class for the DB2 Universal JDBC provider when you are accessing data, you should now use the DB2UniversalDataStoreHelper class.

public int getJMSPriority();

Relational resource adapter interface (com.ibm.websphere.rsadapter)

Methods have been deprecated in these types:

com.ibm.websphere.rsadapter.DataStoreHelper
  public int processSQL(java.lang.String.sqlString, 
    int isolevel, boolean addForUpdate, 
    boolean addextendedForUpdateSyntax);
  public DataStoreAdatperException 
    mapException(DataStoreAdapterException e);

com.ibm.websphere.rsadapter.GenericDataStoreHelper
  public int processSQL(java.lang.String.sqlString, 
    int isolevel, boolean addForUpdate, 
    boolean addextendedForUpdateSyntax);
  public DataStoreAdatperException 
    mapException(DataStoreAdapterException e);

com.ibm.websphere.rsadapter.WSCallHelper
  public static DataStoreHelper 
    createDataStoreHelper(String dsClassName)

For com.ibm.websphere.rsadapter.WSCallHelper, use the getDataStoreHelper(datasource) method to get a DataStoreHelper object.

Relational resource adapter interface (com.ibm.websphere.rsadapter).

Methods have been deprecated in these types:

com.ibm.websphere.rsadapter.DataStoreHelper
  public int processSQL(java.lang.String sqlString,
    int isolevel);

com.ibm.websphere.rsadapter.GenericDataStoreHelper
  public int processSQL(java.lang.String sqlString,
    int isolevel);

com.ibm.websphere.rsadapter.DB2390DataStoreHelper
  public int processSQL(java.lang.String sqlString, 
    int isolevel);

public boolean getPessimisticUpdateHintWeakestLockAtLoad();

public boolean getPessimisticUpdateHintNoCollision();

public boolean getPessimisticUpdateHintExclusive();

This is a base API.

public int getPessimisticUpdateLockHint();

public final static int 
 PESSIMISTIC_UPDATE_LOCK_HINT_NOCOLLISION = 1;

public final static int 
 PESSIMISTIC_UPDATE_LOCK_HINT_WEAKEST_LOCK_AT_LOAD = 2;

public final static int 
 PESSIMISTIC_UPDATE_LOCK_HINT_NONE = 3;

public final static int
 PESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE = 4;

• com.ibm.websphere.pmi.stat.StatsUtil
• com.ibm.websphere.pmi.PmiJmxTest
• com.ibm.websphere.pmi.client.PmiClient

• com.ibm.websphere.pmi.stat.StatsUtil

  There is no replacement for StatsUtil.

• com.ibm.websphere.pmi.PmiJmxTest

  Use PmiClient.findConfig() instead.

• com.ibm.websphere.pmi.client.PmiClient

  The getNLSValue (String key) is replaced with getNLSValue (String key, String moduleID).