Migration Approach
Most large organizations have many independent or semi-independent OpenROAD applications. Usually the same end users are running these applications. In other cases, independent groupings of end users are running applications. Some organizations also use multi-tier architectures using the OpenROAD Server.
These situations raise the question of whether separate applications running different OpenROAD image versions can be migrated independently.
Observe the following guidelines when you are considering selective migrating of OpenROAD applications:
• Dual development environments are required for OpenROAD 5.1 and OpenROAD 12.0.
• Running OpenROAD 5.1 images using OpenROAD 12.0 runtime is not supported.
• If you are using an OpenROAD 5.1 Server, it is not imperative that you migration it just because its OpenROAD clients have been migrated to 12.0. But we recommend, as a best practice, that you migration both sides as part of the overall project. This will keep all your OpenROAD software running on top of the OpenROAD 12.0 runtime while also ensuring that all OpenROAD software was built against OpenROAD 12.0.
Actian Corporation also recommends as a best practice that, if you do plan to migration both OpenROAD clients and OpenROAD Servers to OpenROAD 12.0, you do so in separate phases of the project, performing adequate testing in between. This will help you isolate problems on either the client or server side of the equation during the migration project. Fix or document any problems before moving on to the next part of the migration.
It does not matter whether the client side or the server side of the system is migrated first. Again, this will allow you to isolate issues that might arise during a particular stage of the overall migration project.
If your OpenROAD installation is complex or sizeable, these considerations emphasize the need to plan your migration project to OpenROAD 12.0 (see
Creating a New OpenROAD Environment).
Last modified date: 06/25/2024