Category: ATG

  1. Home
  2. Blog
  3. Category: ATG

Oracle Commerce Droplets

Droplets Droplet is a Servlet Bean to dynamically generate HTML from a Java Object. It minimizes the amount of Java code that has to appear in HTML and amount of HTML that has to be hard-coded into Java classes. DAF (Dynamo Application Framework) comes with a set of out-of-the-box droplets that can be used. The user can also create their […]

Continue Reading

ATG 11.1 Forge-based deploy pattern

When working with ATG 11.1, if we are looking to support forge-based deployment template, we have to configure “IndexingApplicationConfiguration ” ATG component. CAS-based deployment template, record store names have format applicationName-recordStoreType. Example: EAC application named Demoen, dimension values record store is named Demoen-dimvals. Forge-based deployment template, format of record store names is applicationName_languageCode_recordStoreType. Example: EAC application named Demoen that indexes records in […]

Continue Reading

HWDI Scenario: Getting Coming Soon Products

HWDI [How We Do It] will be series of business queries and there answers using Oracle Commerce. When there are new products [example The New MacBook] which are coming to market and your website need to handle a situation, where you want to allow users to providing their email for future contacts and information as the device becomes available for sale. Also […]

Continue Reading

Oracle Commerce 11.1 CreateProcess error=206

When trying to access the Dyn Admin getting below error. The detailed exception is: Cannot run program “javac”: CreateProcess error=206, The filename or extension is too long Simple solution to this is by adding ExtendedJhtmlPageProcessor component at atg\dynamo\servlet\pagecompile\ location and restart sever. Navigate to ATG_HOME\localconfig directory. Create atg\dynamo\servlet\pagecompile directory structure. Create file and add below content to it      #atg\dynamo\servlet\pagecompile\      […]

Continue Reading

Resetting CIM

Resetting CIM will clear “Done” flags and all previously used values like database product selection, connection details and application server selection. To do so, delete the “data” directory in the CIM module. The full path would be something like “C:\ATGATG-versionCIMdata”. Running through Product Selection will clear all “Done” flags but keep previously used values. Let's Share

Continue Reading
Show Buttons
Hide Buttons