How To

How do I remove the embedded DS 5.x, 6.x or OpenDJ 3.x after migrating to an external instance?

Last updated Jun 18, 2020

The purpose of this article is to provide assistance with removing the embedded DS/OpenDJ to prevent it from starting up with AM/OpenAM once you have migrated to an external instance. The embedded DJ instance is started and stopped with internal calls rather than through the standard DS/DJ stop/start scripts. The procedure in this article assumes you are not using the embedded instance for any of your data stores.


Removing the embedded DS/OpenDJ

Warning

You must be certain that you are not using the embedded DS/OpenDJ for any of your data stores before proceeding.

You can remove the embedded DS/OpenDJ as follows:

  1. Stop the web application container in which AM/OpenAM runs. 
  2. Make a backup of the $HOME/[am_instance]/opends directory:
    $ cp -r $HOME/[am_instance]/opends /path/to/backupFiles/opends 
  3. Remove the $HOME/[am_instance]/opends directory:
    $ rm -rf $HOME/[am_instance]/opends
    
  4. Restart the web application container in which AM/OpenAM runs.

Restore

To restore the embeded DS/OpenDJ instance copy back the opends backup folder to the AM instance directory as follows:

$ cp -r /path/to/backupFiles/opends $HOME/[am_instance]/opends

Restart the web application container in which AM/OpenAM runs.

See Also

How do I migrate from an embedded to external DS/OpenDJ in AM/OpenAM (All versions)?

How do I add a second configuration store or edit an existing configuration store in AM 5.x, 6.x and OpenAM 13.x?

Data stores in AM/OpenAM

Related Training

N/A

Related Issue Tracker IDs

N/A



Copyright and TrademarksCopyright © 2020 ForgeRock, all rights reserved.
Loading...