Application profiling interoperability
The effect of 5.x Compatibility Mode
Application profiling supports forward compatibility. Application profiles created in previous versions of WAS (Enterprise Edition 5.0 or WebSphere Business Integration Server Foundation 5.1) can only run in WAS V6 if the Application Profiling 5.x Compatibility Mode attribute is turned on. If the 5.x Compatibility Mode attribute is off, V5 application profiles might display unexpected behavior. For information about the 5.x Compatibility Mode, see Application profiling service settings.
Similarly, application profiles that you create using WAS V6 are not compatible with V5 or earlier versions. Even applications configured with application profiles run on V6 servers with the Application Profiling 5.x Compatibility Mode attribute turned on cannot interact with applications configured with profiles run on V5 servers.
Note: If you select the 5.x Compatibility Mode attribute on the Application Profile Service’s console page, then tasks configured on J2EE 1.3 applications are not necessarily associated with units of work and can arbitrarily be applied and overridden. This is not a recommended mode of operation and can lead to unexpected deadlocks during database access. Tasks are not communicated on requests between applications that are running under the Application Profiling 5.x Compatibility Mode and applications that are not running under the compatibility mode.
For a v6 client to interact with applications run under the Application Profiling 5.x Compatibility Mode, set the appprofileCompatibility system property to true in the client process. We can do this by specifying the -CCDappprofileCompatibility=true option when invoking the launchClient command.
Considerations for a clustered environment
In a clustered environment with mixed WAS product versions and mixed platforms, applications configured with application profiles might exhibit unexpected behavior because previous versions of server members cannot support the application profiling of V6.
If a clustered environment contains both V5.x and 6.0 server members, and if any applications are configured with application profiles, the Application Profiling 5.x Compatibility Mode attribute must be turned on in V6 server members. Still, this cluster can only support V5 application profiling behavior. To support applications configured with V6 application profiles in a cluster environment, all server members in the cluster must be at the V6 level.
WebSphere Application Server Enterprise Edition V5.0.2
If you use WAS Enterprise Edition 5.0.2, apply WebSphere Application Server V5 service pack 7 or later service pack to enable Application Profiling interoperability.
Related Tasks
Using the TaskNameManager interface
See Also
Application profiling service settings