UNICORE Files

UVOS is a complex Virtual Organisations solution. One of its main
design principles was overall simplicity. Therefore UVOS is very
easy to setup and to manage. However for beginners it may be hard 
to get started as there are multiple modules providing a vast 
functionality. This document may be used as a practical guide
of the UVOS system.


UVOS web page is located at:
		http://uvos.chemomentum.org
You can find a lot of information there, including download links.

To get support please write to the UNICORE support mailing list:
		unicore-support@lists.sourceforge.net

UVOS was created in the EU-founded Chemomentum project. See:
		http://chemomentum.org 
to get more information about this project.
 
UVOS is an Open Source software and is distributed on a flexible 
BSD license. Sources are currently hosted at Chemomentum project
SVN repository but it is anticipated that after the Chemomentum 
project end the whole UVOS code will be moved to the UNICORE
SourceForge repository. UVOS releases are already available from 
the UNICORE SourceForge project:
		http://sourceforge.net/projects/unicore   


For general overview of the UVOS features please read the document 
"UNICORE Virtual Organisations Service Overview". It is available 
at the UVOS web page and in UVOS server distribution. It is good 
to start your UVOS experience from going quickly through this document, 
however you do not have to read it carefully.

UVOS main components are:

 * UVOS server (distribution package name is called 'uvos-...')
		The UVOS server provides the functionality and is the core
		of the whole system. UVOS server can be extended with 
		additional modules (see below). The distribution package
		contains installation and configuration manual. Content 
		of the UVOS server can be managed only by one of the UVOS 
		management clients. All of them can be used remotely.
		UVOS is used as a service by other clients: e.g. grid
		users or grid servers. 

 * UVOS command line client - UVOS CLC (package is called 
   'uvos-client-...')
   		The command line client can be used to administer UVOS
   		from the console. It can be used in interactive or batch 
   		mode. Usage is very simple. The distribution contains 
   		the documentation in simple text format.

 * UVOS VO Manager (package is called VOManager-...)
 		The VOManager is a powerful GUI application based on
 		Eclipse Rich Client platform. It is much easier to use
 		then a command line client. Please note that you need 
 		a package matching your system. Installation is trivial
 		- it is enough to unpack the package and run 'VOManager'
 		binary.
 
Using the server and one of the management clients you can start 
to play with the UVOS. Install the server and unpack one of the 
clients. To connect to the fresh installation of the UVOS server 
use the following credentials:
 * authentication type: login(email) & password
 * login: voadmin@localhost
 * empty password
In UVOS Rich Manager there is a wizard which creates login settings for 
a fresh UVOS server installation. Then you can try to add contents 
using a client. Also for the first time it might be good to use an example
content - it can be generated by a script available in the UVOS server.
See its documentation for details.

Except management clients and the base server UVOS system contains
also additional modules:

 * Web VO applications module (package is called 'uvos-webapp-...')
		It is a UVOS server extension providing a web interface for 
		users who want to apply for a VO account. It is trivial to be 
		installed - see the instructions contained in the package.
		
 * Web authentication module (package is called 'uvos-webauth-...')
		It is a UVOS server extension providing implementation of 
		HTTP POST binding of SAML Authentication protocol. More simply 
		it is useful when portals or other WWW sites should authenticate
		their users using UVOS server. Such a site redirects client's 
		web browser to the web page provided by uvos-webauth module 
		(served by UVOS server itself), user logins there and appropriate
		response is returned to the originating site (where client's 
		web browser is redirected back). Installation of this module is
		also trivial but it is more difficult to setup such a behavior 
		at the portal side. Do not hesitate to contact UVOS support 
		for further information.
    
The last part of UVOS ecosystem are actual VO consumers: grid nodes
which authorize users and users themselves. 

 * UNICORE supports UVOS authorization out of the box from the
 version 6.1 on. See relevant documentation available at: 
 	http://unicore.eu   
 	
 * UNICORE users can check their attributes at UVOS server and also push
 them to a UNICORE service using a special plugin for the UNICORE Rich 
 Client. This plugin is available from the version 1.3.1 of UVOS system
 
 * New from the version 1.3.1: Globus Toolkit 4.X users can be authorized 
 using UVOS with the additional package which has to be added to the Globus
 installation. It is called 'uvos-gtk'. See its documentation for details. 
 
 * Developers of XFire based web services can use special library called
 xfire-voutils to simply add UVOS authorization in the same style as 
 UNICORE does.