|
|
| Troubleshooting / I Have a Problem with AgilePoint Performance | |
In an NLB environment, when I use process activities that access a local file system — for example, SharePoint Upload or Download, or Word or PDF file generator — the operations appear to fail intermittently.
This issue occurs because operations are transferred on the fly from one server to another in an NLB environment. A file may be uploaded to one machine, but the download operation may be attempted on another machine.
Set up a file synchronization between folders on the AgilePoint Server machines in your NLB environment. You can use file synchronization software from Microsoft, or any reliable vendor. Once this is set up, the files will be mirrored on your machines, and the issue will be corrected.
It is recommended that if you use this approach, use a Delay activity after your activity that accesses the local file system to allow time for the synchronization to occur. Usually this synchronization takes a maximum of a few seconds, but it is wise to avoid any synchronization errors that might occur.
Dynamically create temporary mapped drive folders AgilePoint Server can use to share files with a single, external file server. The mapped drives appear as a local folder on the AgilePoint Server machine that only the AgilePoint Server software can access. The mapped drives are deleted when AgilePoint Server shuts down, and recreated when it starts up again.
By using an external file server, this solves some potential network administration issues with synchronizing folders on multiple machines. It simply requires an additional AgileConnector.
To set up the Map Drive AgileConnector, download the attached file from this KB article, and do the following on each AgilePoint Server machine in your environment:
|
|
