Deprecated, stabilized, and removed features of WebSphere Application Server traditional
If you are migrating from an earlier release of WebSphere® Application Server traditional, you should be aware of the various features that have been deprecated, stabilized, and removed.
- Deprecated features
-
WebSphere Application Server uses the
V.R.M.F
naming scheme, where- V = version
- R = release
- M = modification
- F = fix pack
If a feature is listed in Deprecated features of WebSphere Application Server traditional as deprecated, IBM® might remove this capability in a subsequent release of the product. Future investment will be focused on the strategic function listed under Recommended Migration Actions. Typically, a feature is not deprecated unless an equivalent alternative is provided. A feature is not removed until at least two full years from the release in which that feature is deprecated. In rare cases, it might become necessary to remove features sooner; such cases are indicated clearly and explicitly in the descriptions of these removed features in Removed features of WebSphere Application Server traditional.
For a list of deprecated features, see Deprecated features of WebSphere Application Server traditional.
- Stabilized features
-
If a feature is listed 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 in Stabilized features of WebSphere Application Server traditional. 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.
For a list of stabilized features, see Stabilized features of WebSphere Application Server traditional.
- Removed features
-
For a list of removed features, see Removed features of WebSphere Application Server traditional.