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 maxSpareThreads is 2, which applies to running with 1 CPU. However, it is recommended to run with more than one CPU.
a) Set MaxThreads in AEConfig.xml to number of CPU's
b) Set maxSpareThreads in AESoapWaspConfig.xml to number of CPU's

maxThreads is the number of requests you can process simultaneously, and this generally should be the number of CPU's available to the engine. If this is higher than the CPUs, the engine will bog down, with slower response times.
maxSpareThreads is the number of worker threads to process requests simultaneously, generally this should be the same as MaxThreads.

(3) Disable the the keep-alive/connection reuse setting
a) Set reuseCount=0

reuseCount is the number of requests that may be accepted using the same connection. The number can be increased to reduce the frequency of opening new connections and improve performance. However, a value that is too high could prevent new connections from being accepted. A value of 0 disables connection reuse. This applies to HTTP 1.1 only.

Comments

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...

ATG CA - BCC home screen : how to add a new link

Activity source is the property which controls the links on the left nav on the BCC home screen. All activity sources are registered with the ActivityManager component at /atg/bizui/activity/ActivityManager . When rendering the BCC home page, the ActivityManager cycles through all the registered ActivitySource components and displays left navigation links for each of them on the BCC home page. For example if I want to add a new link "My New Link" , below screen shots exaplins how this can be done 1. Add activityManager.properties to specify the activityresources. In this activityManager, I specified one MyActivitySource. 2. Add MyActivitySource.properties to specify the name of the link and the other details . Here it refers to a bundle properties file. 3. Add the bundle properties file to specify the name of the link. 4. Now you could see the new link...

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 ...

GC Log Analyzer from IBM

This blog is about the GC( garbage collection) log analyzer from IBM. If you have a GC log and you want to analyze the file, this IBM tool will help you with some graphical analyzer and some recommendations. You can download it from the following URL : https://www.ibm.com/support/pages/ibm-pattern-modeling-and-analysis-tool-java-garbage-collector-pmat Please find below some screenshots and details that might help you. 1. Screenshot 1: 2. Screenshot 2 : 3. Screenshot 3 : 4. Screenshot 4:

ATG Search and startRemoteLauncher

If the search engine application is running in a separate box than the ATG CA-BCC deployed server, the search engine is invoked through a remoteLauncher running in these boxes. Means, a remoteLauncher needs to run in the host where SearchEngine is installed remotely to start the search engine. You could find the startRemoteLauncher.sh @ ATG/ATG2007.1/Search2007.1/SearchAdmin/bin/startRemoteLauncher.sh Start remoteLauncher using the command ./startremotelauncher.sh –p <RMI Launcher service Port > & The Launcher Service Port on the host machine can be found in BCC @ Search Administration>Projects > Search Project: gmri_search_en_CA > Environments > Host Machine: > Advanced Settings. If the startRemoteLanucher reports a BindingException , then you need to find the process that is using the launchServicePort. For that run the netstat command like : netstat -an |grep 10880 Then inorder to identify the process t...

Tips from Sony Thomas

Search This Blog