Publishing the Aurora starter store in the Turkish language

The Aurora.sar is fully translated into Turkish. However, the data is not automatically loaded to the database with the other supported languages unless you complete these steps:

These store archives are fully translated into Turkish. However, the data is not automatically loaded to the database with the other 13 supported languages unless you enable the sections specific to the Turkish locale.

To ensure that you are using the correct process for locating, updating, and then deploying the WebSphere Commerce configuration file, follow the instructions in Updating the WebSphere Commerce configuration file.

Make the following updates to the WebSphere Commerce configuration file for the Turkish language:

Follow the steps in Adding a currency to WebSphere Commerce. You can use the following SQL statements to load the Turkish Lira currency:

insert into setcurr (setccurr, setccode, setcexp) values 
('TRY', 949, -2)

insert into setcurrdsc (setccurr, language_id, description) values
('TRY', -1, 'Turkish Lira')

insert into setcurrdsc (setccurr, language_id, description) values
('TRY', -13, 'Trkçe')  

insert into curformat (storeent_id, setccurr, roundingmultiple, numbrusg_id, 
roundingmethod, decimalplaces, minapproveamount) values 
(-1, 'TRY', 1, -1, 'R', 2, null)  

insert into curfmtdesc (storeent_id, setccurr, language_id, currencysymbol, customizedcurrstr, 
currencyprefixpos, currencysuffixpos, displaylocale, currencyprefixneg, currencysuffixneg, 
radixpoint, groupingchar, numberpattern, description) values  
(-1, 'TRY', -1, '₺', null, '₺', null, null, '₺', 
null, null, null, '#,##0.00', 'Turkish Lira')  

insert into curfmtdesc (storeent_id, setccurr, language_id, currencysymbol, customizedcurrstr, 
currencyprefixpos, currencysuffixpos, displaylocale, currencyprefixneg, currencysuffixneg, 
radixpoint, groupingchar, numberpattern, description) values  
(-1, 'TRY', -13, '₺', null, '₺', null, null, '₺', 
null, null, null, '#,##0.00', 'Trk Liras')  

insert into curconvert (storeent_id, fromcurr, tocurr, factor, multiplyordivide, 
bidirectional, updatable, curconvert_id) values 
(-1,'USD','TRY','1.93','M','Y','Y',-101)

By default, the Aurora starter store uses the indexed price mode instead of the computed price mode. In the indexed price mode, the store loads all prices into the WebSphere Commerce Search (Solr) index and displays prices directly from the index. In the default index, all product prices for the Aurora sample data are in USD currency only. Therefore, when you switch to a different currency, such as Turkish, the store page displays Price pending instead of the price of a product because the index does not contain prices in those currencies.

If you want to display prices for currencies other than USD by using currency conversion rates, you must switch to computed price mode. You can switch price modes by running the following SQL statement to update the price mode in the STORECONF table:

UPDATE STORECONF SET VALUE='0' WHERE STOREENT_ID=TargetStoreId AND NAME='wc.search.priceMode'

Where TargetStoreId is the store ID of the store for which you are changing the price mode, for example, 10001.

For detailed instructions, see Changing search configuration properties in the STORECONF table.

Another way to display prices in a particular currency is to enter prices for all products in that currency. For performance reasons, consider entering product prices in each supported currency in the index rather than relying on currency conversion.