Skip to main content

ATG search installation and search engine log files

Here I would like to explain how your ATG search folder structure looks like after you do the ATG search installation and also about the search engine log files.

To get the ATG search, you need to install the ATGSearch<version>Windows.exe after you do the ATG installation. When you install ATG search, the generated folders include an OS dependant folder. In the below screen shot, you could see the "i686-win32-vc71" folder and this is generated since the ATG search ins installed in a windows machine.


The ATG search engine is actually an exe file inside this "i686-win32-vc71" folder. Below screen shot give you an idea about the "atgsearch.exe", which is the search engine application. This search engine application (atgsearch.exe) is started by a remote launcher call from the BCC search administration UI. 



The log files like "atgsearch_20120106112413_568.log" are the search engine log files where you could see the engine logs like the index file used by the search engine,enigne load ,enigne throughput and query response time,.. You could enable the debug logging for the search engine to find the different request processing by the engine including the ip address of the requesting host. Also the search engine start and end time can be obtained from this log.



The engine log will show slow request based on the <SlowRequestThreshold> parameter in the AEConfig.xml, like <SlowRequestThreshold>5000</SlowRequestThreshold>. If you set engineLogLevel to D in launchingService component, you will be able to see the ip address of  of the requesting host.

                 engineLogLevel = D

Example of the search engine log with requesting host ip:
2011/03/22 11:12:59 : DEBUG : Server : 0 : Accept socket 12068 at port 4790 from IP 100.222.46.124
2011/03/22 11:12:59 : DEBUG : Server : 0 : AEXmlWorker::Shutdown
2011/03/22 11:12:59 : INFO : Server : 0 : Shutdown received
2011/03/22 11:12:59 : DEBUG : Server : 0 : Accept socket 12068 at port 4791 from IP 100.222.46.124
2011/03/22 11:12:59 : INFO : Server : 0 : Waiting for pending requests to complete.
2011/03/22 11:12:59 : INFO : Server : 0 : Exiting engine
2011/03/22 11:12:59 : INFO : Server : 0 : Scheduled shutdown.


Consider the following search engine log :

2011/03/11 09:36:35 : INFO : Server : 0 : load: 0.6875 throughput: 1.72804 q/s time: 6.60434 s

Load  of .6 means that 60% of the search engine thread are active. Throughput is the number of requests that the engine is able to server per second. Time is the average response time.

So load is specified as percentage and 0.6875 is roughly 69 percent of load, where as anything greater then 1 would suggest the search engine is overburden. Throughput is telling us how many requests the engines can handle across all the cores of the engine hosted box. So throughput is kind of like saying how many request can be placed into the bucket. But it doesn't say how fast the objects in the bucket are moving.



Labels:

Comments

  1. Unknown26 July 2012 at 23:48

    Hi,

    I have a problem with Service Center's search engines, ATGOrder and ATGProfile. Both has a scheduled shutdown at midday and midnight causing searches and live indexing to stop. How can I turn the scheduled shutdown off?

    Thanks in advance and good blog!

    ReplyDelete
  2. Sony Thomas26 August 2012 at 09:25

    you mean search engine for atgorder or for atgcatalogue ? U mean at midnight ur search engine s are going down ? Any scheduled search indexing is configured for the search engine ?

    ReplyDelete

Post a Comment

Popular posts from this blog

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

How to simulate Browser back button

When someone asks how to simulate a back button, they really mean to ask how to create a link that points to the previously visited page. Most browsers tend to keep a list of which websites the user has visited and in what order they have done so. The DOM window object provides access to the browser's history through the history object. Moving backward and forward through the user's history is done using the   back(), forward(), and go() methods of the  history  object. To move backward through history, just do window.history.back() ; This will act exactly like the user clicked on the Back button in their browser toolbar. Find below a sample html code: <html> <head> <script type="text/javascript"> function goBack(){  window.history.back() } </script> </head> <body>    <input type="button" value="Back" onclick="goBack()" /> </body> </html>
Post a Comment
Read more

Useful windows shortcut keys

Following are the most useful set of windows shortcut keys that I would like to share with you. run commands calc        -->  Calculator  mspaint   -->  To get Paint textpad   -->  To get Textpad if installed cmd        -->  Opens a new Command Window (cmd.exe)  control    -->  Displays Control Panel  msconfig   -->  Configuration to edit startup files  compmgmt.msc  -->  Computer management  fsmgmt.msc      -->  Folder Sharing Management  services.msc     -->   System Services  appwiz.cpl  --> Add/Remove Programs  ncpa.cpl     -->  Network Connections  %userprofile%  -->  Opens you User's Profile  %temp%  -->  Opens temporary file Folder  temp ...
1 comment
Read more

Jsp and CSS size limits that web developers need to aware

Here I am listing some erroneous cases that might occur in your web development phase, due to some size restrictions. JSP file size limit : You might get some run time exceptions that the JSP file size limit exceeds. Please find below the reason : In JVM the size of a single JAVA method is limited to 64kb. When the jsp file is converted to Servlet, if the jspservice method's size exceeds the 64kb limit, this exception will occur. Keep in mind that this exception depends on the implementation of the JSP translator, means the same JSP code may give an exception in Tomcat and may run successfully in Weblogic due to the the difference in the logic to built the Servlet methods from JSP. The best way to omit this issue is by using dynamic include.For example, if you are using                  <%@ include file="sample.jsp" %> (static include),  replace this to               ...
1 comment
Read more

JBoss - how to take thread dumps

Following are the different options in JBoss to take the thread dump. 1. Using JBoss jmx-console :    Got to http://localhost:8080/jmx-console  and search for the mbean " serverInfo " and click on that link. Click the  invoke mbean operation under listThreaddump() method. This will give you the current snapshot of threads which are running in your JBoss jvm. 2. By using twiddle :   In the commnad promt go to <JBOSS-HOME>/bin and run the command  twiddle.bat invoke "jboss.system:type=ServerInfo" listThreadDump > threadDump.html  and you could find the threadDump.html with the JBoss thread dump. 3. Using "Interrupt" signal :  Use kill -3 <process-id> to generate thread dump. You will find the thread dumps in server logs.
1 comment
Read more