Mapping types of ATG repository

The mapping a repository is very important in a database design, because if it is not done correctly, you may not be able to set-up your repository XML correctly, and if this is not done, you'll never be able to figure out what went wrong, or why your repository is functioning properly. Let us pick up various mapping topics and learn when to use them.

Another references about ATG

During my research to solve problems or get content for our blog ATG, some sites/blogs caught my attention and deserved to be saved for future reference.

Below are being sharing a list of links collected with good contents about ATG:

Basic concepts about ATG.

This post is for the ATG beginners to get some basic overview about ATG.

At the framework level, ATG is a java based application platform for hosting web-based applications, as well as RMI accessible business components, with an ORM layer, a component container, an MVC framework, and a set of tag libraries for JSP.

RQL - Repository Query Language

Repository Query Language

DAF provides a generic language for formulating queries. Because these queries must map to any repository implementation, the queries cannot be expressed in terms of any one back-end implementation (such as SQL or LDAP query syntax). Instead, the queries must be expressed in Repository Query Language (RQL), and the individual repository connectors are responsible for translating those queries into the query syntax expected by the underlying data store.

FormHandlers ATG

What is Formhandler?

In many web applications users input are taken from the forms. A form may need to handle user input in a variety of formats, check input for validity, handle errors, and pass input to a servlet for processing or to a database for storage.  ATG java classes that process these forms are none other than Formhandlers.

A Formhandler is just like any other component. They can exist out-of-the box, and can be used as-is OR they can be extended like any other component OR they can be created right from scratch.

To start with, formhandlers mostly are of "request" scope as we dont want our form-data to be manipulated multiple times. If our formhandler's scope is session or global, our submitted form data can be modified within a session or globally by any user worldwide.

A form handler class must include one or more handler methods. A handler method is typically invoked when the user clicks the submit button, and handles the processing of the form. Depending on the purpose of the form handler, it can have several different handler methods that each perform a different operation.

XML Files Combination

    An XML file might appear at several points in the CONFIGPATH. The ATG platform, at runtime, automatically combines all the XML files in the CONFIGPATH with the same name into a single composite file, which is then used by the appropriate component.
    When two files are matched up, the way that they are combined is defined by an extra attribute that is specified in file 2 called xml-combine. This attribute is used only to specify how the files are combined, and is removed before the resulting file is generated. The xml-combine attribute can have the following values:

• xml-combine="replace"
• xml-combine="remove"
• xml-combine="append"
• xml-combine="append-without-matching"
• xml-combine="prepend"
• xml-combine="prepend-without-matching"

Product Catalog Database Diagram

    Devido a baixa cobertura da documentação Oracle ATG e a grande quantidades de tabelas no banco de dados, há uma certa dificuldade em visualizar graficamente as relações entre as entidades.
    Para melhor entendimento do relacionamento entre as tabelas, segue abaixo três imagens do diagrama de entidade relacional do Catalogo de Produtos.

English version:   
    Due to low coverage of Oracle ATG documentation and the large amounts of tables in database, there is some difficulty in graphically display the relationships between entities.
    For a better understanding of the relationship between the tables, see below three pictures of the Product Catalog entity relational diagram.