Migrate V5 Application Profiles to V6

 

Overview

The WAS V6 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.

In order to support Java 2 platform, Enterprise Edition (J2EE) 1.3 applications with an application profile configuration from WebSphere Application Server V5.x , the Application Profile service on a V6 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 V6 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.

After the server starts without loading the 5.x compatibility mode support, if a J2EE 1.3 application with an application profile V5.x configuration installs on the server and attempts to start, the following message is displayed, and the server must be restarted

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.

This situation only happens when:

  1. the server started with the Application Profile service enabled and 5.x compatibility mode turned on

  2. you try to install and start a J2EE 1.3 application with an application profile configured in V5.x.

To avoid this situation, install at least one J2EE 1.3 application with an application profile V5.x configuration before starting the server.

Ideally, you would upgrade your J2EE 1.3 applications to use the V6 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 V5. Application profiles migration only requires you to re-configure your applications in the V6 Application Server Toolkit (AST). See Application profiling: Overview and Automatic configuration of application profiling for more information.


 

See Also


Application profiling: Overview
Automatic configuration of application profiling

 

Related Tasks


Using the TaskNameManager interface