Versions Compared

Old Version 3

changes.mady.by.user Chandresh Patel

Saved on

compared with

New Version 4

changes.mady.by.user Chandresh Patel

Saved on

Key

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

...

  • Take backup of artifact repository folder using tar/zip commands on Production FlexDeploy database. For example,
    • cd /flexdeploy/artifacts
    • tar -czvf /app/backup/flexdeploy_artifacts_prod.tar.gz *
  • Make sure Test FlexDeploy is now stopped for import process.
  • Copy fd_bkup.dmp file on to Test FlexDeploy database server in to data pump directory, for example - C:\oraclexe\app\oracle\admin\XE\dpdump.
  • Import data in to target FlexDeploy database. Make sure to run this on Test environment only.
    • You will be prompted to enter password for system user. You must delete FD,FF,FD_ADMIN users from Test environment before starting import process. If necessary take backup of Test FlexDeploy database prior to starting this process.
    • Make sure there are no errors in import process. If there are errors, make corrections appropriately and restart import process.

...

  • At this point Test FlexDeploy database should be copy of Production database.
  • Now make various updates to make sure limit access to FlexDeploy Test environment and limit what FlexDeploy Test can do against various endpoints. You can customize any of these steps as per your needs.

    • Disable external realm and users, so access to FlexDeploy is very limited. Update SQL as appropriate for your setup. For example,

      Code Block
      update fd.fd_realm set is_active='N';
update fd.fd_user set is_active='N' where local_user='N'; -- update as appropriate
commit;


    • Disable all endpoints, so Test FlexDeploy can not run any executions until Administrator explicitly enables some endpoints. For example,

      Code Block
      update fd.endpoint set is_active='N' where connection_type='SSH';
commit;


    • Disable production environment. so Test FlexDeploy can not run any executions even for testing against Production environment. For example,

      Code Block
      update fd.environment set is_active='N' where environment_code='PROD'; -- update as appropriate
commit;


  • Copy artifacts zip file to Test FlexDeploy server and extract it in artifact repository folder. Make sure to run this on Test environment only.
    • cd /flexdeploy/artifacts
    • tar -czvf /app/backup/flexdeploy_artifacts_test.tar.gz *
    • rm -rf *
    • tar -xzvf /app/backup/flexdeploy_artifacts_prod.tar.gz
  • Now FlexDeploy artifact repository is also copied.
  • Now you can start Test FlexDeploy and validate it.
  • You can make necessary adjustments to Realm, User, Groups to validate setup and perform tests as necessary. This is necessary as we had disabled user and realms in previous steps.
  • If you have workflows that perform tags on Source Control Systems, make sure to update it before running builds, so you do not conflict with tags created by Production FlexDeploy.