Page Comparison

...

Upgrade Instructions

1. Stop the Tomcat server. Use shutdown.sh on Linux and shutdown.bat on Windows.
   
   

2. Backup the FlexDeploy schemas and Artifact Repository. In case you need to back out FlexDeploy, you can use these backup data.
   
   For back-out purposes, it is highly recommended that a database backup of the Oracle database be taken using standard tools like RMAN. Another option would be to export the FD, FD_ADMIN, and FF schemas using data pump. The schemas can be exported using the following data pump command:

   Tip
   title Backup Database
   expdp system directory=DATA_PUMP_DIR dumpfile=fd_bkup.dmp schemas=FD,FF,FD_ADMIN If this database is exclusively used for just FlexDeploy application, you can rely on Database backup and recovery processes (RMAN) instead of export data procedure.

   It is recommended that a backup of the artifact repository file system be taken in case a back-out is required. The location of the artifact repository was identified in the first step of this documentcan be identified by looking at value of -Dflexagon.fd.repository.root in setenv.sh or setenv.bat file. This file will be in <FlexDeploy Home>/apache-tomcat-flexdeploy/bin/. Standard file backup procedures can be followed. Optionally, the following command (unix only) can be used to create a tar file backup of the entire directory.

   Tip
   title Backup Artifact Repository
   tar –cvzf artifact.tar.gz <artifact repository location>

   
   

3. Upgrade the FlexDeploy schemas
   
   

   Include Page
   FlexDeploy Schema Upgrade FlexDeploy Schema Upgrade

    
4. From the FlexDeploy Tomcat distribution, copy /apache-tomcat-flexdeploy/webapps/flexdeploy.war into <TOMCAT_HOME><FlexDeploy Home>/apache-tomcat-flexdeploy/webapps (overwrite existing file). If you want to take backup of existing file, please copy it outside of FlexDeploy installation folder to avoid confusion later.
   
   
5. If using the Salesforce integration, from the FlexDeploy Tomcat distribution, copy /apache-tomcat-flexdeploy/lib/ant-salesforce.jar into <TOMCAT_HOME> into <FlexDeploy Home>/apache-tomcat-flexdeploy/lib.
   
   
6. Configure Tomcat logging as per Tomcat Logging Setup.
    
7. If using IBM ClearCase, you will need to copy some jar files from your ClearCase server to the FlexDeploy installation
   1. Copy all of the jar files found in the com.ibm.rational.teamapi_8.0.1.vxxx folder of your ClearCase server to <FlexDeploy Home>/apache-tomcat-flexdeploy/lib.
      
      

8. Include Page
   Copy Plugins for Auto Upload - Migration Guide Copy Plugins for Auto Upload - Migration Guide

9. Start tomcat by running the following script
   
   1. <TOMCAT_HOME><FlexDeploy Home>/apache-tomcat-flexdeploy/bin/startup.sh (startup.bat on Windows)
      
      
10. Launch FlexDeploy in your browser - http://<hostname>:<port>/flexdeploy
    
    

11. You should activate newer versions of the Plugins by clicking Activate button as explained below.

12. Make sure there are no plugin jar files left in folder where you copied new plugin jar files as part step 7 above. It may take few minutes for all plugins to load. If there are still plugin jar files after 10 minutes, please look at logs and contact Flexagon support or upload plugins using Upload button on plugins page.
13. Go to Administration - Plugins.
14. You will see newly uploaded plugins on top. Refer to Installed On date.
Activate each new plugin version one at a time. In future versions, plugins will automatically be activated

There is no need to activate plugins manually. FlexDeploy will automatically upload and activate new versions of plugins once they are copied to plugins folder. You will notice that plugins that you copied in Step 8 will eventually be uploaded automatically and folder will not have any jar files left. You can also look at Administration - Plugins in UI and see newer versions of plugins.