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

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

  • 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.
Children
No Data