...
- Stop your existing FlexDeploy Tomcat server from OLD_TOMCAT_HOME. Use shutdown.sh on Linux and shutdown.bat on Windows.
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 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 document. 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 tar –cvzf artifact.tar.gz <artifact repository location>
- Extract the zip file in the desired location (referred to as "FlexDeploy Home"). This should be an empty directory, and not unzipped over an existing install.
- Upgrade the FlexDeploy schemas
Include Page FlexDeploy Schema Upgrade FlexDeploy Schema Upgrade Copy the Tomcat configuration files from your existing install (OLD_TOMCAT_HOME) to the new FlexDeploy Home. This will make sure that new installation points to your existing Database and existing Working folder & Artifact Repository.
Info title Windows Copy <OLD TOMCAT_HOME>/conf/context.xml to <FlexDeploy Home>/apache-tomcat-flexdeploy/conf/context.xml
Copy <OLD TOMCAT_HOME>/conf/server.xml to <FlexDeploy Home>/apache-tomcat-flexdeploy/conf/server.xml
Copy <OLD TOMCAT_HOME>/bin/setenv.bat to <FlexDeploy Home>/apache-tomcat-flexdeploy/bin/setenv.bat
Info title Linux Copy <OLD TOMCAT_HOME>/conf/context.xml to <FlexDeploy Home>/apache-tomcat-flexdeploy/conf/context.xml
Copy <OLD TOMCAT_HOME>/conf/server.xml to <FlexDeploy Home>/apache-tomcat-flexdeploy/conf/server.xml
Copy <OLD TOMCAT_HOME>/bin/setenv.sh to <FlexDeploy Home>/apache-tomcat-flexdeploy/bin/setenv.sh
chmod +x <FlexDeploy Home>/apache-tomcat-flexdeploy/bin/*.sh
- If using the Salesforce integration, from the FlexDeploy Tomcat distribution, copy /apache-tomcat-flexdeploy/lib/ant-salesforce.jar into <TOMCAT_HOME>/lib
- Configure Tomcat logging as per Tomcat Logging Setup.
- If using IBM ClearCase, you will need to copy some jar files from your ClearCase server to the FlexDeploy installation
- 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.
- 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.
Include Page Copy Plugins for Auto Upload - Migration Guide Copy Plugins for Auto Upload - Migration Guide - Start tomcat by running the following script
- <FlexDeploy Home>/apache-tomcat-flexdeploy/bin/startup.sh (startup.bat on Windows)
- <FlexDeploy Home>/apache-tomcat-flexdeploy/bin/startup.sh (startup.bat on Windows)
- Launch FlexDeploy in your browser
- http://<hostname>:<port>/flexdeploy
- default credentials are fdadmin/welcome1
There is no need to activate plugins with FlexDeploy 4.5 after Step 9. FlexDeploy will automatically upload and activate new versions of plugins once they are copied to plugins folder