Showing results for 
Search instead for 
Do you mean 
Reply

Template upgrade tips for TC10.1 from 8.3

Started to check on our upgrade from TC8.3 to TC10.1

In the TEM upgrade process I have come to the step Upgrade Database features when it's verifiying the different templates.

What I now can see is that our company template needs an upgrade ... but I haven't installed the new BMIDE version yet.Smiley Surprised

 

So as I understand I need to install BMIDE 10 first and make upgrade of our template.

And so I did just coming to the next stop ... BMIDE needs the templates for our other integrations like swim, ipem, tcic etc and they need to be from the supporting version of TC10.

... so to be able to get the BMIDE import step to work I needed to extract some parts of each integration template package (the file [integrationname]_template.zip) plus the fountation_template.zip (found it in the TC10 installation folder) then finally add the old master.xml file which we have in our 8.3 BMIDE template folder located in [TCROOT8.3]\bmide\template.

 

So now I have been able to upgrade our BMIDE template so that good but the steps to get there I feel is akward!

How did you do it?

 

 

2 REPLIES

Re: Template upgrade tips for TC10.1 from 8.3

We didn't do it by ourselves, the Siemens consultant checking that the upgrade process succeeds did it.

 

He then used the migrated template for the migration of our production system.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk    Testing: NX11.0 EAP, NX12.0 EAP

How to Get the Most from Your Signature in the Community

Re: Template upgrade tips for TC10.1 from 8.3

I have recently started doing this as well.  I installed BMIDE 10 and then through the BMIDE added the baseline templates.  Configuration Manager>Perform maintanance>BMIDE>Add/Update Templates for workingg with BMIDE click add and then browse...

 

I started by adding CM from the list...

 

I did not manually rip anything out I just had to browse to the "feature_<proj name>.xml" file location in the deployment package.  This automatically built up the dependant templates and master.xml file.

 

 

Hope that helps,