Planning for Migration from Release 5.x to 6.x

Upgrade migration from Release 5.x to Release 6.x involves several tasks. Before you begin, organize your work with this planning procedure.

1. Choose all of the tasks appropriate to your current release version and use of TIBCO FTL.
   • From Release 5.3 or earlier: If you have not yet upgraded to Release 5.4, you must do so first. Add this task to your plan:
     • A Upgrading from Release 5.3 or Earlier

   • From 5.4: All enterprises use realm servers. You can migrate to FTL servers that provide realm services (6.x) without downtime. Add this task to your plan:
     • B Migrating Realm Servers to FTL Servers

   • From 5.4: If you use persistence servers, and the persistence cluster definitions use dynamic TCP cluster and client transports, then you can migrate to FTL servers that provide persistence services and realm services (6.x) without downtime. Add this task to your plan:
     • C1 Migrating Persistence Servers with Dynamic TCP to FTL Servers

   • From 5.4: If you use persistence servers, and the persistence cluster definitions use static TCP cluster or client transports, then you can migrate to FTL servers that provide persistence services and realm services (6.x). However, the procedure requires some downtime during which persistence clients cannot access persistence data. Add this task to your plan:
     • C2 Migrating Persistence Servers with Static TCP to FTL Servers

   • From 5.4: If you use transport bridges, then you can migrate to FTL servers that provide bridge services (6.x) without downtime. Add this task to your plan:
     • D Migrating Bridge and eFTL Services

     Note that you can complete task D to migrate transport bridges, eFTL servers, or both simultaneously. In any of these cases, complete task D only once.

   • From FTL 5.4 and eFTL 3.4: If you use eFTL servers, then you can migrate to FTL servers that provide eFTL services (6.x) without downtime. Add this task to your plan:
     • D Migrating Bridge and eFTL Services

     Note that you can complete task D to migrate transport bridges, eFTL servers, or both simultaneously. In any of these cases, complete task D only once.

   • From 5.3: To upgrade your client programs to Release 5.4, add this task to your plan:
     • E Upgrading FTL Clients

2. Read the task instructions for the applicable tasks in your plan.
3. Determine the locations of FTL servers and services.
   Assign each FTL server to a host and port location.

   Determine the services that each FTL server should provide.