1 Reply Latest reply on Jul 12, 2012 4:31 PM by Frank

    Enabling Relationship Discovery

    Hemant Maddala
      1.How do I enable Relation Discovery for Platform Services - ProductConfig.xml?

      2. How do i set a Global Language ID for Platform Services - ProductConfig.xml?

      Is there any document for this ? In the Relationship Discovery Guide
      LANG pass-through
      The LANG pass-through specifies the language ID to use on a global basis. Currently, you can specify
      either EN (or en) to run the English version of the text extractor or FR (or fr) to run the French version.
      If you do not specify this pass-through, the global language ID defaults to the first language specified
      in the product configuration file (named ProductConfig.xml). Although this pass-through is optional, it
      is recommended that you use it to explicitly set the global language ID.

      When i am using the term Extraction jar i am getting the following error
      Running on: Java HotSpot(TM) 64-Bit Server VM 14.3-b01
      LoggerX: Using logger settings from file: /opt/endeca/apps/earthdev/logging.properties
      Can't load log handler "com.endeca.soleng.eac.toolkit.logging.RelativePathFileHandler"
      java.lang.ClassNotFoundException: com.endeca.soleng.eac.toolkit.logging.RelativePathFileHandler
      java.lang.ClassNotFoundException: com.endeca.soleng.eac.toolkit.logging.RelativePathFileHandler
      at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
      at java.security.AccessController.doPrivileged(Native Method)
      at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
      at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
      at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
      at java.util.logging.LogManager$7.run(LogManager.java:918)
      at java.security.AccessController.doPrivileged(Native Method)
      at java.util.logging.LogManager.initializeGlobalHandlers(LogManager.java:911)
      at java.util.logging.LogManager.access$900(LogManager.java:129)
      at java.util.logging.LogManager$RootLogger.getHandlers(LogManager.java:1018)
      at java.util.logging.Logger.log(Logger.java:454)

      at java.util.logging.Logger.doLog(Logger.java:480)
      at java.util.logging.Logger.log(Logger.java:569)
      at com.endeca.edf.adapter.AdapterRunner.run(AdapterRunner.java:190)
      at com.endeca.edf.adapter.AdapterRunner.main(AdapterRunner.java:43)
      Jul 11, 2012 5:00:20 PM com.endeca.edf.adapter.AdapterRunner run
      SEVERE: There are no licensed languages for the Term Extractor.
      com.endeca.edf.adapter.AdapterException: There are no licensed languages for the Term Extractor.
      at com.endeca.edf.termextractor.ConfigInfo.getNPClassName(ConfigInfo.java:186)
      at com.endeca.edf.termextractor.ConfigInfo.<init>(ConfigInfo.java:127)
      at com.endeca.edf.termextractor.TermExtractor.execute(TermExtractor.java:39)
      at com.endeca.edf.adapter.AdapterRunner.run(AdapterRunner.java:168)
      at com.endeca.edf.adapter.AdapterRunner.main(AdapterRunner.java:43)
        • 1. Re: Enabling Relationship Discovery
          To quote from the Relationship Discovery Guide: "The implementation of Term Discovery and Cluster Discovery requires that you must have purchased a license for Relationship Discovery.The license package includes documentation that describes how to enable the feature."

          The enablement doc also describes how to set the global language. However, as you noted, you can set the global language ID in the Java manipulator by using the LANG pass-through. Keep in mind that you are not setting a global language ID for the entire Platform Services product, but only for the Term Discovery piece.