Upgrade path - TeamTrack circa 2003, to latest and greatest


We are trying to upgrade Teamtrack, Version Manager, Licence Server to SBM and equivalent VM and LS, and our db from MSSQL2000 to MSSQL2008, and our servers from 32 to 64 bit architecture... and this is turning out to be a complete nightmare. Does anyone have a simple upgrade path to move from without having to completely rewrite our workflows?


Parents

  • Hi Daryl - Remember that in SBM there are more "moving parts" than there were in TeamTrack.

    You might want to see if you want to separate out the different parts (Application Engine, Orchestration Engine, etc.) on to different servers. Also, there are portions of the data which you might want to separate out into separate databases on your SQL server.

    The documentation for SBM 2009 R4 has not been released yet, however, to do what you are describing, you can get a good feel for the decisions you have to make if you read the "Moving To Business Mashups Suite" for SBM 2009 R3.02.

    Also, you might want to run the upgrade preparation scripts found in Knowledge Base article S137372 to see what changes will be made to your Workflow and Project structure.
Reply

  • Hi Daryl - Remember that in SBM there are more "moving parts" than there were in TeamTrack.

    You might want to see if you want to separate out the different parts (Application Engine, Orchestration Engine, etc.) on to different servers. Also, there are portions of the data which you might want to separate out into separate databases on your SQL server.

    The documentation for SBM 2009 R4 has not been released yet, however, to do what you are describing, you can get a good feel for the decisions you have to make if you read the "Moving To Business Mashups Suite" for SBM 2009 R3.02.

    Also, you might want to run the upgrade preparation scripts found in Knowledge Base article S137372 to see what changes will be made to your Workflow and Project structure.
Children
No Data