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

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 and Search engine activity log

We could use the SearchEngineActivity log files to get the request/response to the search engine from a commerce instance. This folder is located in each commerce instance or the instances from which the call to the search engine is done. The SearchEngineActivity log file folder can be configured @ SearchEngineService component ( /dyn/admin/nucleus/atg/search/routing/SearchEngineService). To get the log files for the search engine calls, you need to specify the SearchEngineService.dumpingRequests as true. Then you need to specify the engineActivityPath as the folder in which you need the SearchEngineActivity logs. Below you could find my SearchEngineActivity log folder. Each successful call to the search engine from the commerce instance will create 5 files in the SearchEngineActivity folder : namely  request, response, search engineinfo, stack trace and response row . Each file name start with a specific sequence. You ...
1 comment
Read more

JBoss - know more about the JBoss directory structure

Fundamentally, the JBoss architecture consists of the JMX MBean server, the microkernel, and a set of pluggable component services - the MBeans. The JBoss Application Server ships with three different server configurations. Within the <JBoss_Home>/server directory, you will find three subdirectories: minimal, default and all. The default configuration is the one used if you don’t specify another one when starting up the server. If you want to know which services are configured in each of these instances, look at the jboss-service.xml file in the <JBoss_Home>/server/<instance-name>/conf/ directory and also the configuration files in the <JBoss_Home>/server/<instance-name>/deploy directory. JBoss 4.0 features an embedded Apache Tomcat 5.5 servlet container. conf --> The conf directory contains the jboss-service.xml bootstrap descriptor file for a given server configuration. This has the jboss-log4j.xml file which configures the Apach...
Post a Comment
Read more

ATG Product Catalog schema ER diagram

Check out the O rder schema ER-Diagram @   http://tips4ufromsony.blogspot.in/2012/02/atg-order-schema-er-diagram.html Check out the User Profile  schema ER-Diagram @ http://tips4ufromsony.blogspot.in/2012/03/atg-user-profile-schema-er-diagram.html If you would like to know the relationship between different Product Catalog tables, please find below screen shots of  Product Catalog schema ER Diagrams.
3 comments
Read more

Search engine shutdown call from the Estore instnace

 When the estore or commerce instances are restarted the routing system service can send shut down requests to stale engines, this can be caused because of any of the following. 1. Some other instance marked the engine as stopped in the DB (This can be caused because the machine could not reach the host running the engine) 2. The eStore instance is using a different search schema that has data about the search engine host and is marked as stopped in that DB. To avoid this overrride \atg\search\routing\RoutingSystemService.properties by setting cleanUpStrayEng=false.
Post a Comment
Read more