Installable enterprise module versions


 

+

Search Tips   |   Advanced Search

 

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 WAS product.

 

Installable application modules

Select only appropriate deployment targets for a module. You must install an application, EJB module, SIP module (SAR), or Web module on a V7.x target under any of the following conditions:

If a module supports J2EE 1.4, then install the module on a V6.x or 7.x deployment target. Modules that call a 6.1.x API or use a 6.1.x feature can be installed on a 6.1.x or 7.x deployment target. Modules that call a 6.0.x API or use a 6.0.x feature can be installed on a 6.0.x, 6.1.x or 7.x deployment target. Modules that require 6.1.x feature pack functionality can be installed on a 7.x deployment target or on a 6.1.x deployment target that has been enabled with that feature pack.

Select options such as Precompile JSPs, Use binary configuration, Deploy Web services or Deploy enterprise beans during application installation indicates that the application uses 6.1.x product features. We cannot deploy such applications on a 5.x or 6.0.x deployment target. You must deploy such applications on a 6.1.x or 7.x deployment target.

We can install an application or module developed for a V5.x product on a 5.x, 6.x or 7.x deployment target.

Avoid trouble: You must package CMP or BMP entity beans in an EJB 2.1 or earlier module. We cannot install an EJB 3.0 module that contains CMP or BMP entity beans. Installation fails when a CMP or BMP entity bean is packaged in an EJB 3.0 module. We can install EJB 2.1 or earlier modules on a 5.x, 6.x or 7.x deployment target.

 

Installable RAR files

We can install a standalone resource adapter (connector) module, or RAR file, developed for a V 5.x product to a 5.x, 6.x or 7.x deployment target, provided the module does not call any 6.x or 7.x runtime APIs. If the module calls a 6.x API, then install the module on a 6.x or 7.x deployment target. If the module calls a 7.x API, then install the module on a 7.x deployment target.

 

Deployment targets

A 5.x deployment target is a server or a cluster with at least one member on a WAS V 5 product.

A 6.x deployment target is a server or cluster with all members on a WAS V 6 product.

A 7.x deployment target is a server or cluster with all members on a WAS V 7 product.

Module type Module Java support Module calls 6.x or 7.x runtime APIs or uses 6.x or 7.x features? Client versions that can install module Deployment target versions
Application, EJB, Web, or client J2EE 1.3 No 5.x, 6.x or 7.x 5.x, 6.x or 7.x
Application, EJB, Web, or client J2EE 1.3 Yes 6.x for 6.x or 7.x APIs or features

7.x for 7.x APIs or features

6.x or 7.x

You must install modules that call 6.1.x runtime APIs or use 6.1.x features on a 6.1.x or 7.x deployment target. You can install modules that call 6.0.x runtime APIs or use 6.0.x features on any 6.x or 7.x deployment target.

Application, EJB, SAR, Web, or client J2EE 1.4 Yes or No 6.x or 7.x 6.x or 7.x
Application, EJB, SAR, Web, or client Java EE 5 Yes or No 7.x 7.x
Resource adapter JCA 1.0 No 5.x, 6.x or 7.x 5.x, 6.x or 7.x
Resource adapter JCA 1.0 Yes 6.x or 7.x 6.x or 7.x

You must install modules that call 6.1.x runtime APIs on a 6.1.x or 7.x deployment target. We can install modules that call 6.0.x runtime APIs on any 6.x or 7.x deployment target.

Resource adapter JCA 1.5 Yes or No 6.x or 7.x 6.x or 7.x

You must install modules that call 6.1.x runtime APIs on a 6.1.x or 7.x deployment target. We can install modules that call 6.0.x runtime APIs on any 6.x or 7.x deployment target.





Related concepts


Enterprise beans
Relational resource adapters and JCA
Web modules

 

Related tasks


Install enterprise application files
Updating enterprise application files