Skip to main content

Installing LS Central - POS on local machine

Introduction:

In this blog, I'm attempting to capture the LS Central - POS installation process on Local Machine.
This blog has nothing to do LS Central - Server Setup for POS.
LS Retail / LS Central - On Premise POS


Pre-requisites:

  • LS Central Installed on Server
  • SSL Setup on LS Server (https://www.olisterr.tech/2020/03/how-to-setup-navuserpassword-with-ssl.html)
  • LS - POS Installer
  • Business Central - On Premise Installer

Demonstration:

Once your LS Retail / LS Central POS is setup on the main server. Just prior to Go-Live, you will actually have to install this POS on multiple systems and connect these POS to the main server with LS Retail / LS Central.

0.Preparation:
Prior to actually installing Business Central On-Premise Windows Client, you need to make sure that you're able to ping the target with the correct Port number. For this I made use of PS-Ping tool. 
PSPing - IP Address: Port

If you're unable to PS-Ping the correct IP with Port number, simply check the Advanced Firewall Setting  in Inbound and Outbound Rules.

Inside Windows:
Inbound Port 7046
Inbound Rules - Port 7046

Outbound Port 7046
Outbound Rules - Port 7046

In Azure:
Inbound Port 7046
Inbound rules - Port 7046

Outbound Port 7046
Outbound Rules - Port 7046


1. Install NAV / Business Central Windows Client:
In Business Central On-Premise Installer, simply select the Windows Client and remove all other components.

Install the NAV / Business - On Premise Windows Client Component

Goto C:\Users\<YOUR USERNAME>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\140

You will find the ClientUserSetting.config file and change the parameters as marked

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <appSettings>
    <add key="Server" value="YOUR SERVER" />
    <add key="ClientServicesPort" value="7046" />
    <add key="ServerInstance" value="BC140" />
    <add key="TenantId" value="" />
    <add key="ClientServicesProtectionLevel" value="EncryptAndSign" />
    <add key="UrlHistory" value="localhost:7046/BC140" />
    <add key="ClientServicesCompressionThreshold" value="64" />
    <add key="ClientServicesChunkSize" value="28" />
    <add key="MaxNoOfXMLRecordsToSend" value="5000" />
    <add key="MaxImageSize" value="26214400" />
    <add key="ClientServicesCredentialType" value="NavUserPassword" />
    <add key="ACSUri" value="" />
    <add key="AllowNtlm" value="true" />
    <add key="ServicePrincipalNameRequired" value="False" />
    <add key="ServicesCertificateValidationEnabled" value="true" />
    <add key="DnsIdentity" value="" />
    <add key="HelpServer" value="" />
    <add key="HelpServerPort" value="0" />
    <add key="ProductName" value="" />
    <add key="TelemetryDeploymentType" value="" />
    <add key="TelemetryInstrumentationKey" value="" />
    <add key="UnknownSpnHint" value="(net.tcp://localhost:7046/BC140/Service)=NoSpn;(net.tcp://YOURSERVER:7046/BC140/Service)=NoSpn;" />
  </appSettings>
</configuration>

The result should be you getting access to Windows Client.
Windows Client


2. Install LS Retail / LS Central POS:
Simply install the LS Retail POS Setup just as you would on your server, and change the config file.
After this is done, head over to C:\Program Files (x86)\LS Retail\NAV\LSStart and find the file LSStart.exe.config File.
Replace the <Nav> section with and change the parameters as marked.

<Nav>
              <Title>POS</Title>
              <ExePath>C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\140\RoleTailored Client\Microsoft.Dynamics.Nav.Client.x86.exe</ExePath>
              <Username />
              <Password />
              <Domain />
              <NetLogin>false</NetLogin>
              <WaitForExit>true</WaitForExit>
              <Company>TEST</Company>
              <Object>
                <Type>Page</Type>
                <Id>99008950</Id>
                <Name>EPOS Main</Name>
              </Object>
              <ServiceTierList>
                <ServiceTier>
                  <Name>BC140</Name>
                  <Port>7046</Port>
                  <Host>YOUR SERVER URL</Host>
                </ServiceTier>
              </ServiceTierList>
              <WindowMode>Fullscreen</WindowMode>
</Nav>

The final result will be that you will get access to LS Retail POS.
LS Retail POS


3. Access Web - POS:
This method is suitable for mobile devices such as Tablets, Phones or mini-computers.
Simply login into your Browser with the Web Client URL
Business Central - Web Client

Select the LS Retail Role

Once, you have selected the correct Role, automatically your Business Central session will refresh and will initiate LS Retail Web-POS
LS Retail - Web POS Initializing
LS Retail - Web POS - Login Screen

LS Retail - Web POS - Transactions


Conclusion:

Although this might look like a complicated process, it is relatively easier than the SSO setup.
Just that you need to verify connectivity at each step. Overall the gist is you just install the client, modify configurations like IP and Port and Instance name and Credential Type and you're done.

I hope this helps 😉






Comments

Popular posts from this blog

Understanding and How to use APIs Business Central - 2

Introduction: In my last blog post ( Business Central API -1 ) on Creating API in Business Central, we discussed all the commonly used properties of the page, query, and controls like field and data-item. In today's blog, we will be diving deeply into the validation of the data passed through the API endpoint, how it enters into the source tables and is manipulated to be inserted/modified into single or multiple tables. Also, I will be demonstrating how APIs are to be used. Pre-requisites: Microsoft Dynamics Business Central (SaaS) VS Code( https://code.visualstudio.com/download ) AL Language Extension( https://tinyurl.com/yyvzxwkb ) API V1 from Business Central On-Premise DVD Books & References: API V1 from Business Central On-Premise DVD API(V1.0) for Business Central ( Click Here ) API(Beta) for Business Central ( Click Here ) Theory: Understanding API in Business Central 1. BINDSUBSCRIPTIONS: Use to trigger IntegrationEvent for the Codeunit stated

Creating APIs in Business Central - 1

Introduction: While writing a blog on Automated Testing in Business Central, I was going through sample apps provided by Microsoft and realized that the complexity is nowhere close to what examples Microsoft has provided on docs.microsoft.com. In this blog, I will try to explain how APIs work and how to be creative with the implementation. Also, an API which were in beta are finally out with version V1.0 in the April 2019 release let's see some important key things from development aspects. This blog is going to be theoretical one kindly bear with me. Pre-requisites: Microsoft Dynamics Business Central (SaaS) VS Code( https://code.visualstudio.com/download ) AL Language Extension( https://tinyurl.com/yyvzxwkb ) API V1 from Business Central On-Premise DVD Books & References: API V1 from Business Central On-Premise DVD API(V1.0) for Business Central ( Click Here ) API(Beta) for Business Central ( Click Here ) Solution: Key Requirements: API source table

Enum Object in Business Central - How to create and how to extend!

Introduction: Since the dawn of Business Central Era (2nd April 2018 - Today), there are many new data types introduced by Microsoft. One such data type is Enum(Enumeration). Essentially, what enumeration is having a single select value with multiple options at a given time! Well, I know what your thinking what about the 'Option' data type. Anyways, enough of talking let's just dive in! Disclaimer:   The knowledge in this blog is true and complete to the best of authors and publishers knowledge. The author and publisher disclaim any liability in connection with the use of this information. Pre-requisites: Microsoft Dynamics Business Central (SaaS or On-Premise) VS code with AL Language extension Code: 1. Enum as an Object: Just like Tables and Pages, Enum behaves like an Object. Enum Object Note that Extensible means that the Enum Object can be extended in another module. By default, this property is set to TRUE. Enums created in a module(App), ca