How to change the version of Creo used by Windchill visualisation (Publishing)

[DavidBrand]

I am using Windchill PDMLink Release 13.0 and Datecode with CPS 13.0.2.1

We are about to upgrade from Creo 11.0.2.0 to Creo 12.4.2 and need to re-configure our Windchill visualisation to use the new version of Creo.

I have tried to find out how to do this using the help system and knowledge base, but have been unable to work out how to do it.

Please provide step by step instructions to change Creo version used by Windchill Visualisation.

[BenLoosli]

Where is your CreoView Adapter (Publishing software) installed? Is it on your Windchill server or another computer in your network?

The steps to install a new version don't differ much.

What version of CreoView Adapter do you currently have installed? You may need to install a newer version of that, too.

The Creo software must be installed on the same computer that has the publishing software.

Install the Creo version that you want to use for your publishing.

Be sure to set your config.pro settings for your local install of Creo for publishing. There are some settings that should be turned off when publishing files.

Run the CreoView Adapter configuration program and set it to use the new Creo install location.

[avillanueva]

I've kept the same CAD worker server for many years now. At some point I will upgrade OS but it serves all my environments. I have separate Daemons (worker services), ports and publishing folders. It was easy to install new versions of Creo, create separate worker folders and you can tied them to specific start commmands from Creo (version specific). In this way, you can upgrade the software versions in parallel with production being in operation. My steps would be to install the new version of Creo you want to use with Windchill 13, highest it can support. Install Creo Adapters to the highest version supported. Configure your CAD worker folder and setup a worker service on a port that will handle your upgrade server. You can change it all for go live but its just a matter of keeping track of what paths and commands are being executed. 

[Chris_Johnson]

In general terms (and all from memory, apologies for any slight errors):

1. Update Windchill to 13.0.2.5 or above (required for Creo 12.4 support)
2. Update the Creo View Adapters to 12.1 and the Creo View installation to 12.1 (use PTC solution installer to do this from the same CPS installer disc that you've downloaded for step 1). Do this on the windchill application itself! 
3. On your CAD worker server, copy the existing creo and office worker folders (e.g. proe_setup and office_setup) out of the install directory to a separate location, e.g. c:\ptc\workers\
4. On your CAD worker server update the Creo View Adapters to 12.1 or later.
5. On your CAD worker, install Creo Parametric 12.4.<latest version>
6. Find your worker settings folders that you copied out of the install in step 3
7. Add any specific config.pro / config.sup settings that you require into the worker folders
8. Open the adapter.pvi file to set it up for Creo 12.4. Make sure the startup command points to parametric.bat in the new install location, e.g. c:\program files\ptc\creo 12.4.2.0\parametric\bin\parametric.bat. Also check the version dropdown matches the version of Creo that is installed. Click setup to finish then close the window.
9. Double click on the purge.bat batch file in the worker folder to tidy things up a bit.
10. On the Windchill server go to site - utilities - Visualisation Adapter Administration
11. Edit the configuration of the proe worker to point at the location of the worker.bat file in the folder from the folder in step 3
12. Save the adpater file and reload 
13. Start the workers and watch out for any errors. If you moved the workers in step 3 then you may need to edit the allow list location in your site.xconf file and run xconfmanager -p from Windchill shell before restarting your methodserver service. You'll know if this is the case because the green flag becomes a white flag with a green outline and you can't start the worker. 

[DavidBrand]

Thanks for this explanation and all the other responses. It looks to be a lot more involved than I thought. I will investigate and update once I have made some progress. Any more advice or in depth explanations would be gratefully received.