This content has been marked as final. Show 4 replies
Hope this thread loop helps you. Sunil andTim helped me earlier on this long dicsussion.
You need to follow the instructions to setup MDEXService and MdexDataService.
Experience Management 2.1.2 micro browser issue
Hi! Did you manage to get this resolved? We too have been working with 3.1 and have received the same error within Experience Manager on some of the cartridges, for example the RecordSpotlight of the default web page of the Discover app.
In our case, we are trying to use a different data set than the Discover data.
Would really appreciate your feedback if the previous response to your post resolved the problem for you.
Thanks in advance,
That thread definetely helped. 2 major things I corrected before it worked for me
1. I had to setup the MDEXService and MDEXDataService properly
2. grab a different version of endeca navigation.jar file from platform services inner folder and place it in MDEXService.
3. Tried few things with the crossdomain.xml file and had entry for any (cross domain access).
I have successfully configured RecordSpotlight editor to use a different endeca instance. What I did is modify apps\[your app name]\config\editors_config\services\dataservice.json file with updated endeca search configuration, save the file, and run apps\[your app name]\control\set_editros_config.bat to apply the change.
To verify, you can run apps\[your app name]\control\export_site.bat command to export your site configuration, the updated data service config should show in the site xml file exported.
Hope it helps,