Skip to main content

ATG features and ATG OOB modules

Features supported by ATG:
  • Product Catalogue --> Custom Catalogue Creation, Localized Catalogs
  • Order Management --> Customize Order Management Process, Integrate with 3rd Party Order Management Tool (Yantra), Partial Order Fulfillment
  • Promotions --> Custom Promotion Creation, Integration with Ad Server (NetGravity)
  • Campaigns --> Custom Campaign Development, Marketing Campaigns, Targeted Campaigns
  • Personalization --> Profile Extensions, Explicit Rule Based Personalization, Implicit Dynamic 
  • Personalization Commerce --> Shopping Cart Customization, Shopping List Creation, Customize Checkout process 
  • Payments --> Integration with Payment Gateway (Cybercash,ClearCommerce), Bulk Payment
  • Collaboration --> Chat, Discussion Forum, Message Board, Net Meetings 
  • Reporting --> Click Stream Analysis, Site Analytics, Integration with 3rd Party Tools (HitBox, Netstat) 
  • Search --> Integration with Search Engine (Verity, Autonomy), Database/Document Search, Catalog Search 
  • Performance Management --> Load Testing and Optimization, Fail Over, Performance optimization 
  • ATG Migration --> JHTML to JSP conversion, DB Access mechanism migrated from Relational Views to Repository way (for 4.x to 5.x migration), Component Mapping and migration 
Main ATG modules:

Module
Description
Admin.Init
Adds missing administrative accounts for the ATG Control Center. 
Admin.Reset
Resets the default login accounts for the ATG Control Center. 
DAF.Search
Enables the ATG platform to use ATG Search to index and search content from product catalogs and other repositories.
DAS-UI
Enables Dynamo to accept connections from the ATG Control Center.
Note: This module must be running if you want to use the ATG Control Center.
DCC
Runs the ATG Control Center in the same JVM used by the application server that the Nucleus-based application is running on. 
DPS
ATG Personalization
DSS
ATG Scenarios
RL
Repository Loader. Takes files that are stored in a file system, converts them into repository items, and loads the items into the repository.
SQLJMSAdmin
Browser-based administration interface for Dynamo’s SQL JMS message system. 
Content Administration modules
Module
Description
AssetUI
Supports the building of browser-based user interfaces for an ATG Content Administration (versioned) environment. The module includes the Asset Picker and functionality related to it. Requires the WebUImodule
BizUI
The ATG Business Control Center. Includes the Home page functionality and the View Mapping system.
PublishingAgent
Publishing Agent. Runs on production and staging servers and performs content deployment operations by communicating with the ATG Content Administration server.
PublishingWebAgent
Publishing Web Agent. Runs on the production and staging Web servers and performs Web content deployment operations by communicating with the ATG Content Administration server.
Publishing.base
ATG Content Administration. 
Publishing.WebAppRef
The source module for the Web Application Reference Implementation provided with ATG Content Administration.
Publishing.WebAppRefVer
The versioning module for the Web Application Reference Implementation provided with ATG Content Administration.
PubPortlet
Supplies the portlets that make up the ATG Business Control Center interface. Including this module also causes the Publishing.base,AssetUI, and BizUI modules to be included. Include this module to perform most basic tasks in ATG Content Administration, such as product evaluation.
WebUI
Contains support for browser-based user interfaces. Examples are the tree-based asset browsing feature and a calendar widget.
Commerce modules
Module
Description
B2BCommerce
ATG Business Commerce
Note: To run ATG Commerce, you must use one and only one of the following modules: B2BCommerce,B2BCommerce.Versioned, B2CCommerce, orB2CCommerce.Versioned.
Including this module also includes DCS.CustomCatalogs and its modules.
B2BCommerce.Search
Enables Business Commerce extensions to the ATG Commerce Search.
B2BCommerce.Versioned
Use instead of B2BCommerce module if running ATG Merchandising. (Requires the DCSUI.management and PubPortlet modules also.)
Note: To run ATG Commerce, you must use one and only one of the following modules:B2BCommerce,B2BCommerce.Versioned, B2CCommerce, orB2CCommerce.Versioned.
Including this module also includes B2BCommerce,DCS.DynamicCustomCatalogs.Versioned, and their modules.
B2CCommerce
ATG Consumer Commerce
Note: To run ATG Commerce, you must use one and only one of the following modules:B2BCommerce,B2BCommerce.Versioned, B2CCommerce, orB2CCommerce.Versioned.
Including this module also includes DCS and its modules.
B2CCommerce.Versioned
Use instead of B2CCommerce module if running ATG Merchandising. (Requires the DCSUI.management and PubPortlet modules also.)
Note: To run ATG Commerce, you must use one and only one of the following modules:B2BCommerce,B2BCommerce.Versioned, B2CCommerce, orB2CCommerce.Versioned.
Including this module also includes B2CommerceDCS.Versioned, and their modules.
DCS
Base ATG Commerce module
Including this module also includes DSSDPS, and their modules.
DCS.AbandonedOrderServices 
Provides tools for dealing with abandoned orders and shopping carts.
Including this module also includes DCS and its modules.
DCS.CustomCatalogs
Runs custom catalogs in an ATG Commerce production environment.
Including this module also includes DCS and its modules.
DCS.DynamicCustomCatalogs
Runs custom catalogs in an ATG Commerce development environment.
Including this module also includes DCS.CustomCatalogs and its modules.
DCS.DynamicCustomCatalogs.
Versioned
Runs custom catalogs in an environment running ATG Commerce and ATG Merchandising. (Requires the DCSUI.management and PubPortletmodules also.)
Including this module also includes DCS.DynamicCustomCatalogs,DCS.CustomCatalogs.Versioned, and their modules.
DCS.PublishingAgent
Use instead of the PublishingAgent module on the target server if Commerce repository items are deployed to that server.
Including this module also includes PublishingAgentDCS, and their modules.
DCS.Search
Enables ATG Commerce to use ATG Search to index and search content from product catalogs and other repositories.
DCS.Versioned
Use instead of DCS module if running Commerce with ATG Merchandising.
Including this module also includes Publishing.baseDCS, and their modules.
Fulfillment
ATG Commerce order fulfillment
Including this module also includes DCS and its modules.

