This content has been marked as final. Show 4 replies
Do the p_product_id and p_name show up correctly on the properties of each record in your endeca_jspref application? If so, they're mapping correctly in your pipeline. The property to be designated as the title of each record in the endeca_jspref application is controlled in your constants.jsp file in your endeca_jspref /webapps directory. By default, this is set to "P_Name", but be careful, this is case-sensitive.
If you're running the reference application via port 8006 (workbench) then look to C:\Endeca\Workbench\<version>\server\webapps\endeca_jspref for the root of the endeca_jspref application to find this constants.jsp file. If you're running it via port 8888 (eac/platform services), then look to C:\Endeca\PlatformServices\<version>\tools\server\webapps\endeca_jspref. Note: these paths do depend on the version of the product you're running, but should point you in the right direction.
Thanks for the valuable inputs given by you.
See, I am running the endeca_jspref web application in my eclipse's tomcat server. As you mentioned about the changes in constants.jsp file , I have changed it according to my endeca_property's value. Actually all the changes I have done from the very begining.
But anyways , the product_id and p_name did not show up correctly on the properties of each record in your endeca_jspref application.
I have correctly mapped the source data to endeca property,that I can say.
Let me tell you one more information, I have created the application using deployment template and navigate to *.esp file and opened it in Developers Studio and modified the pipeline there. Is there any thing wrong in my approach ?
I don't know why this is happening in one system and on other system, it is not replicating. I am really surprised about the fact. Same set up with same version of endeca are being installed on both the system but results are different.
Let me tell you one thing, I am trying to making index from database records (as a jdbc adapter).
Anyways , thanks for your prompt and valuable response.