Sometimes you may need to login to another Commonspace, eg: another location within your company, or a test server, etc. This is a fairly straightforward thing to do with the Intralink client you've already got installed.
Here are a few steps to set up a "multi-launch" client... talk to your administrator about the best way to implement this in your company.
The key file in this process is tnsnames.ora in your Intralink loadpoint (eg: \ptc\ilink\proiclient).
A typical file is included here (with the server name srv1 as an example):
1 - The first step is to make copies of this file in the loadpoint folder, with a suffix for each server,
eg: tnsnames_srv1.ora, tnsnames_srv2.ora .
Edit each of these in a text editor (eg: notepad, editpad) - and change the servername appropriately.
2 - Next, add a line to your startup batch file (either a custom pro.bat or the original proilink.bat file) to set the server location you're working with- eg:
set LOC=srv2
3 - Then add a line to copy the appropriate tnsnames file before you call Intralink:
cd \ptc\ilink\proiclient copy tnsnames_%LOC%.ora tnsnames.ora
4 - Finally set an appropriate workspace folder - DON'T MIX workspaces from different servers
set PDM_LDB_PATH=c:\ptc\workspace_%LOC%
So now you have the ability to start Intralink with any server specified in the %LOC% variable. Just be sure not to mix up workspaces created with different commonspaces, and don't try to start 2 instances of Intralink at the same time! That's just asking for trouble...
