This process is useful in many situations, for example, Initial proof of concept is completed and production installation needs to be done on different Server and Database.

These steps are provided as guidelines and extreme care must be taken during such migrations. This process is set up for Tomcat but variations of this process can be applied to WebLogic as well.

Export-Import Database

• Export data from source FlexDeploy database.

• Import data into target FlexDeploy database.

Export-Import Metrics Data

• Startup InfluxDB so that the time series data can be exported from the source database

  -- Start up InfluxDB. You can determine the bin directory by looking at the classpath for the FlexDeploy process on the server command line
  cd /flexdeploy/apache-tomcat-flexdeploy/bin
  ./influxd-start.sh

• Take a backup of the data present in the source Influx database

  -- Create a backup of all the data and resources in the source InfluxDB
  cd /flexdeploy/influxdb
  mkdir backup
  ./influx backup ./backup/
  tar -czvf /app/backup/flexdeploy_influx_data.tar.gz ./backup/*
  rm -rf ./backup

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.

• Create tar/zip archive of artifact repository, 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 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

• Update context.xml with target database URL and password for fd_admin user.
• Now start target FlexDeploy and validate it.
• Update System Settings as appropriate.
  • Change FD_SERVER_BASE_URL.
  • Change SMTP_FROM_ADDRESS. This will make sure that emails are coming from different address for Test FlexDeploy.