Issues while creating a search project in BCC

Question

Hi There,
Migrating the apps from 2007.3 to 10.0.3.Experiencing issues while creating a search project.
Step #1.In Search Administration,navigating through Project > Global Settings & creating a Content Label named as "Catalog"
Step #2.Navigating through Project > Create Production Project.Creating a project with Content Set as "CatalogSet"
Step #3.Adding a Content with this info:
          Content Name: Catalog
          Type of Content : ATG Repository
          IndexingOutputConfig Path : /atg/commerce/search/ProductCatalogOutputConfig
          Host name : localhost
          RMI : 10160 ( RMI port of commerce instance)
     Creating a content & getting the message as New Content "CatalogTest" has been created.
     Issue #1: Content is not displaying in the Content eventhough content has been created successfully.
     Issue #2: Getting error for "Default Text Processing Options"
     You can refer these issues in the attached screenshot "Content-Page-with-error.jpg"
Step #4.Creating a new TPO as "English" & trying to "Associate Search Project" & getting an error.Refer the attached error log "Associate-Search-Project.log"
Due to these issues, "Build Index" button is disabled.Did anybody experienced these issues? Any help/comments are appreciated.
Also attached the full server logs as commerce-server.log & publishing-server.log.
Since no options for attachment in this forum, I posted the attachment in this link.Please refer it.
https://groups.google.com/forum/?fromgroups#!topic/atg_tech/csEHi-x3Nyc
Thanks in advance!
Mani
Edited by: user11263665 on Apr 25, 2012 10:38 PM

Answer 1

We faced the same problem when migrating from 2007 to ATG 10.0.3. The reason this error comes up is because the Search depends on a local customization adapter /atg/searchadmin/adapter/customization/LocalCustomizationDataAdapter which adds English as a language in the text processing options.
After the migration you need to import the initial ATG search related data into your Search schema. These instructions have been mentioned in the ATG install guide. Here is the extract from the docs.
Note: The import scripts import data using startSQLRepository. Make sure your JTDataSource and
FakeXADatasource are configured to permit this in home/localconfig. JTDataSource should automatically
point to FakeXADataSource. FakeXADataSource should point to the administration database, and
FaxeXADataSource_production should point to the production database. Note that some product
installation processes, including Oracle ATG Web Knowledge Manager Self Service, need FakeXADataSource
pointed at the production database, so you may need to change the FakeXADataSource between installations.
once you are done with the configurations above, import only the searchadmindata xml into search schema as this imports the LocalCustomizationDataAdapter config information into your search schema. Once this is done, you should be good to index.
<ATG10dir>\home\bin\startSQLRepository.bat|sh -m SearchAdmin.AdminUI
-repository /atg/searchadmin/SearchAdminRepository -import
<ATG10dir>\Search10.1\SearchAdmin\common\data\initial\searchadmindata.
xml