Well, of cource you can use this hub for other software but I created it for NAV.
Lets look at these issues
- You can’t support the hardware directly within NAV
- You like to have one method of communicating with hardware from NAV
- Your hardware is on another machine
- Your hardware is on the client machine and you are running NAV as a Remote Application
- Your hardware is on the client machine and you are using remote desktop for your work
This is why I created the Hardware Hub Web Service.
This is an open Web Service that can be used to move data between NAV and a device interface.
To use the hardware hub you will need to create a GUID string. This you can do with the C/AL command FORMAT(CREATEGUID). This string is stored in a text(50) field in the database. When you send a request you include this unique identifier and when you use the receive command to check for commands you use the same unique identifier.
Attached is the Hub Proxy Class to use with NAV. In a production environment the Hub Proxy Class should be places in the service tier Add-ins folder. I also attached a test page that you can use to test the hardware hub service. The test page is running the proxy class on the client side so you will need to copy the Hub Proxy Class (HardwareHubProxy.dll) into the Role Tailored Client Add-ins folder.