Requirements for Barcode Integration using NAS and ADCS

ally

Hi there,

Can anyone help me clarify the below issues? :?
Our client requires bar code to be integrated into Navision. We are currently proposing to use Navision Application Server (NAS) and Automated Data Capture System (ADCS).

1. What licenses need to be bought in order to provide the above solution?
a. Web User
According to the price list guide for NAS, at least 1 Web User is needed to access external services via NAS. What is the purpose of the Web user? Is it to enable users to access into NAS to setup certain configurations since NAS does not have a GUI? And if so, is 1 Web user enough to access more than 1 external services connected to the NAS?
b. C/Front
Is it necessary to purchase C/Front for NAS? C/Front is used to access graphics from Navision. Thus if I do not need to display pictures in my devices, it is not necessary to purchase C/Front?
c. Just wanted to clarify that there is no seperate license for Navision Database Server unlike NAS
d. Any other licenses that need to be bought besides ADCS,NAS and the above?

2. NAS and ADCS
According to the ADCS document which comes with Navision CD, it shows that Navision Database Server is in 1 box while the ADCS Box has NAS, Communication System Service (CSS) and plugins. Does the CSS and plugins come with the ADCS or are these separate components that need to be bought? And if so, where can I get them?

3. Thus is it sufficient to purchase 2 servers, 1 for NAS and 1 for Navision Database Server for the above solution?

Last but not least, would appreciate if anyone could share with me their experience integrating Barcode with Navision and if there are other possible solutions besides using NAS and ADCS.

Thanks and regards in advance.

Ally

Miklos_Hollender

ADCS is a fairly complicated and expensive feature. It's basically about a dumbed-down version of Navision running on a handheld, with textmode menus (MiniForms) and you can do picking etc. with it with with radio connection. It requires broadcasters in the warehouse, expensive handhelds, etc. Once I checked it out but gave up as I couldn't find sufficient documentation f.e. which handheld devices fit and which not.

Are you sure you need such a sophisticated solution? There are handheld devices for just $400 each that can do such things and instead of radio, they just connect by putting it into a cradle, upload text files, and then you can import the text files into Navision to the appropriate places - it's only a few days of development, 5-10 at most for f.e. picking and taking physical inventory.

If you still want a radio-based solution, I'd suggest to check out the Add-on Catalog. I mean I've never seen anybody use ADCS so I'm a bit suspicious about it, but there are similar add-ons that are tested, have many clients, and I think it' always easier to get support from another partner than from MS. They tend to be more responsive.

Poltergeist

Installation of ADCS is not hard at all. I've done it several times, without any problem. You need the client, de NAS (Navision Application Server), .net framework 1.1 and MSXML version 3, which are al on the Navision product CD.

It can all be installed on one box. I even suggest to do this. ADCS does not use a lot of bandwidth, memory and the processor, so it would be silly to use a seperate box.

Just follow the installationinstructions in the w1w1InstADCS.pdf in the doc directory of the product CD. It works!

Any handheld device which can set up a telnet session or does understand the telnet communication, can use the ADCS, so I think it's save to say that almost any device can be used. Wired, wireless, it's no problem at all. Even a $400 HP handheld should be able to use it (it ofcourse has no barcodescanner, but alas)

Biggest advantage is that everything is working from Navision. No need to adapt any external programs. Validation is done from Navision. Programming is done from Navision. It doesn't get much easier then that...

ally

Hi there,

Thanks for responding to my post.. Really appreciate it, managed to get better clarity from 2 different prespectives.
However poltergiest, you mentioned you have implemented ADCS before. Did you have to purchase a Web User License and C/Front?
Secondly, correct me if I'm wrong, but the ADCS comes with the CSS and whatever i need to properly install ADCS (eg MSXML and .net framework) will come already in the disk without purchasing anything else?

Thanks once again.

Regards

ally

johnson_alonso

Hi Ally,

Poltergeist wrote:

Installation of ADCS is not hard at all. I've done it several times, without any problem...

Poltergeist is correct. It's all depends on the license and the requirement needed to use it.



Rgds,
Johnson

fl

Hi,

Off course is the ADCS a possible solution to you. But keep in mind that there must allways be a connection (wired or wireless) between the device and the NAS. It's the same when you would use terminal server (because the terminal server client is for the moment on practical all the handheld devices), you can set-up then a direct connection between the device and a terminal server that uses Navision then directly (you need in that case some modified forms to show on the smaller screens of the handheld devices).

For the reason that there allways should be a live connection, I developed a solution, so that I can use the handheld devices (I use Symbol PPT8846) in either batch or wired status. If there is no connection the command will be saved local on the device. When there is connection, it's transfered wireless. I used MCL-designer to develop the solution on the handheld device. On a wired PC, I installed MCL-Net to push the data in the database. On that same PC could a scheduler or NAS be runnning to run a codeunit to post the commands. Because only the wired PC is connected to the database, only one navision client there is needed. The handhelddevice needs a MCL-client license, but thats much cheaper then a Navision client (less then 200$ and even on some brands of handhelddevices included). From navison point of view you only need a scheduler or NAS, a few objects (basicaly one table and one codeunit), one client and N/odbc incase of native database.