WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results
             New or updated topic for this feature pack

Installable J2EE module versions

The contents of a module affect whether you 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 feature pack applications New or updated for this feature pack

You must install an application that requires feature pack functionality to a v6.1.x deployment target that has been enabled with that feature pack.

That is, you must install an application that uses the Feature Pack for Web Services to a server that has a profile which has been enabled with the feature pack.

[AIX HP-UX Linux Solaris Windows] Installing Feature Pack for Web Services on distributed operating systems explains how to install the Feature Pack for Web Services and enable a profile for the feature pack.

You cannot install your application that requires a feature pack to a v6.1.x server that does not support the feature pack. Nor can you install it to a v5.x or v6.0.x server.

If your application does not require a feature pack, you can install it to a server that has been enabled with a feature pack or to any other supported deployment target. See Installable application modules for information on other supported deployment targets.

Installable application modules

You can install an application, enterprise bean (EJB) module, Session Initiation Protocol (SIP) module (SAR), or Web module developed for a Version 5.x product on a 5.x or 6.x deployment target, provided the module:

If the module supports J2EE 1.4, then you must install the module on a 6.x deployment target. If the module calls a 6.1.x API or uses a 6.1.x feature, then you must install the module on a 6.1.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 or 6.1.x deployment target.

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

Similarly, you must deploy an application that uses J2EE 1.4 features such as Java Authorization Contract for Containers (JACC) provided by an application server on a 6.x deployment target.

Installable RAR files

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

Deployment targets

A 5.x deployment target is a server or a cluster with at least one member on a WebSphere Application Server Version 5 product.

A 6.x deployment target is a server or cluster with all members on a WebSphere Application Server Version 6 product.

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

Modules that call 6.1.x runtime APIs or use 6.1.x features must be installed on a 6.1.x deployment target. Modules that call 6.0.x runtime APIs or use 6.0.x features can be installed on any 6.x deployment target.

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

Modules that call 6.1.x runtime APIs must be installed on a 6.1.x deployment target. Modules that call 6.0.x runtime APIs can be installed on any 6.x deployment target.

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

Modules that call 6.1.x runtime APIs must be installed on a 6.1.x deployment target. Modules that call 6.0.x runtime APIs can be installed on any 6.x deployment target.




Related concepts
Enterprise beans
Resource adapters
Web modules
Related tasks
Installing J2EE application files
Updating J2EE applications
Concept topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/crun_app_moduleversion.html