After Installation

You can "ping" the Commerce Web Service to see if the WCF web service is working properly. First, ping them from a browser on a laptop (Chrome/Edge or Firefox recommended), and later from a browser on your mobile phone.

The ping checks the connection to Commerce Service and LS Central SQL Server Databases and LS Central Web Service.

If the ping is successful, a “pong” reply is returned. After a successful ping, a Mobile App should be able to connect with the web service. If the ping returns an error, see Troubleshooting Communication Between LS Nav/Central and Commerce.

In Windows Explorer, open C:\LS Retail\Commerce\CommerceService\. The \Sql folder has all the sql scripts used and the \logs folder has the logfile.txt which is extremely useful.

You can change the values you entered during the setup in the AppSettings.config file or in the Commerce admin portal, depending on the setup.

The connection strings to Commerce and LS Central SQL databases are stored in the AppSettings.config file (see Appsetting Configuration). You can control the error logging with the NLog.config file, see Logging Configuration.

Note: If you change these configuration files, you must restart the Commerce Service web service. To restart go to IIS Manager and restart Web Service where Commerce Service is located. You should not change the web.config, unless you setting up SSL.

Single-tenant

After a successful installation, the next step is to validate the data entered during the installation. Configuration for Single-tenant is stored in the Appsettings.config file, located where Commerce Service is installed.

Multi-tenant

After a successful installation, the next step is to create the first tenant, see Commerce Admin Portal. When you have set up the first tenant, your next step is to validate the tenant configuration.

Note: Commerce Admin Portal is only used for Multi-tenant configurations; it is not needed in a Single-tenant setup.

LS Central in SaaS

  1. Set correct Protocol for Commerce to communicate with LS Central in SaaS.
  2. Open the Appsetting.config file.
  3. Find the following line in this file:
    <add key="BOConnection.Nav.Protocol" value=""/>

The default value is Ss13 but you have to know which value to fill in here for your cloud instance.

Tip: If you are not sure, try one of the valid options Ssl3 - Tls - Tls11 - Tls12 - Tls13 - S2S and see which one works. The most common option for SaaS is S2S.

See also

LS Central Configuration

SQL Server Database