<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_SAP_Commerce_Cloud_Essentials_for_Develope_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2024-11-21T07:42:21.000Z

Examining the Build Framework

<div id="content"><p tabindex="0">Generally, the first question technical developers have when they begin working with SAP Commerce is about how they can build the SAP Commerce Cloud system.</p><p tabindex="0">Let's find the answer in the following video by examining how the build framework operates.</p><div class="kalturaVideoLessonWrapper"><div aria-label="This video introduces the build framework that uses Apache Ant and outlines the available build targets for SAP Commerce Cloud." class="kalturaVideoLessonContainer" data-testid="video" id="1_7zkxvvkh"></div></div></div>

Build Framework

Exploring the Technical Essentials of SAP Commerce Cloud

SAP Commerce Cloud has a custom build framework based on Apache Ant. Ant handles source-code generation, compilation, and a number of automation tasks We will look at some of them later. Please note that when some IDEs compile (notably, Eclipse), they generate their own, separate set of class executables. Such IDE-specific executables are unrelated to those used during the Ant Build process, thus are completely ignored by SAP Commerce. There are two ways to build SAP Commerce, either platform-wide or extension-specific. By "build", we mean "executing an ant target", such as ant all or ant clean. If a platform-wide build is performed, i.e., under the platform folder, platform and all extensions listed or referenced in localextensions.xml file are built. But if an extension-specific build is performed i.e., invoked from the extension's base folder, then only that extension is built, even if other extensions are connected to it via a dependency. Extension-specific builds work because a build.xml file is generated for each extension when it is initially built. Even so, we generally use the one in the platform extension to build the entire suite.  When you call ant, the build framework generates and compiles Model classes according to the definitions in the *-items.xml files, in the order needed for honoring the declared extension dependencies collects localization properties from their respective .properties files updates configuration of the Commerce Server Please note that, only during the first run, the ant build also generates some new folders, such as: A config folder for storing platform-wide configuration files, such as localextensions.xml and local.properties A data folder for keeping developer-mode database files, media files, search-engine index files, and other types data-storage files A log folder for keeping log files Our ant build framework, is configured with a number of predefined build targets for your use. For example: ant all is used to build the platform and configure the server ant clean will clean-up the core platform and extensions by deleting build-generated files, such as .class files ant extgen is used to generate a single, custom extension, based on an individual extension template ant initialize is used to initialize the system, which includes creating and populating the underlying database tables. Invoking ant –p displays a list of all available ant targets, with a brief description of each.