Deprecated and removed features

This section summarizes deprecated features in WebSphere Application Server product offerings beginning with v6 and ending with Version 5.0. As they become available, links to additional information will be provided to help you migrate away from deprecated features.

 

IBM deprecated and removed features

See the following

topics to find more information on deprecated and removed features:

Deprecation list

The following tables summarize what is deprecated, by version and release. Each table represents on what version and release the deprecation took effect and what is being deprecated, such as features, APIs, scripting interfaces, tools, wizards, publicly exposed configuration data, naming identifiers, or constants. Where possible, the recommended migration action is provided.

This article consists of the following versions and releases:

Deprecated features in V6.0

Application programming model and container support features
Support for the following tsx tags in the JSP engine is deprecated:

  • repeat

  • dbconnect

  • dbquery

  • getProperty

  • userid

  • passwd

  • dbmodify

Recommended migration action:

Instead of using the tsx tags, you should use equivalent tags from the JavaServer Pages Standard Tag Library (JSTL). JSTL is supported in WebSphere Application Server V6.0, and the tag library is shipped with the product. Use the following table as a guideline for converting tsx tags to JSTL tags:

tsx tag JSTL tag
tsx:repeat c:forEach
tsx:dbconnect sql:setDataSource
tsx:dbquery sql:query
tsx:getProperty use standard EL syntax, for example, c:out value="${book.title}", 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
Application services features
The WebSphere JRAS Extensions API is deprecated in this release. No further enhancements are planned for JRAS support.

Recommended migration action:

Begin moving over to the java.util.logging package (JSR47), particularly for any new code you are writing.

The UDDI version 2 EJB interface to the UDDI Registry is deprecated.

Recommended migration action:

There is no replacement for the EJB interface. This interface is included in WAS V6.0 for compatibility with V5.x. Users do not need to take any specific actions, and can continue to use the version 2 EJB API, but should be aware that it does not include any UDDI functionality that is new to UDDI version 3, and that the interface may be removed in a future release of WebSphere Application Server.

The UDDI4J version 2 class library, uddi4jv2.jar, is deprecated.

Recommended migration action:

Start using the version 3 UDDI APIs. A client library is provided to simplify constructing and sending UDDI v3 requests from Java. This is the IBM UDDI v3 Client for Java, provided in uddiv3client.jar. The UDDI4J APIs may still be used, but you should be aware that they do not provide access to any of the new UDDI version 3 functionality, and that they may be removed in a future release of WebSphere Application Server.

All of the low-level UDDI Utility Tools (UUT) APIs, such as BusinessStub, ServiceStub, etc., are deprecated. These are all replaced by the high-level PromoterAPI interface.

Recommended migration action:

Start using the PromoterAPI in place of these low-level APIs, which will be removed in a future release of WebSphere Application Server. The PromoterAPI provides the same functionality at a higher level of abstraction.

The following methods in the J2EE Connector Architecture runtime are deprecated:

  • com.ibm.ws.management.descriptor.xml.ConnectionFactory.xml (getPoolContents and getAllPoolContents methods)

  • com.ibm.websphere.j2c.ConnectionManager interface

  • com.ibm.websphere.j2c.ConnectionEventListener interface

Also, container-managed authentication aliases on a J2C Connection Factory or Datasource are deprecated.

Recommended migration action:

For container-managed authentication aliases, specify the container-managed credentials via the application's resource binding information.

The ApplicationProfile property on the WorkManager panel in the administrative console is deprecated.

Recommended migration action:

None.

Two items from the DataSource panel in the administrative console are deprecated:

  • Container-Managed Authentication Alias

  • DefaultPrincipleMapping

Recommended migration action:

None.

All classes in the com.ibm.websphere.servlet.filter package are deprecated:

  • ChainedRequest

  • ChainedResponse

  • ChainerServlet

  • ServletChain

Recommended migration action:

