How do I remove the embedded DS 6.x after migrating to an external instance?
The purpose of this article is to provide assistance with removing the embedded DS to prevent it from starting up with AM once you have migrated to an external instance. The embedded DS instance is started and stopped with internal calls rather than through the standard DS 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
You must be certain that you are not using the embedded DS for any of your data stores before proceeding.
You can remove the embedded DS as follows:
- Stop the web application container in which AM runs.
- Make a backup of the /path/to/am/opends directory: $ cp -r /path/to/am/opends /path/to/backupFiles/opends
- Remove the /path/to/am/opends directory: $ rm -rf /path/to/am/opends
- Restart the web application container in which AM runs.
To restore the embeded DS instance copy back the opends backup folder to the AM instance directory as follows:$ cp -r /path/to/backupFiles/opends /path/to/am/opends
Restart the web application container in which AM runs.
How do I migrate from an embedded to external DS in AM 6.x?
How do I add a second configuration store or edit an existing configuration store in AM (All versions)?
Related Issue Tracker IDs