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?

  • Hello Daryl,
    A project of this complexity is best broken down into separate upgrade projects.
    You could upgrade the license manager first, as the latest SLM server can act in a backward compatible fashion.
    How the TeamTrack/VM combo is best upgraded depends on how they are currently integrated. Are you using issue association from within Version Manager? If so, can you please indicate from which VM interfaces this is used? Examples are: desktop client GUI, web client, SCC IDE interface and Rich IDE (RIDE) interface.
    With respect to retaining your workflows, I'll leave that part of your question for a TeamTrack/SBM expert to answer. I'd be happy to provide info on the License Manager and VM issues, though :-)
    Kind regards,
    - Richard.

  • TeamTrack and Version manager are not integrated at all. They just share the same license manager.
    We use Version manager to manage Powerbuilder and VB projects, and the desktop client GUI to manage VM (to add projects and view/restore to previous versions). We would like to integrate SBM with VM in the future.

  • SBM is not currently supported on a 64-bit server, but it will be in the next release (SBM 2009 R4) that should be available within the next few weeks. It also looks like the integration with VM for that version of SBM needs VM 8.3 or newer if you are going to be using Sourcebridge. Also, as Richard stated, it is best to do the upgrade in steps so that you're not changing too much at one time.

  • So we know that we can upgrade our production TeamTrack 6.5 database to 32bit MSSQL2008
    (we are already at TT6.6.1

  • 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.

  • Also, TeamTrack 6.5 is not officially supported on SQL Server 2008 because SQL Server 2008 was not available when TeamTrack 6.5 was released so it was not tested by us. You will want to upgrade to TeamTrack 6.6.1 before you go to SBM and your test platform with SQL Server 2005 should work for that.

  • Bill,
    What part of SBM is 64bit in SBM R4?
    You suggest that Application engine and Orchestration engine can be 32bit? What's left? I read the Moving to SBM documents once, so now that we're in the process of migrating, and I have more questions, another read might be in order...
    Last time I checked the scripts were all Perl scripts, which we don't use.
    As I mentioned we already are in 6.6.1 on our testing platform. However our production copy of TT, which we are not touching for now, is still in 6.5. The purpose of moving to 6.6.1 is to prepare the Db for the jump to SBM. Since we've done that already, our test-Db should be ready for our test-SBM.
    So the question remains - at this point can we just install a brand new version of SBM in a sql2008 environment(along with its "engines") and import the TT Db when we're ready?

  • Daryl,

    SBM 2009 R4 has the ability for any of the Components to be loaded on either 32-bit or 64-bit Microsoft Windows Servers.

    The Components are:

    - Applicaton Engine

    -- Web Interface

    -- Notification Server and Mail Client

    -- Web Services

    - Mashup Manager

    - Orchestration Engine

    -- Event Manager

    -- BPEL Engine

    - Single Sign On

    - Common Services

    Also, you may combine all the data into one single database or separate it out among up to 4 databases:

    - Application Engine (the old "TeamTrack" tables, plus some)

    - Orchestration Engine

    - Mashup Repository

    - Common Log

    It is common practice to separate out the Application Engine tables from the other tables.

    Now for the upgrade...

    Yes, you can install all the components fresh on your new Windows (64-bit?) server(s) and then just point the various components to the restored database.

    You will need to run the Unicode Upgrade Utility before connecting any of the other components to the database.

    After a succssful Unicode Upgrade, when the SBM System Administrator (new name for the TeamTrack Administrator) is pointed to the TeamTrack 6.6.1 database, it will complete the upgrade of the database to SBM 2009 R4.

    Please refer to the Moving To SBM document I mentioned before for complete instructions. Also take backups of your database at critical steps to avoid having to repeat steps in case of a problem during the upgrade.