Skip to main content

ATG Search - how to create a search project

Here I am going to explain how we can create a new ATG search project.

It involves 3 steps --> Specify the general search project settings, Specify the content of search indexing and Build the index.


Below I am elaborating the different steps involved with screen shots :

1. Go to Search Project Administration ui @  BCC and Click the button "New Search Project" to create a new search project.


2. Specify the search project name, give description and click the button "Create Search Project".


3. Click the button "Add Content" to add the search project content.


4. Specify the content name, select the content type and specify the IndexingOutputConfig path if the content type is ATG repository. Specify the remote host and port if you are using another server for fetching the content.


5. Click the content in the left side and expand the advanced option to specify the language and other customizations.



6. Click the environments in the left side and you could see the environments.You can add/remove a new Production/Staging environment.


7. Click on the Environment name to specify the host where you want to run the search engine. Here you could add more search engine hosts.


8. After you specify all these details, click on the build index button to build the search index and to complete the search project creation.






Comments

  1. Hi Sony, This is a wonderful blog. lot of help items. can you please tell me.. when i do the index i get the following error.. doing it in local

    atg.repository.search.indexing.IndexingException: /atg/repository/search/indexing/IndexingOutputConfig: java.lang.NullPointerException
    at atg.searchadmin.adapter.content.impl.RepositorySource.run(RepositorySource.java:496)
    at java.lang.Thread.run(Thread.java:595)
    Caused by :atg.repository.search.indexing.IndexingException: java.lang.NullPointerException
    at atg.repository.search.indexing.BulkLoaderImpl.bulkLoad(BulkLoaderImpl.java:831)
    at atg.repository.search.indexing.IndexingOutputConfig.bulkLoad(IndexingOutputConfig.java:1187)
    at atg.repository.search.indexing.IndexingOutputConfig.bulkLoad(IndexingOutputConfig.java:1162)
    at atg.searchadmin.adapter.content.impl.RepositorySource.run(RepositorySource.java:482)
    at java.lang.Thread.run(Thread.java:595)
    Caused by (#2):java.lang.NullPointerException
    at atg.repository.search.indexing.BulkLoaderImpl.loadPagedIteration(BulkLoaderImpl.java:424)
    at atg.repository.search.indexing.BulkLoaderImpl.bulkLoad(BulkLoaderImpl.java:748)
    at atg.repository.search.indexing.IndexingOutputConfig.bulkLoad(IndexingOutputConfig.java:1187)
    at atg.repository.search.indexing.IndexingOutputConfig.bulkLoad(IndexingOutputConfig.java:1162)
    at atg.searchadmin.adapter.content.impl.RepositorySource.run(RepositorySource.java:482)
    at java.lang.Thread.run(Thread.java:595)

    Any clue?

    ReplyDelete
  2. which ATG and ATG search vresion you are using ? Check your IndexingOutputConfig definition xml file . Just try to laod the file in a browser and check for any data error.

    ReplyDelete

Post a Comment

Popular posts from this blog

ATG Search Indexing - overview of different steps in search indexing

Read more about the search indexing behind the scene steps @  http://tips4ufromsony.blogspot.in/2011/12/atg-search-indexing-behind-scene-steps.html ATG Search prepares searchable content by indexing the products specified in the XML definition file (/atg/commerce/search/ProductCatalogOutputConfig). Generally there are two types of indexing 1.  Full Indexing  --> all data taken for indexing 2.  Incremental Indexing --> only changed data will be taken for indexing When full indexing is triggered, following happens:    1. The out of box component BulkLoader will call IndexedItemsGroup.getGroupMembers() to load the products to the XHTL document. It prevents uncategorized products from getting indexed. The definition file format begins with a top-level item as a product and includes the properties of parent category and childskus. For each product, the set of Variant Producers configured in ProductCatalogOutputConfig is execute...

Google Chrome shortcut keys

If you are a Google Chromey guy, please find below the list of shortcut keys for some of the most used features  :-) Find more shortcut keys @  http://www.google.com/support/chrome/bin/static.py?page=guide.cs&guide=25799&topic=28650

ATG search and Monitoring the request and response

To get an idea of the SearchEngineActivity logs, please read the blog :  http://tips4ufromsony.blogspot.com/2012/01/atg-search-and-search-engine-activity.html Other than using the SearchEngineActivity logs, we could monitor the search engine request/reponse  by enabling the monitoring in the SearchEngineService component @ /dyn/admin/nucleus/atg/search/routing/SearchEngineService. Once you enable this "monitoringEnabled", each request/response and the response time like last response time and average response time can be found @ SearchEngineService component. After you send a request to the search engine, just refresh the SearchEngineService component and you could see that the total command count will be incremented by one and the response time also get updated. If you click this total command count, a new window will be opened with the request and response details.

Eclipse plug-in to create Class and Sequence diagrams

ModelGoon is an Eclipse plug-in avaiable for UML diagram generation from Java code. It can be used to generate Package Dependencies Diagram, Class Diagram, Interaction Diagram and Sequence Diagram. You coud get it from http://marketplace.eclipse.org/content/modelgoon-uml4java Read more about it and see some vedios about how to create the class and sequence diagram @ http://www.modelgoon.org/?tag=eclipse-plugin Find some snapshots below which gives an idea about the diagram generation.

ATG Search - search engine tuning settings

In this blog, I am going to list the best tuning settings for ATG Search engine. The AESoapConfig.xml, AESoapWaspConfig.xml  and AEConfig.xml are the xmls referred below and you can find it @  <ATG_DIR>\<Searchx.x>\SearchEngine\<operating_system>\bin\ folder. (1)  Make sure that the AESoapConfig.xml's rwTimeout is less than or equal to routing's readTimeoutMs. You could find the routing's readTimeoutMs @ atg\search\routing\SearchEngineService component.               rwTimeout is the  length of time in seconds to wait before a read or write operation times out on an active connection. The number can be decreased to improve performance. However, a value that is too low could cause slow connections to be prematurely closed. (2)  Adjust the number of engine threads to match the number of CPUs available to the engine. Note that the minimal value for maxThreads and maxSpar...