WAN Performance Intralink 3.x

[ocorten-2]

Hi,

Are there any tools/configurations/tricks available to speed up
Intralink 3.x over a WAN?

In our case the clients are at the other end of the world working on a
server at our end over a dedicated WAN.

I know that Windchill is THE solution, but at this time we need urgent
WAN performance improvement for Intralink 3.x and can't go to Windchill
on such short notice.

From tests we can see that the latency is the biggest problem.
Our remote users also experience frequent Intralink client crashes.

Any ideas?

Thanks in advance,

Olaf Corten.


Olaf Corten
CAD/PLM Manager, Besi Comptence Center - Other Business Applications
Fico BV, Duiven, The Netherlands
Tel.: +31 26 3196215
Fax: +31 26 3196200
Mobile: +31 644548554
www.fico.nl

[pwilliams-3]

Look into HP RGS. It's not Pro/INTRALINK over the WAN. It's more like Remote Desktop but it works well.


Patrick Williams | Engineering Systems | Sr. Applications Engineer | Steelcase Inc. | 616.698.4078

[cid:image001.jpg@01CA4E4B.0035A5B0]

[ptc-113113]

I use plain ole RDP over our WAN to run 3.4 remotely. Works much better than running 3.4 over the WAN. Downside is I need to have a dedicated workstation at the remote site, which so far has not been an issue for us. Pro/E over WAN, not so good, so probably not a solution.
Andrew

[TerryMcFall]

I have heard of, but not played with, a setup where you RDP to a workstation near the server and checkout files. Then FTP the entire .proi folder to your remote site to perform the work. Reverse the process to check files back in.

Folder structure would have to be the same for local and remote workstations. You may also want to beef up the network connection (Riverbed Technology?).

Not the most elegant solution but it could bypass a lot of IL frustrations.

-Ter

Terrence (Terry) McFall
CAD Systems Administrator

Varian Medical Systems
911 Hansen Way
Palo Alto, CA 94304
650-424-6039 desk
650-799-0179 cell

[BarrySchaeffer]

That's what our China users do. The .proi lives in a folder called
ILPACKAGE, you set PDM_LDB_PATH to that folder in a script and all runs
as before.



Checkin and checkout happen only on the box that has low latency to the
intralink server, in our case using Remote Administrator.