Migrate from external configuration store (OpenDJ) to embedded

This topic has 1 reply, 2 voices, and was last updated 2 years, 6 months ago by Andy Cory.

  • Author
  • #27366

    Is there a guide to migrate from external to embedded configuration store ? (I found only the opposite way in Forgerock knowledge base). Also what are the advantages and disadvantages between having configuration store configured as external or embedded ?
    Thank you for help

     Andy Cory

    Hi Visin

    I believe the only advantage of using the embedded config store is simplicity, so is good for a local dev instance, a PoC or similar. In all other ‘real life’ scenarios best practice would be to use an external DS instance. The headline advantages of externalising the config store would be those of scalability, separation of concerns, ease of DS patching, flexibility of architecture (as in, you don’t necessarily need a config store instance per AM in a deployment with many servers – spinning up extra AM instances can be more lightweight, and point to an existing cluster of DS config stores, leading to AM instances being more ‘disposable’.)

    That’s my view, but I’d definitely be interested in others’ opinions on this. I’m aware I haven’t answered your primary question of migration from external to internal, I wonder if that’s ever been done.


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

You must be logged in to reply to this topic.

©2022 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?