11 Replies Latest reply: Oct 22, 2012 8:13 AM by 967507 RSS

    ATG Endeca CRS Integration baseline_update.bat issue

    967507
      HI,

      I try to describe all steps my integration ATG and Endeca

      First I create special user for endeca
      And installing that soft.
      1)MDEX 6.2.2
      2)PlatformServices 6.1.3
      3)ToolsAndFrameworks 3.1.0
      4)CAS 3.0.2

      Then I installing ATG and configuring CRS by CIM.
      1) Next I go to ToolsAndFrameworks\3.1.0\reference\discover-data-pci\ and modify configuration of install-config-example.xml and rename install-config-example2.xml.
      2) Run command *deploy.bat no-prompt install-config C:\Endeca\ToolsAndFrameworks\3.1.0\reference\discover-data-pci\install-config-example2.xml*
      3) Delete all files and folders from ATGen\config\ifcr\content\, where ATGen my endeca application
      4) Modify ATGen\control\initialize_services.bat (comment line 83-89.It's about import sample content)
      5) Run initialize_services.bat
      6) Go to */atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin/* and run baseline index
      7) I got exeception.Run again baseline_update.bat and got

      [10.17.12 14:35:14] SEVERE: Batch component 'Dgidx' failed. Refer to component logs in D:\ATG\Endeca\Apps\ATGen\config\script\..\..\.\logs\dgidxs\Dgidx on host ITLHost.
      Occurred while executing line 26 of valid BeanShell script:
      [[

      23| Forge.archiveLogDir();
      24| Forge.run();
      25| Dgidx.archiveLogDir();
      26| Dgidx.run();
      27|
      28| // distributed index, update Dgraphs
      29| DistributeIndexAndApply.run();

      ]]

      [10.17.12 14:35:14] SEVERE: Caught an exception while invoking method 'run' on object '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.component.BatchComponent run - Batch component 'Dgidx' failed. Refer to component logs in D:\ATG\Endeca\Apps\ATGen\config\script\..\..\.\logs\dgidxs\
      Dgidx on host ITLHost.

      [10.17.12 14:35:14] INFO: Released lock 'update_lock'.



      Dgidx.log

      ============================================================================
      === DGIDX: Version = "6.2.2.621294"
      === Start Time : Wed Oct 17 15:56:01 2012
      === Arguments : "d:\ATG\Endeca\MDEX\6.2.2\\bin\dgidx.exe -v --compoundDimSearch --lang en --out D:\ATG\Endeca\Apps\ATGen\logs\dgidxs\Dgidx\Dgidx.log --dtddir d:\ATG\Endeca\MDEX\6.2.2\\conf\dtd --tmpdir D:\ATG\Endeca\Apps\ATGen\data\temp D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen D:\ATG\Endeca\Apps\ATGen\data\dgidx_output\ATGen"
      === Current Directory : D:\ATG\Endeca\Apps\ATGen
      === Host : EPBYMINW0841
      === Exec Path : d:\ATG\Endeca\MDEX\6.2.2\\bin\dgidx.exe
      ============================================================================

      Language/collation in use is English (collation=endeca)
      No application configuration specified. Using "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen" as the application configuration prefix.
      ============================================================================
      === DGIDX: Starting phase "Read raw dimensions, properties, and records"
      === Current Time : Wed Oct 17 15:56:01 2012
      === Total Elapsed : 0.0231 seconds
      === User CPU Time : 0.000000 seconds
      === System CPU Time : 0.0624 seconds
      === Memory Usage : 3.81 MB
      ============================================================================

      Parsing XML dimensions data with validation turned on
      Parsing project file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.xml" (project="ATGen")
      XMLParser: Reading dimensions, dvals, and synonyms from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\\ATGen.dimensions.xml"
      Dval [id=102185] "clothing-sku.color" is non-searchable.
      Dval [id=102186] "clothing-sku.size" is non-searchable.
      Dval [id=102187] "furniture-sku.woodFinish" is non-searchable.
      Dval [id=102190] "product.disallowAsRecommendation" is non-searchable.
      Dval [id=102191] "product.nonreturnable" is non-searchable.
      Dval [id=102192] "product.siteId" is non-searchable.
      Dval [id=100972] "product.category" is non-searchable.
      Dval [id=102260] "item.type" is non-searchable.
      XMLParser: Done reading dimensions, dvals, and synonyms from "D:\ATG\Endeca\Apps\ATGen\data\forge_output\\ATGen.dimensions.xml"
      XMLParser: Reading auto propmap file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\\ATGen.auto_propmap.xml"
      XMLParser: Done reading auto propmap file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\\ATGen.auto_propmap.xml"
      XMLParser: Reading properties from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.prop_refs.xml"
      XMLParser: Done reading properties from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.prop_refs.xml"
      XMLParser: Reading rollup properties and dimensions from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.rollups.xml"
      XMLParser: Done reading rollup properties and dimensions from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.rollups.xml"
      XMLParser: Reading record spec property from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.record_spec.xml"
      XMLParser: Property "common.id" is a record spec property.
      XMLParser: Done reading record specs from "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.record_spec.xml"
      XMLParser: Reading record filter properties from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.record_filter.xml"
      XMLParser: Done reading record filter properties from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.record_filter.xml"
      XMLParser: Creating dimensions from dvals.
      XMLParser: Reading rollup properties and dimensions from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.rollups.xml"
      XMLParser: Done reading rollup properties and dimensions from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.rollups.xml"
      XMLParser: Reading dimensions from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dimension_refs.xml"
      XMLParser: Done reading dimensions from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dimension_refs.xml"
      XMLParser: Reading dimension groups from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dimension_groups.xml"
      XMLParser: Done reading dimension groups from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dimension_groups.xml"
      XMLParser: Reading precedence rules from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.precedence_rules.xml"
      XMLParser: Done reading precedence rules from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.precedence_rules.xml"
      XMLParser: Reading dval refs from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dval_refs.xml"
      XMLParser: Done reading dval refs from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dval_refs.xml"
      XMLParser: Reading dval ranks from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dval_ranks.xml"
      XMLParser: Done reading dval ranks from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dval_ranks.xml"
      XMLParser: Reading refinement config from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.refinement_config.xml"
      XMLParser: Done reading refinement config from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.refinement_config.xml"
      XMLParser: Reading dimension search index configuration from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dimsearch_index.xml"
      XMLParser: Done reading dimension search index configuration from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.dimsearch_index.xml"
      XMLParser: Reading record search index configuration from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.recsearch_indexes.xml"
      XMLParser: Done reading record search index configuration from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.recsearch_indexes.xml"
      XMLParser: Reading search chars from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.search_chars.xml"
      XMLParser: Done reading search chars from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.search_chars.xml"
      XMLParser: Reading language stemming settings from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.stemming.xml"
      XMLParser: Done reading per-language stemming settings from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.stemming.xml"
      XMLParser: Reading word forms from file "d:\ATG\Endeca\MDEX\6.2.2\conf\stemming\en_word_forms_collection.xml"
      XMLParser: Done reading word forms from file "d:\ATG\Endeca\MDEX\6.2.2\conf\stemming\en_word_forms_collection.xml". There are 50374 word forms.
      XMLParser: Reading language config from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.languages.xml"
      XMLParser: Done reading language config from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.languages.xml"
      XMLParser: Reading stop words from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.stop_words.xml"
      XMLParser: Done reading stop words from file "D:\ATG\Endeca\Apps\ATGen\data\forge_output\ATGen.stop_words.xml", finished in 0.000549 seconds.
      FATAL     10/17/12 12:56:01.905 UTC (1350478561905)     DGIDX     {dgidx,baseline}     ENE Indexer: No records file found.     

      Dgidx.start.log
      WARN     10/17/12 12:56:01.288 UTC (1350478561288)     DGIDX     {dgidx,baseline}     Notice: the '--tmpdir' option has been deprecated; see the product documentation for more details.

      In ATGen\data\forge_output\ I have a lots of xml files and one ATGen-sgmt0.records.binary file with abracadabra

      Could somebody help me?Maybe I do something wrong?

      Edited by: Andrew Karzhou on Oct 17, 2012 4:16 PM
        • 1. Re: ATG Endeca CRS Integration baseline_update.bat issue
          Michael Peel-Oracle
          6) Go to /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin/ and run baseline index
          7) I got exeception.Run again baseline_update.bat and got

          If you got an exception in step six - generating your data - I'd say that was the cause of the dgidx "no records found" error. What is the exception you are getting?

          Michael
          • 2. Re: ATG Endeca CRS Integration baseline_update.bat issue
            967507
            */atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin/* start */atg/endeca/index/commerce/EndecaScriptService* which call baseline_update.bat.That is why it doesn't matter first exception.

            But if it helps

            **** info Wed Oct 17 09:45:22 VET 2012 1350483322987 /atg/endeca/index/commerce/EndecaScriptService Starting script BaselineUpdate in application ATGen
            **** info Wed Oct 17 09:45:49 VET 2012 1350483349038 /atg/endeca/index/commerce/EndecaScriptService Script BaselineUpdate for application ATGen finished with status Fai
            led
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin --- atg.repository.search.indexing.IndexingExcep
            tion: Script BaselineUpdate for application ATGen failed
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.eacclient.ScriptRunner.waitFor
            Script(ScriptRunner.java:381)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.eacclient.ScriptIndexable.runU
            pdateScript(ScriptIndexable.java:319)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.eacclient.ScriptIndexable.perf
            ormBaselineUpdate(ScriptIndexable.java:246)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.index.admin.IndexingTask.doTas
            k(IndexingTask.java:401)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.index.admin.IndexingTask.perfo
            rmTask(IndexingTask.java:359)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.index.admin.IndexingPhase$Inde
            xingTaskJob.invoke(IndexingPhase.java:469)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.common.util.ThreadDispatcherThread.ru
            n(ThreadDispatcherThread.java:178)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin Caused by :atg.repository.search.indexing.IndexingEx
            ception: Script BaselineUpdate of application ATGen failed
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.eacclient.ScriptRunner.waitFor
            Script(ScriptRunner.java:378)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.eacclient.ScriptIndexable.runU
            pdateScript(ScriptIndexable.java:319)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.eacclient.ScriptIndexable.perf
            ormBaselineUpdate(ScriptIndexable.java:246)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.index.admin.IndexingTask.doTas
            k(IndexingTask.java:401)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.index.admin.IndexingTask.perfo
            rmTask(IndexingTask.java:359)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.endeca.index.admin.IndexingPhase$Inde
            xingTaskJob.invoke(IndexingPhase.java:469)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin at atg.common.util.ThreadDispatcherThread.ru
            n(ThreadDispatcherThread.java:178)
            **** Error Wed Oct 17 09:45:49 VET 2012 1350483349061 /atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin
            • 3. Re: ATG Endeca CRS Integration baseline_update.bat issue
              Ravi Honakamble|
              Hi Andrew,

              There are couple of places where you can look into:
              1) Check whether data pushed from the ATG to CAS.

              FYI: Here are the CAS commands to read the Data
              recordstore-cmd read-baseline -a ATGen_en_data -n 50000 -f C:\Endeca\CAS\3.0.2\bin\data\ATGen_en_data.xml
              recordstore-cmd read-baseline -a ATGen_en_schema -n 50000 -f C:\Endeca\CAS\3.0.2\bin\data\ATGen_en_schema.xml
              recordstore-cmd read-baseline -a ATGen_en_dimvals -n 500 -f C:\Endeca\CAS\3.0.2\bin\data\ATGen_en_dimvals.xml
              recordstore-cmd read-baseline -a ATGen_en_prules -n 50000 -f C:\Endeca\CAS\3.0.2\bin\data\ATGen_en_prules.xml

              You can find the data in above mentioned location Ex: C:\Endeca\CAS\3.0.2\bin\data\ATGen_en_data.xml

              2) If data is inserted into the CAS then look into the Forge log what error has been logged if any.

              Look into below mentioned log files:
              ATGen\logs\forges\ConfigurationGeneratorForge\ConfigurationGeneratorForge.log
              ATGen\logs\forges\ConfigurationGeneratorForge\ConfigurationGeneratorForge.start.log

              3) Nothing found from the above two steps then try below steps
              - Delete all the files from ATGen\test_data\baseline and ATGen\test_data\config_apit_input
              - Run Initialize_services.bat
              - Run baseline Update using Dynamo admin

              Hope this helps.

              Thanks & Regards,
              Ravi
              • 4. Re: ATG Endeca CRS Integration baseline_update.bat issue
                967507
                Hi Ravi,

                My results:

                STEP 1:

                I run this commands and folder data was created with 4 xml.

                ATGen_en_data.xml
                <?xml version='1.0' encoding='UTF-8'?>
                <RECORDS/>

                ATGen_en_dimvals.xml

                <RECORD>
                <PROP NAME="dimval.dimension_spec">
                <PVAL>item.type</PVAL>
                </PROP>
                <PROP NAME="dimval.display_name">
                <PVAL>item.type</PVAL>
                </PROP>
                <PROP NAME="dimval.qualified_spec">
                <PVAL>item.type</PVAL>
                </PROP>
                <PROP NAME="dimval.spec">
                <PVAL>item.type</PVAL>
                </PROP>
                </RECORD>
                <RECORD>
                <PROP NAME="dimval.dimension_spec">
                <PVAL>item.type</PVAL>
                </PROP>
                <PROP NAME="dimval.display_name">
                <PVAL>Catalog</PVAL>
                </PROP>
                <PROP NAME="dimval.parent_spec">
                <PVAL>item.type</PVAL>
                </PROP>
                <PROP NAME="dimval.qualified_spec">
                <PVAL>item.type:catalog</PVAL>
                </PROP>
                <PROP NAME="dimval.spec">
                <PVAL>catalog</PVAL>
                </PROP>
                </RECORD>
                <RECORD>
                <PROP NAME="dimval.dimension_spec">
                <PVAL>item.type</PVAL>
                </PROP>
                <PROP NAME="dimval.display_name">
                <PVAL>Category</PVAL>
                </PROP>
                <PROP NAME="dimval.parent_spec">
                <PVAL>item.type</PVAL>
                </PROP>
                <PROP NAME="dimval.qualified_spec">
                <PVAL>item.type:category</PVAL>
                </PROP>
                <PROP NAME="dimval.spec">
                <PVAL>category</PVAL>
                </PROP>
                </RECORD>
                <RECORD>
                ...........

                ATGen_en_prules.xml

                <?xml version='1.0' encoding='UTF-8'?>
                <RECORDS/>

                ATGen_en_schema.xml

                <RECORD>
                <PROP NAME="attribute.name">
                <PVAL>clothing-sku.color</PVAL>
                </PROP>
                <PROP NAME="attribute.property.data_type">
                <PVAL>string</PVAL>
                </PROP>
                <PROP NAME="attribute.source_name">
                <PVAL>clothing-sku.color</PVAL>
                </PROP>
                <PROP NAME="attribute.type">
                <PVAL>dimension</PVAL>
                </PROP>
                <PROP NAME="attribute.dimension.autogen">
                <PVAL>true</PVAL>
                </PROP>
                <PROP NAME="attribute.search.searchable">
                <PVAL>true</PVAL>
                </PROP>
                <PROP NAME="attribute.display_name">
                <PVAL>clothing-sku.color</PVAL>
                </PROP>
                </RECORD>
                <RECORD>
                <PROP NAME="attribute.name">
                <PVAL>clothing-sku.size</PVAL>
                </PROP>
                <PROP NAME="attribute.property.data_type">
                <PVAL>string</PVAL>
                </PROP>
                <PROP NAME="attribute.source_name">
                <PVAL>clothing-sku.size</PVAL>
                </PROP>
                <PROP NAME="attribute.type">
                <PVAL>dimension</PVAL>
                </PROP>
                <PROP NAME="attribute.dimension.autogen">
                <PVAL>true</PVAL>
                </PROP>
                <PROP NAME="attribute.search.searchable">
                <PVAL>true</PVAL>
                </PROP>
                <PROP NAME="attribute.display_name">
                <PVAL>clothing-sku.size</PVAL>
                </PROP>
                </RECORD>
                ............................


                STEP 2:

                ATGen\logs\forges\ConfigurationGeneratorForge\ConfigurationGeneratorForge.log and ATGen\logs\forges\ConfigurationGeneratorForge\ConfigurationGeneratorForge.start.log doesn't created.
                But I open old logs and found exception.Maybe it helps

                ConfigurationGeneratorForge.log
                ......................................................
                WARN     10/18/12 07:57:37.142 UTC (1350547057141)     FORGE     {baseline}: (com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator): Skipping dval record missing dimension spec 'dimval.dimension_spec': [dimval.prop.category.ancestorCatalogIds=masterCatalog, %XEF%XBB%XBFdimval.dimension_spec=product.category, dimval.prop.category.rootCatalogId=masterCatalog, dimval.prop.category.siteId=storeSiteUS, dimval.display_name=Shirts, dimval.parent_spec=rootCategory.catMen, dimval.prop.category.repositoryId=catMenShirts, dimval.qualified_spec=product.category:rootCategory.catMen.catMenShirts, dimval.display_order=0, dimval.prop.category.catalogs.repositoryId=masterCatalog, dimval.spec=rootCategory.catMen.catMenShirts]     
                INFO     10/18/12 07:57:37.165 UTC (1350547057164)     FORGE     {baseline}: (com.endeca.itl.recordstore.forge.RecordStoreSource$RecordStoreSourceExecutor): Committed transaction 2     
                WARN     10/18/12 07:57:38.204 UTC (1350547058204)     FORGE     {baseline}: RecordAdapter 'LoadDimValsCsv': file 'D:\ATG\Endeca\Apps\ATGen\config\api_input\dimension_values.csv' is empty or does not exist.     
                WARN     10/18/12 07:57:38.207 UTC (1350547058206)     FORGE     {baseline}: (com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator): Skipping dval record missing dimension spec 'dimval.dimension_spec': [dimval.prop.category.ancestorCatalogIds=masterCatalog, %XEF%XBB%XBFdimval.dimension_spec=product.category, dimval.prop.category.rootCatalogId=masterCatalog, dimval.prop.category.siteId=storeSiteUS, dimval.display_name=Shorts, dimval.parent_spec=rootCategory.catMen, dimval.prop.category.repositoryId=catMenShorts, dimval.qualified_spec=product.category:rootCategory.catMen.catMenShorts, dimval.display_order=2, dimval.prop.category.catalogs.repositoryId=masterCatalog, dimval.spec=rootCategory.catMen.catMenShorts]     
                ERROR     10/18/12 07:57:38.207 UTC (1350547058206)     FORGE     {baseline}: (AdapterRunner): No root taxonomy node was found, a root node must be included. For example, if your taxonomy dimension in your schema feed has the spec 'product.category', you must have a corresponding top-level node in the taxonomies feed with the node spec 'product.category'.
                com.endeca.edf.adapter.AdapterException: No root taxonomy node was found, a root node must be included. For example, if your taxonomy dimension in your schema feed has the spec 'product.category', you must have a corresponding top-level node in the taxonomies feed with the node spec 'product.category'.
                     at com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator.execute(TaxonomyGenerator.java:197)
                     at com.endeca.itl.fcm.integration.cadk.ConfigurationAdapter.execute(ConfigurationAdapter.java:118)
                     at com.endeca.esource.springadapter.SpringDelegateAdapter.execute(SpringDelegateAdapter.java:60)
                     at com.endeca.edf.adapter.AdapterRunner.run(AdapterRunner.java:168)
                     at com.endeca.edf.adapter.AdapterRunner.main(AdapterRunner.java:43)
                     
                ERROR     10/18/12 07:57:39.248 UTC (1350547059248)     FORGE     {baseline}: The java process evaluating the java manipulator class 'com.endeca.esource.springadapter.SpringDelegateAdapter' failed. Check the file 'D:\ATG\Endeca\Apps\ATGen\config\script\..\..\.\logs\forges\ConfigurationGeneratorForge\Edf.Pipeline.RecordPipeline.JavaManipulator.ConfigurationAdapter.log' for more information.     
                INFO     10/18/12 07:57:39.248 UTC (1350547059248)     FORGE     {baseline}: Processed 0 records.     
                ...............................

                ConfigurationGeneratorForge.start.log
                ..................................................
                WARN     10/18/12 07:57:37.139 UTC (1350547057138)     FORGE     {baseline}: (com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator): Skipping dval record missing dimension spec 'dimval.dimension_spec': [dimval.prop.category.ancestorCatalogIds=masterCatalog, %XEF%XBB%XBFdimval.dimension_spec=product.category, dimval.prop.category.rootCatalogId=masterCatalog, dimval.prop.category.siteId=storeSiteUS, dimval.display_name=Accessories, dimval.parent_spec=rootCategory.catMen, dimval.prop.category.repositoryId=catMenAccessories, dimval.qualified_spec=product.category:rootCategory.catMen.catMenAccessories, dimval.display_order=4, dimval.prop.category.catalogs.repositoryId=masterCatalog, dimval.spec=rootCategory.catMen.catMenAccessories]     
                WARN     10/18/12 07:57:37.140 UTC (1350547057139)     FORGE     {baseline}: (com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator): Skipping dval record missing dimension spec 'dimval.dimension_spec': [dimval.prop.category.ancestorCatalogIds=masterCatalog, %XEF%XBB%XBFdimval.dimension_spec=product.category, dimval.prop.category.rootCatalogId=masterCatalog, dimval.prop.category.siteId=storeSiteUS, dimval.display_name=Jackets, dimval.parent_spec=rootCategory.catMen, dimval.prop.category.repositoryId=catMenJackets, dimval.qualified_spec=product.category:rootCategory.catMen.catMenJackets, dimval.display_order=3, dimval.prop.category.catalogs.repositoryId=masterCatalog, dimval.spec=rootCategory.catMen.catMenJackets]     
                WARN     10/18/12 07:57:37.141 UTC (1350547057140)     FORGE     {baseline}: (com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator): Skipping dval record missing dimension spec 'dimval.dimension_spec': [dimval.prop.category.ancestorCatalogIds=masterCatalog, %XEF%XBB%XBFdimval.dimension_spec=product.category, dimval.prop.category.rootCatalogId=masterCatalog, dimval.prop.category.siteId=storeSiteUS, dimval.display_name=Pants, dimval.parent_spec=rootCategory.catMen, dimval.prop.category.repositoryId=catMenPants, dimval.qualified_spec=product.category:rootCategory.catMen.catMenPants, dimval.display_order=1, dimval.prop.category.catalogs.repositoryId=masterCatalog, dimval.spec=rootCategory.catMen.catMenPants]     
                WARN     10/18/12 07:57:37.142 UTC (1350547057141)     FORGE     {baseline}: (com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator): Skipping dval record missing dimension spec 'dimval.dimension_spec': [dimval.prop.category.ancestorCatalogIds=masterCatalog, %XEF%XBB%XBFdimval.dimension_spec=product.category, dimval.prop.category.rootCatalogId=masterCatalog, dimval.prop.category.siteId=storeSiteUS, dimval.display_name=Shirts, dimval.parent_spec=rootCategory.catMen, dimval.prop.category.repositoryId=catMenShirts, dimval.qualified_spec=product.category:rootCategory.catMen.catMenShirts, dimval.display_order=0, dimval.prop.category.catalogs.repositoryId=masterCatalog, dimval.spec=rootCategory.catMen.catMenShirts]     
                INFO     10/18/12 07:57:37.165 UTC (1350547057164)     FORGE     {baseline}: (com.endeca.itl.recordstore.forge.RecordStoreSource$RecordStoreSourceExecutor): Committed transaction 2     
                WARN     10/18/12 07:57:38.204 UTC (1350547058204)     FORGE     {baseline}: RecordAdapter 'LoadDimValsCsv': file 'D:\ATG\Endeca\Apps\ATGen\config\api_input\dimension_values.csv' is empty or does not exist.     
                WARN     10/18/12 07:57:38.207 UTC (1350547058206)     FORGE     {baseline}: (com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator): Skipping dval record missing dimension spec 'dimval.dimension_spec': [dimval.prop.category.ancestorCatalogIds=masterCatalog, %XEF%XBB%XBFdimval.dimension_spec=product.category, dimval.prop.category.rootCatalogId=masterCatalog, dimval.prop.category.siteId=storeSiteUS, dimval.display_name=Shorts, dimval.parent_spec=rootCategory.catMen, dimval.prop.category.repositoryId=catMenShorts, dimval.qualified_spec=product.category:rootCategory.catMen.catMenShorts, dimval.display_order=2, dimval.prop.category.catalogs.repositoryId=masterCatalog, dimval.spec=rootCategory.catMen.catMenShorts]     
                ERROR     10/18/12 07:57:38.207 UTC (1350547058206)     FORGE     {baseline}: (AdapterRunner): No root taxonomy node was found, a root node must be included. For example, if your taxonomy dimension in your schema feed has the spec 'product.category', you must have a corresponding top-level node in the taxonomies feed with the node spec 'product.category'.
                com.endeca.edf.adapter.AdapterException: No root taxonomy node was found, a root node must be included. For example, if your taxonomy dimension in your schema feed has the spec 'product.category', you must have a corresponding top-level node in the taxonomies feed with the node spec 'product.category'.
                     at com.endeca.itl.fcm.integration.cadk.ifdi.TaxonomyGenerator.execute(TaxonomyGenerator.java:197)
                     at com.endeca.itl.fcm.integration.cadk.ConfigurationAdapter.execute(ConfigurationAdapter.java:118)
                     at com.endeca.esource.springadapter.SpringDelegateAdapter.execute(SpringDelegateAdapter.java:60)
                     at com.endeca.edf.adapter.AdapterRunner.run(AdapterRunner.java:168)
                     at com.endeca.edf.adapter.AdapterRunner.main(AdapterRunner.java:43)
                     
                ERROR     10/18/12 07:57:39.248 UTC (1350547059248)     FORGE     {baseline}: The java process evaluating the java manipulator class 'com.endeca.esource.springadapter.SpringDelegateAdapter' failed. Check the file 'D:\ATG\Endeca\Apps\ATGen\config\script\..\..\.\logs\forges\ConfigurationGeneratorForge\Edf.Pipeline.RecordPipeline.JavaManipulator.ConfigurationAdapter.log' for more information.     
                INFO     10/18/12 07:57:39.248 UTC (1350547059248)     FORGE     {baseline}: Processed 0 records.     
                ............................................



                STEP 3:

                I deleted files.Then run command *initialize_services.bat --force* and baseline index in */atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin/* from production configuration.
                But it doesn't help.The same error.Maybe I did something wrong when I described my integration steps above?

                And one more question:
                When I run */atg/endeca/index/commerce/ProductCatalogSimpleIndexingAdmin/* my folder forge_output is empty.I think that is why starting of Dgidx failed.It should be with some data.Am I right?

                Dgidx.log
                ..........
                FATAL     10/17/12 13:35:08.981 UTC (1350480908980)     DGIDX     {dgidx,baseline}     ENE Indexer: No records file found.
                ..................     


                Thanks & Regards,
                Andrew
                • 5. Re: ATG Endeca CRS Integration baseline_update.bat issue
                  Ravi Honakamble|
                  Hi Andrew,

                  Looks strange to me.

                  Did you find any Error logged into in D:\ATG\Endeca\Apps\ATGen\config\script\..\..\.\logs\forges\ConfigurationGeneratorForge\Edf.Pipeline.RecordPipeline.JavaManipulator.ConfigurationAdapter.log?

                  Few more questions - Did you do any modification at ATG tables or trying to run BU with default CRS data? Any modification in /atg/endeca/index/commerce/product-sku-output-config.xml file?

                  I am suspecting either Data causing the issue or some jar's missing at FCM. Just check what else you can get from the forge logs. I am sure it will help to troubleshoot the issue.

                  Regards,
                  Ravi
                  • 6. Re: ATG Endeca CRS Integration baseline_update.bat issue
                    967507
                    No I didn't modify ATG tables and /atg/endeca/index/commerce/product-sku-output-config.xml file.
                    • 7. Re: ATG Endeca CRS Integration baseline_update.bat issue
                      Ravi Honakamble|
                      Did you find any Error logged into D:\ATG\Endeca\Apps\ATGen\config\script\..\..\.\logs\forges\ConfigurationGeneratorForge\Edf.Pipeline.RecordPipeline.JavaManipulator.ConfigurationAdapter.log file?
                      • 8. Re: ATG Endeca CRS Integration baseline_update.bat issue
                        Shreyas Ram R
                        Hi Guys

                        I am shreyas.
                        For this issue,kindly verify whether you have checked "Require data" in your "Record Adapter" you are using.

                        Regards
                        Shreyas

                        Edited by: 966473 on Oct 19, 2012 11:28 AM

                        Edited by: Shreyas Ram R on Feb 27, 2013 9:43 PM
                        • 9. Re: ATG Endeca CRS Integration baseline_update.bat issue
                          967507
                          Edf.Pipeline.RecordPipeline.JavaManipulator.CASDataFeed.log in folder /logs/forge

                          Can't load log handler "com.endeca.soleng.eac.toolkit.logging.RelativePathFileHandler"
                          java.io.IOException: Couldn't get lock for d:\ATG\Endeca\Apps\ATGen\/logs/Discoveren.%u.%g.log
                          java.io.IOException: Couldn't get lock for d:\ATG\Endeca\Apps\ATGen\/logs/Discoveren.%u.%g.log
                               at java.util.logging.FileHandler.openFiles(FileHandler.java:372)
                               at java.util.logging.FileHandler.<init>(FileHandler.java:237)
                               at com.endeca.soleng.eac.toolkit.logging.RelativePathFileHandler.<init>(RelativePathFileHandler.java:93)
                               at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
                               at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
                               at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
                               at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
                               at java.lang.Class.newInstance0(Class.java:355)
                               at java.lang.Class.newInstance(Class.java:308)
                               at java.util.logging.LogManager$7.run(LogManager.java:919)
                               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 com.endeca.edf.adapter.AdapterRunner.run(AdapterRunner.java:137)
                               at com.endeca.edf.adapter.AdapterRunner.main(AdapterRunner.java:43)


                          No error in file D:\ATG\Endeca\Apps\ATGen\config\script\..\..\.\logs\forges\ConfigurationGeneratorForge\Edf.Pipeline.RecordPipeline.JavaManipulator.ConfigurationAdapter.log file

                          Folder forge_output is empty.I think it's main reason why Dgidx.log is failed
                          • 10. Re: ATG Endeca CRS Integration baseline_update.bat issue
                            Ravi Honakamble|
                            Hi Andrew,

                            From log it looks like it is looking for Discoveren.log file and not able to find it. Did you see that file in the mentioned folder? If it is not there then change the log file name.

                            you can do the changes in ATGen\config\script\logging.properties
                            Example: com.endeca.soleng.eac.toolkit.logging.RelativePathFileHandler.pattern=logs/ATGen.%u.%g.log

                            FYI
                            In windows if you keep log files open during Baseline update Don't forget to try the steps mentioned by me in previous conversation.

                            Let me know if that helps.

                            Regards,
                            Ravi
                            • 11. Re: ATG Endeca CRS Integration baseline_update.bat issue
                              967507
                              I reinstall application again and I don't have exceptions at all.Right now I have only

                              Dgidx.log
                              .......................................................................
                              XMLParser: Reading language stemming settings from file "D:\ATG\Endeca\apps\ATGen\data\forge_output\ATGen.stemming.xml"
                              XMLParser: Done reading per-language stemming settings from file "D:\ATG\Endeca\apps\ATGen\data\forge_output\ATGen.stemming.xml"
                              XMLParser: Reading word forms from file "d:\ATG\Endeca\MDEX\6.2.2\conf\stemming\en_word_forms_collection.xml"
                              XMLParser: Done reading word forms from file "d:\ATG\Endeca\MDEX\6.2.2\conf\stemming\en_word_forms_collection.xml". There are 50374 word forms.
                              XMLParser: Reading language config from file "D:\ATG\Endeca\apps\ATGen\data\forge_output\ATGen.languages.xml"
                              XMLParser: Done reading language config from file "D:\ATG\Endeca\apps\ATGen\data\forge_output\ATGen.languages.xml"
                              XMLParser: Reading stop words from file "D:\ATG\Endeca\apps\ATGen\data\forge_output\ATGen.stop_words.xml"
                              XMLParser: Done reading stop words from file "D:\ATG\Endeca\apps\ATGen\data\forge_output\ATGen.stop_words.xml", finished in 0.000553 seconds.
                              FATAL     10/22/12 13:08:40.538 UTC (1350911320538)     DGIDX     {dgidx,baseline}     ENE Indexer: No records file found.     

                              Dgidx.start.log
                              WARN     10/22/12 13:08:39.986 UTC (1350911319986)     DGIDX     {dgidx,baseline}     Notice: the '--tmpdir' option has been deprecated; see the product documentation for more details.

                              Edited by: Andrew Karzhou on Oct 22, 2012 4:12 PM