Re-architect your legacy applications to use javax.servlet.filter classes rather than com.ibm.websphere.servlet.filter classes. Starting from the Servlet 2.3 specification, javax.servlet.filter classes give you the capability to intercept requests and examine responses. They also allow you to achieve chaining functionality, as well as embellishing and/or truncating responses.

MIME filtering is deprecated. MIME filters were first introduced in WAS V3.5 as a way for servlets to embellish, truncate, and/or modify the responses generated by other servlets, based on the MIME types of the output content.

Recommended migration action:

javax.servlet.filters, which were introduced in the Servlet 2.3 specification, allow users to plug in filters which can intercept requests to and responses from servlets. They also have the capability to modify content flowing in either direction.

javax.servlet.filters maintain all 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.

Container-managed persistence (CMP) entity beans configured with method level access intent may run into data access problems, like deadlock. Therefore, the method level access intent is deprecated.

Recommended migration action:

Re-configure CMP entity beans to use bean level access intent, or re-configure Application profiles with WebSphere Application Server Tool (AST).

All the methods and fields in com.ibm.websphere.product.product and com.ibm.websphere.product.buildInfo classes are deprecated. Hence, the following methods from com.ibm.websphere.product.WASProduct class (which involves com.ibm.websphere.product.product and com.ibm.websphere.product.buildInfo objects) are deprecated:

  • public product getProductByFilename(String basename)

  • public product getProductById(String id)

  • public boolean productPresent(String id)

  • public boolean addProduct(product aProduct)

  • public boolean removeProduct(product aProduct)

  • public Iterator getProducts()

  • public Iterator getProductNames()

  • public String loadVersionInfoAsXMLString(String filename)

  • public String getProductDirName()

  • public static String computeProductDirName()

Recommended migration action:

Use the following supported methods from com.ibm.websphere.product.WASDirectory:

  • public WASProductInfo getWASProductInfo(String id)

  • public boolean isThisProductInstalled(String id)

  • public WASProductInfo[] getWASProductInfoInstances()

  • public String getWasLocation()

Also, instead of getting product information (name, version, build level, build date) from the old WASProduct API (com.ibm.websphere.product.WASProduct), you should now use the following methods in the WASDirectory class to get that information:

  • com.ibm.webpshere.product.WASDirectory.getName(String)

  • com.ibm.webpshere.product.WASDirectory.getVersion(String)

  • com.ibm.webpshere.product.WASDirectory.getBuildLevel(String)

  • com.ibm.webpshere.product.WASDirectory.getBuildDate(String)

Data Access Beans, which are shipped with WAS in databeans.jar, are deprecated.

Recommended migration action:

Instead of using Data Access Beans, you should use Service Data Objects (SDO).

The reloadInterval and reloadingEnabled attributes of the IBM deployment descriptor extensions are deprecated, including both the WAR file extension (WEB-INF/ibm-web-ext.xmi) and the application extension (META-INF/ibm-application-ext.xmi).

Recommended migration action:

Instead of using deployment descriptor extensions, you should use the reload enable and interval options provided during application deployment. See Enterprise application settings for additional details.

The com.ibm.websphere.servlet.session.UserTransactionWrapper API is deprecated.

Recommended migration action:

There is no replacement for this API. The UserTransaction object can be placed directly into the HTTP session without using a wrapper.

Security features
SOAP-Security (XML digital signature) based on Apache SOAP implementation is deprecated.

Recommended migration action:

Instead of using SOAP-Security, you should migrate your application to JSR-109 implementation of Web service. Also, migrate (reconfigure your application) to use WSS (Web Service Security) 1.0 implementation.

WSS (Web Service Security) draft 13 specification-level support is deprecated in favor of the WSS 1.0 implementation.

Recommended migration action:

Applications should be migrated to the supported WSS 1.0 standard. The draft-level support does not provide interoperability with some third party vendors, as the message level has been changed between the draft and the WSS 1.0 implementation.

WSS 1.0 is only supported in J2EE 1.4 applications. Hence, we need to migrate applications to J2EE 1.4 first. The next step is to use AST/RAD tooling to reconfigure WSS for the migrated application. There is no automatic migration of WSS in this release of AST/RAD tooling for V6.0; the migration has to be done manually.

