WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Migrating internationalized applications

Why and when to perform this task

Applications that used the internationalization service in WebSphere Application Server versions 4 and 5 can use the service in later versions with no modification. The packaging and structure of the internationalization context API remain identical across releases. Most importantly, the semantics of the API remain as well.

In Version 4, the internationalization service did not provide internationalization deployment descriptor policy information to direct how the service manages internationalization context across the various application components. Rather, the service employed the implicit client-side internationalization (CSI) and server-side internationalization (SSI) policies, which dictated how the service managed context according to the type of Java 2 Platform, Enterprise Edition (J2EE) container hosting a component. For details, refer to the combined information center for WebSphere Application Server Version 4. Briefly, all server components in Version 4 are SSI, and all EJB client applications are CSI.

In versions 5 and later, the internationalization type setting of all server components is configured to Container by default. The internationalization service assigns the RunAsCallercontainer internationalization attribute by default to any container-managed (CMI) servlet or enterprise bean invocation lacking a container internationalization attribute. As a result, the invocations of server components that lack internationalization policy information in the deployment descriptor run under the policy, [CMI, RunAsCaller], which is semantically equivalent to the SSI internationalization policy of Version 4; EJB client applications run under the logical policy [AMI, RunAsServer], which is equivalent to the CSI policy of Version 4.

When migrating a Version 4 application to versions 5 or later, it is unnecessary to configure the internationalization deployment descriptor information during application assembly because all component invocations run under semantically equivalent internationalization context management policies.




Related concepts
Internationalization context: Management policies

Related tasks
Assembling internationalized applications

Related reference
Internationalization context API: Programming reference

Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/i18n/tasks/tin_migration.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)