HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Configuration files

Introduces configurations for Optimizely Customized Commerce.

General configuration for the Optimizely platform with configuration files and syntax is described in the Configuration section for CMS. You should study the general platform configuration documentation to understand the Optimizely configuration fully.

Similar to Optimizely Content Management System (CMS), Optimizely Customized Commerce provides Options classes that you can use to configure options for different subsystems. The Options classes are based on .NET Core Options pattern, and works in similar fashion. Each settings inside the Options class has a default value. If you want to override a default setting value, you can do either of the following:

  1. Provide the value in the corresponding section.

  2. Set the value using services.Configure in the ConfigureServices method of the Startup.cs file.

Classes and methods mentioned here are available in the EPiServer.ServiceLocation namespace.

Customized Commerce configuration files

The following Options classes define settings for the ecommerce framework (ECF) part of Customized Commerce.

  • ApplicationOptions. Contains non-feature-specific settings.
  • CatalogOptions. Contains settings for the Catalog subsystem.
  • CustomerOptions. Contains settings for the Customer Management subsystem.
  • MarketingOptions. Contains settings for the legacy Marketing subsystem, replaced by the new Marketing system).
  • OrderOptions. Contains settings for the Order subsystem.
  • SearchOptions. Corresponds to the Mediachase.Search.SearchOptions class, containing settings for indexing and search features. See also Search.

The following configuration files define settings for the Business Foundation subsystem.

  • BusinessManagerOptions. Contains settings for handlers and plug-in collections for meta classes.
  • MetaObjectOptions. Contains a set of meta-object related settings.

Connection strings

Commerce (PaaS) looks for a connection string named "EcfSqlConnection" inside appsettings.json. You can provide connection strings inside appsettings.json like this:

    "ConnectionStrings": {
        "EcfSqlConnection": "{commerce connection string}",
        "EPiServerDB": "{Cms connection string}"