InstallationSingle Server Deployment

Single Server Deployment

Configure the Providers (NAV Connector)

By default both NAV and SQL providers are configured in the 'web.config' files of the Starter Site and backoffice. Therefore the SQL Provider configuration must be deleted.

Configuration of providers for users of Sana Commerce - NAV Connector is shown below:

  • Open the 'web.config' file of the Sana Commerce Starter Site project in VS2008
    (do the same for the 'web.config' file of the 'Sana.Commerce.BackOffice' project in VS2008);
  • Locate the <modules> configuration section and delete the SQL Provider configuration or just copy the code below and replace the <modules> section in the 'web.config' files:
<modules>
        <catalog defaultProvider="NavisionStandardCatalogProvider">
          <providers>
            <clear />
            <add name="NavisionStandardCatalogProvider" type="Sana.Commerce.Customization.Catalog.NavisionExtendedCatalogProvider, Sana.Commerce.Sdk, Culture=neutral" description="CatalogProvider which retrieves catalog information from Navision using NAS" serviceConnection="NavisionStandardService" />
        </providers>
        </catalog>
        <customer defaultProvider="NavisionStandardCustomerProvider">
          <providers>
            <clear />
            <add name="NavisionStandardCustomerProvider" type="Sana.Commerce.Customization.Customer.NavisionExtendedCustomerProvider, Sana.Commerce.Sdk, Culture=neutral" description="CustomerProvider which retrieves customer information from Navision using NAS" serviceConnection="NavisionStandardService" />
          </providers>
        </customer>
        <order defaultProvider="NavisionStandardOrderProvider">
          <providers>
            <clear />
            <add name="NavisionStandardOrderProvider" type="Sana.Commerce.Customization.Order.NavisionExtendedOrderProvider, Sana.Commerce.Sdk, Culture=neutral" description="OrderProvider which retrieves order information from Navision using NAS" serviceConnection="NavisionStandardService" />
          </providers>
        </order>
        <shop defaultProvider="SanaSqlShopProvider">
          <providers>
            <clear />
            <add name="SanaSqlShopProvider" type="Sana.Commerce.Customization.Shop.DatabaseExtendedShopProvider, Sana.Commerce.Sdk, Culture=neutral" description="ShopProvider which retrieves shop information (baskets, ect) from SQL database" serviceConnection="LocalSqlServer" />
          </providers>
        </shop>
        <common defaultProvider="NavisionStandardCommonProvider">
          <providers>
            <clear />
            <add name="NavisionStandardCommonProvider" type="Sana.Commerce.Customization.Common.NavisionExtendedCommonProvider, Sana.Commerce.Sdk, Culture=neutral" description="CommonProvider which retrieves common information from Navision using NAS" serviceConnection="NavisionStandardService" />
          </providers>
        </common>
        <content defaultProvider="SanaSqlContentProvider">
          <providers>
            <clear />
            <add name="SanaSqlContentProvider" type="Sana.Commerce.Customization.Content.LinqContentProvider, Sana.Commerce.Sdk, Culture=neutral" description="ContentProvider which retrives content information(content pages, product descriptions) from SQL DB" serviceConnection="LocalSqlServer" />
          </providers>
        </content>
</modules>
If you use NAV 2009 you should add the additional 'connectionType' attribute for a provider in the 'modules' section in which providers for each subsystem are registered:

Add the additional 'connectionType' attribute with the value 'Nav2009' to providers which use the NAV 2009 WebService connection:

<add name="Navision2009StandardCatalogProvider" connectionType="Nav2009" type="Sana.Commerce.Provider.Navision.Catalog.NavisionCatalogProvider, Sana.Commerce.Provider.Navision, Culture=neutral,PublicKeyToken=2b26dc7ce8e04e9f" description="CatalogProvider which retrieves catalogdata from Navision using NAV2009 WebService" serviceConnection="Nav2009StandardWebService"/>
InstallationSingle Server Deployment