Catalog Maintenace Service Console Output

-
12:55:11,015 INFO [CatalogMaintenanceService] Service CatalogMaintenance - processing functions: AGS_GENPROPERTIES
12:55:11,104 INFO [CatalogMaintenanceService] Service Lock CatalogMaintenance obtained for service CatalogMaintenance.
12:55:11,110 INFO [AncestorGeneratorService] Service AncestorGenerator - processing functions: AGS_GENPROPERTIES
12:55:11,110 INFO [AncestorGeneratorService] TreeWalkUpdateService:performService starting.
12:55:11,110 INFO [AncestorGeneratorService] Update Catalogs: started at Mon Jun 18 12:55:11 IST 2012
12:55:11,116 INFO [AncestorGeneratorService] Executing count queries for base catalogs, categories and folders.
12:55:11,118 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to process base catalogs.
12:55:11,118 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree ended processing of base catalogs.
12:55:11,120 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to process base categories.
12:55:11,365 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree ended processing base categories.
12:55:11,367 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to process base catalog folders.
12:55:11,367 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree ended processing of base catalog folders.
12:55:11,367 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to update repository for catalogs and categories.
12:55:11,516 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree update to repository ended for catalogs and categories.
12:55:11,516 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to update repository for products and skus.
12:55:11,518 INFO [AncestorGeneratorService] updateProducts: starting to process products.
12:55:11,518 INFO [AncestorGeneratorService] Product range builder loop
12:55:11,519 INFO [AncestorGeneratorService] Execution of rangebean query starting at:0 using query:all with starting index:0
12:55:11,546 INFO [AncestorGeneratorService] Execution of rangebean query completed.
12:55:11,655 INFO [AncestorGeneratorService] Creating UpdateProductRange object:missing_product - prod2001
12:55:11,657 INFO [AncestorGeneratorService] Update thread started for range missing_product to prod2009
12:55:12,054 INFO [AncestorGeneratorService] Finished update of data.
12:55:12,076 INFO [AncestorGeneratorService] updateProducts: finished processing product requests.
12:55:12,077 INFO [AncestorGeneratorService] updateSkus: starting to process skus.
12:55:12,092 INFO [AncestorGeneratorService] Sku range builder loop
12:55:12,092 INFO [AncestorGeneratorService] Execution of rangebean query starting at:0 using query:all with starting index:0
12:55:12,108 INFO [AncestorGeneratorService] Execution of rangebean query completed.
12:55:12,118 INFO [AncestorGeneratorService] Creating UpdateSkuRange object:missing_product_sku - sku50001
12:55:12,120 INFO [AncestorGeneratorService] Update thread started for range missing_product_sku to sku50111
12:55:12,121 INFO [AncestorGeneratorService] Sku Range calculation completed.
12:55:13,541 INFO [AncestorGeneratorService] Finished update of data.
12:55:13,559 INFO [AncestorGeneratorService] updateSkus: finished thread.
12:55:13,559 INFO [AncestorGeneratorService] updateSkus: finished processing skus.
12:55:13,559 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree update to repository ended for products and skus.
12:55:13,559 INFO [AncestorGeneratorService] Update Catalogs: ended at Mon Jun 18 12:55:13 IST 2012
12:55:13,559 INFO [AncestorGeneratorService] Update Catalogs: total processing time is seconds: 2
12:55:13,559 INFO [AncestorGeneratorService] TreeWalkUpdateService:performService finished in 2 seconds.
12:55:13,560 INFO [CatalogMaintenanceService] Service Lock CatalogMaintenance released for service CatalogMaintenance.

See different ways to update catalog structure

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

remote debug in eclipse with both Admin and Managed Servers running

-
For configuring Remote Debug in Managed Weblogic Server,the very first golden rule is,you should not specify any port number of  weblogic admin or  managed server which is running ,it has to be a free port(use this link to find the appropriate ports List of Ports ). How to create managed weblogic server and run multiple EAR's can be found in this link -> Run Multiple Ear in Managed Server Mode How to run remote debug in Admin server can be found in the link -> Remote Debugging Weblogic Admin Server The configuration  for remote debug is specified in the startup script 'setDomainEnv.cmd'. First Approach Here we need to  create three scripts corresponding to the orignial scritps,'startManagedWeblogic.cmd', 'startWeblogic.cmd' and 'setDomainEnv.cmd. For Eg: Create the scripts  startManagedATGProductionWeblogic.cmd, startWeblogicATGProduction.cmd, setDomainEnvATGProduction.cmd by copying fr...
Read more

Oracle Recommended Approach for ATG10.1.2 Siebel 8.1.1.10 Integration

-
Oracle has provided the code base for atg siebel integration, this code base is an enhanced version of the current CRS implementation we have for user registration,order capture and product configurator. Configuration Steps Extract the given integration code to your atg folder (eg:C:\ATG\ATG10.1.2) Set up the project in your eclipse,you can setup this as  an existing ATG Project Once you Run the siebelBuild.xml with the ant task "all-with-ws" a new Folder Siebel will be created in your atg root path (eg:C:\ATG\ATG10.1.2) There will also a SiebelWS folder created with a SiebelWS.ear file inside your newly created Siebel folder. Create an ear using runAssembler for the Siebel web application by specifying either the module -m Siebel.PublishingAgent or Siebel.Versioned based on whether running application in Production or Publishing Run the necessary scripts in production publishing and switching schemas. Define the Webservice endpoints. Run the Application !! See h...
Read more