|
Hi
Mike
A while back
we simulated some long distance Axapta client connections by bouncing the
connection backwards and forwards across the Atlantic between two data centres;
one in the UK and one the west coast US. By increasing the number of times it
hopped back and forth before completing the connection we were able to simulate
a connection of much greater distance (i.e. we increased the latency on the
connection).
Using native
Axapta thin client technology the user experience was sluggish when the
connection had been extended to 2 round trips (after allowing time for the
Axapta caching to take effect). Using terminal services eradicated the problem,
but Citrix was the real killer. If I recall correctly, we were able to extend
the connection to 6 round trips using Citrix and still get an acceptable level
of user experience.
With the
distribution of locations that you have I would say that you'd get acceptable
performance using plain terminal services (we did our tests on W2k terminal
services; my understanding is that the W2003 RDP protocol is a bit more
efficient). There is also no reason why you shouldn't use Axapta object servers
in combination with terminal services or Citrix, in fact I would recommend it as
it means all your users benefit from the object server caching rather than
maintaining their own caches.
Regards
Malcolm Burtt
Global
IT Group
"Business Solutions designed for YOUR business
processes"
Global IT Group is the trading name of Touchstone Global Business
Solutions Ltd. and is part of the Touchstone Group
PLC.
Regards
Malcolm Burtt
Global
IT Group
"Business Solutions designed for YOUR business
processes"
Global IT Group is the trading name of Touchstone Global Business
Solutions Ltd. and is part of the Touchstone Group
PLC.
My Company is about to sign a contract to
purchase Axapta and Consulting services from a local VAR. We are an
International Company. Our main office and IT Dept (including
all servers) are on the East Coast. We also have offices in Europe,
the UK, Canada, and we have a warehouse in California. We have
concerns about the ability of Axapta to respond in a timely manner
from remote sites (like Eastern Europe, UK, Canada, and
California). We did a site visit and did some testing with remote
access. They had really slow response times unless they used
terminal services. Even then, the performance did not seem
consistent.
We are purchasing all modules except HR.
Our heaviest traffic will be in the areas of CRM, Quoting, Sales Order
Processing, Product Management and purchasing, and manufacturing. We
have about 125 local users and about 30 - 40 remotes users who need full
capability (not just sales reps that can use the web portal to view stock
status, or create quotes)
I would like to hear from anyone with experience
in remote access. If you had this problem I would like to hear how you
fixed it. If you have remote users who never had this problem, I would
like to hear that too. Any help would be greatly
appreciated.
Best Regards,
Mike Matta
Sharing the
knowledge on Axapta.
Sharing the knowledge on Axapta.
Yahoo! Groups Links
| 
