Config.pro for PDM link
Config.pro for PDM link
(OP)
Please respond to the following query:
When we start Pro/E using PDM Link, the system should pull the config.pro from PDM Link server rather than pulling it from the local location.How to achieve this requirement?
Thanks.
When we start Pro/E using PDM Link, the system should pull the config.pro from PDM Link server rather than pulling it from the local location.How to achieve this requirement?
Thanks.





RE: Config.pro for PDM link
Wildfire looks in certain folders for config.pro and these seem to be coded into the software, as does the order the files are processed.
1) Wildfire_Loadpoint_folder
2) $Home
3) Wildfire Start-in Location folder
4) Mapkey run at Wildfire start that reads a config.pro file
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: Config.pro for PDM link
I was just wondering if there was some technique for storing config.pro in the server and pulling it to the local machine while opening Pro/E.
Please Comment. Thanks.
RE: Config.pro for PDM link
V
RE: Config.pro for PDM link
The copy of a text file is so small and fast that the users won't notice it. It assures that everyone is always using the latest company file and that any personalized changes have been made in the proper config.pro.
We used to have a setup like that. It was done by a PTC Application Engineer! Must be in their training.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: Config.pro for PDM link
We use PDM Link and Windchill Product Point for different projects. I was intending to have a config.pro in the server, which could have multiold applications.
Viz making the config file fool proof of any tampering(as per company standards, especially if you have users in different locations, using Pro/E connected to a central server). And secondly, one can remotely control the config settings.
Please let me know if anyone knows a workaround for this.
Thanks.
RE: Config.pro for PDM link
It does slow down the initial startup of Wildfire by about 30 seconds and subsequent Wildfire starts by about 7 seconds. These are after a reboot on Wintel boxes. So you will see the delay every morning at first launch of Wildfire. With a Wintel box, the machine should be rebooted EVERY night to regain memory that Windows doesn't reclaim when an application closes.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli