Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

These steps can be useful if you are installing a new FlexDeploy environment, and want to load it with specific configurations from a different environment but without execution data. For this process, the source environment must be same FlexDeploy version as the target.

...

  • Stop the source FlexDeploy server in order to take cold backup., or if you have Flashback enabled on the database, you can use FLASHBACK_TIME = SYSTIMESTAMP

  • Export data from source FlexDeploy database. (FF, FD, FD_ADMIN). DBA/admin to perform the activity.

...

  • Plugin folder backup from Source FlexDeploy(This step is needed only if changes were made to any plugin) :Take backup of plugins folder using tar/zip commands on source FlexDeploy server. Plugins folder is under server working directory. You can determine working folder by looking at flexagon.fd.application.root system property on server command line. For example,

    • cd /flexdeploy/application/plugins

    • tar -czvf /app/backup/flexdeploy_plugins.tar.gz *

...

  • We will not copy any Artifact Repository in this process, as we are purging the execution data.

  • Plugin folder restore to target FlexDeploy(This step is needed only if changes were made to any plugin) :Copy plugins tar/zip file to target FlexDeploy server and extract it in the plugins directory under working directory. 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

  • FlexDeploy in target server should ideally be installed before the database copy activity(as per steps in FlexDeploy Installation Guide). However it can be installed in target environment after database copy as well but skip database tier as it was already copied from a different environment.

  • You can also follow the FlexDeploy Upgrade process if the target will have a newer version of FlexDeploy than the source.

  • At the end of process, start FlexDeploy and validate that your configurations are present in various screens.

...