Migrating internationalized applications

Why and when to perform this task

Applications that used the internationalization service in WebSphere Application Server Version 4 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 J2EE container hosting a component. For details, refer to the Target can be accessed only when this topic is linked to the World Wide Web   combined information center for WebSphere Application Server Version 4 . Briefly, all server components in Version 4 were SSI, and all EJB client applications were 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 default container internationalization attribute, RunAsCaller, to any container-managed (CMI) servlet or enterprise bean invocation lacking a container internationalization attribute. Hence, invocations of server components lacking 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 execute 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



Searchable topic ID:   tin_migration
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/i18n/tasks/tin_migration.html

Library | Support | Terms of Use | Feedback