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
Code Block | ||
---|---|---|
| ||
mkdir /u01/software/downloaded cd /u01/software/downloaded unzip <download location path>/Tomcat_Complete-6.x.x.x.zip |
...
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.
...
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
...
Code Block | ||
---|---|---|
| ||
cd %FLEXDEPLOY_HOME%\influxdb set INFLUX_DB_PASSWORD=<arbitrary value> rmdir /s <user directory>\.influxdbv2 influx setup --bucket flexbucket --token %INFLUX_DB_TOKEN% --org flexdeploy --username=flexuser --password=%INFLUX_DB_PASSWORD% --host=http://localhost:8086 --rem force rem need to adjust the influx database retention policy influx bucket list ID Name Retention Shard group duration Organization ID Schema Type 8eec65b90f79c55e _monitoring 168h0m0s 24h0m0s 9050d0dddc192df9implicit 4d6413cbaad04850 _tasks 72h0m0s 24h0m0s 9050d0dddc192df9implicit a3521682726cd901 flexbucket infinite 168h0m0s 9050d0dddc192df9implicit rem take the ID value for the flexbucket (Name) so we can update the retention policy to 104 weeks or 2 years influx bucket update --id a3521682726cd901 --retention 104w |
...
Step 11. Verify Ulimit and adjust if needed (Linux only)
Check your open file limits. Influx opens a large number of files to complete its work.
ulimit -Hn
will show the open file limit for the current user. Make sure you run it as the user who will be executing FlexDeploy and Influx.
If it is less that 65536, raise it or your influxdb log will likely grow very quickly and potentially run you out of disk space.
sudo vi /etc/security/limits.conf
where oracle is the user logged into the box to run FlexDeploy:
oracle soft nofile 16384
oracle hard nofile 65536
Step 12. Start tomcat
Info |
---|
If running FlexDeploy 6.0 or higher, do not use startup.sh as this will not start the influx database. User StartFlexDeploy.sh or StartFlexDeploy.bat. |
...