The aim of this document is to describe the neccessary steps to be taken in order to install P-GRADE Portal on your machine.
Before proceeding the installation, make sure that all the following requirements are met:
gpt-build --nosrc gcc32dbg gcc32dbgpthr on a fresh installation)First create the user as root that will run P-GRADE Portal:
$ adduser pgportal
Copy the installation package to the user HOME directory, and unpack it:
$ tar zxf pgportal-2.7.tgz
$ cd pgportal
There are a number of configuration items the administrator must set before continuing with portal installation. The file which needs to be updated is portal_config.txt. The variables that must be set are the followings:
HOSTNAME: hostname of the machine running P-GRADE Portal. You only need to set this if the HOSTNAME environment variable is unset and hostname returns unusable informationDEFAULT_PORT: non-secure listening port of P-GRADE PortalDEFAULT_SECURE_PORT: HTTPS listening port of P-GRADE PortalSHUTDOWN_PORT: shutdown port of Apache TomcatDEFAULT_VO: default VO of P-GRADE Portal. This VO name will appear on the welcome screenMYPROXY_HOSTNAME: hostname of the MyProxy server for MDS2 authenticationMYPROXY_PORT: MyProxy port for MDS2 authenticationUSER_NAME: user name on MyProxy server for MDS2 authenticationREG_URL: registration URL link on the welcome screenEMAIL: support team e-mail address on the welcome screenPORTAL_NAME: name of the PortalFTP_URL: URL of the example FTP repositoryFTP_PORT: port of the example FTP repositoryFTP_USER: login username of the example FTP repositoryFTP_PASS: password of the example FTP repositoryKEYSTORE_PASS: Tomcat keystore password for HTTPS key.JAR_PASS: Tomcat keystore password for jar-file keyDISABLE_EGEE: set this to yes in order to disable EGEE support.It is possible to configure GridSphere to use databases like MySQL, Mckoi SQL or PostgreSQL instead of HSQL. Using such databases is highly recommended, as they enhance P-GRADE Portal stability greatly. In
order to configure for example MySQL, you must modify the hibernate.properties file to use MySQL. Please refer to GridSphere documentation how to do this. Access to these databases assuses
additional jar files, the required files must be copied to the jars directory before P-GRADE Portal installation
Before proceeding to installation, it is possible to check if all the requirements are met using the Infrastructure check script. If you would like to skip this test, you can continue with the next step, but this isn't recommended. If you install the portal on top of an EGEE-type Grid, we highly recommend not to skip this test phase. Previous installation failures showed that this test is crucial making sure that the underlying EGEE infrastructure works correctly If you skip this step and the portal does not work correctly, please, return to this check phase. After a successful examination, the Infrastructure check script starts the installation procedure.
For a more detailed description of the Infrastructure check script consult the inst_check_manual14.txt file in the portal installation directory!
Run the Infrastructure check script:
$ ./inst_check.pl
If you have skipped the Installation check script execution in the previous section, start the installer by hand:
$ ./install.sh
Installation doesn't need user interaction in case everything works fine. In case of problems the install script notifies you about the error file produced.
You can start P-GRADE Portal using the following commands:
$ cd ~/pgportal
$ ./portalstart.sh
You can stop P-GRADE Portal using the following commands:
$ cd ~/pgportal
$ ./portalstop.sh