The following SPI has also been deprecated 

com.ibm.wsspi.wssecurity.config.KeyLocator
You need to migrate your implementation to the new SPI for WSS 1.0 support in V6.0 

com.ibm.wsspi.wssecurity.keyinfo.KeyLocator

Finally, the JAAS LoginModule implementation needs to be migrated to the new programming model for JAAS LoginModule in V6.0.

In future releases, IBM will no longer ship or support the SAS IIOP security protocol. It is suggested that you use the Common Secure Interoperability version 2 (CSIv2) protocols.

Recommended migration action:

Use the Common Secure Interoperability version 2 (CSIv2) protocols.

System administration features
Configuring resources under cell scope is deprecated.

Recommended migration action:

You should configure resources under cluster scope instead. In previous releases, you configured cell scope resources to allow the cluster members to share the resource configuration definition. In V6, cell scope resource configuration is discouraged because cell scope resources are visible to every node in the cell, even though not every node in the cell is able to support the resource.

The depl.extension.reg and installdir options for the install command in the AdminApp scripting object are deprecated.

Recommended migration action:

There is no replacement for the depl.extension.reg option. In V5.x, this option was a no-op. For the installdir option, use the installed.ear.destination option instead.

Performance features
The PMI Client API, which was introduced in V4.0 to programmatically gather performance data from WebSphere Application Server, is deprecated.

Recommended migration action:

The Java Management Extension (JMX) interface, which is part of the J2EE specification, is the recommended way to gather WAS performance data. PMI data can be gathered from the J2EE-managed object MBeans, or from the WebSphere PMI Perf MBean. While the J2EE MBeans provide performance data about a specific component, the Perf MBean acts as a gateway to the WAS PMI service, and provides access to the performance data for all the components.

Deprecated features in V5.1.1

Application programming model and container support features
The Web services gateway customization API is deprecated.

Recommended migration action:

No action is required at this time. However, use of Java API for XML-based Remote Procedure Call (JAX-RPC) handlers is recommended over Web services gateway-specific interfaces, such as filters, where possible. The Web services gateway API will be replaced in a future release. For more information, see JAX-RPC handlers and service integration bus mediations.

Application services features
The following JDBC drivers are deprecated:

  • MS SQL Server 2000 Driver for JDBC

  • SequeLink JDBC driver for MS SQL Server

Recommended migration action:

If you are using either of these JDBC drivers and still want to use MS SQL Server as their database, one can switch to the Connect JDBC driver. We can purchase the Connect JDBC driver from DataDirect Technologies, or use the Connect JDBC driver shipped with WebSphere Application Server, which is free for use with WebSphere Application Server.

Deprecated features in V5.1

Table 1.
Installation and migration tools
The Application Assembly Tool (AAT) used for developing J2EE applications is being replaced by the Assembly Tool (ATk) component of the Application Server Toolkit (ASTk).

Recommended migration action:

Instead of running the Application Assembly Tool, users will install and run the Assembly Toolkit component of the Application Server Toolkit. ASTk is based on the eclipse framework. Upon starting the ASTk, the J2EE function is found by opening the J2EE Perspective.

JDOM (a Java representation of an XML document which provides an API for efficient reading, manipulating and writing documentation). The currently packaged version of JDOM in WAS will not be packaged in future releases of WebSphere.

Recommended migration action:

Go to JDOM and get the latest copy of JDOM and bundle it inside your application.

Note: Customers running WebSphere Studio Application Developer Integration Edition Version 4.1 applications will need to migrate them to WebSphere Studio Application Developer Integration Edition V5.0.

In future releases, IBM intends to remove the C++ Object Request Broker (ORB), the C++ library for IDL valuetypes and the WAS C++ security client. IBM will no longer ship or support the Common Object Request Broker Architecture (CORBA) C++ Developer Kit. The CORBA technology is a bridge for migration to a Java 2 Platform Enterprise Edition (J2EE) and WAS environment.

