When selected, Java 2 Platform, Enterprise Edition (J2EE) 1.3 applications
that use application profiling execute exactly as they did in the 5.x releases
of WebSphere Application Server.
For a Version 6.x and Version 7.0 client to interact with applications
run under the Application Profiling 5.x Compatibility Mode, you must set the appprofileCompatibility system
property to true in the client process. You can do this by specifying
the -CCDappprofileCompatibility=true option when invoking the launchClient command.
Operation in this mode can lead to unexpected deadlocks during database
access. Also, tasks do not propagate on remote invocations between J2EE 1.3,
J2EE 1.4 and Java Platform, Enterprise Edition (Java EE) applications, possibly
resulting in the use of unexpected access intent policies. This mode also
results in performance degradation if applications configured with application
profiling are installed on the server.
Support for J2EE 1.3 applications operating with 5.x Compatibility Mode
= true is deprecated as of WebSphere Application Server Version
6.x and later. When cleared, J2EE 1.3 applications that use application profiling
execute with the same constraints as Java EE 1.4 and Java EE applications.
In this mode, tasks are established only when a new unit of work begins. This
means the complete unit of work executes under at most one task.
Default |
Selected |
Range |
- Selected
- J2EE 1.3 applications that are dependent on the behavior of application
profiling service for Version 5.x can run with the same behavior in Version
6.0 and Version 7.0.
- Cleared
- Tasks are established only when a new global unit of work begins.
|