Java 2 platform, Enterprise Edition (J2EE) 1.3 applications created using WebSphere Application Server Version 5.x have an application profile configuration formatted for Version 5.x. Although you can use applications with an application profile configuration from Version 5.x on WebSphere Application Server Version 6, you must change a setting. Also, there are several implications to using version 5.x application profiles on version 6.
Why and when to perform this task
The WebSphere Application Server 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.
Steps for this task
This setting is necessary to support Java 2 platform, Enterprise Edition (J2EE) 1.3 applications with an application profile configuration from WebSphere Application Server Version 5.x. 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.
Application profiles migration requires you to re-configure your applications in the Version 6 Application Server Toolkit (AST). See Overview of application profiling and Automatic configuration of application profiling for more information.
Related concepts
Overview of application profiling
Automatic configuration of application profiling
Related tasks
Using the TaskNameManager interface