1 2 Previous Next 28 Replies Latest reply: Sep 25, 2012 1:55 PM by 964067 Go to original post RSS
      • 15. Re: Experience Management 2.1.2 micro browser issue
        John P
        I verified every both the things you recommended to verify

        App.Config

        <app appName="nfm2011" eacHost="localhost" eacPort="8888" dataPrefix="nfm2011" sslEnabled="false" lockManager="LockManager">
        <working-dir>${ENDECA_PROJECT_DIR}</working-dir>
        <log-dir>./logs</log-dir>
        </app>

        <host id="ITLHost" hostName="localhost" port="8888" />
        <host id="MDEXHost" hostName="localhost" port="8888" />
        <host id="webstudio" hostName="localhost" port="8888" >
        <directories>
        <directory name="webstudio-report-dir">./reports</directory>
        </directories>
        </host>

        .....
        <custom-component id="ConfigManager" host-id="ITLHost" class="com.endeca.soleng.eac.toolkit.component.ConfigManagerComponent">
        <properties>
        <property name="webStudioEnabled" value="true" />
        <property name="webStudioHost" value="localhost" />
        <property name="webStudioPort" value="8006" />
        <property name="webStudioMaintainedFile1" value="thesaurus.xml" />
        <property name="webStudioMaintainedFile2" value="merch_rule_group_default.xml" />
        <property name="webStudioMaintainedFile3" value="merch_rule_group_default_redirects.xml" />
        <property name="webStudioMaintainedFile4" value="merch_rule_group_Banners.xml" />
        <property name="webStudioMaintainedFile5" value="merch_rule_group_FeaturedContent.xml" />
        <property name="webStudioMaintainedFile6" value="merch_rule_group_ProductMerchandising.xml" />
        <property name="webStudioMaintainedFile7" value="merch_rule_group_Electronics.xml" />     
        <property name="webStudioMaintainedFile8" value="merch_rule_group_Furniture.xml" />     
        <property name="webStudioMaintainedFile9" value="merch_rule_group_Appliance.xml" />     
        <property name="webStudioMaintainedFile10" value="merch_rule_group_Rugs.xml" />     
        <property name="webStudioMaintainedFile11" value="merch_rule_group_Email_Marketing.xml" />     
        <property name="webStudioMaintainedFile12" value="merch_rule_group_General.xml" />     
        <property name="webStudioMaintainedFile13" value="merch_rule_group_Coupons.xml" />     
        <property name="webStudioMaintainedFile14" value="merch_rule_group_Home.xml" />     
             <property name="webStudioMaintainedFile15" value="merch_rule_group_Default.xml" />     
        </properties>
        <directories>
        <directory name="devStudioConfigDir">./config/pipeline</directory>
        <directory name="webStudioConfigDir">./data/web_studio/config</directory>
        <directory name="webStudioDgraphConfigDir">./data/web_studio/dgraph_config</directory>
        <directory name="mergedConfigDir">./data/complete_index_config</directory>
        <directory name="webStudioTempDir">./data/web_studio/temp</directory>
        </directories>
        </custom-component>


        One more thing I noticed (i have little different than what you recommeneded was this), hope if this help you understand exactly what I got or what I am over looking.

        You recommended this piece (earlier).
        com.endeca.webstudio.pagebuilder.editors.config=http://localhost:8006/pbx/etc/pbconfig.xml

        When I do this, On the server my workbench rule group load without error. but when I try from outside (Failed to load http://localhost:8006/pbc/etc/pbconfig.xml).

        So I had to change it to (and I do not get this above error)
        com.endeca.webstudio.pagebuilder.editors.config=/pbx/etc/pbconfig.xml


        Thanks
        John
        • 16. Re: Experience Management 2.1.2 micro browser issue
          John P
          Here is the default cartridge template xml. should I force any ServiceId to hit MDEXService instead of using default MDEX?



          <?xml version="1.0" encoding="UTF-8"?>
          <ContentTemplate xmlns="http://endeca.com/schema/content-template/2008"
          xmlns:editors="editors"
          xmlns:xavia="http://endeca.com/schema/xavia/2010"
          type="MainColumnContent"
          id="ResultsList">

          <Description>Displays search and navigation results in a list or grid view.</Description>
          <ThumbnailUrl>/thumbnails/ResultsList.png</ThumbnailUrl>

          <ContentItem>
          <Name>New Results List</Name>
          <Property name="boostStrata">
          <xavia:List/>
          </Property>
               
          <Property name="buryStrata">
          <xavia:List/>
          </Property>

          <Property name="sort">
          <xavia:Item>
          <Property name="label">Default</Property>
          <Property name="attribute"/>
          <Property name="ascending"/>
          </xavia:Item>
          </Property>
          <Property name="relrank">
          <String/>
          </Property>
               <Property name="recordSpec">
          <String>p_sku</String>
          </Property>
          <Property name="recsPerPage">
          <String>10</String>
          </Property>
               <!-- The BoostBuryResultsProcessor MUST be last in the definition of properties -->
               <Property name="navigation_records">
                    <BoostBuryResultsProcessor xmlns="http://endeca.com/schema/content/xtags/2010"/>
               </Property>
          </ContentItem>

          <EditorPanel>
          <BasicContentItemEditor>

               <editors:SortEditor propertyName="sort" label="Sorts">
          <choice label="Default" />
                    
                    <choice label="Name (Ascending)" value="p_name" />
                    <choice label="Name (Descending)" value="p_name" />
                    
                    <choice label="Brand (Ascending)" value="p_vendor_code" />
                    <choice label="Brand (Descending)" value="p_vendor_code" />
               
          <choice label="Score (Descending)" value="p_is_bestseller" />
                    
          <choice label="Price (Ascending)" value="p_region_1_olp" />
          <choice label="Price (Descending)" value="p_region_1_olp" />
                    
                    
          </editors:SortEditor>

          <editors:ChoiceEditor propertyName="relrank" label="Relevance ranking">
          <choice label="Default" />
          <choice label="First" value="first" />
          <choice label="By Price (Static)" value="static(p_region_1_olp)" />
          <choice label="Frequency" value="freq" />
          </editors:ChoiceEditor>


               <editors:ChoiceEditor propertyName="recsPerPage" label="Records per page">
          <choice label="10" value="10"/>
          <choice label="20" value="20"/>
          <choice label="30" value="30"/>
          <choice label="50" value="50"/>
          <choice label="100" value="100"/>
          </editors:ChoiceEditor>

          <editors:RecordStratificationEditor propertyName="boostStrata" buryProperty="buryStrata" label="Customize Results List" />

          </BasicContentItemEditor>
          </EditorPanel>
          </ContentTemplate>
          • 17. Re: Experience Management 2.1.2 micro browser issue
            John P
            As per Tim.K Suggestion, I was trying to see this setup. Hope this gives more infromation.

            #1

            http://dev-endeca-02.dev.xyz:8006/MetaService
            or
            http://localhost:8006/MetaService


            HTTP Status 404 - /MetaService

            type Status report
            message /MetaService
            description The requested resource (/MetaService) is not available.
            Apache Tomcat/6.0.20


            #2

            When I try to call this (I get exception)

            http://dev-endeca-02.dev.xyz:8006/MetaDataService
            or
            http://localhost:8006/MetaDataService


            HTTP Status 500 -

            type Exception report

            message

            description The server encountered an internal error () that prevented it from fulfilling this request.

            exception

            javax.servlet.ServletException: com.endeca.navigation.ENEException: Navigation Engine not able to process request 'http://dev-endeca64-02.idcdev.nfm:30008/graph?node=0&offset=0&nbins=10&keyprops=all&irversion=620'.
                 com.endeca.metadataservice.MetaDataService.procMetaData(MetaDataService.java:72)
                 com.endeca.metadataservice.MetaDataService.doService(MetaDataService.java:45)
                 com.endeca.metadataservice.MetaDataService.doGet(MetaDataService.java:39)
                 javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
                 javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
            root cause

            com.endeca.navigation.ENEException: Navigation Engine not able to process request 'http://dev-endeca64-02.idcdev.nfm:30008/graph?node=0&offset=0&nbins=10&keyprops=all&irversion=620'.
                 com.endeca.navigation.OptiBackendRequest.getContent(Unknown Source)
                 com.endeca.navigation.OptiBackend.getNavigation(Unknown Source)
                 com.endeca.navigation.HttpENEConnection.query(Unknown Source)
                 com.endeca.metadataservice.MetaDataService.procMetaData(MetaDataService.java:65)
                 com.endeca.metadataservice.MetaDataService.doService(MetaDataService.java:45)
                 com.endeca.metadataservice.MetaDataService.doGet(MetaDataService.java:39)
                 javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
                 javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
            note The full stack trace of the root cause is available in the Apache Tomcat/6.0.20 logs.

            Apache Tomcat/6.0.20



            Also I noticed in steps to setup rel rank and else where - endeca_navigation.jar file is asked to be copied. Here I notice under MDEXService and MDEXDataService /lib/endeca_navigation 6.2.jar. is this correct?
            I see a link up in the url last piece showing this - ="all&irversion=620"

            Please help!

            Edited by: John P on Aug 21, 2012 1:16 PM
            • 18. Re: Experience Management 2.1.2 micro browser issue
              John P
              I get a valid XML load for all these 4 URLS

              http://dev-endeca64-02.dev.xyz:8006/pbx/services/mdex.xml
              http://dev-endeca64-02.dev.xyz:8006/pbx/services/zones.xml
              http://dev-endeca64-02.dev.xyz:8006/pbx/services/images.xml
              http://dev-endeca64-02.dev.xyz:8006/pbx/etc/pbconfig.xml

              even I get the rel rank page load up and its intreacting with the right MDEX engine.
              http://dev-endeca64-02.dev.xyz:8006/relrankEvaluator/


              #1
              Am I supposed to get something back for these? I get 404 or 500 error

              http://dev-endeca64-02.dev.xyz:8006/MdexService
              http://dev-endeca64-02.dev.xyz:8006/MdexDataService

              Also the folder MdexDataService & MdexService dosen't have any content in its root (only has 2 folders one is Web-inf and meta-inf)


              #2
              Do I have to add an entry in server.xml in CONF? documentation made me to add one for rel rank setup.


              I wish the XMgrExtensionsUserGuide.pdf clearly explained steps setting up this MDEXService and MdexDataService.
              • 19. Re: Experience Management 2.1.2 micro browser issue
                957290
                Hi,

                I am not able to upload images in JCR that is provided in Extension Manager.
                Can any one help me on this.

                regards,
                Adarsh
                • 20. Re: Experience Management 2.1.2 micro browser issue
                  John P
                  this is my server.xml, am I missing something for MDEXService and MdexDataSerivce?



                  <!-- Alternate Example-less Configuration File -->
                  <!-- Note that component elements are nested corresponding to their
                  parent-child relationships with each other -->

                  <!-- A "Server" is a singleton element that represents the entire JVM,
                  which may contain one or more "Service" instances. The Server
                  listens for a shutdown command on the indicated port.

                  Note: A "Server" is not itself a "Container", so you may not
                  define subcomponents such as "Valves" or "Loggers" at this level.
                  -->

                  <!-- NOTE: ENDECA HAS MODIFIED TOMCAT'S DEFAULT SHUTDOWN PORT OF 8005.
                  ENDECA'S USES A DEFAULT SHUTDOWN PORT OF 8084 TO AVOID CONFLICTS.
                  Note that this is NOT the port that Tomcat serves pages on, it is the
                  port that Tomcat listens for the shutdown command on.
                  -->

                  <Server port="8084" shutdown="SHUTDOWN" debug="0">

                  <!-- A "Service" is a collection of one or more "Connectors" that share
                  a single "Container" (and therefore the web applications visible
                  within that Container). Normally, that Container is an "Engine",
                  but this is not required.

                  Note: A "Service" is not itself a "Container", so you may not
                  define subcomponents such as "Valves" or "Loggers" at this level.
                  -->

                  <!-- Define the Tomcat Stand-Alone Service -->
                  <Service name="Standalone">

                  <!-- A "Connector" represents an endpoint by which requests are received
                  and responses are returned. Each Connector passes requests on to the
                  associated "Container" (normally an Engine) for processing.

                  By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
                  You can also enable an SSL HTTP/1.1 Connector on port 8446 by
                  following the instructions below and uncommenting the second Connector
                  entry. SSL support requires the following steps (see the SSL Config
                  HOWTO in the Tomcat 5 documentation bundle for more detailed
                  instructions):
                  * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
                  later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
                  * Execute:
                  %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
                  $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
                  with a password value of "changeit" for both the certificate and
                  the keystore itself.

                  By default, DNS lookups are enabled when a web application calls
                  request.getRemoteHost(). This can have an adverse impact on
                  performance, so you can disable it by setting the
                  "enableLookups" attribute to "false". When DNS lookups are disabled,
                  request.getRemoteHost() will return the String version of the
                  IP address of the remote client.
                  -->

                  <!-- NOTE: ENDECA HAS MODIFIED THE DEFAULT TOMCAT NON-SSL HTTP PORT OF 8080.
                  ENDECA' USES A DEFAULT NON-SSL HTTP PORT OF 8006. This is the port that
                  Tomcat serves pages on.
                  -->

                       <!-- Define a non-SSL HTTP/1.1 Connector on port 8006 -->
                  <Connector port="8006" maxHttpHeaderSize="8192"
                  maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
                  enableLookups="true" redirectPort="8446" acceptCount="10"
                  connectionTimeout="60000" disableUploadTimeout="true" debug="0" URIEncoding="UTF-8"/>
                  <!-- Note : To disable connection timeouts, set connectionTimeout value
                  to -1 -->

                  <!-- Define a SSL HTTP/1.1 Connector on port 8446 -->
                  <!--
                  <Connector port="8446" maxHttpHeaderSize="8192" SSLEnabled="true"
                  maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
                  enableLookups="false" disableUploadTimeout="true"
                  acceptCount="100" scheme="https" secure="true"
                  clientAuth="false" sslProtocol="TLS"
                  keystoreFile="conf/eac.ks" keystorePass="eacpass"
                  truststoreFile="conf/ca.ks" truststorePass="eacpass"
                  URIEncoding="UTF-8"/>
                  -->

                  <!-- An Engine represents the entry point (within Catalina) that processes
                  every request. The Engine implementation for Tomcat stand alone
                  analyzes the HTTP headers included with the request, and passes them
                  on to the appropriate Host (virtual host). -->

                  <!-- Define the top level container in our container hierarchy -->
                  <Engine name="Standalone" defaultHost="localhost" debug="0">

                  <!-- Define the default virtual host -->
                  <Host name="localhost" debug="0" appBase="state/webapps" unpackWARs="false" autoDeploy="true">

                  <!-- Access log processes all requests for this virtual host. By
                  default, log files are created in the "logs" directory relative to
                  $CATALINA_HOME. If you wish, you can specify a different
                  directory with the "directory" attribute. Specify either a relative
                  (to $CATALINA_HOME) or absolute path to the desired directory.
                  -->
                  <Valve className="org.apache.catalina.valves.AccessLogValve"
                  directory="logs" prefix="localhost_access_log." suffix=".txt"
                  pattern="common"/>

                  </Host>

                       <!-- Context configuration file for the Relevance Ranking Evaluator -->
                            <Context path="/relrankEvaluator"
                            docBase="E:/Endeca/Solutions/relrankEvaluator-1.6/relrankEvaluator"
                            debug="0" privileged="false">
                            </Context>


                  </Engine>

                  </Service>


                  </Server>
                  • 21. Re: Experience Management 2.1.2 micro browser issue
                    TimK
                    Turns out it was a Presentation API version mis-match. MdexService and MdexDataService both have endeca_navigation.jar files in the WEB-INF/lib directories - these Presentation API jar files need to match the MDEX version (or be compatible with the current MDEX version).
                    • 22. Re: Experience Management 2.1.2 micro browser issue
                      TimK
                      In reply to the question about testing MdexService and MetaDataService - here are the URLs to test those services:
                      http://localhost:8006/MdexService/mdex?meta=1
                      http://localhost:8006/MetaDataService/mdex?meta=1
                      • 23. Re: Experience Management 2.1.2 micro browser issue
                        John P
                        Thanks Tim. It was great of you that you spend you time to go over my settings and find the issue.

                        Hope this helps others who are in the same boat like me.

                        Thanks
                        John
                        • 24. Re: Experience Management 2.1.2 micro browser issue
                          964067
                          I have the same issue. I tried all versions of navigation.jar and it doesn't seem to work.

                          http://localhost:8006/MdexService/mdex?meta=1 ---------------------- works
                          http://localhost:8006/MetaDataService/mdex?meta=1 ------------------------errors out

                          javax.servlet.ServletException: com.endeca.navigation.ENEException: Navigation Engine not able to process request 'http://localhost:8006/graph?node=0&offset=0&nbins=10&keyprops=all&irversion=620'.
                               com.endeca.metadataservice.MetaDataService.procMetaData(MetaDataService.java:72)
                               com.endeca.metadataservice.MetaDataService.doService(MetaDataService.java:45)
                               com.endeca.metadataservice.MetaDataService.doGet(MetaDataService.java:39)
                               javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
                               javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

                          Any help will be appreciated
                          • 25. Re: Experience Management 2.1.2 micro browser issue
                            TimK
                            Are you trying to setup the experience manager extensions to go against multiple MDEX's or just one?

                            What is the error you are receiving?

                            For this error, I would try the following:
                            first validate that you have setup a context configuration file for the MetaDataService and that it points to the root directory of the MetaDataService application.
                            second validate that your edits in the web.xml file for the MetaDataService application do indeed point to the same mdex-host and mdex-port.
                            • 26. Re: Experience Management 2.1.2 micro browser issue
                              964067
                              Tim,

                              Thanks for the reply. I'm trying to run one MDEX engine. very new to endeca.
                              I just installed the discover app and trying to see if I can install the experience manager extension.
                              The spot light records is inactive for me. I want to enable the 'Edit query' micro browser.

                              Am I in right track?
                              • 27. Re: Experience Management 2.1.2 micro browser issue
                                964067
                                I have the same problem when I tried http://localhost:8006/endeca_jspref

                                host port
                                Go / Stats
                                status >> ENE error
                                ENEException
                                com.endeca.navigation.ENEException: HTTP Error 404 - Navigation Engine not able to process request 'http://localhost:8006/graph?node=0&offset=0&nbins=10&irversion=630'.


                                Version : MDEX - 6.3.0
                                Platform services - 6.1.3

                                I copied the endeca_logging6.3.0 and endeca_navigation_6.3.0 to
                                C:\Endeca\PlatformServices\6.1.3\tools\server\webapps\endeca_jspref\WEB-INF\lib

                                Still not working
                                • 28. Re: Experience Management 2.1.2 micro browser issue
                                  964067
                                  I changed the port to 15000 intead of 8006 and it seems to be working.

                                  http://localhost:8006/MetaDataService/mdex?meta=1

                                  brings all the data.


                                  <init-param>
                                  <param-name>mdex-port</param-name>
                                  <param-value>15000</param-value>
                                  </init-param>


                                  Question : Now, if I go to my discover app ->Experience Manager ->Default Browse Page ->Top rated products ->Spot Light Records
                                  This section should have the Edit Query enabled ???

                                  Is that Right? or do i need to do anything else to get it activate in discover app?

                                  Thanks,
                                  Alagu
                                  1 2 Previous Next