data:Ogsadai/2.2/server

From Dgiref
Jump to: navigation, search

See also troubleshooting for this page.


Please open a NGI-DE ticket if you experience any Installation or Configuration problem.

Contents

OGSA-DAI

Prepare

Operating system
Scientific Linux v.5.4 64 bit

Optimizing the configuration:


Use minimal operating system installation without firewall. To verify installed packages use the command

  • rpm -qa | grep package_name

Install the following additional packages:

  • yum -y install wget yum rpm make gcc gcc-c++ tar sed zlib openssl

After the installation is complete, turn off any unnecessary services (like gpm, sendmail, cups, haldaemon, messagebus, pcmcia, anacron, atd) with the following command:

  • chkconfig <SERVICE> off

Configure the following settings for the server:

Additional Software
  • the Globus_toolkit prerequisites:
    • without Torque client
    • java-1_6_0-sun (not fully compatible with java-1_6_0-ibm)
    • DBMS (MySQL 5, PostgreSQL or Oracle)
    • There is specially prepared Globus binary version for OGSA-DAI which was designed to run on 64 bit SL 4 platforms.
  • JDBC driver
    • MySQL versions 3.1.6 and 5.0.6
    • PostgreSQL version 8.1-407 (JDBC2)
    • Oracle version 1.4

WARNING: Oracle is not fully supported at the moment. If you use Oracle, you need to setup the user accounts and databases for VOs manually. The user accounts and databases have to match the settings as they are defined withing the 'SiteConfigure.properties' file.

Note-icon.png
  
To make all libraries from ant available do the following as root:
su -
cd /usr/share/ant/lib
ln -s /usr/share/java/ant.jar ant.jar
ln -s /usr/share/java/ant-launcher.jar ant-launcher.jar
Firewall configuration

The GT4 frontend runs GRAM + MDS + GridFTP + RFT services (how to open port in firewall).

Service Incoming ports (TCP) Change to default default
GRAM (GT2) 2119 No
GRAM (GT2) 20000-25000 Yes
WS-GRAM 8443 No
WS-GRAM 20000-25000 Yes
WS-MDS 8443 No
GridFTP 2811 No
GridFTP 20000-25000 Yes
RFT 8443 No

Install

To provide OGSA-DAI, you need to install the Globus Toolkit middleware. The Globus toolkit installation instructions are available here.

Note-icon.png
  
The uniqueness of this special Globus version is that the GRAM service has been removed. Therefore, in the Globus installation instructions you can ignore all PBS/Torque, Gatekeeper and GRAM related contents. All other steps must be performed without changes.

Configure

The following database setup assumes that the database is located on the same machine as the Globus container by default. If this is not the case, the admin user mentioned in the properties file below must be allowed to access the database server from the OGSA-DAI host. Standard database admin users e.g. root, are only allowed to access the database from 'localhost'. For detailed explanation on changing user privileges for your database system please consult the database documentation.

To see how to update the user mappings please refer to the section 'Grid-mapfile update' and the cfengine setup.

To configure the OGSA-DAI service do the following:

  1. Download SecurityExtensions.jar
  2. Download SiteConfigure.properties to the OGSA-DAI Server.
    1. Adjust the settings inside the file depending on the conditions of your site.
    2. Pay attention to the comments within the file. The VO related settings should, where possible, remain unchanged.
  3. Download setupSite.sh
    1. When all settings are taken download setupSite.sh to your OGSA-DAI Server, too.
    2. Then change the umask
    3. start the setupSite.sh script with the following parameters:
      • Select one of the database types (MySQL, PGSQL or Oracle), using the '--type' command line switch. The value of this option depends on the database system installed at your site. Other data resource types are currently not supported by this tool. Please keep in mind the 'Oracle is not fully supported' by the tool, so the user setup is not carried out automatically!
      • The '--sp' command line switch must point to the 'SiteConfigure.properties' file adapted before.
  4. Finally edit the file $GLOBUS_LOCATION/etc/ogsadai_wsrf/server-config.wsdd
Note-icon.png
  
Tool setupSite.sh performs the following steps:
  • Creating one database user per VO (not for Oracle)
  • Creating one database per VO (not for Oracle)
  • Deployment and publication of one data resource per VO
  • MDS 4 registry activation for each data resource
  • Setting up the global Rolemap for access authorization depending on VO membership

It is assumed that all VOs use the same database system. For individual settings modifications to the available data resources are necessary. By default OGSA-DAI only uses Transport Level Security (TLS). For running on D-Grid OGSA-DAI needs to be configured with full security support (Message Level Security (MLS))


Initial test

  • Testing general connectivity

The following steps must be executed as user 'globus'. The expected result should look as follows:

Update

  • to uninstall OGSA-DAI, stop the Globus container and remove the files in:
    • $GLOBUS_LOCATION/etc/ogsadai_wsrf
    • $GLOBUS_LOCATION/share/schema/ogsadai
    • $GLOBUS_LOCATION/lib/ogsadai*
  • if you want to cleanup all OGSA-DAI related content remember to recursively remove the directories ~globus/ogsadai-wsrf-2.2/
  • to reinstall OGSA-DAI uninstall OGSA-DAI and execute all installation and configuration steps again
Personal tools