Upgrading AM nodes from 5.0.0 to using amster import/export


This topic has 2 replies, 3 voices, and was last updated 1 year, 4 months ago by Scott Heger.

  • Author
  • #27718


    I am planning to upgrade my AM cluster from 5.0.0 to

    I was wondering if it was possible to clone configuration from my AM 5.0.0 master node to my new AM node following a procedure looking like : https://backstage.forgerock.com/docs/amster/6.5/user-guide/#clone-example.

    I am aware that I certainly need to update JSON configuration files and some configuration parameters in order to :

      Configure new critical functionnalities listed here : https://backstage.forgerock.com/docs/am/6.5/upgrade-guide/#table-critical-changes
      Upgrade the “amsterVersion” : “${amster.version}”, claim in all JSON files exported with amster

    Have you ever tried such an upgrade strategy ?

     William Hepler

    Can you clarify if you plan to
    A. Clone then upgrade
    B. Deploy with the amster export from 5.x?

    Option A should be fine, I wouldn’t recommend option B as there is more than a few changes to the Json/configuration store, there are also scripts that run to register new components and features.

     Scott Heger

    The last step of the cloning process uses the amster import-config command. The rules around that command contain the following:

    You must ensure that the configuration data you are trying to import is compatible with the version of AM you have deployed.

    For example, do not try to import configuration data exported from an AM 5 instance into an AM 6.5 instance.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

©2021 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?