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.






Labels:

Comments

  1. Kaushik24 May 2012 at 02:17

    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. Sony Thomas24 May 2012 at 10:11

    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

Basic design decisions for a commerce search setup ( with an ATG Search view)

In this blog I would like to explain the basic set of configuration/design decisions needed to setup an ATG search project. Most of these design decisions are common for all Enterprise search applications. 1. Decide the searchable properties :   This means the properties that the business want the user to search in the ecommerce platform. In ATG search these are configured as the text properties in the product-catalog-output-config.xml ( the definitionFile of the \atg\commerce\search\ProductCatalogOutputConfig). Usually the displayName of product/sku, displayName of department/category/sub-category, skuId, brandName are the properties configured as searchable. 2. Decide the search refinement properties or the faceted properties :   After a user search for a keyword, search refinement is the next step done to filter his results. ATG supports the search refinement using the Faceted Search concept. Read more about facted search @...
6 comments
Read more

ATG - more about Forms and Form Handlers

An ATG form is defined by the dsp:form tag, which typically encloses DSP tags that specify form elements, such as dsp:input that provide direct access to Nucleus component properties. Find below a sample dsp:form tag.    <dsp:form action="/testPages/showPersonProperties.jsp" method="post" target="_top">      <p>Name: <dsp:input bean="/samples/Person.name" type="text"/>      <p>Age: <dsp:input bean="/samples/Person.age" type="text" value="30"/>      <p><dsp:input type="submit" bean="/samples/Person.submit"/> value="Click to submit"/>    </dsp:form>   When the user submits the form, the /samples/Person.name property is set to the value entered in the input field.Unlike standard HTML, which requires the name attribute for most input tags; the name attribute is optional for DSP form element tags. If an input tag omits the n...
11 comments
Read more

ATG Search troubleshooting tips

In this blog, I have listed some basic ATG Search troubleshooting tips in some general scenarios. 1. If the index did not deploy, consider the following possible causes : Is the DeployShare property configured @ /atg/search/routing/LaunchingService component ?  Is enough space available @ deployment share box for the index ?  Are the RMI ports configured correctly in the RoutingSystemService component ?  If the search engine application is running in a separate box, this application is invoked through a RemoteLauncher running in these boxes. Check whether these RemoteLaunchers are running in these boxes ? 2. If you have trouble in launching one or more search engines, try the following remedies: If the Search engine is standalone, set the /atg/search/routing/LaunchingService component’s engineDir property to the absolute path of the Search engine directory.  3. Search unavailable in the estore page, even when the SearchEngine is in "Running" st...
5 comments
Read more

Search Facets - how to create a new search facets in ATG Search

A Facet is a search refinement element that corresponds to a property of a commerce item type. ATG supports the search result refinement using the Faceted Search concept. Read more about facted search @  http://en.wikipedia.org/wiki/Faceted_search . Facet can either be ranges or specific values. Each facet is stored in the RefinementRepository as a separate refineElement repository item. Facets are divided into Global and Local facets. Global facets apply to all the categories and local facets only to the category in which they are created. For example Price/Brand can be considered as the facets that are common for all skus and New Release/Coming Soon can be considered as the facets that are specific to Physical Media products like Vidoe/DVD/Blue-ray/Books. We can use the ATG BCC - Merchandising UI to create facets. The Faceting Property depends on the meta-properties defined in the \atg\commerce\search\product-catalog-output-config.xml ( the def...
4 comments
Read more

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.
8 comments
Read more