This page provides instructions for upgrading a FlexDeploy installation. These instructions upgrade Tomcat to the version included in the distribution zip depending on current version of FlexDeploy.
...
Make sure that you have downloaded the latest version of FlexDeploy and unzip it into a temporary location (for example, /u01/software), so it can be accessed during the upgrade process. You can get download links from http://support.flexagon.com. Do not unzip the FlexDeploy distribution directly into the FLEXDEPLOY_HOME directory so we can prevent unwanted file(s) or folder(s) from being overwritten.
Linux
...
language | bash |
---|
Note that following instructions show unzip being done in separate folder than where you have stored downloaded file.
Linux
Code Block | ||
---|---|---|
| ||
mkdir /u01/software/downloadedupgradetempdir cd /u01/software/downloadedupgradetempdir unzip <download location path>/Tomcat_Complete-68.x.x.x.zip |
Windows
Code Block | ||
---|---|---|
| ||
mkdir c:\u01\software\downloadedupgradetempdir cd c:\u01\software\downloadedupgradetempdir unzip <download location path>\Tomcat_Complete-68.x.x.x.zip |
...
Step 3. Backup current implementation
...
See the following example. Make sure to backup apache-tomcat-flexdeploy folder as that is going to be replaced during next steps.
Linux
Code Block | ||
---|---|---|
| ||
cd <artifact repository location>/ tar -cvzf ../artifacts.tar.gz * # The plugins folder may not exist yet depending which version of FlexDeploy you are upgrading from cd <server application directory> cd plugins tar -cvzf ../plugins.tar.gz * # apache-tomcat-flexdeploy (if apache-tomcat-flexdeploy-old exists then use some other folder name) cd $FLEXDEPLOY_HOME mv apache-tomcat-flexdeploy apache-tomcat-flexdeploy-old |
...
Step 5. Apply new version
You must have performed backup of apache-tomcat-flexdeploy folder by now as described in Step 3. If you have not done that, please go back to Step 3 for details.
Note on additional extension jar files : If you had placed additional libraries in apache-tomcat-flexdeploy/lib
folder or in the apache-tomcat-flexdeploy/libext
folder, then you will need to copy them from backup folder into the new apache-tomcat-flexdeploy/libext
folder. Note that all extension jars should be kept in libext folder. Examples might be JDBC driver (for Oracle drivers there is additional detail in the following step), CyberArk libraries etc. Note that Tomcat jar files should never be kept in libext folder.
Copy shell/bat scripts from root folder of extracted FlexDeploy download zip
Copy new Tomcat folder from extracted FlexDeploy download zip
Copy additional jar files from backup taken in step 3
...
Code Block | ||
---|---|---|
| ||
cd $FLEXDEPLOY_HOME cp /u01/software/downloadedupgradetempdir/*.sh . chmod +x *.sh mkdir apache-tomcat-flexdeploy cd apache-tomcat-flexdeploy cp -r /u01/software/downloadedupgradetempdir/apache-tomcat-flexdeploy/* . chmod +x bin/*.sh # restore the libext from the tomcat backup done in Step 3 # if necessary copy other files that you may have placed in lib cd # only run this if you had libext cp $FLEXDEPLOYfolder in your apache-tomcat-flexdeploy-old folder. cd libext cp $FLEXDEPLOY_HOME/apache-tomcat-flexdeploy-old/libext/* . |
...
Code Block | ||
---|---|---|
| ||
cd %FLEXDEPLOY_HOME% copy c:\u01\software\downloadedupgradetempdir\*.bat . mkdir apache-tomcat-flexdeploy cd apache-tomcat-flexdeploy xcopy c:/u01/software/downloadedupgradetempdir/apache-tomcat-flexdeploy /e # restore the libext from the tomcat backup done in Step 3 cd libext xcopy %FLEXDEPLOY_HOME%\apache-tomcat-flexdeploy-old\libext /e |
...
Download the Oracle JDBC 8 driver from https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html. Click on the driver link matching your Oracle database version, and download the driver compatible with JDK8. For example,
ojdbc8-full.tar.gz
.Clean up ojdbc jars from <FLEXDEPLOY_HOME>/apache-tomcat-flexdeploy/lib. (For example, ojdbc6dms.jar)
Save new driver jarsfrom downloaded jdbc driver to <FLEXDEPLOY_HOME>/apache-tomcat-flexdeploy/libext. You may have done this already as part of Step 4. Make sure that if you copied the jars for libext of your backup to your new libext, you don’t end up with multiple versions of the Oracle JDBC jars. If migrating from an old version of FlexDeploy, you may want to clean your libext folder and start with a new Oracle Database driver download.
If using Oracle database and have not switched to using UCP connection pool, then see Implementing UCP connections with Tomcat and Oracle for more information. Look at type in context.xml, if it is
oracle.ucp.jdbc.PoolDataSource
, then you are already setup to use UCP connection pool.
...
Plugin files to copy are in /u01/software/downloadedupgradetempdir/application/plugins in the unzipped Tomcat Complete file.
Let's determine where to copy files in your installation now. Locate flexagon.fd.install.root folder for your FlexDeploy installation, which is FlexDeploy application directory. This is specified on the Java command line. For example, -Dflexagon.fd.install.root=/u01/flexdeploy/application.
You can look for this information in setenvoverride.bat or setenvoverride.sh file depending whether using Windows or Unix.
Create plugins folder if it does not exist under flexagon.fd.install.root folder. Copy files from download zip (#1 above) to this plugins folder.
...
Code Block | ||
---|---|---|
| ||
tar xf <tar file directory>/influxdb2-2.2.0-linux-amd64.tar.gz --strip-components 1 -C $FLEXDEPLOY_HOME/influxdb tar xf <tar file directory>/influxdb2-client-2.2.1-linux-amd64.tar.gz --strip-components 1 -C $FLEXDEPLOY_HOME/influxdb |
Copy config files. See example below on steps necessary.
Linux
Code Block | ||
---|---|---|
| ||
cd $FLEXDEPLOY_HOME
cd influxdb
mkdir config
cd config
cp /u01/software/upgradetempdir/influxdb/config/* . |
Windows
Code Block | ||
---|---|---|
| ||
cd %FLEXDEPLOY_HOME%
cd influxdb
mkdir config
cd config
xcopy c:/u01/software/upgradetempdir/influxdb/config /e |
Adjust the influx database configuration file. <FLEXDEPLOY_HOME>/influxdb/config/config.yaml
...
Change the following locations: You must put absolute path as no environment variables are allowed in this file.
bolt-path: from <FLEXDEPLOY_HOME>/influxdb/data/influxd.bolt to <FLEXDEPLOY_HOME>/application/vsm/data/influxd.bolt
engine-path: from <FLEXDEPLOY_HOME>/influxdb/data/engine to <FLEXDEPLOY_HOME>/application/vsm/data/engine
sqlite-path: <FLEXDEPLOY_HOME>/influxdb/data/influxd.sqlite to <FLEXDEPLOY_HOME>/application/vsm/data/influxd.sqlit
...