Follow these steps to upgrade an existing instance of FCC Studio:
3. Upgrade Steps without OFSAA
4. Configure the studio-env.yml File for Upgrade
You can upgrade an existing instance of FCC Studio as follows:
· Upgrade FCC Studio from v8.0.7.1 onwards to v8.0.8.0.0 with OFSAA.
NOTE |
Here, ensure to provide the same BD database, Studio schema, Hive schema, wallet related information that you used during the installation of the existing instance FCC Studio. |
· Upgrade FCC Studio from v8.0.7.1 onwards to v8.0.8.0.0 without OFSAA.
NOTE |
Here, ensure to provide the same Studio schema and wallet related information that you used during the installation of the existing instance of FCC Studio. |
Before you begin the upgrade process, perform the following cleanup steps:
1. Navigate to the DATABASECHANGELOG table in the StuÂdio Schema.
2. Run the following SQL command in the Studio Schema:
select * from DatabaseChangeLog a where REGEXP_LIKE
(a.id,'FCC_DATASTUDIO_CONFIG')
The entries in the DATABASECHANGELOG table that match the criteria are displayed.
3. Delete all the entries generated as the result of the command.
For example:
FCC_DATASTUDIO_CONFIG_8.0.7.3.0
FCC_DATASTUDIO_CONFIG_8.0.7
To perform the ETL cleanup, follow these steps:
· Extract the contents of the installer archive file in the download directory using the unzip -a <FCC_Studio_Installer_Archive_File>.zip. The FCC Studio installer file is extracted in the <Studio_Installation_Path> directory.
· Configure the applicable parameters in the config.sh file. For more information, see Configure the config.sh File.
· Generate the keystore file. For more information, see Generate the Key Store File for Secure Batch Service.
· Generate an encrypted password. For more information, see Generate an Encrypted Password.
· Remove the existing jar files from the spark cluster.
· Create the folder in the GRAPH_FILES_PATH parameter in a node of the big data cluster.
· Create a folder called jars.
· Navigate to the <STUDIO>/ficdb/etlJars directory and copy all the jars present in this directory into the big data node inside the folder jars.
NOTE |
To use the ES-Hadoop connector, download the commons-httpclient-3.0.1.jar and elasticsearch-spark-20_2.11-7.6.2.jar files and place them in the jars folder. |
· Run FCCM_Studio_SchemaCreation.sh HIVE.
The following table provides the steps to upgrade FCC Studio with OFSAA.
Table 16: Upgrade Steps with OFSAA
Sl. No. |
Activity |
Pre-installation Steps |
|
1 |
Install all the prerequisite hardware and software |
2 |
Setup the environmental settings |
3 |
Download the files for Big Data |
4 |
Configure the Elastic Search Component |
5 |
Configure the Interpreter Settings |
6 |
Create the Studio Schema |
7 |
Assign Grants for the Database Schemas |
8 |
Setup Password Stores with Oracle Wallet |
9 |
Create the Credential Keystore |
10 |
Download the installer kit. |
Installation Steps |
|
1 |
Extract the installer kit. |
2 |
Place files in the Installation Directories |
3 |
Generate an Encrypted Password |
4 |
Generate the Public Key and Private Key |
5 |
Generate the Key Store File for Secure Batch Service |
6 |
Add the Batch Service (SSL) to PGX Trust Store |
7 |
Configure the Preferred Services |
8 |
Configure the studio-env.yml File |
9 |
Configure the Extract Transfer and Load (ETL) Process |
10 |
Verify the Resource Allocation for FCC Studio Services |
11 |
Deploy FCC Studio on the K8s Cluster |
Post-Installation Steps |
|
1 |
Verify the Installation |
2 |
Configure the Schema Creation |
3 |
Configure the ICIJ Data |
4 |
Access the FCC Studio Application |
5 |
Perform the OFSAA Configuration for Batch Execution |
6 |
Configure and Run Published Notebooks |
To start the FCC Studio application, follow these steps:
1. Navigate to the <Studio_Installation_Path>/bin/ directory.
2. Run the following command:
./fcc-studio.sh --registry <registry URL>:<registry port>
The FCC Studio application is restarted.
Check the logs of the FCC Studio services from the Kubernetes Dashboard. For more information, see Checking Logs of FCC Studio Services.
Once all the services are up and running, the FCC Studio application can be accessed using the following URL:
http://<HostName>:30078
The following table provides the steps to upgrade FCC Studio without OFSAA.
Table 17: Upgrade Steps without OFSAA
Sl. No. |
Activity |
Pre-installation Steps |
|
1 |
Install all the prerequisite hardware and software |
2 |
Setup the environmental settings |
3 |
Download the files for Big Data |
4 |
Configure the Elastic Search Component |
5 |
Configure the Interpreter Settings |
6 |
Create the Studio Schema |
7 |
Assign Grants for the Database Schemas |
8 |
Setup Password Stores with Oracle Wallet |
9 |
Create the Credential Keystore |
10 |
Download the installer kit. |
Installation Steps |
|
1 |
Extract the installer kit. |
2 |
Place files in the Installation Directories |
3 |
Generate an Encrypted Password |
4 |
Generate the Public Key and Private Key |
5 |
Generate the Key Store File for Secure Batch Service |
6 |
Add the Batch Service (SSL) to PGX Trust Store |
7 |
Configure the Preferred Services |
8 |
Configure the studio-env.yml File |
9 |
Configure the Extract Transfer and Load (ETL) Process |
10 |
Verify the Resource Allocation for FCC Studio Services |
11 |
Deploy FCC Studio on the K8s Cluster |
Post-Installation Steps |
|
1 |
Verify the Installation |
2 |
Access the FCC Studio Application |
Configure the studio-env.yml file to upgrade FCC Studio with OFSAA. For more information, see Configure_the_studio-env.yml_File.