ATG Topics

Slots are Nucleus components,Container that show personalized  content to the users.These containers are filled with contents,Targeters and scenarios are used to deliver the personaliszed contents.Slots have the capability to store a cached list of items from scenarios. In ACC under Components by path slots can be located under /atg/registry/slots ,Slots like other components can have all the three scopes,but the default scope is session,the scope can be persisted so items added in one session will  be there when the user starts a new session. Targeters can also be used to select content that is  personalized for the user.This is knowledge-driven  personalization and Work with scenarios to deliver dynamic personalized content.Scenarios use Targeters to fill slots. With slots: best performance, because business rules are  executed once, when the scenario runs and slots cache the  output.The content can also be changed over time (adde...

The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration...

Navigate to BCC -> http://host:port/atg/bcc Username:admin,Password:admin After login you will see 'Operations' tab under which you can see Search Administration option. Expand the ‘Search Administration’ under the ‘Operations’ tab. Click on ‘Browse Search Projects’ under Search Administration, Click on ‘New Search Project’ button. Enter the Search Project Name and Description under ‘General’ label,Search Project Name: Test_Search_Sebastian. Description:Any meaningful description(Example:Search Index). Click on the ‘Create Search Project’ button. click the ‘Add Content’ button under the ‘Content for Indexing’ label,Specify the Content Name. You can give any name (Ex:Content_Sebastian) and select ‘ATG Repository’ from the content Type dropdown. In the IndexingOutputConfig Path textbox, type the relative path  /atg/commerce/search/ProductCatalogOutputConfig of ProductCatalogOutputConfig located in C:\ATG\ATGXXX\home\ localconfig\atg\commerce\search ...

C ommerce Module W e need to keep certain files on the below location for the  Search functionality to work.You need put the below three files in the location ->     C:\ATG\ATGXXX\Commerce_Module\config\atg\commerce\search ProductCatalogOutputConfig.properties       indexingSynchronizations+=/atg/commerce/search/refinement      /RefinementConfigurationSubmitter     loggingDebug=true product-catalog-output-config.xml      This is a xml file where you will specify the indexing        parameters ProductCatalogQueryFormHandler.properties loggingDebug=true siteName=staging environment 0 (TestSearchProj) relQuestSettings=activeSolutionZones^=/atg/commerce/search/ProductCatalogOutputConfig.textActiveZones docProps=$repositoryId,childSKUs.displayName, childSKUs.description. If BCC is running in a different machine, then only the following file is required in C:...

BCC Module (BCC Server) Put the below three files on this location ->C:\ATG\ATGXXX\BCC_Module\config\atg\commerce\search ProductCatalogOutputConfig.properties indexingSynchronizations+=/atg/commerce/search/refinement/RefinementConfigurationSubmitter loggingDebug=true product-catalog-output-config.xml This is a xml file where you will specify the indexing parameters. ProductCatalogQueryFormHandler.properties loggingDebug=true siteName=staging environment 0 (TestSearchProj) relQuestSettings=activeSolutionZones^=/atg/commerce/search/ProductCatalogOutputConfig.textActiveZones docProps=$repositoryId,childSKUs.displayName,childSKUs.description Make sure the initial.properties under C:\ATG\ATGXXX\BCC_Module\config\atg\dynamo has the following entries. /atg/commerce/search/ProductCatalogSearchService,\ /atg/commerce/search/ProductCatalogOutputConfig Make sure the following files/folders present in the following location C:\ATG\ATGXXX\BCC_Module\config\atg\search\ Config folder ...

Module to include in build & manifest files Commerce Module META-INF     Manifest-Version: 1.0 ATG-Config-Path: config/ ATG-Required: DAF.Search.Query DafEar.Admin DCS.Search DCS.Search.CustomCatalogs.common DAF.Search.Query.Search DAF.Search.Routing DAF.Search.Base DAF.Search.common DAF.Search.Index DAF.Search.Topics PublishingAgent   BCC_Module Buld.xml            <target name= "create-search-ear" >   <delete dir= "BCC_Module" />   <assemble-ear dynamoRoot= "C:\ATG  \ATGXXX " dynamoModules="DAS,DPS,DCS,DSS,DafEar.Admin,  DCS-UI.management,DCSUI.Search,B2CCommerce.Versioned,PubPortlet,  DCS.Search.Versioned,DAF.Search.Routing,SearchAdmin.AdminUI,  DCS.Search.CustomCatalogs.Versioned,DAF.Search.Base,  DAF.Search.Query,DAF.Search.common,DAF.Search.Index,  DAF.Search.Topics,DAF.Search.Versioned,DataLoader,RL"   overwrite= "true"  des...

Workflow changes not reflecting in particular(Production/Testing) environments. Solution You need to Stop CA first then,copy the workflowProcessManager.xml file to your localconfig like below. localconfig/atg/epub/workflow/process/workflowProcessManager.xml Process Editor Server Information Make sure the serverName and drpPort for the particular instance is correct. Otherwise workflow will not work. <?xml version="1.0" encoding="UTF-8" ?> <process-manager-configuration>   <process-editor-server>    <server-name> hostname:drp-port </server-name>   </process-editor-server> </process-manager-configuration> You can also find the hostname:drp-port from the component /atg/dynamo/service/ServerName.The serverName() method of this component will return these values. You can also refer other BCC issues here BCC Manage Snapshot functionality BCC Delete Meta Data Files  

Below are the queries to delete projects which are in pending deployments stage and Meta data files from the CA database. Delete from epub_deployment; -- Deleting pending deployment. DELETE FROM das_depl_depldat;-- Deleting Meta data files from BCC. DELETE FROM das_depl_options; DELETE FROM das_depl_repmaps; DELETE FROM das_depl_item_ref; DELETE FROM das_depl_progress; DELETE FROM das_thread_batch; DELETE FROM das_deploy_data; DELETE FROM das_dd_markers; DELETE FROM das_deploy_mark; DELETE FROM das_rep_mark; DELETE FROM das_file_mark; DELETE FROM das_dep_fail_info; DELETE FROM das_deployment; Fix in case CA server taking time to start . Stop CA Server delete the entries from the table das_gsa_subscriber. Start CA Server Also see how to solve BCC snapshot mismatch issue .

B2BCommerce Selling has made to some corporates like some departments or to some companies Since this is based on corporates,the corresponding Promotions also based on this. We have custom catalogs comes along with B2B implementation,and these catalogs often can be customised for each buying companies. Payments is generally made through invoicing or through purchase orders. Orders can be done at a regular intervals(recurring). Order restriction can be imposed based on several factors,like role, order approval chain etc. B2CCommerce Targeted to individual customers . Since this is based on individuals,the corresponding Promotions also based on individual activity. Catalogs are Regional and very less restrictions on Order. Payments generally through credit card and gift certificates. Orders will be one-time. See the functional difference also

There are some functionalities which is specific to B2B only that are not there in B2C.Those are listed below in the table format. Feature B2B B2C Roles & Organisation Yes Yes Derived Yes Yes Custom Catalogs Yes Yes Price Lists Yes Yes Contracts Yes No Split Shipping/Payment Yes Yes Purchase Orders/Invoice Generation Yes No Order Approvals Yes No Saved Orders Yes Yes Scheduled Orders Yes Yes Since B2C is targeted for individual consumers we dont have contracts there,also in B2C we generally pay through credit card or gift certificate,so we dont have the concept of Purchase Orders or Invoice ,similiary there is no much Order  approvals flow in B2c module. See also the basic difference between B2B and B2C modules

Whenever if you are creating a custom form handler,make sure it extend GenericFormHandler class. Your custom form handler must define properties successUrl and errorUrl with the respectieve getters and setters methods. Other than this every property submitted with this formhandlers  must have the respectieve getters and setters methods. Each submit button should have a prexx(), handlexxx() and validate() methods The prexxx() method will be void most of the cases,but if you need to specifically clear the formException vector,in case of session scoped components you can add your logic here. validate method should validate the properties as per the requirement,incase of validation failure,create a new DropletException and add it to the formException Vector. eg:super.addFormException(new DropletFormException(msg, "key")); The flow will be something like this,handlexxx()-prexxx()-return super.checkFormRedirect(successUrl,errorUrl,request,response). Also verify Form...

Creation and Updation of Repository Items must be enclosed with a  Transaction block. Reading Items from Repository does not require a transaction. if we are doing multiple operations and is dependant on each other,then we must use a single transaction,this is to either commit or roll back the entire transaction,other wise each operation has to be enclosed in a separate transaction block. Use the finally block to end the transaction,this will ensure our statement will get executed even an Exception is thrown. Dont try to call nested methods inside one transaction,this will not serve the purpose. Dont use any complex logic,inside the transaction,like below. Bad Practice try {       td.begin(this.getTransactionManager(),       TransactionDemarcation.REQUIRED);       MutableRepositoryItem newItem =       mutableRepository.createItem(“shipping”);   ...

Make sure you have ATG running with your Application  module. We are adding a jsp page fragment called addcart.jsp . This fragment will use two parameters passed from other jsp, skuInfo.jsp - skuId and productId . Add the form and inputs required to add an item to the order,  as shown in the sample code below: <dsp:input type="hidden" bean="CartModifierFormHandler.catalogRefIds" paramvalue="skuId"/> <dsp:input type="hidden" bean="CartModifierFormHandler.productId" paramvalue="productId"/> <dsp:input type="text" size="5" bean="CartModifierFormHandler.quantity" value="1"/> <dsp:input type="hidden" bean="CartModifierFormHandler.addItemToOrderSuccessURL" value="cart.jsp"/> <dsp:input type="submit" bean="CartModifierFormHandler.addItemToOrder" value="Add to Cart"/> Don't forget to import the /at...

Lets assume we have an external Reviews and Rating module with us for integration.The first thing we need to do is, include this module in ourrunAssembler. runAssembler yourApp.ear -m your_module ReviewsAndRating DSS  DafEar DafEar.Admin This module will basically helps us to read and write reviews for your product as shown below. Once the user navigated to the products page,he can see an option to add that product to the CART,but before that he has now the option to check the ratings and review for this product,and if he is satisfied by the ratings and review he can go ahead and add it to CART. There will be basically two links,one for ' Reading all Reviews ' and ' Write a Review '.

There will be basically three levels of Rating we can provide. 1. User Rating 2. Rate Product 3. Customer Satisfactor Rating While writing reviews and rating the product,you can also mention the Product name in the title and write a detailed review which would be considered as the most important part in this functionality.These information will be stored in the Ratings and Reviews tables and will be shown to the customers who want to buy that product.There will be a link provided to Read Reviews

Here you can read reviews and ratings of the Product you are going to purchase,For testing purpose i am showing only one  record ,ideally will have a lots of reviews and ratings  for a particular product. We are seeing the feedback given by one of the customers of this Product(Black Berry Phone). Rating and Reviews is going to become an unavoidable option for Ecommerce Application as the customers can gather lot of trusted information/opinions about the product they were going to buy from the Application site itself instead of wasting time in the Internet and other medias,sounds great isn't it ?