Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Here you will find the relevant information about on-prem to on-prem and on-prem to cloud migration paths.

Expand
titleMigration on the Cloud instance

If you have been using Stratus-addon’s PlantUML on-prem solution, no action is required on your part.

If you have been using Avono’s PlantUML on-prem solution you need to perform the conversion.

Migration page is available at <your_instance_url>/wiki/plugins/servlet/ac/com.mxgraph.confluence.plugins.plantuml/plantUmlConfig

Image Removed

Converter requires page and attachment write permissions for the user running it.

It is recommended to first run the conversion on a copy of production space. Converter is not guaranteed to provide 100% fidelity immediately as it is subject of continuous development.

Feedback is welcome and you may direct it at our help desk.

Expand
titleMigration on the on-prem instances (server and DC)

If you have been using Stratus-addon’s PlantUML on-prem solution, no action is required on your part.

If you have been using Avono’s PlantUML on-prem solution you need to perform the conversion.

Migration page is available at <your_instance_url>/plugins/servlet/plantumlcloud/admin

Image Removed
  1. Create a test environment by importing or cloning the production Confluence server instance. This step is optional but we always recommend running the import on a test instance first.

  2. Install the PlantUML Diagrams for Confluence server add-on.

  3. Rebuild the search index.

  4. Navigate to <confluence_url>/plugins/servlet/plantumlcloud/admin and open the Avono import tab like on the example screenshot below.

  5. To perform the import, click on 'Import' button and wait for the process to finish.

  6. Download the import report .

  7. Perform visual inspection of imported pages to make sure the import process has completed with satisfactory results.

Important notice on migrating Avono’s macros

Avono’s add-on contains set of Confluence macros. Most users use only plantuml macro but there are several others like flowchart or plantumlrender which use non-standard PlantUML syntax. This migration procedure will only migrate plantuml and linkgraph macros, other macros are currently not supported.

Empty Avono diagrams will not be migrated to Stratus Addons’s format and users will need to remove them manuallyPlantUML Diagrams for Confluence supports automated conversion of Avono’s PlantUML diagrams.

There are two ways to do it. We recommend the first on in order to minimize https://stratus-addons.atlassian.net/wiki/spaces/PDFC/pages/1935835153/Known+issues?atlOrigin=eyJpIjoiNzUzZWZhMmU3MDRkNGU1N2FmMTVkODhkOTEyNzE1NzciLCJwIjoiYyJ9

First approach

  1. SeeConverting on Data Centre.

  2. Migrate to cloud using CMA.

  3. See Converting in the Cloud

Second approach

  1. Migrate to cloud using CMA.

  2. See Converting in the Cloud

Is is always recommended to run the first conversion on a staging system before running it in production in order to make sure results are satisafactory.