The LS Commerce solution consists of the following:
- LSCommerceService: a WCF service running under IIS.
- LS Commerce Service SQL Database.
- Mobile apps, all of which communicate with the IIS.
LS Commerce Service connects directly to the LS Central Database. No replication is needed to transfer data from the LS Central Database to the LS Commerce Database. Only COMMERCE_XXXX jobs are needed to prepare some basic data, like prices, discounts, and store hours, for LS Commerce Service. LS Commerce Database is only used to cache some data, like user device information, images, and web baskets that will not be stored in LS Central.
If LS Commerce Service is set to run on a separate database instead of directly on the Main HQ LS Central Database, create a clone of the LS Central Database and use either SQL Replication or a standard LS Scheduler Job to update the Remote LS Central database. The remote database will be used for LS Commerce Service to replicate and pull most of the retail data. LS Commerce Service will still need to connect to the Main HQ Web Services to send in orders, sales, and to look up information about orders, contacts, and other live data.
See Running LS Commerce Service on a Separate LS Central Database for more information about running LS Commerce Service on a remote LS Central database.
See also
LS Commerce Service Configuration