In addition to the preceding information, the CORBA C++ client feature will be removed from the Application Clients installation image in future releases.

Recommended migration action:

It is recommended that customers migrate to the Object Request Broker (ORB) service for Java technology that ships with WebSphere Application Server. However, there is no equivalent J2EE functionality for the C++ security client or the C++ Valuetype library. Customers that require such functionality must provide or develop their own. For information on the ORB service for Java technology, see Manage Object Request Brokers.

The deprecation of the CORBA C++ Developer Kit does not affect support for CORBA interoperability with vendor software for CORBA services. View the following links for additional information about interoperability:

IBM Cloudscape 5.1.x.

Recommended migration action:

No action is required at this time.

Servers and clustering features
IBM HTTP Server (IHS) 1.3.x.

Recommended migration action:

If you are using IHS 1.3.x with modules:

  • that are shipped as part of IHS 1.3.x packages, you do not need to take any action to migrate those modules.

  • supplied by a third party (including other IBM products), we need to obtain IHS/Apache 2 versions of these modules from the third party.

  • that have been customized or are in-house, we need to port these modules to the new IHS/Apache 2 API.

Application programming model and container support features
Bean Scripting Framework (BSF). JSP execution and debugging functionality is being deprecated in WAS version 5.1.

Recommended migration action:

If using the Javascript, Tcl, and Python languages, the functionality will need to be re-architected. If using BSF scripting in your own custom applications, they will be unaffected. Custom scripts written for the WAS admin console will also be unaffected.

This functionality will continue to exist in WebSphere Application Server app server release 5.1, and succeeding releases, until v6.0. If debugging JSPs you may have to restart the app server during Javascript debugging sessions.

Data access programming interfaces in com.ibm.websphere.rsadapter.

Relational resource adapter interface:

(com.ibm.websphere.rsadapter)

Methods have been deprecated in these types: 

com.ibm.websphere.rsadapter.OracleDataStoreHelper
    public void doSpecialBLobWork(ResultSet rset, 
                InputStream[] data, String[] blobColumnNames)  
    public String assembleSqlString(String[] blobColumnNames, 
                  StringBuffer whereClause, String[] varValues, String tableName)

Recommended migration action:

These relational resource adapter deprecated methods do not impact the application.

Note: You will not need to implement these deprecated methods in their subclasses if you have the subclass of OracleDataStoreHelper class. Those deprecated methods will not be called by the WebSphere Application Server runtime.

Webcontainer API modifications:

Note: There are no declared deprecations. The only changes are caused because of a Java API that changed between 1.3 and 1.4.

The changed class is com.ibm.websphere.servlet.error.ServletErrorReport. The return signature for getStackTrace( ) is changed because java.lang.Throwable now defines the same method with a different return signature.

  • Old method signature
    public String getStackTrace();  
// returns a String representation of the
exception stack

  • New method signature (JDK 1.4, WAS 5.1)
    public StackTraceElement[] getStackTrace(); 
// returns an array of stack trace
elements

  • Replacement method (WebSphere Application Server 5.1) (a replacement method that carries on the old functionality has been provided) 

    public String getStackTraceAsString(); 
// returns a String representation
of the Exception Stack

Recommended migration action:

If you are using com.ibm.websphere.servlet.error.ServletErrorReport.getStackTrace( ) and expecting a return type of String, we need to change your application to use the replacement method.

Application services features
Data access binaries -- Common Connector Framework:

The following jar files will be deprecated in V5.1:

  • ccf.jar

  • ccf2.jar

  • recjava.jar

  • eablib.jar

Recommended migration action:

The J2EE Connector Architecture solution should be used instead of the Common Connector Framework.

For more information on the usage (tools and runtime) of the J2EE Connector Architecture see Data access from J2EE Connector Architecture applications.

Setting the XA partner log directory via the 'TRANLOG_ROOT' variable is deprecated in V5.1.

Recommended migration action:

