Skip to main content
S
spapik1-Visitor
1-Visitor
September 24, 2019
Question

Node-Locked Creo4 with multiple Windchill cache

  • September 24, 2019
  • 2 replies
  • 2424 views

Dear Experts,

 

I would like to set our Creo4/WCH 11.0 system with multiple cache. I searched the earlier topics in this theme but there aren't clear exatly.

In the psf file have to define the next if i understood well :

ENV=PTC_WF_CACHE=D:\loca1\SPAPIK\C4_M70\
ENV=PTC_WF_ROOT=D:\loca1\SPAPIK\C4_M70\
ENV=PTC_WLD_ROOT=D:\loca1\SPAPIK\C4_M70\
ENV=CREO_AGENT_HOME=D:\loca1\SPAPIK\C4_M70\

SPAPIK is an user.

 

I didn't find anything else in previous descriptions .

Do i have to set anything else ? ( environmental variables )

We have an local active Creo2 and WCH10.2 system with multiple cache. It's work and we like it, but we have to move to a central system ( Creo4;WCH11.0). There are other server adress, other install configuration, etc.

We bought node-locked licenses and we can open more Creo4 sessions, but we cannot use more WS with the different sessions in the absence of the correct settings.

 

I need a little help that what did i set wrong.

 

Thanks

 

 

 

2 replies

T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
September 24, 2019

If you are running Creo from a shared central location then you need to set these two variables as well:

ENV=CREO_AGENT_EXE_PATH=H:\Creo 4.0\M080\Agent\creoagent.exe
ENV=CREO_AGENT_LDP_LIST=H:\Creo 4.0\M080\Platform\4\manifests

 

See https://www.ptc.com/en/support/article?n=CS255889 for more info.

S
spapik1-VisitorAuthor
1-Visitor
September 24, 2019

Hi,

The Creo4 is installed in the local PCs in same localisations but the WCH is on the central server.

THe problem is that just we use ( our location ) node-locked lisenses.

 

I will try your suggest tomorrow

 

Thanks a lot for your help

 

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
September 24, 2019

If you have network servers for Windchill, use part of a disk for a common Creo install. Much easier to mainatain a single copy than XX workstations.

I worked at 1 company where we had 250+ workstations loaded with Wildfire locally. What a PITA to go in and update each one for a new build. It took weeks! Another company had 50+ seats in various departments. An upgrade had to be thought out and sequenced so someone did not try to load a file that had been saved in a newer version. So much easier to do single update and tell the user base "Here is the new shortcut to use". This also allows some user testing before going live.

    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    September 24, 2019

    I put all of my customizations in my own batch file that is called from parametric.bat before the parametric.exe and parametric.psf are read. This way PTC does not overwrite what I want!

    You should also use environment variables instead of a username if it is a network common file.

    %username% would replace sparks.

    Terms & ConditionsCookie settingsAccessibility statement