Making the transition from CCMS Desktop to CCMS Web for localization
It's important to plan the transition from CCMS Desktop localization to CCMS Web very carefully. Here are some guidelines and recommendations.
You cannot localize in both CCMS Desktop and CCMS Web indefinitely. At the same time, you probably cannot make the switch all at once. It's more likely that as you complete localization projects in CCMS Desktop, you will plan to start the next round of localization for that map in CCMS Web. The timing for this can vary widely depending on your organization's processes and schedules.
There is no one perfect approach for this transition so this topic provides some very general considerations. It depends on your content and your current requirements. Contact IXIA CCMS Customer Support and request assistance in creating your specific transition plan.
No going back and forth!
The two models are significantly different enough that it is not possible to localize the same map in CCMS Web one time and CCMS Desktop the next time. Once you commit to localizing a map in CCMS Web, you must continue to localize it only in CCMS Web. This means the entire map. You cannot localize the map for some languages in CCMS Desktop and others in CCMS Web.
Content localized in CCMS Desktop is view-only in CCMS Web, and content localized in CCMS Web is not even visible in CCMS Desktop. To try to combine the two is an impossible task that IXIA CCMS does not support.
A simple transition scenario
As mentioned, you will most likely transition from CCMS Desktop to CCMS Web for localization on a map-by-map basis. The details of this can vary widely, but here is a sample scenario.
Suppose you localized the WidgetPro 2.0 map, using CCMS Desktop. In the interim, your company shifted to using CCMS Web. Your translation agency notified you that your localization submission is ready. As you receive the translated content, you import it into CCMS Desktop. After you complete an import of the entire map and finalize it, you can mark the WidgetPro v2.0 map so that any future localization requires CCMS Web. See Marking a map for localization in CCMS Web only for more details.
You repeat this process for the WonderWidget 1.1 map you also submitted using CCMS Desktop after you receive it back from the translation agency. You mark it so that future localizations require CCMS Web. Over time, this completes your migration from CCMS Desktop to CCMS Web. Again, see Marking a map for localization in CCMS Web only for more details.
When your users are all using CCMS Web to localize all content, or if you reach a point where all CCMS Desktop translations are simultaneously complete, then it's time to disable localization in CCMS Desktop to prevent anyone from accidentally starting a new Localization cycle using CCMS Desktop. See Disabling localization in CCMS Desktop.