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

ATG - quick reference to commonly used DSP Tags

In this blog, I would like to give a quick reference to the most commonly used DSP Tags.Note that in this DSP tag details : bean refers to a Nucleus path, component name, and property name param refers to a Page parameter value refers to a Static-value var refers to a EL variable id refers to a scripting variable ============================================================== 1.dsp:importbean example: <dsp:importbean bean="/atg/dynamo/droplet/Switch"/> ============================================================== 2.dsp:page usage: It encloses a JSP. The dsp:page invokes the JSP handler, which calls the servlet pipeline and generates HTTPServletRequest. example: <dsp:page> ..... </dsp:page> ============================================================== 3.dsp:include usage: Embeds a page fragment in a JSP. example: <dsp:include src="/myPage/Result...

ATG - more about Forms and Form Handlers

An ATG form is defined by the dsp:form tag, which typically encloses DSP tags that specify form elements, such as dsp:input that provide direct access to Nucleus component properties. Find below a sample dsp:form tag. <dsp:form action="/testPages/showPersonProperties.jsp" method="post" target="_top"> <p>Name: <dsp:input bean="/samples/Person.name" type="text"/> <p>Age: <dsp:input bean="/samples/Person.age" type="text" value="30"/> <p><dsp:input type="submit" bean="/samples/Person.submit"/> value="Click to submit"/> </dsp:form> When the user submits the form, the /samples/Person.name property is set to the value entered in the input field.Unlike standard HTML, which requires the name attribute for most input tags; the name attribute is optional for DSP form element tags. If an input tag omits the n...

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

ATG - how to use the Transaction Manager

Basic concepts of Java transaction In its simplest definition, a transaction is a set of actions that is treated as an atomic unit; either all actions take place (the transaction commits), or none of them take place (the transaction rolls back). Managing transactions is one of the primary tasks of an application server. The application server keeps track of transactions, remembering which transaction is associated with which request, and what transactional resources (such as JDBC or JMS connection) are involved. Each active transaction is represented by a transaction object, which implements the interface javax.transaction.Transaction. A transaction is usually associated with a thread and only one transaction can be associated with a thread at any one time. A central service, called the Transaction Manager, is responsible for keeping track of all these transactions. The Transaction Manager is implemented through the Java Transaction API (JTA). Transaction and Dynamo ap...

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.

Tips from Sony Thomas

Search This Blog