This page provides instructions for upgrading a FlexDeploy to use newer version of FlexDeploy Docker image. You will need to download appropriate version of FlexDeploy Tomcat distribution for database scripts and plugins.
Upgrade Instructions
Step 1. Stop the Docker container using name. docker stop <name>
Step 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 database be taken using standard tools like RMAN for Oracle. 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 for Oracle as shown below. Follow standard procedures for PostgreSQL and MySQL for database backup.
| Tip |
|---|
| title | Recommendation for Oracle database backup |
|---|
|
You will need to setup environment variables before running expdp. For example,
export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
export ORACLE_SID=fd01
export statements above are for example only as values will be different for your installation.
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 can 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 |
|---|
|
cd <artifact repository location>
tar –cvzf artifact.tar.gz <artifact repository location> |
Step 3. Upgrade the FlexDeploy schemas
| Include Page |
|---|
| FlexDeploy Schema Upgrade |
|---|
| FlexDeploy Schema Upgrade |
|---|
|
Step 4. Copy plugins from download zip for auto upload. This would be a volume that you had configured during installation process.
| Include Page |
|---|
| Copy Plugins for Auto Upload - Migration Guide |
|---|
| Copy Plugins for Auto Upload - Migration Guide |
|---|
|
Step 5 . Pull and start new docker image for FlexDeploy.
| Code Block |
|---|
docker pull flexdeploy/fd_tcat_53:5.3.0.0 |
User same values as used for previous version of FlexDeploy when starting new version of image.
| Code Block |
|---|
docker run --name flexdeploy53 -p 8004:8080 -e FLEX_DB_URL="jdbc:oracle:thin:@129.213.91.244:1521:xe" -e FD_ADMIN_PWD="welcome1" -e TZ=America/Chicago -e dbtype=oracle|postgres|mysql -v /scratch/DockerVolume/flexdeploy:/home/oracle flexdeploy/fd_tcat_53:5.3.0.0 |
| Tip |
|---|
| title | Example JDBC URL (FLEX_DB_URL) |
|---|
|
- Oracle
- Localhost XE connection will look like this. jdbc:oracle:thin:@localhost:1521:XE
- SID based JDBC URL Syntax - jdbc:oracle:thin:@HOSTNAME:PORT:SID
- Service Name based JDBC URL Syntax - jdbc:oracle:thin:@//HOSTNAME:PORT/SERVICENAME
- PostgreSQL
- MySQL
|
Step 6. Launch FlexDeploy in your browser - http://<hostname>:<port>/flexdeploy
Step 7. 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.