ATG Topics

When the system loads Scenario,it is stored in an in-memory lookup table.if a new event generates,it comes to the system and system looks into the cache to see any scenarios are waiting for those events.Since this caching is done in Memory,it will be extremely fast. Scenarios are precompiled when Dynamo starts up, it parses Scenario’s XML  file into a state machine. During this pre-compilation phase, the system also performs a number of optimizations which maximize server performance.    Cost of a scenario will depend upon how often its triggered,if its triggered frequently then the cost associated will be high,to minimize this restrict the scenarios to group, lets say the group be 'all high end customers'.Also try to limit the occurrences of Scenarios. While starting the Dynamo instance we are running the  Dynamo Scenario Server software as well,this means both the  Dynamo activities and Scenario activities occur in same JVM. Internally L...

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