Steps to install OPOS drivers

vicky hu — Fri, 17 Apr 2015 02:15:51 GMT

When working with partners who have problems connecting to their Retail peripherals. I sometimes found that they had both Windows Driver and OPOS driver installed or have the drivers installed in different sequence. Usually I’d suggest them to follow below steps to install the OPOS driver.

Firstly, please uninstall any Windows drivers for the retail peripheral from the PC, otherwise it might have some conflicts with the OPOS driver framework. Note that we must completely remove the drivers and then re-deploy the OPOS driver for the hardware.
Secondly, install the most recent OPOS driver from the printer manufacturer’s web site. You will also receive the complete install guide as well as other materials esp. the built-in OPOS driver test utility to verify your OPOS driver is running successfully.
After that, deploy other OPOS hardware, following the OPOS CCO once again which is from this 3rd party vendor web site: https://monroecs.com/oposccos_current.htm. You could install 1.13.001 CCO Runtime (Windows Installer MSI).
Now you can run the OPOS driver test utility provided by the manufacturer to verify whether the driver is installed correctly.

If additional POS peripherals are implemented, please repeat step 3.

Before updating the hardware profile in AX, we will need the peripherals info from registries. The root path of interest is below for both 32 or 64 bit systems.

32-bit Systems: HKEY_LOCAL_MACHINE\SOFTWARE\OLEforRetail\ServiceOPOS

64-bit Systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OLEforRetail\ServiceOPOS

Beneath the ServiceOPOS you should see keys for each device type installed, such as a CashDrawer and POSPrinter key. Beneath each of these you'll see the names of the devices. The name shown here is what needs to be used in your Hardware Profile when configuring these within AX. For example, if you have an TM-T88IVP and it is in the registry as HKEY_LOCAL_MACHINE\SOFTWARE\OLEforRetail\ServiceOPOS\POSPrinter\TM-T88IVP, the name entered in AX should be TM-T88IVP. The same will be true of any CashDrawer or other hardwares. Check the registry entries for your drawer/printer exist in the registry and make sure that the names match those you have configured in the hardware profile.

After updating the hardware profile in AX, we could run 1090 job to push the settings in POS client.

[AX2012 ]Accessing Commerce Data Exchange RealTime Service from workgroup POS

vicky hu — Thu, 16 Apr 2015 01:38:00 GMT

Commonly in test/POC scenarios, we will use self signed certificate for realtime service. And when we need to access real time service from workgroup POS (eg. perform inventory look), it will report us security errors. To make self-signed certificate works in this scenario, we need to manually export the .pfx and .cer file for the self signed cer and import it into the workgroup computer. here are the detailed steps.

How to install a Self signed Certificate

Creating the self-signed certificate on the IIS server

Open Administrative Tools and click on the “Internet Information server (ISS) Manager”
On the Instance home, click on “Server Certificates”

3. In the right actions pane, click on the “Create Self Signed Certificate”

4. Specify a friendly name and press OK

5. The Server certificate is now created.

To export the .pfx and .cer files

On the server where you installed the certificate, choose Start, choose Run, and then in the Open box, type MMC. Choose OK.
On the Console page, on the File menu, select Add/Remove Snap in.
On the Add/Remove Snap-in dialog box, choose Add. The Add Standalone Snap-in page appears. Select Certificates and then choose Add.
On the Certificates snap-in page, select Computer account, and then choose Finish. On the Add Standalone Snap-in page, choose Close, and then on the Add/Remove Snap-in page, choose OK.
On the Console page, in the navigation pane, expand Certificates – Local Computer, and then expand Personal.
In the navigation pane, select Certificates.
In the details pane, locate the certificate with the friendly name you just specified before.Right-click this certificate, select All Tasks, and then choose Export.
The Welcome to the Certificate Wizard dialog box appears. Choose Next to continue.
On the Export Private Key page, select Yes, export the private key. Choose Next.
On the Export File Format page, make sure that you select Personal Information Exchange – PKCS #12(.PFX).. Choose Next.
On the Password page, supply a password, and then choose Next.
On the File to Export page, type the path and file name of the .pfx file. For example, C:\testcert.pfx. Choose Next.
Choose Finish. On the Certificate Export Wizard page, choose OK to confirm that the export was successful.
Repeat steps 7 and 8.
On the Export Private Key page, select No, do not export the private key, and then choose Next.
On the Export File Format page, make sure that you select DER encoded binary X.509 (.CER), and then choose Next.
On the File to Export page, type the path and file name of the .cer file. For example, C:\testcert.cer. Choose Next.
Choose Finish. On the Certificate Export Wizard page, choose OK to confirm that the export was successful.

Installing the certificate on each workgroup machine

Copy the Pfx and Cer file to the each workgroup machine were you have POS installed.
Double click on the pfx to start the import wizard, and click Next
Click Next
Enter the password for the private key

Do the same for the Cer file. Click on the Install certificate.
You will be prompted that the certificate can´t be certified by the Certificate Authority (CA). Ignore this and finish the import. And now workgroup POS machines should trust teh self-signed cert issued in RTS server.