DS_EMB_REPL* settings for configurator.jar alternative

This topic has 4 replies, 2 voices, and was last updated 4 years, 4 months ago by emimarz.

  • Author
    Posts
  • #18788
     emimarz
    Participant

    Hi all,
    I have two machines on which OpenAM 13 should be installed. I need to start OpenAM installation on both systems in an indipendent way, so I don’t want to include DS_EMB_REPL* settings for configurator.jar. I’d like to give replication settings only later. Will I be able to reproduce all DS_EMB_REPL* options with dsreplication (enable and initialize) commands? Will I be able to get an equivalent effect in terms of dsreplication commands or is something else needed to obtain exactly the same final result?
    Thank you!

    Regards,
    Michele

    #18792
     Peter Major
    Moderator

    If you configure the two OpenaM servers independently, then there isn’t really a way to share the configuration afterwards. Both of those configuration stores will have additional entries that the other does not have, so configuring a replication behind OpenAM’s back will just result in a very confused deployment.

    #18797
     emimarz
    Participant

    Hi Peter,
    thank you for your reply. I explain better. The two OpenAM at the final stage should work in a site and should have exactly the same configuration. So, initial installation and configuration steps for both of them will be exactly the same. After this parallel (indipendent) setup, I’d like to set replication. Is it possibile to act (at the end) with dsreplication commands in order to have the same effect of configurator.jar settings?
    Thank you

    Michele

    #18798
     Peter Major
    Moderator

    They are not going to be identical. Each independent server will have itself listed as the first server (with serverid 01), and the other one will have serverid 02 or 03 depending on when you set up the site.
    You can only implement this if you set up the first server to know about both deployments, and then import that config into the second OpenAM without ever setting up replication. This will mean that the config is identical only because you manually sync’d it. Once you are done with the manual syncs, you can set up replication, which shouldn’t make a difference at that point.

    #18799
     emimarz
    Participant

    Ok understood.
    I try with another hypotesis: has some side effect a procedure in which Openam installation/configuration for both machines start at the same time in a way that one of them sets site and the other one sets site and DS_EMB_REPL* settings (all settings done in configurator.jar options)? In this way, the second machines find itself to activate replication settings while the first is doing further configuration (with another scripted ssoadm batch). Is it problematic? Or is it convenient for the second machine to start installation with replication settings once the first has interely completed installation and configuration?
    Thank you

    Michele

Viewing 5 posts - 1 through 5 (of 5 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?