Access Keys:
Skip to content (Access Key - 0)

Portal

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (36)

View Page History
----
h1. Portal 2.0 Installation Guide
----
{cagridroundpanel}
{pre:class=cagridheaderfont}Table of Contents{pre}
----


h2. Obtaining the caGrid Portal Software
----

You can download the caGrid Portal release or check out the code from CVS.

{code}

After checkout, the caGrid Portal source code directory (referred to henceforth as $SRC) will be located under ./cagrid-portal.

h2. Obtain Required Software
----

The following software must be installed:
* Java 1.5

{anchor:Create Databases}

h2. Create Databases
----

Two databases are needed for the caGrid Portal application. One for Liferay data, and one for caGrid Portal data. By convention, the names of these databases are 'lportal' and 'portal2'. If you are using these database names, then you need to execute the following SQL in your MySQL database:
{code}
create database lportal character set utf8;
h2. Create SSL Certificate and Keystore
----

Some pages in the portal need to be protected with HTTPS. You will need to create an SSL certificate that the embedded Tomcat instance (running in JBoss) will use. The installation script will take care of configuring the Tomcat HTTPS Connector, but you still must either create a certificate and PKCS12 keystore, or specify the path to an existing keystore and provide the keystore password.


Complete instructions on using keytool can be found here:
* [http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/keytool.html|http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/keytool.html]

Instructions on configure JBoss and Tomcat to use SSL are here:
* [http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html|http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html]
* [http://docs.jboss.org/jbossas/jboss4guide/r5/html/ch9.chapt.html#ch9.https.sect|http://docs.jboss.org/jbossas/jboss4guide/r5/html/ch9.chapt.html#ch9.https.sect]

By default, the installation script will assume that the keystore is located at $HOME/portal-liferay/portal-keystore and that the keystore password is 'portal'. This location and password can be configured in the properties file that the installation script uses (described later).

{anchor:Obtain Google Maps API Key}

h2. Obtain Google Maps API Key
----

You can get a Google Maps API key here: [http://www.google.com/apis/maps/signup.html|http://www.google.com/apis/maps/signup.html]If your host's name is my.host.com, and the HTTP server is listening to port 8080 then the URL you should use is: [http://my.host.com:8080|http://my.host.com:8080/]Save this key for future use.

{anchor:Obtain Yahoo ApplicationID}

h2. Obtain Yahoo ApplicationID
----

Get an ApplicationID from Yahoo: [http://developer.yahoo.com/wsregapp/index.php|http://developer.yahoo.com/wsregapp/index.php]Save this for future use.

h2. Configure caGrid Trust Fabric
----
The caGrid Portal uses GAARDS to authenticate users, so the caGrid trust fabric must be configured on the machine that will host the portal. The portal itself will use the GTS client to maintain the trust fabric, but the trust fabric must be bootstrapped.

The caGrid Portal uses GAARDS to authenticate users, so the caGrid trust fabric must be configured on the machine that will host the portal. The portal itself will use the GTS client to maintain the trust fabric, but the trust fabric must be bootstrapped.

By default, the portal will use the nci_prod as the target grid. If you are using this grid, you don't need to do anything.

Then the trust synchronization configuration has already been provided. You will just need to create a corresponding build.properties file. Look at build-nci_qa.properties as an example. When you run the installation script, you'll have to specify the name of your target environment. More details about this are provided in the Configure caGrid Portal Installation section below.

If you are using another target grid, the you need to do three things:
# Create a sync-description.xml file to configure the GTS client that the portal uses.
# Bootstrap the trust fabric by placing root certificates under the $HOME/.globus/certificates directory
h2. Configure caGrid Portal Installation
----
The caGrid Portal installation script is at $SRC/build.xml. This is an Ant build file. It is configured by the properties that are defined in the build.properties file in the same directory. To customize the installation, you can directly edit build.properties or you can override those properties by adding them to the build-local.properties file.

The caGrid Portal installation script is at $SRC/build.xml. This is an Ant build file. It is configured by the properties that are defined in the build.properties file in the same directory. To customize the installation, you can directly edit build.properties or you can override those properties by adding them to the build-local.properties file.

Furthermore, if you want to maintain installation configurations for multiple deployment tiers, you can create multiple properties files whose names have the form: build-<tier>.properties, where '<tier>' is replaced with the name of the tier. For example, if I have created a configuration for the 'testing' tier, then I would create a file named build-testing.properties, and then run Ant from the $SRC directory like this:
{code}
ant -target.env=testing install
{code}

See the $SRC/build.properties file itself for descriptions of all the properties. If you are using the nci_prod target grid and default installation location, then you will usually only need to edit the following properties:
* liferay.admin.password
* liferay.db.host
h1. Installation
----

From the $SRC directory, run the following command:
{code}
h1. Post-Installation
----

h2. Setup Environment
----

On MS Windows, use the System application in the Control Panel to set the JBOSS_HOME environment variable to point to the directory in which JBoss was installed. By default, this will be:
{code}
h2. Start the Application Server
----

On MS Windows, go to %JBOSS_HOME%\bin and double-click run.bat

h2. Import the Site Structure
----
The basic site structure can be configured by using the Liferay administrative portlets to import Liferay Archive (lar) files. I've created these lar files in the $SRC/portals/liferay/lars/ directory.

The basic site structure can be configured by using the Liferay administrative portlets to import Liferay Archive (lar) files. I've created these lar files in the $SRC/portals/liferay/lars/ directory.

Follow these directions to import the lar file:


{anchor:Secure Encryption Key}

h2. Secure Encryption Key

A file named 'cagridportal.properties' will be generated and placed in two locations on the filesystem:
* $JBOSS_HOME/server/default/deploy/liferay-portal.war/WEB-INF/classes/cagridportal.properties
* $JBOSS_HOME/server/default/deploy/cagridportlets/WEB-INF/classes/cagridportal.properties

The value of the 'cagrid.portal.security.encryption.key' property in this file will be used to encrypt authentication tickets as well as portal users' temporary grid credentials (in the database). It is important that these files are protected so that users' grid credentials cannot be decrypted by a malicious user who has access to both the hosting system and database. Set file permissions appropriately for your system.

h1. Re-Installation
----

This section describes the steps needed to wipe out an existing installation and re-install. All existing data will be destroyed. See the Administrator's Guide for directions on backing up data and doing batch imports of data.
# Stop the JBoss application server
h1. Firewall/Connectivity Considerations
----

By default, the portal installation script will download JBoss and several Liferay artifacts. If you are behind a firewall, you will need to provide the proxy configuration for your JVM. Essentially, you just need to set the ANT_OPTS environment variable to include the standard Java proxy settings, like so:
{code}
Last edited by
Sarah Honacki (1419 days ago) , ...
Adaptavist Theme Builder Powered by Atlassian Confluence