cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Release new Workgroup Managers separately from CPS

Release new Workgroup Managers separately from CPS

In Windchill 10.2 PTC offers the new "Critically Patch Set" -Strategy (CPS).

The reason was to keep Bug-Fixing as simple as possible (via monthly CPS) and release new features via Maintenance Release (Mxxx).

At the moment new versions of Windchill Workgroup Managers (WGM) will also released via CPS.

As a consequence - the effort to implement a CPS is much higher (nearly the same like a Maintenance!) as it should be.

Example: If you are using Windchill Workgroup Manager for CATIA V5 - and you plan to install the latest CPS (due security reasons or whatever) - it might happen that you have to reconfigure the whole WGM including Abstraction Libraries for CATIA!

Also all fileservers has to be updated after CPS.

So it would be very helpful to keep new WGM releases separately from CPS. Or better: Make the WGM completely independent within a Windchill Major Release!

Example: Customer is on Windchill 10.2 M020 and needs a fix for a security issue or a bug. It should be possible to fix this without installing a new WGM.

Example: Customer is on Windchill 10.2 M020 and needs Support for CATIA V5-6 R2015. It should be possible to install only a new WGM-Version - without a complete Maintenance

7 Comments
Amethyst

 

Hi Daniel,

 

 

Yes, installation of 10.2 M020 WWGM-CPS content is NOT optional in 10.2 M020.  But this has changed in 10.2 M030 CPS releases:

 

 

    • PTC Windchill Workgroup Manager for CPS is currently an optional installation in PTC Windchill 10.2 M030 CPS. This means the administrator has the option to choose whether to install PTC Windchill Workgroup Manager CPS.

 

 

    • If the administrator chooses not to install 10.2 M030 PTC Windchill Workgroup Manager CPS and goes ahead with only PTC Windchill 10.2 M030 CPS, then there is no requirement to reinstall PTC Windchill Workgroup Manager on all client systems; however, the administrator would not receive any of the PTC Windchill Workgroup Manager fixes that were provided in PTC Windchill Workgroup Manager CPS.

 

 

    • If the administrator chooses to install PTC Windchill Workgroup Manager CPS, then reinstallation of PTC Windchill Workgroup Manager on all client systems is mandatory.

 

 

    • The administrator can also update the server installation later, if PTC Windchill Workgroup Manager CPS is required.

 

 

Regards,

 

Pankaj Mooteri

 

Emerald II

Starting with Windchill 11.0, workgroup manager installation and update will become completely separate from Windchill and the critical patch set.  The model is being changed to one like Creo - separate downloads and separate maintenance releases for each.  You will need to follow the compatibility matrix, just like Creo today, but upgrades to Windchill will be able to happen before, after, or even without upgrading the workgroup manager.

Newbie

Hi Tom,

Some clarifications on the future plans for  PTC Windchill Workgroup Manager 11.0..  PTC Windchill Workgroup Manager 11.0 will be installed from CD (or download from PTC.COM) similar to the way Creo is installed.  However, it will still be following the schedule of PTC Windchill 11.0.

The current plan is to support any CPS of a given PTC Windchill Workgroup Manager maintenance release with any CPS of the same PTC Windchill  maintenance release.  This will allow CPS to be taken on the PTC Windchill Workgroup Manager side without updating the PTC Windchill server to the same CPS.  Like wise, a CPS can applied to a PTC Windchill server without having to apply the PTC Windchill Workgroup Manager client CPS.   

We sometimes have SPR's that require a submission to WWGM and to Windchill. If an SPR like this is addressed in a CPS, then in order to see that SPR fixec, both PTC Windchill Workgroup Manager and Windchill server will need to be updated to that CPS.   Because of the dependency between PTC Windchill Workgroup Manager and Windchill, it is not possible for them to have different  major and maintenance release cycles.

We are starting with supporting compatibility of any CPS for a maintenance release between PTC Windchill Workgroup Manager and PTC Windchill starting in the first Maintenance release of PTC Windchill Workgroup Manager 11.0 M010.   That information may be different than what was presented in the past, but after reviewing the effort required to support compatibility across maintenance releases, we decided to start with across CPS first.

Regards,

Celia Lee

Emerald II

Celia Lee‌,

Thanks for the update.  Based on what you're describing this doesn't seem much different than what we have now with 10.2 M030.  The Windchill CPS patches already allow us to not update the workgroup manager if we don't want to.

Many of those at PTC Live Global last summer were hoping for the ability to install new maintenance releases of the workgroup manager without having to upgrade Windchill itself.  Do you see this happening at some point in the future?

It's too bad this couldn't make it into 11.0 F000.  I'm guessing M010 is quite a ways out...

What we were hoping for:

What it sounds like we will get (at least for now):

Correct?

Newbie

Tom,

Your diagram is essentially correct. However, we do not provide an CPS for F000 Releases on the PTC Windchill Workgroup Manger as of 10.2 M020.  PTC Windchill Workgroup Manger 11.0 CPS will only start in M010 which is currently planned for June 2016.

Also, the CPS cross compatiblity will be different than it is today. Today, only the  PTC Windchll Workgroup Manger CPS is optional, so you can move forward on PTC Windchill server and keep your PTC Windchiill Workgroup Manager client the same.  In 11.0, you will be able to keep your PTC Windchill server in place and only update the CPS of the PTC Windchill Workgroup Manger.  That allows you to  a new PTC Windchill Workgroup Manager CPS to support a new version of a CAD Tool without having to update the PTC Windchill server.

We realized in planning the cross compatibility of maintenance releases that we would also need to test every CPS.  That quickly expanded the compatibility testing matrix beyond what we could support initially. The revised plan is to first make sure we can support the cross CPS compatibility. This will allow the possibility in the future to support maintenance release cross compatibility through a specific CPS.   In other words, once we have the CPS cross compatibility working,we can look at introducing a specific CPS of PTC WIndchill Workgroup Manger to work with a PTC WIndchill server of different maintenance release, or vice versa.

I understand that it is disappointing to learn that the scope has been reduced, but we needed to break the project down into smaller pieces rather than drop it completely.

THX guys - for clarification! This sounds very good and would be very helpful!

Regards Daniel

Community Manager
Status changed to: Acknowledged