Installable enterprise module versions
The contents of a Java EE module affect whether we can install the module on a deployment target. A deployment target is a server or a cluster with at least one member on a WebSphere Application Server product.
Installable application modules
Select only appropriate deployment targets for a module. We must install an application, enterprise bean (EJB) module, SIP archive (SAR), web module, or client module on a v9.x target under any of the following conditions:
- The module supports a Java EE 7 technology added in 9.x.
- The module calls a 9.x runtime API.
- The module uses a 9.x product feature.
For example, because support for using Java EE default bindings was added in v9.0, install a module that uses Java EE default bindings only to a v9.x target.
If a module supports Java EE 6, then we can install the module on a v9.x or 8.5.x deployment target. Modules that call an 8.x API or use an 8.x feature can be installed on a 9.x or 8.x deployment target. If a module supports J2EE 1.4, then we can install the module on a v9.x, 8.x, or 7.x deployment target. Modules that call a 7.x API or use a 7.x feature can be installed on a 9.x, 8.x, or 7.x deployment target. Modules that require 7.x feature pack functionality can be installed on a 9.x or 8.x deployment target or on a 7.x deployment target that has been enabled with that feature pack.
Select options such as Precompile JavaServer Pagesfiles, Deploy web services or Deploy enterprise beans during application installation indicates that the application uses features of the current product version. Do not select these options if the targets of the applications are on older version nodes. Use the tools available in the older version, such as JspBatchCompiler, wsgen, or ejbdeploy, to update the application with generated code before deploying the application.
We must package container-managed persistence (CMP) or bean-managed persistence (BMP) entity beans in an EJB 2.1 or earlier module. We cannot install an EJB 3.x module containing CMP or BMP entity beans. Installation fails when a CMP or BMP entity bean is packaged in an EJB 3.x module. We can install EJB 2.1 or earlier modules on a 9.x, 8.x, or 7.x deployment target.
Installable RAR files
We can install a stand-alone resource adapter (connector) module, or RAR file, developed for a v7.x product to a 9.x, 8.x, or 7.x deployment target. We must install a module that calls an 8.x API on a 9.x or 8.x deployment target. We must install a module that calls a 9.x API on a 9.x deployment target.
Deployment targets
The following table lists the compatible deployment target versions for various modules. "9.x, 8.x, or 7.x" for Deployment target versions indicates that we can deploy the module to a WAS v9, 8, or 7 server or cluster.
Module type Module Java support Module calls 7.x, 8.x, or 9.x runtime APIs or uses 7.x, 8.x or 9.x features? Client versions that can install module Deployment target versions Application, EJB, or web J2EE 1.3 No 9.x, 8.x, or 7.x 9.x, 8.x, or 7.x Application, EJB, or web J2EE 1.3 Yes 9.x, 8.x, or 7.x for 7.x APIs or features 9.x or 8.x for 8.x APIs or features
9.x, 8.x, or 7.x Application, EJB, SAR, or web J2EE 1.4 Yes or No 9.x, 8.x, or 7.x 9.x, 8.x, or 7.x Application, EJB, SAR, or web Java EE 5 Yes or No 9.x, 8.x, or 7.x 9.x, 8.x, or 7.x Application, EJB, SAR, or web Java EE 6 Yes or No 9.x. or 8.x 9.x or 8.x Application, EJB, SAR, or web Java EE 7 Yes or No 9.x 9.x or 8.5.x for web modules
9.x 9.x or 8.5.x for web modules
Client Any Java EE version Yes or No 9.x or 8.x 9.x or 8.x Resource adapter JCA 1.0 No 9.x, 8.x, or 7.x 9.x, 8.x, or 7.x Resource adapter JCA 1.0 Yes 9.x, 8.x, or 7.x 9.x, 8.x, or 7.x Resource adapter JCA 1.5 Yes or No 9.x, 8.x, or 7.x 9.x, 8.x, or 7.x Resource adapter JCA 1.6 Yes or No 9.x or 8.x 9.x or 8.x Resource adapter JCA 1.7 Yes or No 9.x 9.x
Related:
Enterprise beans Relational resource adapters and JCA Web modules Install enterprise application files Update enterprise application files