Note: MS recommend that you install Microsoft Dynamics NAV Server and the VT100 plug-in on separate computers.
Overview and Architecture
ADCS enables you to accurately capture data for inbound, outbound, and internal documents, primarily for warehouse activities.
For example, you can have users scan the bar codes of items in your warehouse as they perform daily tasks, and that information is recorded from these handheld device activities in Microsoft Dynamics NAV.
Microsoft Dynamics NAV Server processes the data coming to in from the handheld devices via the plug-in and sends the appropriate response back to the handheld devices via the plug-in.
An XML format is used to send and receive the data.
The VT100 plug-in makes sure that the response from Microsoft Dynamics NAV is directed to the correct handheld device. This reduces the load on the server.
The VT100 plug-in provides the link between the server and the Access Points for the handheld devices and acts as a virtual Telnet server.
All connection requests and data transmissions are handled by this service, and the incoming native protocol is transformed into standard XML that the server can interpret.
After a request has been transformed, the request is forwarded by the VT100 plug-in to the server.
When a reply is received, it is converted from XML into the native protocol of the handheld device.
Function keys are mapped using an XSLT file that you can modify. After the data has been transformed and formatted, it is forwarded to the handheld device.
Design Overview
The following illustration provides a simple diagram of ADCS. The part of the illustration that is shaded, which does not include ADCS, represents what could be developed.
Consider the following when you deploy an ADCS solution:
You can configure multiple instances of Microsoft Dynamics NAV Server on a single computer, but each instance can only access one company.
Therefore, if you want to access several companies from the same computer, you must configure several Microsoft Dynamics NAV Server instances for NAS Services.
You can only install one instance of the VT100 plug-in on a single computer. The VT100 plug-in can only serve one company but it can communicate with multiple instances of Microsoft Dynamics NAV Server.
This means that all of the instances of the server that use the same VT100 plug-in can only access the same company.
If you want to communicate with more than one company, you must install the VT100 plug-in on more than one computer, one for each company.
Each of the VT100 plug-in installations must then use a separate Microsoft Dynamics NAV Server to access one of the companies.
Note: You can also install the VT100 plug-in multiple times on the same computer, one for each company.
Supported Devices
An ADCS device includes devices such as bar code readers or optical character readers that are used to mechanize the entry of information into the database.
All character-based handheld devices that have a VT100 interface will work with ADCS, although you may have to implement minor adjustments with some models.
When you use a handheld device, you must be able to connect either the Access Point or the RF terminal to the IP or port address of the ADCS server.
If you want to use a graphics-based handheld device, you will have to develop your own plug-in.
You can connect multiple handheld devices to the VT100 plug-in.
However, if performance becomes an issue, you can always add an additional Microsoft Dynamics NAV Server and direct the VT100 plug-in to also connect with the new server to improve performance.
For Step wise Step Installation & Configuration, please follow below posts in order listed below:
Automated Data Capture System Requirements
Installing ADCS
How to: Add Users for ADCS
How to: Enable Web Services for ADCS
How to: Configure ADCS Options
How to: Test the ADCS Connection
No comments:
Post a Comment