VITAL 3.1.1 Installation Procedure
1 About this document
- Purpose
- This procedure outlines how the RUBRIC Tech Team installed VITAL 3.1.1 on RedHat Linux Enterprise Version 4.
- Audience
- RUBRIC Tech Team and Partner System Administrators
- Requirements
- ssh or console access to server
- Installed basic RedHat EL4 OS on server
- “convert” installed (part of ImageMagick installed as part of RHEL4 (test by issuing command “which convert”))
- Server with ports open to enable web and Fedora access: 8080 and 6080
- Version 5 mysql tar file on server. Due to licensing issues mysql is unable to be shipped within the VITAL 3.1.1 application package. Version 5 mysql can be downloaded from mysql website or downloaded from RUBRIC.
- (https://rubric-central.usq.edu.au/svn/code/vital/vital_install/mysql-standard-5.0.27-linux-i686.tar.gz)
- Complete VTLS questionnaire to finalise installation requirements and readiness for this installation procedure.
- A valid license file provided to you by VTLS
2 Set up environment for VITAL installation
Change to the root user and create the dbadmin user in the dba group:
su -
[enter root password]
groupadd dba
useradd -g dba dbadmin
passwd dbadmin
[enter the password for dbadmin twice]
3 Create Perl directory for VITAL installation
As root, create the directory for the Perl used by VITAL in /usr/. Note that Perl used by VITAL has particular modules compiled within. Should you wish to use your own system Perl, you will need to compile these modules into it. You will need to contact VTLS for a list of these modules. If you are happy to use the Perl provided by VTLS, follow the next step.
mkdir /usr/vtls
4 Create and prepare install directory for VITAL installation
As root, create the directory for VITAL in /opt
mkdir /opt/vtls
As root, move the tar file to the opt/vtls directory:
mv vital-no-mysql-3.1.1-rhel4.tar /opt/vtls
As root, change the ownership of the install directories:
chown -R dbadmin:dba /usr/vtls
chown -R dbadmin:dba /opt/vtls
5 Install VITAL
5.1 Unpack the tar file
As the dbadmin user, run the following commands to unpack the Vital install package:
/opt/vtls
tar xvf vital-no-mysql-3.1.1-rhel4.tar
5.2 Add mysql component
As the root user, move the mysql tar file in position.This will ensure that the install script below detects mysql and provides mysql menu options as part of the installation.
mv /path_to/mysql-standard-5.0.27-linux-i686.tar.gz /opt/vtls/vital-full-3.1.1.20070831-rhel4
As root, change the ownership of the mysql tar file:
chown -R dbadmin:dba /opt/vtls/vital-full-3.1.1.20070831-rhel4/mysql-standard-5.0.27-linux-i686.tar.gz
5.3 Run the install script
As the dbadmin user, run the install script:
cd vital-full-3.1.1.20070831-rhel4
./install.sh
Answer questions regarding Perl location and version (Note – If you are using your own system Perl you will need to alter the location to which VITAL looks for Perl Answer yes unless you have installed alternative Perl).
Read Java license agreement and answer yes/no option
5.4 Main Menu
The options mentioned below are those that will definitely need to be edited, all others are optional dependent upon your own institutional requirements .
Items from the main menu can be selected by pressing the appropriate number followed by pressing enter key
5.4.1 Global Settings
From the Main Menu Select Edit Global Settings option
Set external hostname
Set internal hostname
Set Administrative Email address
5.4.2 Fedora Settings
Set Repository name
Set Administrative password
Leave port settings unless you have special port requirements
Set PID namespace
5.4.3 Database settings
Select database to use (mysql option will only appear here if step 3.2 was carried out)
5.4.4 MySQL
Set MySQL Username
Set MySQL Password
Set MySQL Root Password
5.4.5 Install and run VITAL
Show summary can be used to double check all settings, once satisfied with setttings select Install VITAL [5].
Once installed press enter to return to the main menu and then select Startup VITAL/Fedora [6]
Once started press enter to return to the main menu and then press select Save and Exit [7]
6 Installing VITAL licence
Place license file from VTLS in the /opt/vtls/vital/config/license directory. The license file must be named vital.license.
Restart VITAL
cd /opt/vtls/vital/bin
./stop
./start
7 Accessing VITAL
Check that your Repository is functioning correctly at the following location.
http://servername.com:8080/vital
8 VITAL Content Manager
8.1 Installing Content Manager Software
Download and run the VITAL Content Manager installation file that is provided with your VITAL3.1 installation package - vital-client-3.1.1.exe onto a users Windows PC.
8.2 Allow access to the VITAL Client.
There is a file within Fedora that limits access to the API-M within Fedora.
You have the option of removing the file, providing API-M access to all IP’s, or editing the file to only allow certain IP’s, or IP ranges. The file is called deny-apim-if-not-localhost.xml, and is located in /opt/vtls/vital/store/fedora-xacml-policies/repository-policies/default/.
Rubric recommends that the file be amended rather than completely removed.
9 AlternateID script
9.1 Download and Install
- Note:
- Before installing this utility, you must migrate your 2.1 system to 3.1 and rebuild the database and Resource Index.
To install the AlternateID Utility:
Make sure your Tomcat/Fedora instance is running.
Download alternateid.war from https://rubric-central.usq.edu.au/svn/code/vital/vital_install/AltId and place it in the /opt/vtls/vital/applications/fedora/server/jakarta-tomcat-5.0.28/webapps directory of your VITAL installation.
Stop and re-start VITAL at /opt/vtls/vital/bin
If installed correctly, it will be available from the following URL:
http://servername.com:8080/alternateid/
9.2 Run AlternateID script
Go to http://servername.com:8080/alternateid/
The application must gather information about your repository. Following this, it will prompt you for a login.
Enter the default login details and click submit
default username is vitalAdmin
default password is vedlativ$
Tick the appropriate synchronisation pairs of mimetype and datastream
Click Submit and confirm




