Why and when to perform this task
WebSphere Application Server Version 5.x enabled you to create Java 2 platform, Enterprise Edition (J2EE) 1.3 applications with application profile configurations formatted for Version 5.x. The implications of using applications with an application profile configuration from Version 5.x on WebSphere Application Server Version 6 are described below.
The Version 6 application profiling function works under the unit of work concept. This gives it a more predictable data access pattern based on the active unit of work, which could be either a transaction or an ActivitySession. See Task overview: Application profiling for more information.
In order to support Java 2 platform, Enterprise Edition (J2EE) 1.3 applications with an application profile configuration from WebSphere Application Server Version 5.x , the Application Profile service on a Version 6 server must enable the Application Profiling 5.x Compatibility Mode as the default. The 5.x compatibility mode has a fair amount of performance overhead on a Version 6 server. Because of this, if there is no J2EE 1.3 application with an application profile V5.x configuration installed, the server does not load the support for the 5.x compatibility mode during startup, even when the 5.x compatibility mode is turned on.
ACIN0031E: The J2EE 1.3 application <ApplicationName> is configured for application profiling and is installed and starting on a running server that enables Application Profiling 5.x Compatibility Mode. You must re-start the server.
Ideally, you would upgrade your J2EE 1.3 applications to use the Version 6 application profiling configuration and turn off the Application Profiling 5.x Compatibility Mode through the administrative console.
Therefore it is recommended that you migrate any application you might have configured with application profiling in Version 5. Application profiles migration requires you to re-configure your applications in the Version 6 Application Server Toolkit (AST). See Application profiling: Overview and Automatic configuration of application profiling for more information. You must also rework the usage of the TaskNameManager API if it is used in your applications. The TaskNameManager API is not supported in container managed transaction beans in Version 6, and the setTaskName() method must be called before beginning a new unit of work. See Using the TaskNameManager interface for more information.
Related concepts
Application profiling: Overview
Automatic configuration of application profiling
Related tasks
Using the TaskNameManager interface