Application profiling service settings

WAS v8.5 > Reference > Sets
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.

Servers | Server types | WebSphere application servers | server_name | Container Settings | Container Services | Application profiling service

Enable service at server startup

Whether the server attempts to start the application profiling service.

Information Value
Default Cleared
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, 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 v7.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 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 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

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 v7.0 and later.

Cleared

Tasks are established only when a new global unit of work begins.

Related

Manage application profiles

+
Search Tips | Advanced Search

Information	Value
Default	Cleared
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.

Information	Value
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 v7.0 and later. Cleared Tasks are established only when a new global unit of work begins.