Modelcheck install on network

[jnoval]

Hi


I want to have modelcheck install on the network. I have been looking for a config option to telle ProE WF2 where to look for modelcheck (...\modchk\text\usascii). If I can place the files in the not default place then the users can have the same configuration and it will nok be overwrite when upgrading ProE.

 

[slashct]

use the mcdir environment variable and point to where the config is on your network...
If this is the first time installing I would recomend getting the PDF and reading it over quickly...

 

[jnoval]

Thanks

 

[[email protected]]

I am currently writing an article on ModelCHECK for Profiles, I will
see if I can cover the network aspect. If not, perhaps an addendum at a
later time.



However, its not much different than having Pro/ENGINEER installed locally.

 

[jnoval]

I am looking forward to your article


Have e look at:


http://www.ptc.com/cs/tpi/114205.htm

 

[[email protected]]

For me I have all access from the server for software. Because I run MC
from the server install, I don't make use of MCDIR. The batch file that
initiates Pro/ENGINEER has the following related to ModelCHECK:





set MODELCHECK_REPORTS_ROOT=%WORKING_BASE%\modelcheck

set MODELCHECK_PREVIEW=%LOCAL_DRIVE%:\%MODELCHECK_REPORTS_ROOT%\ preview

set MODELCHECK_REPORT=%LOCAL_DRIVE%:\%MODELCHECK_REPORTS_ROOT%\r eports

set MODELCHECK_METRICS=%REMOTE_DRIVE%:\modelcheck\metrics

set MODELCHECK_DUPREAD=%REMOTE_DRIVE%:\modelcheck\dup_read

set MODELCHECK_DUPWRITE=%REMOTE_DRIVE%:\modelcheck\dup_write



if exist %MODELCHECK_REPORTS_ROOT% goto START_PROE

mkdir %MODELCHECK_REPORTS_ROOT%

mkdir %MODELCHECK_REPORTS_ROOT%\reports

mkdir %MODELCHECK_REPORTS_ROOT%\preview



You're only going to use the MCDIR if you set your configurations files
to load from somewhere else other than loadpoint. Pros and cons doing
it either way. I just backup the loadpoint so I don't find having a
separate config folder useful. However for workstation based installs,
I still didn't use MCDIR as I pushed the config files from a server.



Sorry, I didn't cover the super techy stuff in the article as time
constraints and the audience to reach was more suited to keep it lite
and "food for thought".

 

[jnoval]

Thanks