Date: Fri, 29 Mar 2024 06:17:52 +0000 (UTC) Message-ID: <722195941.1.1711693072804@8fdbf95ce13d> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_0_1159317296.1711693072787" ------=_Part_0_1159317296.1711693072787 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page provides instructions for upgrading a FlexDeploy insta= llation to the latest version.
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 dat=
abase 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 comman=
d:
expdp system directory=3DDATA_PUMP_DIR dumpfile=3Dfd_bkup.dmp schemas= =3DFD,FF,FD_ADMIN
If this database is exclusively used for just FlexDepl= oy application, you can rely on Database backup and recovery processes (RMA= N)
instead of export data procedure.
It is recommended that a backup of the artifact repository file system b= e taken in case a back-out is required. The location of the artifact reposi= tory can be identified by looking at value of -Dflexagon.fd.repository.root in setenv.sh or setenv.ba= t file. This file will be in <FlexDeploy Home>/a= pache-tomcat-flexdeploy/bin/. Standard file backup proced= ures can be followed. Optionally, the following command (unix only) can be = used to create a tar file backup of the entire directory.
tar =E2=80=93cvzf artifact.tar.gz <artifact repository location>=
From the downloaded zip file, extract the /database/ora= cle/upgrade folder. This folder includes a number of fol= ders containing migration.sql and patch release SQL files,= which upgrade the FlexDeploy schemas.
You will need to execute these scripts from the version of FlexDeploy yo= u currently have, up to the latest version. And they must be executed in th= at order.
If you are upgrading from 4.6.0.0 or higher then you can just look at Bu= ild Version in About window and use that information to derive SQL files to= be executed. Previously, it was necessary to compare Build Time as well.= p>
Follow this guideline when deriving SQL Patches to be applied.
Current version is 4.6.0.0 or higher
Current version is before 4.6.0.0
See some examples below to help you underst= and database upgrade process.
Keep in mind that upgrading 4.6 to 5.0 requires running various migratio= n scripts to jump through various intermediate versions.
v4.6.0.0-to-4.6.1.0/migration.sql v4.6.1.0-to-4.6.2.0/migration.sql v4.6.2.0-to-4.6.3.0/migration.sql v4.6.3.0-to-5.0.0.0/migration.sql
v4.0-to-v4.0.1/migration.sql v4.0.1-to-v4.0.2/migration.sql v4.0.2-to-v4.0.3/migration.sql v4.0.3-to-v4.5.0/migration.sql v4.5.0-to-v4.6.0.0/migration.sql v4.6.0.0-to-4.6.1.0/migration.sql=20 v4.6.1.0-to-4.6.2.0/migration.sql=20 v4.6.2.0-to-4.6.3.0/migration.sql=20 v4.6.3.0-to-5.0.0.0/migration.sql
The 4.0.2-to-4.0.3/migration.sql file includes all of the 403Pa= tchRelease*.sql files in it. Patch Release SQL files are only necessary if = you are on a 4.0.3 or 4.5.x Release.
If you are upgrading from a 4.0.3 Patch Release, follow the date based S= QL files in sequence by Date. If you have already a applied specific Patch = Release patch then skip it. You can make determination of which Patch Relea= se files to run by looking at Build Time on the About window of yo= ur FlexDeploy installation that you saved from a previous step. After compl= eting the last 403PatchRelease, run the migration4.0.3_to_4.5.0.sql file an= d v4.5.0-to-v4.6.0.0/migration.sql. Contact Flexagon support for detai= ls if you are not sure. See example below.
v4.0.2-to-v4.0.3/403PatchRelease_04-24-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_05-01-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_05-5-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_05-11-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_05-22-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_06-14-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_07-19-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_07-24-2017.sql v4.0.3-to-v4.5.0/migration.sql v4.5.0-to-v4.6.0.0/migration.sql v4.6.0.0-to-4.6.1.0/migration.sql=20 v4.6.1.0-to-4.6.2.0/migration.sql=20 v4.6.2.0-to-4.6.3.0/migration.sql=20 v4.6.3.0-to-5.0.0.0/migration.sql
v4.0.2-to-v4.0.3/403PatchRelease_05-22-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_06-14-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_07-19-2017.sql v4.0.2-to-v4.0.3/403PatchRelease_07-24-2017.sql v4.0.3-to-v4.5.0/migration.sql v4.5.0-to-v4.6.0.0/migration.sql v4.6.0.0-to-4.6.1.0/migration.sql=20 v4.6.1.0-to-4.6.2.0/migration.sql=20 v4.6.2.0-to-4.6.3.0/migration.sql=20 v4.6.3.0-to-5.0.0.0/migration.sql
v4.0.3-to-v4.5.0/450PatchRelease_12-09-2017.sql v4.0.3-to-v4.5.0/450PatchRelease_01-12-2018.sql v4.0.3-to-v4.5.0/450PatchRelease_01-30-2018.sql v4.5.0-to-v4.6.0.0/migration.sql v4.6.0.0-to-4.6.1.0/migration.sql=20 v4.6.1.0-to-4.6.2.0/migration.sql=20 v4.6.2.0-to-4.6.3.0/migration.sql=20 v4.6.3.0-to-5.0.0.0/migration.sql
These scripts should be executed as system, sys= em>, or another user which has privileges to create objects in other schema= s, performs grants, etc. You can load and execute these scripts using= other tools such as Toad or SQL Developer, but the instructions here are f= or using the sqlplus client.
sqlplus
Oracle sqlus is part of the Oracle Client, and may be executed on any ho= st which has it installed. If the Oracle Client is not installed on the sam= e host as where you are installing FlexDeploy, you can copy the scripts to = another host which has it installed.
Make sure to spool output to a file, so it can be analyzed later= if necessary.
To launch sqlplus:
export = ORACLE_HOME=3D<your Oracle Home directory> export ORACLE_SID=3D<the SID of your database> spool migration4.5.0.out #(change for each script execution so logs are pre= served) $ORACLE_HOME/bin/sqlplus #(login as sys or system when prompted) SQL> <<execute scripts as shown above>>
If running on another host other than the database server, you must upda= te your tnsnames file and and launch sqlplus as follows:
export = ORACLE_HOME=3D<your Oracle Home directory> export ORACLE_SID=3D<the SID of your database> spool migration4.5.0.out #(change for each script execution so logs are pre= served) $ORACLE_HOME/bin/sqlplus system@<tnsname> SQL> <<execute scripts as shown above>>
For example,
Copy plugins from the zip file that you downloaded. They are found in th= e plugins folder of the zip file. Plugins placed= in the folder shown below automatically upload and activate on the Server.=
This is very useful during initial install as well as when upgrading Fle= xDeploy, as there may be many new plugins or versions available as part of = new FlexDeploy release, but you can use the procedure any time.
There is no need to activate plugins manually. FlexDeploy will automatic= ally upload and activate new versions of plugins once they are copied to pl= ugins folder. You will notice that plugins that you copied in Step 8 will e= ventually be uploaded automatically and folder will not have any jar files = left. You can also look at Administration - Plugins in UI and see newer ver= sions of plugins.