Module 4: Pos Framework Module Overview: Objectives

MODULE 4: POS FRAMEWORK
Module Overview
This module explains the POS technical architecture. This module also provides
information about the different components in the POS framework
Objectives
The main objective of this module is to help understand the POS technical
framework, its components and other retail components it uses.
Microsoft Official Training Materials for Microsoft Dynamics

Your use of this content is subject to your current services agreement
4-1
Microsoft Dynamics AX 2012 R2 For Retail in Brick and Mortar Stores Development and Customization
POS Architecture Overview

This course provides information about the different POS architecture
components that include the following:
POS Core
CDX: Real time service and Synch service
POS Database
POS Architecture
The POS Architecture consists of the POS Core components.
FIGURE 4.1: POS ARCHITECTURE CORE COMPONENTS
4-2

Module 4: POS Framework

POS Core
The POS core is the focal point of POS that interacts between the POS user
interface (UI), and the POS data layer, services and triggers.
The key components of the POS core include the following:
Operations
Transaction
SystemFramework
SystemeSettings
DataAccess (Data Layer)
Contracts
The components in the POS core are not extensible.
FIGURE 4.2: POS COMPONENTS

4-3
Operations
An operation is an activity that occurs in Retail POS. Operations can be a single
step, or a multi-step. For example, Add Item adds a sales line to the current
transaction. The Customer add operation presents a form for a cashier to enter
customer information. After data is entered and the form is closed, the customer
information is sent to Retail Headquarters.
Microsoft Dynamics AX 2012 includes a collection of core operations that cannot
be modified. However, you can create new functionality by using the
BlankOperations. You can use Blank Operations to extend Microsoft Dynamics AX
for Retail POS by adding custom logic to the Retail POS register buttons. In the
Retail POS register, you can add the blank operation button to the POS layout and
link it with your custom operations.
Transaction
The transaction dll contains the core transaction classes and Interfaces that are
used in standard and extended components. Most POS operations will have the
POS transaction passed as parameters that are during the operation.
System Framework:
This dll contains the transaction service. This service is a direct start to
Headquarters (HQ).
System Settings:
This dll contains all the settings that are related to connection details, operator
details, terminal details, store details, transaction service details, hardware profile,
functionality profile and other Application details that can be used while
extending POS.
Data Access:
This dll acts as a data layer between the application and the POS database. It
provides a set of interfaces and, or classes that are used in standard operations,
services and triggers.
Contracts
The contracts dll contains interfaces that are used across multiple core and
extended components of Point of Sale. When POS Plugins are installed, this dll is
included as part of plugin code. When you extend a service and, or triggers, add
this dll to the project. Also, dll should be deployed to the POS folder, after you
extend.
4-4


POS Extensibility
POS Extensibility points give the user the option to extend the POS for custom
requirements. The key components include the following:
Services Forms
Although third-party components from the DevExpress libraries were used to
build the POS application, you do not have to be familiar with how to set up a
development environment by using the DevExpress libraries.
All Windows forms in POS are developed by using the "DXExperience Winforms"
product that is created by DevExpress. However, you must have a DevExpress
license to modify the design-time visual changes to existing forms. Although you
are not required to have DevExpress tools to create new POS forms, it is
recommended that you use them to have a consistent appearance with the rest of
the product.
Microsoft Dynamics AX 2012 R2 POS introduces a new way to customize forms by
using the Interaction service. Multiple developers can customize one or more
forms in one service. If there are multiple customizations, the Interaction service
loads only the first customization it finds for a form. The following list of forms
uses this new pattern and their implementations are included in the
InteractionDefaults service.
ExtendedLogOnForm
ExtendedLogOnScanForm
frmBarcodeSelect
frmDimensions
frmInput
frmPayCash
frmPayCurrency
frmPayCustomerAccount
frmReturnTransaction
LogbookForm
LogOnForm
ManagerAccessForm
RegisterTimeForm
ViewTimeClockEntriesForm
ProductDetailsForm
ProductInformationForm