The setting currently stored in the TRANLOG_ROOT variable (if any) will need to be added to the Transaction Service panel for any servers who wish to use the XA partner log. If the default location is to be used, then no action is required. The Transaction Service panel can be found on the Administrative Console by selecting Application Servers on the left, choosing the application server to be modified, and selecting Transaction Service on the panel that is displayed. The directory currently in TRANLOG_ROOT should be entered in the Logging Directory box on the panel.

Security features
Security programming interfaces:

  • The API is being deprecated for 

    com.ibm.websphere.security.auth.WSPrincipal.getCredential()

    Recommended migration action:

    Instead of getting the WSCredential from the principal, you should now use one of the following methods to get the Subject which contains the WSCredential:

  • The interface is being deprecated in 

    com.ibm.websphere.security.auth.WSSecurityContext

    Recommended migration action:

    Use JAAS for any authentication related functionality.

  • The exception is being deprecated in 

    com.ibm.websphere.security.auth.WSSecurityContextException

    Recommended migration action:

    Use JAAS for any authentication related functionality.

  • The class is being deprecated in 

    com.ibm.websphere.security.auth.WSSecurityContextResult

    Recommended migration action:

    Use JAAS for any authentication related functionality.

System administration features
The following class is deprecated 

com.ibm.websphere.rsadapter.DB2390DataStoreHelper

Recommended migration action:

If you currently use the DB2390DataStoreHelper class for the DB2 Legacy CLI-based provider when you are accessing data, you should now use the DB2DataStoreHelper class.

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

Deprecated features in V5.0.2

Table 2.
Application programming model and container support features
Apache SOAP channel in Web services gateway.

Recommended migration action:

Gateway services should be deployed to the SOAP HTTP channel instead of the Apache SOAP channel. The Endpoint ( URL) of the service will be different for this channel and therefore client programs that are talking to the gateway will need to use the new service Endpoint.

Apache SOAP, WEBSJAVA.SOAP:

  • soap.jar,

  • wssoap.jar

Recommended migration action:

See Migrating Apache SOAP Web services to Web Services for J2EE standards for more information.

Application services features
Data access programming interfaces in com.ibm.websphere.rsadapter.

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)

Recommended migration action:

These relational resource adapter deprecated methods do not impact the application.

Note: You will not need to implement these deprecated methods in their subclasses if you have the subclass of GenericDataStoreHelper. Those deprecated methods will not be called by the WAS runtime.

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

System administration features
The testConnection command in the AdminControl scripting object ($AdminControl TestConnection configId props) is deprecated. Running this command in WebSphere Application Server, Version 5.0.2 or later returns the following message: WASX7390E: Operation not supported - testConnection command with config id and properties arguments is not supported. Use testConnection command with config id argument only.

Recommended migration action:

As of WebSphere Application Server, Version 5.0.2 or later, the preferred way to test a data source connection is the testConnection command passing in the data source configuration ID as the only parameter.

The getPropertiesForDataSource command in the AdminControl scripting object ($AdminControl getPropertiesForDataSource configId) is deprecated. This command incorrectly assumes the availability of the configuration service when you run it in the connected mode. Running this command in WebSphere Application Server, V5.0.2 or later returns the following message: WASX7389E: Operation not supported - getPropertiesForDataSource command is not supported.

Recommended migration action:

There is no replacement for this command.

Deprecated features in V5.0.1

Table 3.
Application services features
Data access programming interfaces in com.ibm.websphere.rsadapter.

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);

Recommended migration action:

These relational resource adapter deprecated methods do not impact the application.

Note: You will not need to implement these deprecated methods in their subclasses if you have the subclass of com.ibm.websphere.rsadapter.GenericDataStoreHelper. Those deprecated methods will not be called by the WebSphere Application Server runtime.

Deprecated features in V5.0

Table 4.
Application services features
The following three methods from com.ibm.websphere.appprofile.accessintent.AccessIntent are deprecated 

public boolean getPessimisticUpdateHintWeakestLockAtLoad();


public boolean getPessimisticUpdateHintNoCollision();


