ATG deprecated code (till ATG 10)

ATG Deprecated Code (till ATG 10)

Technology	Deprecated as of	Notes
ACC Reporting functionality	ATG 2007.2, 9.2, 10.0.1
Oracle WebLogic and IBM WebSphere JMS Providers	ATG 10.0	This includes the WebLogic.JMSProvider and WebSphere.JMSProvider modules
Support for CA deployment to prior versions	ATG 10.0	CA will only support deployments to the same version
Standard Commerce Catalogs	ATG 10.0	Standard Catalogs are deprecated in favor of Custom Catalogs
Pioneer Cycling Reference Application	ATG 10.0	Replaced by Commerce Reference Store application
Cache Switch Hot (cacheSwitchHot)	ATG 10.0
.NET Client Software	ATG 10.0
Facet Droplets	ATG 9.0	The FacetSearchDroplet is deprecated in favor of using the atg.search.formhandlers.QueryFormHandler to issue faceted search queries. As of ATG 10.0, the FacetSearchDroplet will be removed entirely and any use of this droplet must be updated to use QueryFormHandler instead. Note that the FacetTrailDroplet has not been deprecated and is still used to construct facet trails.
Response Management	ATG 2007.1	All versions of Response Management have reached End-of-Life status on November 1, 2009. As of ATG 10.0, all Response Management code will have been removed from the ATG products.
Relational Views	ATG 6.0	Relational Views are deprecated in favor of ATG Repositories.
HTML and XML Repositories	ATG 6.0	Deprecated in favor of SQL/File System Connector (SQL Content Repository with Content Repository Loader)

Comments

Eclipse plug-in to create Class and Sequence diagrams

ModelGoon is an Eclipse plug-in avaiable for UML diagram generation from Java code. It can be used to generate Package Dependencies Diagram, Class Diagram, Interaction Diagram and Sequence Diagram. You coud get it from http://marketplace.eclipse.org/content/modelgoon-uml4java Read more about it and see some vedios about how to create the class and sequence diagram @ http://www.modelgoon.org/?tag=eclipse-plugin Find some snapshots below which gives an idea about the diagram generation.

ATG Search Indexing - behind the scene steps explained

Read more about the search indexing @ http://tips4ufromsony.blogspot.com/2011/11/atg-search-architectural-flow-search.html ATG search indexing involves index file creation, deploying and copying the index file to the search engine's box. The steps can be divided into Initial stage, Preparing Content, Indexing and Deploying. Please find below the detailed analysis of each step. 1. Initial stage: a. Check whether the folder deployshare configured correctly @ LaunchingService.deployShare ( \atg\search\routing\LaunchingService.deployShare ). Lets assume that it is configured to \Search2007.1\SearchEngine\i686-win32-vc71\buildedIndexFiles. b. Lets assume that the index file folder ( \Search2007.1\SearchEngine\i686-win32-vc71\indexFiles) has the following segments (folders) currently : 66900...

Eclipse Kepler - good features of Eclipse 4.3 ( Eclipse Kepler ) JDT / Workbench

Detached windows with sash When you detach a view or editor into its own separate window, it now has all the capabilities of a normal workbench window. They now support multiple stacks of views separated by sashes with arbitrary layouts. The detached parts will remain synchronized with the master window that they were detached from. This is especially handy for people developing with two or more monitors, so they can spread views across several monitors and keep them synchronized. Import nested projects The Import Projects wizard now has an option to continue searching for projects to import recursively within any project it finds. This allows you to import physically nested projects at the same time. Open Resource dialog enhancements The Open Resource (Ctrl+Shift+R) dialog now offers direct access to the Show In and Open With menus via drop-down buttons. On platforms that support mnemonics, the buttons are also accessible via Alt+W and Alt+H. Whole word option...

Basic design decisions for a commerce search setup ( with an ATG Search view)

In this blog I would like to explain the basic set of configuration/design decisions needed to setup an ATG search project. Most of these design decisions are common for all Enterprise search applications. 1. Decide the searchable properties : This means the properties that the business want the user to search in the ecommerce platform. In ATG search these are configured as the text properties in the product-catalog-output-config.xml ( the definitionFile of the \atg\commerce\search\ProductCatalogOutputConfig). Usually the displayName of product/sku, displayName of department/category/sub-category, skuId, brandName are the properties configured as searchable. 2. Decide the search refinement properties or the faceted properties : After a user search for a keyword, search refinement is the next step done to filter his results. ATG supports the search refinement using the Faceted Search concept. Read more about facted search @...

ATG Search architectural flow : Search and Index

I would like to explain the high level ATG Search implementation architecture ( for an online store) through the above diagram. In this diagram 1.x denotes the search functionality and 2.x denotes the indexing functionality. I have given JBoss as the application server. Physical Boxes and Application Servers in the diagram ( as recommended by ATG ) : Estore ( Commerce ) Box --> The box with the estore/site ear (with the site JSPs and Java codes). Search Engine Box --> The box with the search engine application running. Indexing Engine Box --> The box with the indexing engine application running. CA (Content Administration) Box --> The box with the ATG CA ear ( where we could take CA -BCC - Search Administration and configure the search projects) . Search Indexer Box --> The box with the ATG Search Index ear ( to fetch the index data from repository). Note that the engine performing indexing will need access ...

Tips from Sony Thomas

Search This Blog