Network Deployment (Distributed operating systems), v8.0 > Migration and coexistence > Migrate Application profiling
Run previous versions of application profiles on v8
J2EE 1.3 applications created using WAS v5.x have an application profile configuration formatted for v5.x. Although, you can use applications with an application profile configuration from v5.x on WAS v7.0 and v8.0, change a setting. Also, there are several implications to using v5.x application profiles on v7.0 and v8.0.
The WAS 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.
Procedure
- Set the Application Profile service on your server to enable the Application Profiling 5.x Compatibility Mode as the default.
See the topic, Using the TaskNameManager interface for more information.
Mixed-version environment: This setting is necessary to support J2EE 1.3 applications with an application profile configuration from WAS v5.x. The 5.x compatibility mode has a fair amount of performance overhead on a v7.0 and v8.0 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.mixv
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. We must re-start the server.
This situation only happens when:
- the server started with the Application Profile service enabled and 5.x compatibility mode turned on, but no J2EE 1.3 applications were installed at server start up. Therefore, the server run time automatically ignores the 5.x compatibility in order to avoid performance costs associated with it.
- you try to install and start a J2EE 1.3 application with an application profile configured in v5.x, but the 5.x compatibility mode is turned off.
To avoid this situation, install at least one J2EE 1.3 application with an application profile v5.x configuration before starting the server, or restart the server after installing a J2EE 1.3 application with the application profile configured in v5.x.
- the server started with the Application Profile service enabled and 5.x compatibility mode turned on, but no J2EE 1.3 applications were installed at server start up. Therefore, the server run time automatically ignores the 5.x compatibility in order to avoid performance costs associated with it.
- Ideally, 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.
See the topic, Application profiling service settings, for more information. .
- Migrate any application we have configured with application profiling in v5.
Application profiles migration requires you to re-configure the applications in the assembly tool. See the topic, Application profiling, for more information.
- Rework the usage of the TaskNameManager API if it is used in the applications. The TaskNameManager API is not supported in container-managed transaction beans, and the setTaskName method must be called before beginning a new unit of work.
See the topic, Using the TaskName Manager interface, for more information. Application profiling
Use the TaskNameManager interface