Comments

  1. Sony- I'm new to the ATG world, in a new role in a new company and am hit with the task of resolving disappeared "Browse" functionality in the Business Control Center. This is in the Merchandising bit, and when the "Show:" option is selected in the Browse tab, the tree is missing where it was previously. "Search" functionality works splendidly. I'm thinking something is missing in a config file somewhere, however, no specifics of what happened are available. This first appeared in the production environment, and when users began investigating, a server reboot was done and the same problem replicated in the test environment where the investigation was being conducted. Any help would be greatly appreciated!

    Eric

    ReplyDelete
  2. can share regarding ATG errors

    ReplyDelete

Post a Comment

Popular posts from this blog

ATG - basic concepts of ATG

This blog is for the ATG beginners to get some basic overview about ATG. I just given the ATG concepts as a list of numbered points for the ease of understanding. 1. 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. 2. Art Technology Group(ATG)'s Dynamo Application Server (DAS) is a Java EE compliant application server. DAS is no longer actively developed as ATG recommends using other Java EE applications servers for its products such as BEA WebLogic, JBoss or IBM WebSphere. 3. Prior to ATG 2007, JHTML was used instead of JSP for view purpose. J...

ATG User Profile schema ER diagram

Check out the Product Catalog  schema ER-Diagram @  http://tips4ufromsony.blogspot.in/2012/01/atg-product-catalog-schema-er-diagram.html Check out the O rder schema ER-Diagram @   http://tips4ufromsony.blogspot.in/2012/02/atg-order-schema-er-diagram.html If you would like to know the relationship between different User Profile schema tables, please find below screen shot of  Profile schema ER Diagrams.  

How to simulate Browser back button

When someone asks how to simulate a back button, they really mean to ask how to create a link that points to the previously visited page. Most browsers tend to keep a list of which websites the user has visited and in what order they have done so. The DOM window object provides access to the browser's history through the history object. Moving backward and forward through the user's history is done using the   back(), forward(), and go() methods of the  history  object. To move backward through history, just do window.history.back() ; This will act exactly like the user clicked on the Back button in their browser toolbar. Find below a sample html code: <html> <head> <script type="text/javascript"> function goBack(){  window.history.back() } </script> </head> <body>    <input type="button" value="Back" onclick="goBack()" /> </body> </html>

ATG : Oracle started new discussion forum for ATG

Oracle has started a new ATG discussion forum on oracle discussion forums.  It has a main ATG section and is divided into technical and business categories. You can access the url   http://forums.oracle.com/forums/category.jspa?categoryID=503 .  After Oracle acquired ATG, this was much expected and we can hope this forum might give us a better chance to discuss our ATG doubts and more people will come and discuss about ATG. Find the ATG docs @   http://www.oracle.com/technetwork/indexes/documentation/atgwebcommerce-393465.html

Jsp and CSS size limits that web developers need to aware

Here I am listing some erroneous cases that might occur in your web development phase, due to some size restrictions. JSP file size limit : You might get some run time exceptions that the JSP file size limit exceeds. Please find below the reason : In JVM the size of a single JAVA method is limited to 64kb. When the jsp file is converted to Servlet, if the jspservice method's size exceeds the 64kb limit, this exception will occur. Keep in mind that this exception depends on the implementation of the JSP translator, means the same JSP code may give an exception in Tomcat and may run successfully in Weblogic due to the the difference in the logic to built the Servlet methods from JSP. The best way to omit this issue is by using dynamic include.For example, if you are using                  <%@ include file="sample.jsp" %> (static include),  replace this to               ...