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 > Application Servers > servername > Container Services> Application Profiling Service.
Configuration tab
- Enable service at server startup
Specifies whether the server attempts to start the application profiling service.
Default Selected Range
- Selected
- When the application server starts, it attempts to start the application profiling service automatically.
- Cleared
- The application profiling service is not enabled when an application server starts. Applications configured with application profiling cannot be started on servers that do not enable the application profiling service.
- 5.x Compatibility Mode
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 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.
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 WAS v6. 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
- Selected
- J2EE 1.3 applications that are dependent on the behavior of application profiling service for V5.x can run with the same behavior in Version 6.0.
- Cleared
- Tasks are established only when a new global unit of work begins.