public boolean getPessimisticUpdateHintExclusive();

This is a base api.

Recommended migration action:

Rather than using the three deprecated methods on the AccessIntent interface, developers should use the following method from the same interface: 

public int getPessimisticUpdateLockHint();

The possible return values are defined on the AccessIntent interface 

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 intPESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE = 4;
Web application programming interfaces -- Various Version 5 methods in com.ibm.websphere.ServletErrorReport
Performance features
Performance Monitoring Infrastructure -- Various Version 5 public methods in:

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

    Recommended migration action:

    There is no replacement for StatsUtil.

  • com.ibm.websphere.pmi.PmiJmxTest

    Recommended migration action:

    Use PmiClient.findConfig().

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

    Recommended migration action:

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

Removal list

The following tables summarize what is removed by version and release. Use these tables to identify which deprecated items are removed.

The following tables describe what is removed, such as features, APIs, scripting interfaces, tools, wizards, publicly exposed configuration data, naming identifiers, or constants. Where possible, the recommended replacement is identified.

Removed features in V6.0

Table 5.
Component Classes and interfaces
activity

  • com.ibm.ws.activity.ActivityConstants

  • com.ibm.ws.activity.ActivityService

  • com.ibm.ws.activity.ActivityServiceInitializer

  • com.ibm.ws.activity.ActivityTrace

  • com.ibm.ws.activity.GlobalIdImpl

  • com.ibm.ws.activity.HighlyAvailableServiceManager

  • com.ibm.ws.activity.HLSLiteDataInterface

  • com.ibm.ws.activity.HLSLiteExtended

  • com.ibm.ws.activity.HLSLiteInfo

  • com.ibm.ws.activity.j2ee_activity_specific_data

  • com.ibm.ws.activity.j2ee_activity_specific_dataHelper

  • com.ibm.ws.activity.ServiceMigration

  • com.ibm.ws.activity.VUTrace

  • com.ibm.ws.activity.WebSphereServiceManager

  • com.ibm.ws.activity.WebSphereUserActivity

  • com.ibm.ws.javax.activity.ActionErrorException

  • com.ibm.ws.javax.activity.ActionNotFoundException

  • com.ibm.ws.javax.activity.ActivityCoordinator

  • com.ibm.ws.javax.activity.ActivityInformation

  • com.ibm.ws.javax.activity.ActivityManager

  • com.ibm.ws.javax.activity.ActivityNotProcessedException

  • com.ibm.ws.javax.activity.ActivityPendingException

  • com.ibm.ws.javax.activity.ActivityToken

  • com.ibm.ws.javax.activity.CompletionStatus

  • com.ibm.ws.javax.activity.ContextPendingException

  • com.ibm.ws.javax.activity.CoordinationInformation

  • com.ibm.ws.javax.activity.GlobalId

  • com.ibm.ws.javax.activity.InvalidParentContextException

  • com.ibm.ws.javax.activity.InvalidStateException

  • com.ibm.ws.javax.activity.NoActivityException

  • com.ibm.ws.javax.activity.NoImplementException

  • com.ibm.ws.javax.activity.NotOriginatorException

  • com.ibm.ws.javax.activity.Outcome

  • com.ibm.ws.javax.activity.PersistentActivityCoordinator

  • com.ibm.ws.javax.activity.PropertyGroupContext

  • com.ibm.ws.javax.activity.PropertyGroupRegisteredException

  • com.ibm.ws.javax.activity.PropertyGroupUnknownException

  • com.ibm.ws.javax.activity.ServiceAlreadyRegisteredException

  • com.ibm.ws.javax.activity.ServiceInformation

  • com.ibm.ws.javax.activity.ServiceNotRegisteredException

  • com.ibm.ws.javax.activity.Signal

  • com.ibm.ws.javax.activity.SignalSetActiveException

  • com.ibm.ws.javax.activity.SignalSetInactiveException

  • com.ibm.ws.javax.activity.SignalSetUnknownException

  • com.ibm.ws.javax.activity.Status

  • com.ibm.ws.javax.activity.SystemException

  • com.ibm.ws.javax.activity.TimeoutRangeException

  • com.ibm.ws.javax.activity.UserActivity com.ibm.ws.javax.activity.coordination.Action

  • com.ibm.ws.javax.activity.coordination.RecoverableAction

  • com.ibm.ws.javax.activity.coordination.ServiceManager

  • com.ibm.ws.javax.activity.coordination.SignalSet

  • com.ibm.ws.javax.activity.coordination.SubordinateSignalSet

  • com.ibm.ws.javax.activity.propertygroup.PropertyGroup

  • com.ibm.ws.javax.activity.propertygroup.PropertyGroupManager

  • com.ibm.ws.javax.ejb.ActivityCompletedLocalException

  • com.ibm.ws.javax.ejb.ActivityRequiredLocalException

  • com.ibm.ws.javax.ejb.InvalidActivityLocalException

