Use this page to enable or disable the application profiling service.
Applications that are configured to use the application profiling service do not start successfully unless the application profiling service is enabled.
To view this administrative console page, click Servers > Application Servers > server_name > Container Services> Application Profiling Service.
Configuration tab
Specifies whether the server attempts to start the application profiling service.
Default | Selected |
Range |
|
When selected, 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.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 and J2EE 1.4 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.0. When cleared, J2EE 1.3 applications that use application profiling execute with the same constraints as J2EE 1.4 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 |
|
Related tasks
Managing application profiles