You’re offline. This is a read only version of the page.
20
Hi,
we are implementing NAV 2009 across 2 sites, that are joined over a secure VPN (2.5mb) that has a Fortinet firewall either side. Essentially, in SITE 1 we have an ecommerce website (with its own web server), and a website db server running SQL 2008 for the web info, and which will also 'house' the NAV db.
The website will need to query the NAV service tier to access to the NAV db for requests such as customer records via web services (WS), as well as writing orders over to the NAV for processing and order management. So far so good...as NAV 2009 should be able to expose and consume WS within this LAN in the CRUD (create read update delete) way.
However, we want to run role tailored clients (RTC) on remote PCs at SITE 2, so that we can put off-line orders directly onto the NAV system, as well as quotes etc - and to synchrosinse with Outlook business contact manager. The problem appears to be that we are being told that this will only work, ie running the RTC's remotely and accessing the NAV service Tier and NAV db in the remote SITE 1, by using Terminal Services (TS) running the RTC local to the other 2 layers, as oppoosed to on the remote machines, which seems crazy. I understood that you can have multiple instances of any of the 3 layers and that you should be able to 'connect' them all up without the need for a private T1 or dedicated ethernet connection (pricey!!).
We are creating a domain with active Directory (AD) users to see if we can get the RTC to access the Service Tier and NAV db without any performance problems, as the TS is going to be very tricky when it comes to synchronising with Outlook on local machines.
Please can someone tell me if they have come across this set up problem, and whther there is another way of tying up the 3 layers without the need for TS. We have successfully completed a test environment using the TS with a virtualized 3 'box' set up, but it is really rather clunky.
Any help would be very much appreciated.
Kind regards, Rupert (UK)
*This post is locked for comments
I have the same question (0)
I think having all the server components on SITE 1 is solid advice. It won't make a difference whether you have a terminal server on SITE 1 or 2, the users won't be inconvenienced by it. Remote access should be through TS/Citrix, running NAV clients locally and connecting to the serice tier remotely will cause major performance issues.
There's a lot of discussion going on around NAV 2009 on mibuso: http://www.mibuso.com/forum/index.php
Share
Report
All responses (
Answers (
