ATG Search BCC Module Configurations

-
BCC Module (BCC Server)

Put the below three files on this location ->C:\ATG\ATGXXX\BCC_Module\config\atg\commerce\search
ProductCatalogOutputConfig.properties

indexingSynchronizations+=/atg/commerce/search/refinement/RefinementConfigurationSubmitter
loggingDebug=true

product-catalog-output-config.xml
This is a xml file where you will specify the indexing parameters.
ProductCatalogQueryFormHandler.properties

loggingDebug=true
siteName=staging environment 0 (TestSearchProj)
relQuestSettings=activeSolutionZones^=/atg/commerce/search/ProductCatalogOutputConfig.textActiveZones
docProps=$repositoryId,childSKUs.displayName,childSKUs.description

Make sure the initial.properties under C:\ATG\ATGXXX\BCC_Module\config\atg\dynamo has the following entries.

/atg/commerce/search/ProductCatalogSearchService,\
/atg/commerce/search/ProductCatalogOutputConfig
Make sure the following files/folders present in the following location C:\ATG\ATGXXX\BCC_Module\config\atg\search\
Config folder - LanguageDimensionService.properties

languageMap=english=en,french=fr
locales=en,fr,en_US,fr_FR
repository folder - RefinementRepository_production.properties
dataSource=/atg/dynamo/service/jdbc/JTDataSource_production
routing folder – This folder has repository sub-folder,

LaunchingService.properties

repository sub-folder (C:\ ATG\ATGXXX\BCC_Module\config\atg\search\routing\repository )- LaunchingService.properties

deployShare=D:\\ATG\\ATGXXX\\SearchXXX\\DeployShare
engineDir=D:\\ATG\\ATGXXX\\SearchXXX\\SearchEngine
Make sure the SearchJTDataSource.properties under C:\ATG\ATGXXX\BCC_Module\config\atg\search\ service has the below content.

componentPath=/atg/dynamo/service/jdbc/JTDataSource_production

Make sure the SearchAdminRepository.properties under C:\ ATG\ATGXXX\BCC_Module\config\atg\searchadmin has the below content.

dataSource=/atg/dynamo/service/jdbc/JTDataSource_production

Indexing

Important note: If you are adding new products/SKUs into BCC, the same products wouldn’t appear in the search results unless bulk-indexing is done via Search Project Administration in BCC.

Before you start the indexing, both the commerce and merchandiser server should be running successfully. Then, create a folder in C:\ATG\ATGXXX\SearchXXX with name ‘DeployShare’ and make it sharable.The path of this directory is specified in the Launching Service Component.


See the configurations for Commerce Module

Comments

Post a Comment

Popular posts from this blog

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more