Scott Lyon - Thursday, July 17, 2014 4:11 PM:
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
With our merger to a company in Tennessee, we are looking for a best practice for Aras that will be shared between multiple locations. Do we have two servers (each running Aras) and somehow keep each in sync with the other, use just one server and have Tennessee connect via the Internet, or go another route that we haven’t yet considered? Are there any white papers on the issue of geographically separated entities using the same instance of Aras? I couldn’t find anything on the Internet that discusses our issue. Thanks.
DavidSpackman - Tuesday, July 22, 2014 7:00 AM:
HI Scott,
Have you read the Platform Specification? http://www.aras.com/support/documentation/
It would depend on how much information needs to be shared between the two sites.
If you need both sites to be accessing the same data to same information and collaborate together, it doesn't make sense have two different application servers.
For two Aras instances you would need to manually setup some kind of data sync between them using AML or webservices. It would be a lot of over head to manage.
If you are under subscription, I believe that Aras will only update one production instance of your database, so keep that in mind too.
We have two locations accessing Aras, one in Australia and one in Taiwan.
Both the application server and vault are located at our Australian office.
Taiwan staff access Aras from our internal intranet, there is no internet access.
Application access from Taiwan isn't as good as Australia, but still OK.
Downloading and uploading of files is slower and can be frustrating for users in Taiwan.
We are soon going to be looking at setting up a replicated vault to overcome the issue.
Dave
DavidSpackman - Wednesday, July 23, 2014 8:49 AM:
HI Scott,
Here is another reference
http://www.aras.com/Blogs/ACE-2010-international/14-ACE-2010-Replication-Workshop.pdf
Dave
