COnnecting Multiple Pro/I clients to ProE

[8675]

I have a local database that I access, and I also support a remote database. I have installed 2 Pro/I clients to do this and was hoping to get away with just installing Pro/E once on my machine. Is there a way to do this so that Pro/E remmebers to save back to the correct workspace?

Thanks.

 

[kdmgooner]

Hello, you dont say which version of PROE you are running but as long as its Wildfire you can use the "server registry" option. In Wildfire select "TOOLS#SERVER REGISRTY" then add the two servers to your list. You can then switch from one server to another and/or one workspace to another without having to close down PROE. The only restriction is that you have to erase any objects from memory in your active PROE session before switching from one server to another, you dont have to make 2 installations of PROE

 

[looslib]

If you enter NO when Pro/E asks if yopu want to close all parts, you can keep what is in memory active. We used this to import files from native filing to PDMLink.

 

[kdmgooner]

I hadnt realised that you could do that with the objects in memory. Going back to the original question then, the answer is use server registry an there are no restrictions.

 

[8675]

The above two methods work, when switching between workspaces. I am not sure whether or not they will work when switching between whole INTRALINK databases, which is our case. I will work on it, and see what happens. My first thoughts are that it won't work, due to the fact that when you install ProE, you need to tell it where the INTRALINK client is installed, and I am not sure how to do that from ptcsetup, for 2 INTRALINK installations

What I have done, is create a new proe1.psf, and proe1.bat, and edit them to refer to the second INTRALINK installation. So far, it seems to be working. Anything that I would miss by editing the psf file? I have also edited the start up batch file to point to the correct env variables.