JavaScript Configuration Files
This topic applies to the Mont Blanc and Denali releases of SuiteCommerce Advanced (SCA) only.
For these implementations, configuration files are stored as JavaScript files for each application module. Each of the configuration JavaScript files are contained within an application module. Each file is compiled and deployed as part of the application. To edit a configuration file, you must create a custom version of its application module.
For information about configurable properties, see Configuration Properties Reference.
There are several files used to configure frontend behavior and a single file backend configuration file to modify server-side behavior.
Frontend Configuration
The SC.Configuration.js file holds general configuration properties used by SCA. Each application-specific configuration file depends on this file, and any JavaScript file in a module that needs configuration properties directly also includes it as a dependency.
SCA uses the following configuration files to control how the frontend application works. They all return a Configuration object that other modules use.
-
SC.Configuration – sets up configuration objects and properties used by all SCA applications globally. It’s part of the SCA application module.
-
SC.Checkout.Configuration – sets up configuration objects and properties for the Checkout application. It’s defined in the CheckoutApplication module.
-
SC.MyAccount.Configuration – sets up configuration objects and properties for the My Account application. It’s defined in the MyAccountApplication.SCA module.
-
SC.Shopping.Configuration – sets up configuration objects and properties for the Shopping application. It’s defined in the ShoppingApplication module.
For a detailed example on how to customize frontend configuration files in a pre-Vinson implementation, see Extend Frontend Configuration Files.
Backend Configuration
The Configuration.js file in the SspLibraries module sets the backend NetSuite configuration properties for SCA. By changing this file, you can set up different server-side objects. Changing these objects can also help your site run faster by limiting search results. There is one Configuration.js file for all applications, but some objects only apply to certain applications (like Checkout).
For a detailed example on how to customize the backend configuration file in a pre-Vinson implementation, see Extend the Backend Configuration File.