REQUIREMENTS ============ 1.If VOMRS is synchronized with VOMS, it is eaiser to install VOMRS on the the same node where VOMS is installed. (Intsall and configure VOMS first, VOMS can be installed via VDT: pacman -get http://vdt.cs.wisc.edu/vdt_1311_cache:VDT:VOMS or by installing it directly from gLite site http://glite.web.cern.ch/glite/packages). 2.If VOMRS is installed on a separate node, you have to install tomcat, mysql or oracle client, glite-java-security, glite-security-trustmanager packages For more information about trustmanager please, check: http://glite.web.cern.ch/glite To configure tomcat you have to replace server.xml in $CATALINA_HOME/conf with "server.xml.template" file in $VOMRS_LOCATION/etc/cfg file copy lcg4-trustmanager.xml.template to $CATALINA_HOME/conf/lcg4-trustmanager.xml modify server.xml and lcg4-trustmanager.xml accordingly copy the following jar files($VOMRS_LOCATION/server/lib) in $CATALINA_HOME/server/lib directory glite-security-trustmanager.jar glite-security-util-java.jar log4j-1.2.8.jar 3. Refer to the {install_dir}/doc/DEPENDENCIES file for more information after you have installed the rpm. UPGRADE VOMRS via rpm ========================= IMPORTANT!!!!!!!!!!! NOTE: If you have to upgrade from 1.3.1 see CONVERSION INSTALL VOMRS via rpm ===================== #rpm -i vomrs-1.3-2.noarch.rpm By default, the vomrs software will be installed in /opt in a directory name vomrs-{version} (/opt/vomrs-1.3). To install in a different directory, the rpm --prefix option can be used. For example: rpm -i --prefix {altdir} vomrs-1.3-2.noarch.rpm will install the vomrs software in {altdir}/vomrs-1.3. BASIC VOMRS CONFIGURATION =========================== The VOMRS installation contains a configuration script called: /sbin/vomrs_configure #export VOMRS_LOCATION= #cd $VOMRS_LOCATION/sbin #./vomrs_configure This is an interactive installation python script. Be sure you have python v2.2.x, at least, available. It performs the following actions: 1. Creates the MySql Oracle VOMRS database for your specific VO 2. Populates database with relevant information: - list of Certificate Authorities (from /etc/grid-security/certificates) - list of the default required personal info First Name Last Name Phone - creates an admin user for the database 3. Collects information about first VO administrator 4. Creates the necessary configuration files for this VOMRS VO instance. This script will prompt you for most information. At any time during this interview process, you can enter 'quit' and gracefully exit without doing any damage. The following are some prerequisites: 1. You need to be the 'root' user 2. You will need your Apache Tomcat CATALINA_HOME CATALINA_USER variables set or you will be prompted for it. 3. The set of valid certificate authorities for your VO are are expected to be in /etc/grid-security/certificates. In addition, you will establishing the necessary initial data regarding your VO and will need the following: 1. Your VO name. The naming rules are: - must contain from 2-12 characters including whitespace. (whitespace will be replaced with '_') - must contain only alphanumeric characters (a-z,0-9) - mixed case is allowed 3. The 'root' group name within your VO - this can be mixed case, but no whitespace is allowed. 4. The identity of the initial VO Administrator: - The home institution of the VOAdmin - DN/CA If you are to be the VOAdmin, this can be retrieved from your certificate file (you will need to supply the path) or populated manually at the prompt. - email address - first name, last name, email, phone 5. If you want synchronize VOMRS and VOMS database, you have to - find out VOMS location - select synchronization level To create the MySql VOMRS database, you will need: 1. the 'root' password for the MySql database 2. You will also be asked to set a password for the VOMRS database administrator of the MySql database that is being created. Be prepared. - the database name will be 'vomrs12_' in lower case - the admin user name will be '_adm in lower case To create the Oracle VOMRS database you will need: 1. First create database, db user and password 2. You will be asked for this information while running the script. Be prepared. Finally, you will be prompted for a place to put the VOMRS log files. Default will be /var/log/vomrs At the end, the script will create a file called.. vomrs__load.cfg in the ./sbin directory showing everything that has been created. IF YOU ARE USING VDT INSTALLATION ============================================================ You have to modify $VDT_LOCATION/apache/conf httpd.conf so all request to vomrs will be forwarded to tomcat example: JkMount /vo/* tomcat4 SSLCACertificatePath /etc/grid-security/certificates SSLVerifyClient require SSLVerifyDepth 10 SSLOptions +StdEnvVars +ExportCertData if "vo" is a you have selected in configuration script TO EFFECT THE INSTALLATION AND BEGIN USING THE VOMRS DATABASE ============================================================= 1. Restart tomcat 2. Test that vomrs.war file is installed properly: In your browser use: http://localhost:8443///vomrs 3. To start/stop the VOMRS server a. first copy $VOMRS_LOCATION/etc/profile.d/vomrs.sh.template to $VOMRS_LOCATION/etc/profile.d/vomrs.sh b. When starting from /etc/init.d on system system startup, the environment may not be the same as when starting the server as 'root' from the command line. For example, java must be available and may automatically be available on system startup as a part of the root's environment. The 'vomrs' script looks for the existence of a vomrs.sh script in the $VOMRS_LOCATION/etc/profile.d directory. A template has been created in that directory (vomrs.sh.template) and can be customized to established any part of the environment that is not available at system boot time. This script should be left as a /bin/bash script. c.service vomrs-1.3 start/stop/restart/status [] where is the name of your VO