Running Commerce Service on a Separate LS Central Database

By default, Commerce Service will tie to the main LS Central Database after installation. If the setup requires Commerce Service to run on a different LS Central Database, a replication from the main database is needed.

The default jobs that are available already in the LS Central Demo company can be used to replicate data to the LS Central Database used for Commerce Service, just as if it were one of the stores or POSs. There are a few extra tables that need to be added to those jobs, both for Normal and Action replication.

To prepare data the first time

  • POS32-ALL
  • POSINFO

For regular data update

  • CONFIGS
  • DISCOUNT
  • ITEMS
  • STOREINF

These tables need to be created as SubJobs and added to either existing jobs or to a new job:

MPOS

23

98

10000704

10000782

10001303

10001404

10012860

10012866

99009045

99009047

99009049

Vendor

General Ledger Setup

Item Distribution

Store Group Setup

Inventory Masks

Item Status Link

WI Setup

WI Store

Member Login

Member Login Device

Member Login Card

INV

10001322

10012800

10012801

10012806

10012808

Counting - Area

Inventory Menus

Inventory Menu Lines

Inventory Terminal-Store

Inventory Location List

As prices are generated with the COMMERCE_INIT and COMMERCE_UPDATE jobs, these jobs need to be able to run on the remote database as well to generate same data there. It also possible to create SubJobs for WI Prices, WI Discount, WI Mix & Match Offer, and Mobile Store Opening Hours tables and add to sub job to the primary jobs that will be used to replicate data to the Remote database.

When LS Central data has been replicated and prepared for Commerce Service, you must change a configuration setting in the AppSettings.config file (C:\LS Retail\Commerce\CommerceService).

This section points to the main LS Central Web Service at HO:

Set this value to false to tell the Commerce Service that it is not running at HO:

This should point to the LS Central remote database that Commerce Service should connect to:

Commerce Service does only do Select when accessing the LS Central tables directly. All updates are done via LS Central Web Services. These are the LS Central tables that are used by Commerce Service:

[COMPANYNAME$Attribute]

[COMPANYNAME$Attribute Option Value]

[COMPANYNAME$Attribute Value]

[COMPANYNAME$Barcodes]

[COMPANYNAME$Barcode Mask Segment]

[COMPANYNAME$Barcode Mask]

[COMPANYNAME$Code128 GS1 Setup]

[COMPANYNAME$Counting - Area]

[COMPANYNAME$Country_Region]

[COMPANYNAME$Currency]

[COMPANYNAME$Currency Exchange Rate]

[COMPANYNAME$Customer]

[COMPANYNAME$Customer Price Group]

[COMPANYNAME$Customer Order Header]

[COMPANYNAME$Customer Order Line]

[COMPANYNAME$Customer Order Payment]

[COMPANYNAME$Data Translation]

[COMPANYNAME$Dining Area Profile]

[COMPANYNAME$Extended Variant Values]

[COMPANYNAME$General Ledger Setup]

[COMPANYNAME$HMP Action]

[COMPANYNAME$HMP Dining Tbl_ Main Status]

[COMPANYNAME$HMP Status Action Set]

[COMPANYNAME$HMP Status Action Set Line]

[COMPANYNAME$HMP Status Color Set]

[COMPANYNAME$HMP Status Color Set Line]

[COMPANYNAME$Hosp_ Standard Text]

[COMPANYNAME$Hospitality Type]

[COMPANYNAME$Inventory Location List]

[COMPANYNAME$Inventory Masks]

[COMPANYNAME$Inventory Menu Lines]

[COMPANYNAME$Inventory Menus]

[COMPANYNAME$Inventory Terminal-Store]

[COMPANYNAME$Item]

[COMPANYNAME$Item Category]

[COMPANYNAME$Item Distribution]

[COMPANYNAME$Item HTML]

[COMPANYNAME$Item Status Link]

[COMPANYNAME$Item Unit of Measure]

[COMPANYNAME$Item Variant Registration]

[COMPANYNAME$Item Variant]

[COMPANYNAME$Location]

[COMPANYNAME$Member Account]

[COMPANYNAME$Member Attribute]

[COMPANYNAME$Member Attribute Setup]

[COMPANYNAME$Member Club]

[COMPANYNAME$Member Contact]

[COMPANYNAME$Member Device]

[COMPANYNAME$Member Login]

[COMPANYNAME$Member Login Card]

[COMPANYNAME$Member Login Device]

[COMPANYNAME$Member Management Setup]

[COMPANYNAME$Member Notification]

[COMPANYNAME$Member Notification Log]

[COMPANYNAME$Member Point Entry]

[COMPANYNAME$Member Process Order Entry]

[COMPANYNAME$Member Scheme]

[COMPANYNAME$Membership Card]

[COMPANYNAME$Mobile Store Opening Hours]

[COMPANYNAME$MobileItemHTML]

[COMPANYNAME$MobileLicenseRegistration]

[COMPANYNAME$Offer]

[COMPANYNAME$Posted Customer Order Header]

[COMPANYNAME$Posted Customer Order Line]

[COMPANYNAME$POS Button Parameters]

[COMPANYNAME$POS Card Entry]

[COMPANYNAME$POS Menu Line]

[COMPANYNAME$POS Terminal]

[COMPANYNAME$Preaction]

[COMPANYNAME$Product Group]

[COMPANYNAME$Published Offer]

[COMPANYNAME$Published Offer Detail Line]

[COMPANYNAME$Restaurant Menu Type]

[COMPANYNAME$Retail Image]

[COMPANYNAME$Retail Image Link]

[COMPANYNAME$Retail Setup]

[COMPANYNAME$Sales Header]

[COMPANYNAME$Sales Line]

[COMPANYNAME$Sales Price]

[COMPANYNAME$Shipping Agent]

[COMPANYNAME$Shipping Agent Services]

[COMPANYNAME$Staff]

[COMPANYNAME$Staff Store Link]

[COMPANYNAME$Store]

[COMPANYNAME$Store Group Setup]

[COMPANYNAME$Store Price Group]

[COMPANYNAME$Tender Type]

[COMPANYNAME$Tender Type Currency Setup]

[COMPANYNAME$Tender Type Setup]

[COMPANYNAME$Trans_ Payment Entry]

[COMPANYNAME$Trans_ Sales Entry]

[COMPANYNAME$Transaction Header]

[COMPANYNAME$Unit of Measure]

[COMPANYNAME$VAT Posting Setup]

[COMPANYNAME$Validation Period]

[COMPANYNAME$Vendor]

[COMPANYNAME$WI Discounts]

[COMPANYNAME$WI Price]

[COMPANYNAME$WI Setup]

[COMPANYNAME$WI Store]