Application profiling service settings
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 > Server types > WebSphere application servers > server_name. Under Container Settings, expand Container Services and click Application profiling service.
Enable service at server startup
whether the server attempts to start the application profiling service.
| Information | Value |
|---|---|
| Default | Cleared |
| Range |
|
5.x compatibility mode
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 WAS.
For a Version 7.0 and later client to interact with applications that 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.
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 JEE 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 WAS v6.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.
| Information | Value |
|---|---|
| Default | Selected |
| Range |
|
Related tasks
Reference topic