4-5
Skins:
By using the DevExpress SkinEditor program, you can change the appearance of
Microsoft Dynamics AX for Retail POS registers by creating new Retail POS skins.
To create new Retail POS skins, you must obtain a license from DevExpress. Retail
POS uses DXExperience Winforms that is created by DevExpress. You can develop
your own forms without having to use DevExpress. However, it is recommended
that you use these to maintain a consistent appearance.
CDX: Real-time service

Retail POS can make real-time calls to Microsoft Dynamics AX 2012 by using the
Commerce Data Exchange: Real-time Service. This service provides real-time,
synchronous communication between Microsoft Dynamics AX 2012 and individual
Retail POS registers.
Retail POS uses real-time service calls to provide some Retail POS functionality,
such as Issue Gift Card or Create Customer. You can create custom, real-time
service functionality in Retail Headquarters and call it from Retail POS.
In Retail R2 the Real-time Service changed from a Windows Service to an IIS Web
Service. It acts as a traffic handler between the POS and Headquarters to share
real-time information. All actual logic is written in X++ code that is hosted in the
Application Object Server (AOS) and accessed through the .Net Business
Connector. This change in architecture means that the installation and
configuration includes many changes. Refer to the installation guide to set up the
new real time service.
4-6

FIGURE 4.3: REAL-TIME SERVICE
CDX: Synch Service (Retail Store Connect)

Commerce Data Exchange: Synch Service is a service that shares data among retail
components. These components include the head office, stores, and individual
point of sale (POS) terminals. When you install Synch Service, the Retail Salt Utility
and Retail Scheduler are also installed. The Retail Salt Utility provides additional
encryption for the passwords and credentials that are associated with the Retail
system. Retail Scheduler is used to manage the distribution of data between the
head office and the stores

4-7
FIGURE 4.4: CDX SYNCH SERVICE
POS Database
This lesson explains about the POS store database and offline database.
Lesson Objectives
Store Database
Offline Database
Retail Offline Synch Service
Store Database
Store database is a central database that is inside a store. Typically, a store
database is hosted on a shared server that is connected to all the POS terminals in
the store. Multiple POS computers in a store can connect to the same store
database.
Store database data is synched with HQ by using the Synch service.
4-8


Offline Database:
Together with the store database, you can also create the offline database on the
POS terminal. This helps make sure that the store operation can continue even if
the connection to the shared database (store database) is lost.
Retail Offline Synch Service:

The shared database and the offline databases are kept in sync by Microsoft
Dynamics AX for Retail Offline Sync Service. This Windows service will run in the
POS computer and synch the data between the shared database and the offline
database.

4-9
Module Review
Module Review and Takeaways
POS Architecture
POS Core
CDX : Real time service and Synch service
POS Database
Test Your Knowledge

Test your knowledge with the following questions.
4 - 10
1.
What are the main components of the POS architecture?
2.
What is the POS Core?
3.
How is the Transaction library used?
4.
How is the CDX Synch service used?
5.
Which service synchs the data between the store database and the offline
database?

Test Your Knowledge Solutions

MODEL ANSWER:
POS Core, CDX Real-time service, CDX Synch service and store
database
The POS core is the focal point of the POS that interacts between the
POS UI and the POS data layer.
The dll transaction contains the core transaction classes and the
Interfaces that are used in standard and extended components. Most
POS operations will have the POS transaction passed as parameters,
which are used during the operation.
Retail offline synch service.

4 - 11
4 - 12


Module 4: Pos Framework Module Overview: Objectives

Uploaded by

Copyright:

Available Formats

Module 4: Pos Framework Module Overview: Objectives

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Module 4: Pos Framework Module Overview: Objectives

Uploaded by

Copyright:

Available Formats

What are the main components of the POS architecture?

What are the main components of the POS architecture?

What is the POS Core?

What is the POS Core?

MODULE 4: POS FRAMEWORK

Microsoft Official Training Materials for Microsoft Dynamics

POS Architecture Overview

CDX: Real time service and Synch service

FIGURE 4.1: POS ARCHITECTURE CORE COMPONENTS

Microsoft Official Training Materials for Microsoft Dynamics