EGEE Home | Intranet Home | Search | EDMS Documents | People | Calendar | Agenda maker | Glossary

               


JRA1: Middleware Integration

euroflag.gif (3058 octets)

Tools Testing Integration Information
Services
Workload
Management
Data
Management
Security Management

JRA1 Home | JRA1 Integration Home | Mandate | People | Meetings | Presentations | Useful links | Execution Plan | Tasks list | Mailing List Web Archive | EDMS | Agenda Maker

 

CREATING A NEW SUBSYSTEM FOR ORG.GLITE

This page explains you the different steps to create a new subsystem for org.glite and to add it to the global org.glite module.

Subsystem creation scripts

In order to facilitate the creation of a subsystem, two scripts allow you to create the basic part of a subsystem and to add it to org.glite.

The scripts can be found in the CVS module org.egee.integration.administration. To use them, go to the root directory of your workspace and check out the module via

 cvs co org.egee.integration.administration

In the directory org.egee.integration.administration you will find then - besides others - the following two scripts:

The script "add_subsystem" assumes the org.glite module to be present in your workspace, so might need to check out the module org.glite from your workspace root directory via

cvs co org.glite

first.

1. Creating a subsystem

Run the scripts create_subsystem from the org.egee.integration.administration directory. Make sure that you specify the name of your subsystem without "org.glite" and that your name contains no "." as this opposes to the naming convention for subsystems.

2. Adapting the subsystem to your needs

Adapt your subsystem according to your specific needs. This might be additional targets, dependencies, task definitions, properties etc.

Adding dependencies

Now that you have added the component to your subsystem, you will have to put the dependencies of your component both for external as well as internal dependencies.

External dependencies

For the external dependencies, you will have to make sure that they are installed to your repository before compiling. To do this, go to the configuration specification file of your subsystem

$WORKSPACE/org.glite.your_subsystem/project/glite.your_subsystem.csf.xml

that takes care that all external dependencies are properly installed.

In this file, you will find a target for the external dependencies looking like

<target name="external" depends=""/>

If your components depends on external libraries, add them under "depends", e.g.

<target name="external" depends="globus"/>

The exact name of the external component targets can be found in the

$WORKSPACE/org.glite/project/targets-external-dependencies.xml

file as a corresponding target. For the version of the external dependency, you can look into

$WORKSPACE/org.glite/project/dependencies.properties

If your component depends on an external library, that is not yet present, please contact the Integration Team to see if it can be added to the global repository.

Dependencies on other subsystems

See below "Addding the subsystem to the global org.glite".

2. Adding the subsystem to the global org.glite

In order to add your subsystem to the global org.glite, run the script add_subsystem from the org.egee.integration.administration directory, taking the name of your newly created subsystem. This will update the corresponding files in the org.glite module.

Dependencies on other subsystems

If your subsystem depends on other subsystems, you will have to add this dependency to the global build file at

$WORKSPACE/org.glite/build.xml

In there you will find a target for your subsystem

<target name="your_subsystem" depends="">

If your components depends on other subsystems, add them under "depends", e.g.

<target name="your_subsystem" depends="subsystem2"/>

As the module org.glite is under the restricted control of the integration team, please ask the integration team to put the updated org.glite module to the CVS repository for you by specifying the new subsystem name and dependencies.

3. Adding a subsystem to CVS

If your happy with your new subsystem, you can import your subsystem as a new CVS module to the jra1 CVS via

cvs import subsystem_name jra1 initial

where subsystem_name is the name of your subsystem (including "org.glite" - e.g. org.glite.wms). Make sure that you run this command from your subsystem root directory e.g. "$WORKSPACE/org.glite.wms"!

4. Adding components

Now you fully added your subsystem and you can tailor it to your specific needs and start adding components to it. A description to add a component can be found here.

 

If you prefer, you can do the modifications also by hand - you can find a short description what you have to do here.

      Contact .   Last modified: 09/07/2004