Table of Contents Previous Next


6 Console Management : 6.6 Upgrading the Console

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
baseurl=http://
user_name:password@yum.enterprisedb.com/edb-ark/redhat/rhel-\\$releasever-\\$basearch
enabled=0
gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY
To 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_name
Where package_name specifies the name of the package that you wish to update.
5.
When prompted, enter y to perform the console upgrade.
Please note: if you are using an OpenStack provider, you must manually modify the Ark console property table, setting the values of the following properties:
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.

6 Console Management : 6.6 Upgrading the Console

Table of Contents Previous Next