Creating Multi-Lingual and Multi-Locale Databases.ppt

Creating Multi-Lingual and Multi-Locale Databases International Unicode Conference 19 Presented by Addison Phillips Globalization Architect webMethods, Inc. Introduction Audience: Beginning Developers Presenter: Addison Phillips Globalization Architect webMethods, Inc. mailto:aphillips@ Presentation: Creating complex systems in a global environment requires more than internationalized code. Since most Enterprise system rely on relational databases, a global-ready system must also consider database design in order to be truly effective. Our Problem This presentation is based on the lessons learned in developing and deploying a B2B “conversation management” system (webMethods for Trading Networks) and “partnership management” software (webMethods PartnerConnect). The products we created share a central database that allow webMethods customers to manage their B2B trading partnerships. Terminology: A “trading partner” is a company that you want to do business with. An “initiative” is a specific opportunity to work together. Trading Networks Companies need to store information about transactions and business relationships world wide and in real time. We call this “Global Business Visibility” Partner Connect Goals Centrally served (one instance). Centrally managed (initiatives can be deployed anywhere). Localized (so partners can interact with initiatives in their own language). Cultural and market sensitivity (customized to fit different market conditions locally). Created and managed by the customer entirely through HTML interface. Profile and Conversation Management Enter the Database Serve both global and local initiatives from a single instance. Store data in multiple writing systems (scripts, languages). Provide for actual differences in the data due to user location (“locale”). Provide for localization of global content. Provide for local content management. Basic Rules for a Global DB Schema Expand fields to support changes in character encoding. Expan