Multiple NAV 2009 Server Services

Configure the Connection Strings

These steps can be performed by webshop administrators only when the Sana Commerce webshop is installed on web and database server.

Step 1: Open the 'web.config' file of the Sana Commerce frontend.

Step 2: Locate the <connectionStrings> configuration section and make sure a node for every NAV 2009 WebService is available. For example:

<connectionStrings>
<remove name="LocalSqlServer"/><add name="IndexDirectory" connectionString="IndexDirectory"/>
<add name="LocalSqlServer" connectionString="Data Source=server\SQL2005;Initial Catalog=database;User Id=user;Password=pwd;" providerName="System.Data.SqlClient" providerName="System.Data.SqlClient"/>
<add name="CatalogCustomerNav2009" connectionString="http://SERVERNAME:7047/DynamicsNAV/WS/COMPANYNAME/Codeunit/SC_NAV2009_WebService" providerName="Nav2009"/>
<add name="OrderShopNav2009" connectionString="http://SERVERNAME:7049/DynamicsNAV2/WS/COMPANYNAME/Codeunit/SC_NAV2009_WebService" providerName="Nav2009"/>
</connectionStrings>

Step 3: Select an appropriate name for these configuration nodes.

Step 4: Locate the <sanaCommerce> modules section. All Sana Commerce subsystems are listed here.

Step 5: Specify the name of the connection string in the Catalog and Customer subsystem, this name already has been specified in the <connectionStrings> section in the serviceConnection attribute of the provider node. In the example mentioned above, the name is CatalogCustomerNav2009.

Step 6: Specify the name of the connection string in the Order and Shop subsystems, also this name already has been specified in the <connectionStrings> section in the serviceConnection attribute of the provider node. In the example, it is OrderShopNav2009.

Step 7: Also a serviceConnection must be specified for the common subsystem. You can select either one of the NAV 2009 WebServices. It does not have any influence on the performance.

Step 8: Open the 'web.config' file of the Sana Commerce backoffice.

Step 9: Since the backoffice only uses the catalog and content subsystems (content subsystem is not relevant at the moment), only one NAV 2009 WebService has to be configured here; the Catalog and Customer NAV 2009 WebService.

Step 10: Change or add a configuration node for this NAV 2009 WebService in the same way as you have done in the frontend 'web.config' file. For consistency, you should give it the same name as used earlier, here this is 'CatalogCustomerNav2009'.

Step 11: Locate the 'sanaCommerce/modules/catalog' configuration section and update the serviceConnection attribute to the name of the connection string specified in the <connectionStrings> section. In the example this is 'CatalogCustomerNav2009'.