This discussion is archived
6 Replies Latest reply: Jan 28, 2013 9:55 PM by 887854 RSS

Endeca Commerce-can't support Chinese search at MDEX 6.4.0 also ?

887854 Newbie
Currently Being Moderated
Dear experts:
I am do a PoC base on the sample discover project. After specifiy the language to Chinese, I can't start the Forge. It seems that the datasource is not ready, but I really have load it to the MDEX and can read it from the web apps. The error log as below:

[01.25.13 16:04:01] INFO: Checking definition from AppConfig.xml against existin
g EAC provisioning.
[01.25.13 16:04:02] INFO: Definition has not changed.
[01.25.13 16:04:02] INFO: Starting baseline update script.
[01.25.13 16:04:02] INFO: Acquired lock 'update_lock'.
[01.25.13 16:04:02] INFO: [ITLHost] Starting shell utility 'move_-toprocessing
[01.25.13 16:04:03] INFO: [ITLHost] Starting copy utility 'fetch_config_to_input
[01.25.13 16:04:04] SEVERE: Utility 'fetch_config_to_input_for_forge_Forge' fail
ed. Refer to utility logs in [ENDECA_CONF]/logs/copy on host ITLHost.
Occurred while executing line 19 of valid BeanShell script:

16| LockManager.removeFlag("baseline_data_ready");
18| // fetch config files to forge input
19| Forge.getConfig();
21| // archive logs and run ITL
22| Forge.archiveLogDir();


[01.25.13 16:04:04] SEVERE: Caught an exception while invoking method 'run' on o
bject 'BaselineUpdate'. Releasing locks.

Caused by java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl invoke0 - null
Caused by com.endeca.soleng.eac.toolkit.exception.AppControlException
com.endeca.soleng.eac.toolkit.script.Script runBeanShellScript - Error executing
valid BeanShell script.
Caused by com.endeca.soleng.eac.toolkit.exception.EacComponentControlException
com.endeca.soleng.eac.toolkit.utility.Utility run - Utility 'fetch_config_to_inp
ut_for_forge_Forge' failed. Refer to utility logs in [ENDECA_CONF]/logs/copy on
host ITLHost.

[01.25.13 16:04:04] INFO: Released lock 'update_lock'.     

what I have configured is:
For data source:
I changed the property 'product.long_desc' of first one record to chinese and load it to MDEX by baseline_update and promote_content (can read it from the web application)
For Forge:
specify the encoding of source data to UTF-8 and specify the per-property language ID for property 'product.long_disc' in the Forge pipeline.
For Digdx
specify the language in DataIngest.xml as below:
- <dgidx id="Dgidx" host-id="ITLHost">
- <properties>
<property name="numLogBackups" value="10" />
<property name="numIndexBackups" value="3" />
- <args>

and add the file Disvover.spell_config.xml with below content:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE SPELL_CONFIG SYSTEM "spell_config.dtd">

For the Dgraph:
specify the language in DgraphDefaults.xml as below:
- <dgraph-defaults>
- <properties>
<property name="srcIndexDir" value="./data/dgidx_output" />
<property name="srcIndexHostId" value="ITLHost" />
<property name="srcPartialsDir" value="./data/partials/forge_output" />
<property name="srcPartialsHostId" value="ITLHost" />
<property name="srcCumulativePartialsDir" value="./data/partials/cumulative_partials" />
<property name="srcCumulativePartialsHostId" value="ITLHost" />
<property name="srcDgraphConfigDir" value="./data/workbench/dgraph_config" />
<property name="srcDgraphConfigHostId" value="ITLHost" />
<property name="numLogBackups" value="10" />
<property name="shutdownTimeout" value="30" />
<property name="numIdleSecondsAfterStop" value="0" />
- <directories>
<directory name="localIndexDir">./data/dgraphs/local_dgraph_input</directory>
<directory name="localCumulativePartialsDir">./data/dgraphs/local_cumulative_partials</directory>
<directory name="localDgraphConfigDir">./data/dgraphs/local_dgraph_config</directory>
- <args>

Dear experts, thank you in advance. Any advice or solution about this issue will be great appreciated!

Best regards


  • Correct Answers - 10 points
  • Helpful Answers - 5 points