Windchill session and stand alone session of Creo...

[snguyen]

Good morning,

Before in Intralink I was able to have a Session on WF4 that
was linked to Intralink and another session with a new license of WF4 that
was not linked to Intralink. Is this possible with Windchill? I use Winchill
in my department to pull up the parts from the Engineers and I use a
standalone to work on the tooling.



Currently I would start a session on Creo and login to Windchill and search
for the part and export it out to a local server. Then I would log off the
Windchill server and shutdown the session of Creo so that my config .pro has
no conflicts of paths. Then I would start another session on Creo and make
sure that I am not linked to Windchill. It is fine most of the time. But
during the day people would ask me questions for parts when I am not linked
to Windchill and I have to save all my work and shutdown that session of
Creo and start a new session that I linked to Windchill. Then go back to a
standalone after I am done with the question.



Before in Intralink I would be able to minimize the session I was in and
fire up Intralink and start a new session of WF4 answer the question and
then resume where I was on the other session of WF4 without switching
servers and working offline.



Switching back and forth with Winchill sometimes takes a long time if I have
a bunch of parts checked out to my workspace and it needs to sync up.

I truly miss Intralink..



Thanks.



Son Nguyen

Great Plains Mfg.

108 W. 2nd Street

Assaria, KS. 67416

785-667-7763 ext. 3477




This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[IainLewis]

Son,



You can obtain the exact behaviour you are after by having a couple of
command to launch ProE. Each different command would set a the system
environment variables that specify the ws location etc.



So for command 1

Set PTC_WF_ROOT=c:\users\with_wc

Set PTC_WF_HOME=c:\users\with_wc

Proe1.bat



Command 2

Set PTC_WF_ROOT=c:\users\without_wc

Set PTC_WF_HOME=c:\users\without_wc

Proe1.bat



You'll then be able to run two different sessions of ProE concurrently
one inside WC and one outside.


I hope that this helps.



Regards



Iain

[davehaigh]

What's not obvious to most users is that even when running ProE outside of Windchill, it still has a cache file.
By default's in:
%USERPROFILE%\application data\PTC\Proengineer <--XP
%USERPROFILE%\AppData\Roaming\PTC\Proengineer <--Win7

Your startup script for ProE can reset the location of this cache file using the command:
set PTC_WF_ROOT=%USERPROFILE%\pro\wf4_maintenance_test\PDMLink_Cache\PTC\ProENGINEER

This allows you to set up different environments for various uses.
As you can see from the command above I have one for testing new maintenance builds of ProE. I also have commands to test our PDMLink QA and Dev servers, each with its own cache.

My suggestion is that you use a startup command for windchill that sets the location somewhere other than default.
You have to also be careful that you never connect to Windchill from the ProE session you want independent. If you do the cache will retain that information and want you to log in the next time.

My startup script looks like this:
set PTC_WF_ROOT=%USERPROFILE%\pro\wf4_maintence_test\PDMLink_Cache\PTC\ProENGINEER
del "%USERPROFILE%\pro\wf4_maintence_test\*.log*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.xml*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.inf*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.m_p*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.out*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.crc*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.usr*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.bom*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.tst*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.ger*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.err*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.lst*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.idx*"
del "%USERPROFILE%\pro\wf4_maintence_test\*.isl*"
del "%USERPROFILE%\pro\wf4_maintence_test\*trail.*"
"P:\wf4-m170-64\proeWildfire 4.0\bin\proe.exe"

I have a shortcut of that on the desktop that has the startin folder set to where I want the home working directory for ProE. This can be different for each startup script.

[cid:image003.jpg@01CC72B5.1DE07C80]

You might want to look at my talk from PTCUser 2010 for more info

[HugoHermans]

Hey Son,

Additional to the reply of Iain, you may use the variable PROE_CACHE to determine where the local cache will be written. By making two startup procedures, pointing to a different local folder for the cache, you may accomplish what you are looking for, as long as you don't register your server from one of the two procedures.

Off topic, but to make it complete, the variable PTC_WF_EVENT is nice to know as well. By cleaning the folder pointed to by this variable, the event list is cleaned every time you start ProE.

Met vriendelijke groeten, Best Regards,

Hugo.