...

Export Import Database

...

• Export data from source FlexDeploy database.

• Import data in to target FlexDeploy database.

Copy Artifact Repository

...

, Plugins Folder, Application Binaries

Goal is to just copy the installation and artifact repository to target server. If artifacts and install is done under one common folder, then you can just create one tar for entire set of folders.

• Make backup Create tar/zip archive of artifact repository folder and application install folder using tar/zip commands on Source. FlexDeploy. For example,

...

• , application binaries, plugins folder etc. on Source server. If you have all folders under one root folder which can be copied then archive entire folder that contains artifact repository, application binaries, plugins folder.

-- tar/zip artifacts files, You can determine artifacts repository folder by looking at flexagon.fd.repository.root system property on server command line
cd /flexdeploy/artifacts
tar -czvf /app/backup/flexdeploy_artifacts.tar.gz *
-- tar/zip plugins folder, You can determine working folder by looking at flexagon.fd.application.root system property on server command line
cd /flexdeploy/application/plugins
tar -czvf /app/backup/flexdeploy_plugins.tar.gz *

• Copy tar file files to target FlexDeploy server and extract it in same location as source. If location is different, some files may need adjustment. (For example, setenv.sh)

-- extract artifacts files, You can determine artifacts repository folder by looking at flexagon.fd.repository.root system property on server command line
cd /flexdeploy/artifacts
rm -rf *
tar -xzvf /app/backup/flexdeploy_artifacts_prod.tar.gz
-- extract plugins folder, You can determine working folder by looking at flexagon.fd.application.root system property on server command line
cd /flexdeploy/application/plugins
rm -rf *
tar -xzvf /app/backup/flexdeploy_plugins.tar.gz

Final configuration and start server

...