admin com.ibm.websphere.management.application.EarUtils
als com.ibm.websphere.als.BufferManager
anttasks

  • com.ibm.websphere.ant.tasks.endptEnabler.Property

  • com.ibm.websphere.ant.tasks.Java2WSDL.Mapping

  • com.ibm.websphere.ant.tasks.Messages

  • com.ibm.websphere.ant.tasks.WSDL2Java.Mapping

dynacache com.ibm.websphere.servlet.cache.CacheConfig
ras

  • com.ibm.ras.RASConsoleHandler

  • com.ibm.ras.RASEnhancedMessageFormatter

  • com.ibm.ras.RASEnhancedTraceFormatter

  • com.ibm.ras.RASErrorHandler com.ibm.ras.RASFileHandler

  • com.ibm.ras.RASFormatter com.ibm.ras.RASHandler

  • com.ibm.ras.RASMessageFormatter

  • com.ibm.ras.RASMultiFileHandler

  • com.ibm.ras.RASSerialFileHandler com.ibm.ras.RASSocketHandler

  • com.ibm.ras.RASTextAreaHandler

  • com.ibm.ras.RASTraceFormatter

  • com.ibm.websphere.ras.WsOrbRasManager

security

  • com.ibm.websphere.security.AuthorizationTable

  • com.ibm.websphere.security.FileRegistrySample

  • com.ibm.websphere.security.SecurityProviderException

  • com.ibm.websphere.security.WASPrincipal

  • com.ibm.websphere.security.auth.AuthDataFileEnc

userprofile

  • com.ibm.websphere.userprofile.UserProfile

  • com.ibm.websphere.userprofile.UserProfileCreateException

  • com.ibm.websphere.userprofile.UserProfileExtender

  • com.ibm.websphere.userprofile.UserProfileFinderException

  • com.ibm.websphere.userprofile.UserProfileManager

  • com.ibm.websphere.userprofile.UserProfileProperties

  • com.ibm.websphere.userprofile.UserProfileRemoveException

Scheduler API

  • com.ibm.websphere.scheduler.pmi.SchedulerPmiModule

  • com.ibm.websphere.scheduler.pmi.SchedulerPerf

Scheduler API Method:

  • com.ibm.websphere.scheduler.MessageTaskInfo.setJMSPriority()

ObjectPool APIs

  • com/ibm/websphere/objectpool/pmi/ObjectPoolPerf.java

  • com/ibm/websphere/objectpool/pmi/ObjectPoolPmiModule.java

Asynchronous Beans APIs

  • com/ibm/websphere/asynchbeans/pmi/AlarmManagerPerf.java

  • com/ibm/websphere/asynchbeans/pmi/AsynchBeanPerf.java

  • com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorManagerPerf.java

  • com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorPerf.java

  • com/ibm/websphere/asynchbeans/pmi/AlarmManagerPmiModule.java

  • com/ibm/websphere/asynchbeans/pmi/AsynchBeanPmiModule.java

  • com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorManagerPmiModule.java

  • com/ibm/websphere/asynchbeans/pmi/SubsystemMonitorPmiModule.java