Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2021
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
According to the following article,
Commerce component events for diagnostics and troubleshooting - Commerce | Dynamics 365 | Microsoft Docs
A POS client makes a call to the Commerce Scale Unit which provides stateless services and business logic for CPOS and MPOS.
And the commerce runtime which is wrapped in a Commerce Scale Unit layer communicates with Headquarters through CDX real-time services.
Can we simply call Commerce Scale Unit a retail server which resides in the IIS?
Short answer : Yes, Commerce scale unit can be called as retail server but it has more components than retail Server.
Details : Commerce scale unit is combination of following components
- Retail Server
- Commerce Runtime (CRT)
- Channel Database
- CDX client for data sync from HQ
- CPOS Server
Commerce scale unit can be on premise or in cloud, if it's on premise called as Retail store scale unit (RSSU). If that's in cloud called as Retail cloud scaling unit (RCSU)
Now a days both are consider as commerce scale unit.
How data flows :
POS client -> Retail Server (part of scale unit) -> CRT (for business logic) -> channel database / HQ database via real-time service.
Refer attached quick architecture diagram for reference. Note : diagram created just for your understanding. Many components can be added
Hope this will answer your questions.
Does that mean that retail related classes containing business logics run on the Retail server or AOS?
Retail related classes run almost all the layers depending on functionality but CRT is the main layer for business logic.
CRT (.net dll): Business logic for example tax calculation, products fetch, info code, void transaction, etc. All major logic that communicate with channel database.
Retail Server (OData Services): CRT classes exposed as API for clients like POS and eCommerce.
Realtime service (X++) : Create Sales Order, Get real-time inventory, create customer, device activations etc.
POS Client (typescript) : Client side code for UI, messages, data binding, etc.
Business Applications communities