Installation

The installation guide is split in two subsections. The first will handle the details about setting up a database. It will describe how to handle with a MySQL database. Oracle and other databases will work simularly when using a different ODBC driver for the connection. The second subsection will explain the changes to be done to let the Job Repository work on your service. This concerns changing LCMAPS configurations and adding new configuration files to your system. At the present time only a CE is supported as service through the use of the LCMAPS framework. Other more common interfaces will not be realised within the EGEE project.

The Database

The Job Repository needs to have a SQL database server. We build it around a MySQL database so this document will only state this database. Also the database creation scripts are written in a MySQL specific style. Take this into account if you wish to upgrade and/or alter the database server into something else like Postgres or Oracle.

The packages listed here are needed for the backend side of the Job Repository:

Tabel 1: RPMs to be installed on the database running machine.

RPM	min. version	description	URL
MySQL-server	4.0.13 (or higher)	the MySQL backend for the job repository	http://www.mysql.com
MySQL-client	4.0.13 (or higher)	the MySQL client, needed by the job repository utils	http://www.mysql.com
MyODBC	3.51.06 (or higher)	the MySQL ODBC 3.51 Driver	http://www.mysql.com

The Job Repository LCMAPS plugin rpm comes with four scripts. Only the 'jobrep-admin' script needs execution. The others are seperate SQL scripts to create the database. They are located in the (standard) location '/opt/glite/sbin/'. The scripts are:

• jobrep-admin, Script to install or remove a Job Repository database through the provided SQL scripts.
• jobrep-create-basic.sql, SQL script to install the default Job Repository DB schema. The schema supports more than one type of service to hold relational information from.
• jobrep-create-CE.sql, SQL script to install the Compute Element specific tables needed to store relevant relational information about the CE activities.
• jobrep-drop-total-database.sql, SQL script to remove a Job Repository database completely.

The Job Repository LCMAPS module

The Job Repository can not exist without the parts that fill the database.

The packages listed here are needed for the frontend side of the Job Repository:

Tabel 2: RPMs to be installed on the CE machine.

RPM	min. version	description	URL
lcmaps	1.2.x (or higher (should also work fine with very old LCMAPS version))	the LCMAPS library ( = pluginframework + utilities)	<LCMAPS link>
lcmaps-plugins-jobrep_plugins	1.3.x (or higher)	the LCMAPS plugin that stores the lcmaps info in the job repository	<LCMAPS jobrep plugin>
unixODBC	unixODBC-2.2.8	the unixODBC libraries	http://www.unixodbc.org
MyODBC	3.51.06 (or higher)	the MySQL ODBC 3.51 Driver	http://www.mysql.com
jobrepository	1.2.x (or higher)	This package contains the api of the job repository	<jobrep api>

Note: The MyODBC has to be installed both on the clientside and on the serverside. The clientside needs a database driver that comes with the package to make a connection to a MySQL database on the backend.

When all these rpms are installed then we can move to the (re)configuration of this system.