ࡱ> Y{f7 bjbjUU 7|7|Au3l""""&&&4.1<<<h =@.1DV|nWnWnWZLjo`=??????$  "c&hq Z"BZ@hqhqct""nWnWxttthq~"nW2%nW=thq=t t&5"z$%@mnWD H/.1 <rQ  0_ #jt#tF&\,"""" DataGrid WP1 - WMS Software Administrator and User Guide  Document identifier:DataGrid-01-TEN-0118-0_7Date:  SAVEDATE \@ "dd/MM/yyyy" \* MERGEFORMAT 19/07/2002Work package:WP1Partner:Datamat SpADocument statusDeliverable identifier: Abstract: This note provides the administrator and user guide for the WP1 WMS software. Delivery SlipNamePartnerDateSignatureFromFabrizio PaciniDatamat SpA19/07/2002 Verified byStefano BecoDatamat SpA19/07/2002 Approved by  Document LogIssueDateCommentAuthor0_021/12/2001First draftFabrizio Pacini0_114/01/2002DraftFabrizio Pacini0_224/01/2002DraftFabrizio Pacini0_305/02/2002DraftFabrizio Pacini0_415/02/2002DraftFabrizio Pacini0_508/04/2002DraftFabrizio Pacini0_613/05/2002Fabrizio Pacini0_719/07/2002Fabrizio Pacini Document Change RecordIssueItemReason for Change0_1General updateTake into account changes in the rpm generation procedure. Add missing info about daemons (RB/JSS/CondorG) starting accounts Some general corrections0_2General UpdateAdd Cancelling and Cancel Reason information. Add OUTPUTREADY job state. Add new profile rpms. Remove /etc/workload* shell scripts. Add summary map table (user / daemon). Add CEId format check. Add new job cancel notification.0_3General UpdateModified RB/JSS start-up procedure Add gridmap-file users/groups issues Add proxy certificate usage by daemons Job attribute CEId changed to SubmitTo Add DGLOG_TIMEOUT setting Add workload-profile and userinterface-profile rpms0_4General UpdateAdd configure option enable-wl for system configuration files Add installation checking option with-globus for Globus to the Workload configure Add new Information Index configure options Remove edg-profile and edg-user-env rpms from II and UI dependencies Add security configuration rpms for all the Certificate Authorities to UI dependencies Add new parameters to RB configuration file Add new Job Exit Code field to the returned job status info Remove dependence from SWIG in the userinterface binary rpm0_5General UpdateModify command options syntax (getopt-like style) Add MyProxy server and client package installation/utilisation Modify job cancel notification Add Userguide rpm0_6General UpdateModify configure options for the various components UI commands modified to use python2 executable Clarify myproxy usage Explain how RB/LB addresses in the UI config file are used by the commands Add logfile option to the UI commands0_7General UpdateModify configure options for the various components Clarify UI commands notify option usage Add make test target for UI FilesSoftware ProductsUser filesWord 97 FILENAME \* MERGEFORMAT Datagrid_01_TEN_0118_0_7_Document Acrobat Exchange 4.0DataGrid-01-TEN-0118-0_7-Document.pdf Content  TOC \o "1-4" \h \z  HYPERLINK \l "_Toc14869523" 1. Introduction  PAGEREF _Toc14869523 \h 7  HYPERLINK \l "_Toc14869524" 1.1. Objectives of this document  PAGEREF _Toc14869524 \h 7  HYPERLINK \l "_Toc14869525" 1.2. Application area  PAGEREF _Toc14869525 \h 7  HYPERLINK \l "_Toc14869526" 1.3. Applicable documents and reference documents  PAGEREF _Toc14869526 \h 7  HYPERLINK \l "_Toc14869527" 1.4. Document evolution procedure  PAGEREF _Toc14869527 \h 8  HYPERLINK \l "_Toc14869528" 1.5. Terminology  PAGEREF _Toc14869528 \h 8  HYPERLINK \l "_Toc14869529" 2. Executive summary  PAGEREF _Toc14869529 \h 10  HYPERLINK \l "_Toc14869530" 3. Build Procedure  PAGEREF _Toc14869530 \h 11  HYPERLINK \l "_Toc14869531" 3.1. Required Software  PAGEREF _Toc14869531 \h 11  HYPERLINK \l "_Toc14869532" 3.2. Build Instructions  PAGEREF _Toc14869532 \h 12  HYPERLINK \l "_Toc14869533" 3.2.1. Environment Variables  PAGEREF _Toc14869533 \h 12  HYPERLINK \l "_Toc14869534" 3.2.2. Compiling the code  PAGEREF _Toc14869534 \h 14  HYPERLINK \l "_Toc14869535" 3.3. RPM Installation  PAGEREF _Toc14869535 \h 24  HYPERLINK \l "_Toc14869536" 4. Installation and Configuration  PAGEREF _Toc14869536 \h 26  HYPERLINK \l "_Toc14869537" 4.1. Logging and Bookkeeping services  PAGEREF _Toc14869537 \h 26  HYPERLINK \l "_Toc14869538" 4.1.1. Required software  PAGEREF _Toc14869538 \h 26  HYPERLINK \l "_Toc14869539" 4.1.1.1. LB local-logger  PAGEREF _Toc14869539 \h 26  HYPERLINK \l "_Toc14869540" 4.1.1.2. LB Server  PAGEREF _Toc14869540 \h 26  HYPERLINK \l "_Toc14869541" 4.1.2. RPM installation  PAGEREF _Toc14869541 \h 27  HYPERLINK \l "_Toc14869542" 4.1.3. The installation tree structure  PAGEREF _Toc14869542 \h 28  HYPERLINK \l "_Toc14869543" 4.1.3.1. LB local-logger  PAGEREF _Toc14869543 \h 28  HYPERLINK \l "_Toc14869544" 4.1.3.2. LB Server  PAGEREF _Toc14869544 \h 29  HYPERLINK \l "_Toc14869545" 4.1.4. Configuration  PAGEREF _Toc14869545 \h 29  HYPERLINK \l "_Toc14869546" 4.1.5. Environment Variables  PAGEREF _Toc14869546 \h 29  HYPERLINK \l "_Toc14869547" 4.2. RB and JSS  PAGEREF _Toc14869547 \h 31  HYPERLINK \l "_Toc14869548" 4.2.1. Required software  PAGEREF _Toc14869548 \h 31  HYPERLINK \l "_Toc14869549" 4.2.1.1. PostgreSQL installation and configuration  PAGEREF _Toc14869549 \h 31  HYPERLINK \l "_Toc14869550" 4.2.1.2. Condor-G installation and configuration  PAGEREF _Toc14869550 \h 32  HYPERLINK \l "_Toc14869551" 4.2.1.3. ClassAd installation and configuration  PAGEREF _Toc14869551 \h 33  HYPERLINK \l "_Toc14869552" 4.2.1.4. ReplicaCatalog installation and configuration  PAGEREF _Toc14869552 \h 34  HYPERLINK \l "_Toc14869553" 4.2.2. RPM installation  PAGEREF _Toc14869553 \h 34  HYPERLINK \l "_Toc14869554" 4.2.3. The Installation Tree structure  PAGEREF _Toc14869554 \h 34  HYPERLINK \l "_Toc14869555" 4.2.4. Configuration  PAGEREF _Toc14869555 \h 39  HYPERLINK \l "_Toc14869556" 4.2.4.1. RB configuration  PAGEREF _Toc14869556 \h 39  HYPERLINK \l "_Toc14869557" 4.2.4.2. JSS configuration  PAGEREF _Toc14869557 \h 42  HYPERLINK \l "_Toc14869558" 4.2.5. Environment variables  PAGEREF _Toc14869558 \h 43  HYPERLINK \l "_Toc14869559" 4.2.5.1. RB  PAGEREF _Toc14869559 \h 44  HYPERLINK \l "_Toc14869560" 4.2.5.2. JSS  PAGEREF _Toc14869560 \h 44  HYPERLINK \l "_Toc14869561" 4.3. Information Index  PAGEREF _Toc14869561 \h 46  HYPERLINK \l "_Toc14869562" 4.3.1. Required software  PAGEREF _Toc14869562 \h 46  HYPERLINK \l "_Toc14869563" 4.3.2. RPM installation  PAGEREF _Toc14869563 \h 46  HYPERLINK \l "_Toc14869564" 4.3.3. The Installation tree structure  PAGEREF _Toc14869564 \h 47  HYPERLINK \l "_Toc14869565" 4.3.4. Configuration  PAGEREF _Toc14869565 \h 47  HYPERLINK \l "_Toc14869566" 4.3.5. Environment Variables  PAGEREF _Toc14869566 \h 48  HYPERLINK \l "_Toc14869567" 4.4. User Interface  PAGEREF _Toc14869567 \h 49  HYPERLINK \l "_Toc14869568" 4.4.1. Required software  PAGEREF _Toc14869568 \h 49  HYPERLINK \l "_Toc14869569" 4.4.2. RPM installation  PAGEREF _Toc14869569 \h 50  HYPERLINK \l "_Toc14869570" 4.4.3. The tree structure  PAGEREF _Toc14869570 \h 51  HYPERLINK \l "_Toc14869571" 4.4.4. Configuration  PAGEREF _Toc14869571 \h 52  HYPERLINK \l "_Toc14869572" 4.4.5. Environment variables  PAGEREF _Toc14869572 \h 54  HYPERLINK \l "_Toc14869573" 4.5. DOCUMENTATION  PAGEREF _Toc14869573 \h 54  HYPERLINK \l "_Toc14869574" 5. Operating the System  PAGEREF _Toc14869574 \h 56  HYPERLINK \l "_Toc14869575" 5.1. LB local-logger  PAGEREF _Toc14869575 \h 56  HYPERLINK \l "_Toc14869576" 5.1.1. Starting and stopping daemons  PAGEREF _Toc14869576 \h 56  HYPERLINK \l "_Toc14869577" 5.1.2. Troubleshooting  PAGEREF _Toc14869577 \h 57  HYPERLINK \l "_Toc14869578" 5.2. LB Server  PAGEREF _Toc14869578 \h 58  HYPERLINK \l "_Toc14869579" 5.2.1. Starting and stopping daemons  PAGEREF _Toc14869579 \h 58  HYPERLINK \l "_Toc14869580" 5.2.2. Purging the LB database  PAGEREF _Toc14869580 \h 59  HYPERLINK \l "_Toc14869581" 5.2.3. Troubleshooting  PAGEREF _Toc14869581 \h 59  HYPERLINK \l "_Toc14869582" 5.3. RB and JSS  PAGEREF _Toc14869582 \h 60  HYPERLINK \l "_Toc14869583" 5.3.1. Startig PostgreSQL  PAGEREF _Toc14869583 \h 60  HYPERLINK \l "_Toc14869584" 5.3.2. Starting and stopping JSS and RB daemons  PAGEREF _Toc14869584 \h 60  HYPERLINK \l "_Toc14869585" 5.3.3. RB troubleshooting  PAGEREF _Toc14869585 \h 61  HYPERLINK \l "_Toc14869586" 5.3.4. JSS troubleshooting  PAGEREF _Toc14869586 \h 61  HYPERLINK \l "_Toc14869587" 5.4. Information Index  PAGEREF _Toc14869587 \h 61  HYPERLINK \l "_Toc14869588" 5.4.1. Starting and stopping daemons  PAGEREF _Toc14869588 \h 61  HYPERLINK \l "_Toc14869589" 6. User Guide  PAGEREF _Toc14869589 \h 63  HYPERLINK \l "_Toc14869590" 6.1. User interface  PAGEREF _Toc14869590 \h 63  HYPERLINK \l "_Toc14869591" 6.1.1. Security  PAGEREF _Toc14869591 \h 63  HYPERLINK \l "_Toc14869592" 6.1.1.1. MyProxy  PAGEREF _Toc14869592 \h 64  HYPERLINK \l "_Toc14869593" 6.1.2. Common behaviours  PAGEREF _Toc14869593 \h 66  HYPERLINK \l "_Toc14869594" 6.1.3. Commands description  PAGEREF _Toc14869594 \h 70  HYPERLINK \l "_Toc14869595" 7. Annexes  PAGEREF _Toc14869595 \h 105  HYPERLINK \l "_Toc14869596" 7.1. JDL Attributes  PAGEREF _Toc14869596 \h 105  HYPERLINK \l "_Toc14869597" 7.2. Job Status Diagram  PAGEREF _Toc14869597 \h 105  HYPERLINK \l "_Toc14869598" 7.3. Job Event Types  PAGEREF _Toc14869598 \h 107  HYPERLINK \l "_Toc14869599" 7.4. wildcard patterns  PAGEREF _Toc14869599 \h 109  HYPERLINK \l "_Toc14869600" 7.5. The Match Making Algorithm  PAGEREF _Toc14869600 \h 111  HYPERLINK \l "_Toc14869601" 7.5.1. Direct Job Submission  PAGEREF _Toc14869601 \h 111  HYPERLINK \l "_Toc14869602" 7.5.2. Job submission without data-accesss requirements  PAGEREF _Toc14869602 \h 111  HYPERLINK \l "_Toc14869603" 7.5.3. Job submission with data-access requirements  PAGEREF _Toc14869603 \h 113  HYPERLINK \l "_Toc14869604" 7.6. Process/User Mapping Table  PAGEREF _Toc14869604 \h 116 Introduction This document provides a guide to the building, installation and usage of the WP1 WMS software released within the DataGrid project. Objectives of this document Goal of this document is to describe the complete process by which the WP1 WMS software can be installed and configured on the DataGrid test-bed platforms. Guidelines for operating the whole system and accessing provided functionalities are also provided. Application area Administrators can use this document as a basis for installing, configuring and operating WP1 WMS software. Users can refer to the User Guide chapter for accessing provided services through the User Interface. Applicable documents and reference documents Applicable documents [A1] Job Description Language HowTo DataGrid-01-TEN-0102-02 17/12/2001 (http://www.infn.it/workload-grid/docs/DataGrid-01-TEN-0102-0_2.pdf)[A2] DATAGRID WP1 Job Submission User Interface for PM9 (revised presentation) 23/03/2001 (http://www.infn.it/workload-grid/docs/20010320-JS-UI-datamat.pdf)[A3]WP1 meeting - CESNET presentation in Milan 20-21/03/2001 (http://www.infn.it/workload-grid/docs/20010320-L_B-matyska.pdf)[A4]Logging and Bookkeeping Service 0705/2001 (http://www.infn.it/workload-grid/docs/20010508-lb_draft-ruda.pdf)[A5]Results of Meeting on Workload Manager Components Interaction 09/05/2001 (http://www.infn.it/workload-grid/docs/20010508-WM-Interactions-pacini.pdf)[A6]Resource Broker Architecture and APIs 13/06/2001 (http://www.infn.it/workload-grid/docs/20010613-RBArch-2.doc)[A7]JDL Attributes - DataGrid-01-NOT-0101-0_6 04/02/2002 (http://www.infn.it/workload-grid/docs/DataGrid-01-NOT-0101-0_6.pdf) Reference documents [R1] Document evolution procedure The content of this document will be subjected to modification according to the following events: Comments received from Datagrid project members, Changes/evolutions/additions to the WMS components. Terminology Definitions CondorCondor is a High Throughput Computing (HTC) environment that can manage very large collections of distributively owned workstationsGlobusThe Globus Toolkit is a set of software tools and libraries aimed at the building of computational grids and grid-based applications. Glossary class-adClassified advertisementCEComputing ElementDBData BaseFQDNFully Qualified Domain NameGDMPGrid Data Management Pilot ProjectGISGrid Information Service, aka MDSGSIGrid Security Infrastructurejob-adClass-ad describing a jobJDLJob Description LanguageJSSJob Submission ServiceLBLogging and Bookkeeping ServiceLRMSLocal Resource Management SystemMDSMetacomputing Directory Service, aka GISMPIMessage Passing InterfacePIDProcess IdentifierPMProject MonthRBResource BrokerRCReplica CatalogueSEStorage ElementSI00Spec Int 2000SMPSymmetric Multi ProcessorTBCTo Be ConfirmedTBDTo Be DefinedUIUser InterfaceUIDUser IdentifierWMSWorkload Management SystemWPWork PackageExecutive summary This document comprises the following main sections: Section 3: Build Procedure Outlines the software required to build the system and the actual process for building it and generating rpms for the WMS components; a step-by-step guide is included. Section 4: Installation and Configuration Describes changes that need to be made to the environment and the steps to be performed for installing the WMS software on the test-bed target platforms. The resulting installation tree structure is detailed for each system component. Section 5: Operating the System Provides actual procedures for starting/stopping WMS components processes and utilities. Section 6: User Guide Describes in a Unix man pages style all User Interface component commands allowing the user to access WMS provided services. Section 7: Annexes Deepens arguments introduced in the User Guide section that are considered useful for the user to better understand system behaviour. Build Procedure In the following section we give detailed instructions for the installation of the WP1 WMS software package. We provide a source code distribution as well as a binary distribution and explain installation procedures for both cases. Required Software The WP1 software runs and has been tested on platforms running Globus Toolkit 2.0 Beta Release 21 on top of Linux RedHat 6.2. Hereafter are listed the software packages, apart from WP1 software version 1.0, that are required to be installed locally on a given site in order to be able to build the WP1 WMS on it. They are: Globus Toolkit 2.0 Beta 21 or higher (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/globus/alpha-15" http://datagrid.in2p3.fr/distribution/globus/beta-21) Python 2.1.1 (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/config/external.html" http://datagrid.in2p3.fr/distribution/config/external.html) Swig 1.3.9 (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/config/external.html" http://datagrid.in2p3.fr/distribution/config/external.html) Expat 1.95.1 (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/config/external.html" http://datagrid.in2p3.fr/distribution/config/external.html) Expat-devel 1.95.1 (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/config/external.html" http://datagrid.in2p3.fr/distribution/config/external.html) MySQL Version 9.38 Distribution 3.22.32, for pc-linux-gnu (i686) (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/config/external_services.html" http://datagrid.in2p3.fr/distribution/config/external_services.html) Postgresql 7.1.3 ( HYPERLINK "http://datagrid.in2p3.fr/distribution/config/external_services.html" http://datagrid.in2p3.fr/distribution/config/external_services.html) Classads library (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/external/RPMS/classads-0.0-edg2.i386.rpm" http://datagrid.in2p3.fr/distribution/external/RPMS/classads-0.0-edg2.i386.rpm) CondorG 6.3.1 for INTEL-LINUX-GLIBC21 (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/external/RPMS/CondorG-6.3.1-edg5.i386.rpm" http://datagrid.in2p3.fr/distribution/external/RPMS/CondorG-6.3.1-edg5.i386.rpm) Perl IO Stty 0.02, Perl IO Tty 0.04 (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/config/external.html" http://datagrid.in2p3.fr/distribution/config/external.html ) MyProxy-0.4.4 (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/external/RPMS/myproxy-0.4.4-edg1.i386.rpm" http://datagrid.in2p3.fr/distribution/external/RPMS/myproxy-0.4.4-edg1.i386.rpm ) Perl 5 (download at  HYPERLINK "http://datagrid.in2p3.fr/distribution/config/external.html" http://datagrid.in2p3.fr/distribution/config/external.html) gcc version 2.95.2 GNU make version 3.78.1 or higher GNU autoconf version 2.13 GNU libtool 1.3.5 GNU automake 1.4 GNU m4 1.4 or higher RPM 3.0.5 sendmail 8.11.6 Build Instructions The following instructions deal with the building of the WMS software and hence apply to the source code distribution. Environment Variables Before starting the compilation, some environment variables related to the WMS components can be set or configured by means of the configure script. This is needed only if package defaults are not suitable. Involved variables are listed below: GLOBUS_LOCATION base directory of the Globus installation The default path is /opt/globus. MYSQL_INSTALL_PATH base directory of the MySQL installation The default path is /usr. EXPAT_INSTALL_PATH base directory of the Expat installation. The default path is /usr. GDMP_INSTALL_PATH base directory of the Gdmp installation The default path is /opt/edg. PGSQL_INSTALL_PATH base directory of the Pgsql installation. The default path is /usr. CLASSAD_INSTALL_PATH base directory of the Classad library installation. The default path is /opt/classads. CONDORG_INSTALL_PATH base directory of the Condor installation. The default path is /opt/CondorG. PYTHON_INSTALL_PATH base directory of the Python installation. The default path is /usr. SWIG_INSTALL_PATH base directory of the Swig installation . The default path is /usr/local. MYPROXY_INSTALL_PATH base directory of the MyProxy installation . The default path is /usr/local. In order to build the whole WP1 package, all the environment variables in the previous list must be set. Instead for building the User Interface module, the environment variables that need to be set are the following: GLOBUS_LOCATION CLASSAD_INSTALL_PATH PYTHON_INSTALL_PATH SWIG_INSTALL_PATH EXPAT_INSTALL_PATH If you plan to build the Job Submission and Resource Broker module, variable to set are: GLOBUS_LOCATION MYSQL_INSTALL_PATH EXPAT_INSTALL_PATH GDMP_INSTALL_PATH PGSQL_INSTALL_PATH CLASSAD_INSTALL_PATH CONDORG_INSTALL_PATH If you plan to build the Proxy module, variables to set are: GLOBUS_LOCATION MYPROXY_INSTALL_PATH Whilst the LB server and Local Logger modules, to be built need the following environment variables: GLOBUS_LOCATION MYSQL_INSTALL_PATH EXPAT_INSTALL_PATH Finally, the LB library module needs: GLOBUS_LOCATION EXPAT_INSTALL_PATH and the Information Index module only: GLOBUS_LOCATION Compiling the code After having unpacked the WP1 source distribution tar file, or having downloaded the code directly from the CVS repository, change your working directory to be the WP1 base directory, i.e. the Workload directory, and run the following command: ./recursive-autogen.sh At this point the configure command can be run. The configure script has to be invoked as follows: ./configure The list of options that are recognized by configure is reported hereafter: ---help --prefix= It is used to specify the Workload installation dir. The default installation dir is /opt/edg. --enable-all It is used to enable the build of the whole WP1 package. By default this option is turned on. --enable-userinterface It is used to enable the build of the User Interface module with Logging/Client, Broker/Client, Broker/Socket++ and ThirdParty/trio/src sub modules. By default this option is turned off. --enable-userinterface_profile It is used to enable the installation of the User Interface profile. By default this option is turned off. --enable-jss_rb It is used to enable the build of the Job Submission and Resource Broker modules with Logging/Client, Common, test, Proxy/Dgpr, and ThirdParty/trio/src submodules. By default this option is turned off. --enable-jss_profile It is used to enable the installation of the Job Submission and Resource Broker profile with JobSubmission/utils, and Broker/utils sub modules. By default this option is turned off. --enable-lbserver It is used to enable the build of the LB Server service with Logging/Client, Logging/etc, Logging/Server, Logging/InterLogger/Net, Logging/InterLogger/SSL, Logging/InterLogger/Error, Logging/InterLogger/Lbserver and ThirdParty/trio/src sub modules. By default this option is turned off. --enable-locallogger It is used to enable the build of the LB Local Logger service with Logging/Client, Logging/InterLogger/Net, Logging/InterLogger/SSL, Logging/InterLogger/Error, Logging/InterLogger/InterLogger, Logging/LocalLogger, man and ThirdParty/trio/src sub modules. By default this option is turned off. --enable-locallogger_profile It is used to enable the installation of the LB LocalLogger profile. By default this option is turned off. --enable-logging_dev It is used to enable the build of the LB Client Library with Logging/Client and ThirdParty/trio/src sub modules. By default this option is turned off. --enable-information It is used to enable the build of the Information Index module.By default this option is turned off. --enable-information_profile It is used to enable the installation of the Information Index profile with InformIndex/utils sub module. By default this option is turned off. --enable-wl It is used to enable the installation of system configuration files that are in the Workload/etc directory. By default this option is turned off. --enable-proxy It is used to enable the build of the Proxy module. By default this option is turned off. --with-globus-install= It allows specifying the Globus installation directory without setting the environment variable GLOBUS_LOCATION. --with-pgsql-install= It allows specifying the Pgsql installation directory without setting the environment variable PGSQL_INSTALL_PATH. --with-gdmp-install= It allows specifying the GDMP installation directory without setting the environment variable GDMP_INSTALL_PATH. --with-expat-install= It allows specifying the Expat installation directory without setting the environment variable EXPAT_INSTALL_PATH. --with-mysql-install= It allows to specify the MySQL installation directory without setting the environment variable MYSQL_INSTALL_PATH. --with-myproxy-install= It allows to specify the MyProxy installation directory without setting the environment variable MYPROXY_INSTALL_PATH During the configure step, 12 spec files (i.e. wl-userinterface.spec, wl-locallogger.spec, wl lbserver.spec, wl-logging_dev.spec, wl-jss_rb.spec, wl-information.spec, wl-userinterface-profile.spec, wl-jss_rb-profile.spec, wl-information-profile.spec, wl-lbserver-profile.spec and wl-locallogger-profile.spec, wl-workload-profile.spec) are created in the following source sub-directories to produce a flavour specific version: Workload/UserInterface Workload/Proxy Workload/Logging Workload/JobSubmission Workload/InformIndex Workload Once the configure script has terminated its execution, check that the make from the GNU distribution is in your path and then always in the Workload source code directory run: make then: make apidoc and then: make check to build the test code. If the two previous steps complete successfully, the installation of the software can be performed. In order to install the package in the installation directory specified either by the --prefix option of the configure script or by the default value (i.e. /opt/edg), you can now issue the command: make install It is possible to run "make clean" to remove object files, executable files, library files and all the other files that are created during make and make check. The command: make -i dist can be used to produce in the workload-X.Y.Z directory, located in the Workload's base directory, a binary gzipped tar ball of the Workload distribution. This tar ball can be both transferred on other platforms and used as source for the RPM creation. For creating the RPMs for Workload 1.0 (according to the configure options you have used) make sure that your PATH is set in such a way that the GNU autotools, make and the gcc compiler can be used and edit the file $HOME/.rpmmacros (if this file does not exist in your home directory, then you have to create it) to set the following entry: %_topdir /rpm/redhat Then you can issue the command: make rpm that generates the RPMs in $(HOME)/rpm/redhat/RPMS. For example if before building the package you have used the configure as follows: ./configure -enable-all then the make rpm command creates the directories: $(HOME)/rpm/redhat/SOURCES $(HOME)/rpm/redhat/SPECS $(HOME)/rpm/redhat/BUILD $(HOME)/rpm/redhat/RPMS $(HOME)/rpm/redhat/SRPMS and copies the previously created tar ball workload-X.Y.Z/Workload.tar.gz in $(HOME)/rpm/redhat/SOURCES. Moreover it copies the generated spec files: JobSubmission/wl-jss_rb.spec JobSubmission/wl-jss_rb-profile.spec UserInterface/wl-userinterface.spec UserInterface/wl-userinterface.spec InformIndex/wl-information.spec InformIndex/wl-informationpthr.spec InformIndex/wl-information-profile.spec Logging/wl-lbserver.spec Logging/wl-lbserver-profile.spec Logging/wl-locallogger.spec Logging/wl-locallogger-profile.spec Logging/wl-logging_dev.spec Proxy/wl-proxy.spec Workload/wl-workload-profile.spec Workload/wl-userguide.spec in $(HOME)/rpm/redhat/SPECS and finally executes the following commands: rpm -ba wl-userinterface.spec rpm ba wl-userinterface-profile.spec rpm -ba wl-locallogger.spec rpm -ba wl-locallogger-profile.spec rpm -ba wl-lbserver.spec rpm -ba wl-lbserver-profile.spec rpm -ba wl-logging_dev.spec rpm -ba wl-jss_rb.spec rpm -ba wl-jss_rb-profile.spec rpm -ba wl-information.spec rpm -ba wl-informationpthr.spec rpm -ba wl-information-profile.spec rpm -ba wl-proxy.spec rpm ba wl-workload-profile.spec rpm -ba wl-userguide.spec generating respectively the following rpms in the $(HOME)/rpm/redhat/RPMS directory: userinterface-X.Y.Z-K.i386.rpm userinterface-profile-X.Y.Z-K.i386.rpm locallogger- X.Y.Z-K.i386.rpm locallogger-profile- X.Y.Z-K.i386.rpm lbserver- X.Y.Z-K.i386.rpm lbserver-profile- X.Y.Z-K.i386.rpm logging_dev- X.Y.Z-K.i386.rpm jobsubmission- X.Y.Z-K.i386.rpm jobsubmission-profile- X.Y.Z-K.i386.rpm informationindex- X.Y.Z-K.i386.rpm informationindexpthr-X.Y.Z-K.i386.rpm informationindex-profile- X.Y.Z-K.i386.rpm proxy-X.Y.Z-K.i386.rpm workload-profile-X.Y.Z-K.i386.rpm userguide-X.Y.Z-K.i386.rpm where X.Y.Z-K indicates the rpms release. This document is issued together with the rpms in version 1.1.1-1. If you have instead built only the User Interface, i.e. used: ./configure --disable-all --enable-userinterface the make rpm command will copy only the file UserInterface/wl-userinterface.spec and the file UserInterface/wl-userinterface-profile.spec in $(HOME)/rpm/redhat/SPECS and will create only the User Interface rpms (userinterface-X.Y.Z-K.i386.rpm and userinterface-profile-X.Y.Z-K.i386.rpm). The User Interface has an additional make target to install the userinterface test suite allowing the performing of unit tests (i.e. without contacting any external component). You have to run the following commands in Worklaod/UserInterface: ./autogen.sh ./configure disable-all enable-tests make tests and you will find the commands ready to run together with the test files in Worklaod/UserInterface/test. An alternative procedure can be followed to build the II and Logging packages. To do this, move in the Workoad/InformIndex dir and run the following commands: ./autogen.sh ./configure [option] where the recognised options are: --prefix= It is used to specify the Information Index installation dir. The default installation dir is /opt/edg --with-globus-install= It allows to specify the Globus install directory without setting the environment variable GLOBUS_LOCATION. Then issue: make make install Afterwards move into the Workload/Logging directory and run the following commands: ./autogen.sh ./configure [option] where the recognised options are: --enable-all It is used to enable the build of the Logging and Bookkeeping package. By default this option is turned on. --enable-userinterface It is used to enable the build of the Client sub module. By default this option is turned off. --enable-graphical_userinterface It is used to enable the build of the Client sub module. By default this option is turned off. --enable-jss_rb It is used to enable the build of the Client sub module. By default this option is turned off. --enable-lbserver It is used to enable the build of the Logging And Bookkeeping Server service with Client, etc, Server, InterLogger/Net, InterLogger/SSL, InterLogger/Error, InterLogger/Lbserver and ThirdParty/trio/src sub modules. By default this option is turned off. --enable-lbserver_profile It is used to enable the installation of the LB Server profile with Logging/utils sub module. By default this option is turned off. --enable-locallogger It is used to enable the build of the Logging And Bookkeeping Local Logger service with Client, InterLogger/Net, InterLogger/SSL, InterLogger/Error, InterLogger/InterLogger, LocalLogger, Apidoc, and ThirdParty/trio/src sub modules. By default this option is turned off. --enable-logging_dev It is used to enable the build of the Logging And Bookkeeping Client Library with Client and ThirdParty/trio/src sub modules. By default this option is turned off. --prefix= It is used to specify the Logging installation dir. The default installation dir is /opt/edg --with-globus-install= It allows specifying the Globus install directory without setting the environment variable GLOBUS_LOCATION. --with-expat-install= It allows specifying the Expat install directory without setting the environment variable EXPAT_INSTALL_PATH --with-mysql-install= It allows specifying the MySQL install directory without setting the environment variable MYSQL_INSTALL_PATH. Then issue: make make apidoc make check make install Summarising, in relation to the WMS module you want to build, the configure script has to be run with the following options: all ./configure userinterface ./configure --disable-all --enable-userinterface information ./configure --disable-all --enable-information lbserver ./configure --disable-all --enable-lbserver locallogger ./configure --disable-all --enable-locallogger logging for developers ./configure --disable-all --enable-logging_dev jobsubmission and broker ./configure --disable-all --enable-jss_rb wl ./configure disable-all enable-wl proxy ./configure --disable-all --enable-proxy userinterface profile ./configure --disable-all --enable-userinterface_profile information profile ./configure --disable-all --enable-information_profile information pthread ./configure --disable-all --enable-information --with-globus-flavor=gcc32dbgpthr lbserver profile ./configure --disable-all --enable-lbserver_profile locallogger profile ./configure --disable-all --enable-locallogger_profile jobsubmission and broker profile ./configure --disable-all --enable-jss_profile RPM Installation In order to install the WP1 RPMs on the target platforms, the following commands have to be executed as root: rpm -ivh workload-profile.X.Y.Z-K.i386.rpm rpm -ivh userinterface-X.Y.Z-K.i386.rpm rpm ivh userinterface-profile-X.Y.Z-K.i386.rpm rpm -ivh informationindex-X.Y.Z-K.i386.rpm rpm ivh informationindexpthr-X.Y.Z-K.i386.rpm rpm -ivh informationindex-profile-X.Y.Z-K.i386.rpm rpm -ivh jobsubmission-X.Y.Z.i386.rpm rpm -ivh jobsubmission-profile-X.Y.Z-K.i386.rpm rpm -ivh locallogger-X.Y.Z-K.i386.rpm rpm -ivh locallogger-profile-X.Y.Z-K.i386.rpm rpm -ivh lbserver-X.Y.Z-K.i386.rpm rpm -ivh lbserver-profile-X.Y.Z-K.i386.rpm rpm -ivh logging_dev-X.Y.Z-K.i386.rpm rpm -ivh proxy-X.Y.Z-K.i386.rpm rpm ivh workload-profile-X.Y.Z-K.i386.rpm rpm -ivh userguide-X.Y.Z-k.i386.rpm By default all the rpms install the software in the /opt/edg directory, but the profile rpms (i.e. informationindex-profile, jobsubmission-profile, locallogger-profile and lbserver-profile) that install instead in /etc/rc.d/init.d. If you install one of the following rpms: jobsubmission-X.Y.Z-K.i386.rpm locallogger-X.Y.Z-K.i386.rpm lbserver-X.Y.Z-K.i386.rpm informationindex-X.Y.Z-K.i386.rpm informationindexpthr-X.Y.Z-K.i386.rpm you will have all needed files installed in /opt/edg and it is necessary to install the configuration and start-up files also in /etc/rc.d/init.d additionally installing the corresponding profile rpms. Namely using the rpms: jobsubmission-profile-X.Y.Z-K.i386.rpm locallogger-profile-X.Y.Z-K.i386.rpm lbserver-profile-X.Y.Z-K.i386.rpm informationindex-profile-X.Y.Z-K.i386.rpm the following scripts are respectively installed in /etc/rc.d/init.d broker and jobsubmission locallogger lbserver information_index The administrator (with root privileges) has then to issue from /etc/rc.d/init.d the command: $