Database considerations for International projects with SDx
For more information on how to configure your SDx database for Internationalization support, see Install database software on the database server.
To change the collation of an SDx SQL database, follow these .
-
Create a new SDx site. For more information, see Create a new site.
The delivered site database will be in a Latin collation.
-
After creating the site, download the SDx.DatabaseCollationSwitch sample SQL files and the associated readme file from Smart Community. This sample will change the collation of a SQL database and its contents to create a homogeneous environment.
For more information on how to download sample files from Smart Community, see Find sample data on Smart Community.
-
Follow the instructions in the readme file.
International projects with client and server in different time zones
If your project includes one or more clients that are located in a different time zone than the HxGN SDx application server, when data is written to the database, any properties that are scoped by the YMD data type and calculated by the server are time-stamped using the time zone of the application server. These YMD data-typed properties are never converted to the local time zone of the client. Any YMD data-typed properties entered by the user and any DateTime data-typed properties are always converted to display in the client’s local time zone.
International projects using Web Client for limited heterogeneous support
For international projects using the Web Client, a limited level of heterogeneous support can be achieved by using the Web Client on independent workstations or devices that do not need to conform to the homogeneous environment rules that are explained above for servers and tool workstations. For instance, if your database and application server are English and you use the Web Client on a Russian workstation that does not run any other integration tool software, in this case the Web Client can provide a Russian "front-end" to the English "back-end" database and application servers.
-
FTR indexing can be run against only a single language. An FTR search that is run against a language that has not been indexed will most likely yield no results because there may be characters in the search text that are not present in the language used by the database server.
-
Extraction of Japanese characters from the content using the Data Capture is not supported in the heterogeneous environment. The limitation is due to the requirement of locale-specific collation settings which is not supported in the heterogeneous environment.
This is how SDx environments hosted in the Smart Cloud are configured.
For more information about language translation and localization, see Web Client localization.