The steps that follow provide detailed instructions about upgrading the Ark console. Before upgrading the console, you must ensure that no users are connected to the console, and that there are no cluster operations (backup, cloning, etc) in progress; you may wish to alert users to the pending upgrade with a wall message.Use the Show logged in users button on the Admin tab to confirm that no users are connected to the console, and check the server log (located in /var/log/edb-ark/ark.log) to confirm that all server activities have completed. Then:
1. Use ssh to connect to the node on which the Ark console resides, and assume root privileges:
2. With your choice of editor, modify the repository configuration file (located in /etc/yum.repos.d), enabling the edb-ark repository URL:[edb-ark]
name=EnterpriseDB EDB Ark
gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEYTo enable the repository, replace the user_name and password placeholders with your user name and password, and set enabled to 1.
3. Use the yum list "edb-ark*" command to review a list of available updates.yum update package_nameWhere package_name specifies the name of the package that you wish to update.
5. When the downloads complete, navigate into the /usr/share/tomcat/ directory:The installation script will prompt you to confirm that the console is not in use, and that you wish to continue with the installation.--2018-07-25 16:15:34-- https://jdbc.postgresql.org/download/postgresql-42.2.4.jar
Resolving jdbc.postgresql.org (jdbc.postgresql.org)... 184.108.40.206, 2001:4800:1501:1::228Connecting to jdbc.postgresql.org (jdbc.postgresql.org)|220.127.116.11|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 814992 (796K) [application/java-archive]
Saving to: ‘postgresql-42.2.4.jar’Script will upgrade the application! Is the EDB-ARK console in a steady state (no logged in users, no activity in the console)?When prompted, enter y to perform the console upgrade.If the Ark upgrade locates an existing ppcd.properties file, the configuration values are written into the Ark console database, and the old file is renamed to ppcd.properties_old_timestamp. The package manager identifies any additional pre-existing files, and creates the new (potential replacement) files with the .rpmnew extension.When the yum update completes, you should examine any files with the .rpmnew extension to see if any functionality (such as new parameter values) should be merged into your current files, and then delete the file with the .rpmnew extension. The ./postInstall.sh script will provide a list of any files that were in conflict.