Installing Ninf-G

Getting Started

System Requirements

• Red Hat Linux 6.1, 6.2, 7.1, 7.2, 7.3
• Solaris 7, 8
• IRIX 6.5

Download

• A "configure" script
• all source code
• C-based XML parsing library
• header files
• makefiles required to build and install Ninf-G
• sample numerical libraries and client applications
• manual documents

create user ninf

Installation

After downloading the Ninf-G software and ensuring the above requirements, perform the following steps. The Ninf-G software is available for UNIX/UNIX-like operating systems. All of the client and server software except the Globus toolkit is bundled into one tar-gzipped file.
We assume that all of the Globus components work properly beforehand. The Globus toolkit is available from the Globus project. The Ninf-G distribution tar file is available from the Ninf homepage. Instruction steps are as below:

• Environment variable GLOBUS_LOCATION (for GT2) or GLOBUS_INSTALL_PATH (for Globus Ver.1) must be defined to specify the installation directory of the Globus Toolkit.
• Notes for GT2.2 or later: --without-gpt option is required if GPT_LOCATION is not defined.
• Place the tar file (e.g. ng-latest.tgz) on the system where you would like to maintain the source.
• Uncompress and untar the file

  % gunzip -c ng-latest.tgz | tar xvf -

  This creates a directory called ng , which makes up the source tree along with its subdirectories.
• Change directories into the ng directory, and type in the top diretory,

  % cd ng/
  %./configure
  

  This aids in the build process by providing host-specific software information to identify compilers and other tools to be used during compilation, and allows you to deploy the system in an easy way.
  If you would rather specify the installation directory explicitely or other site-specific parameters, you could add some arguments after the command like the following,

   
  % ./configure --prefix=/usr/local/ng 
                --with-globus=/usr/local/globus
                --with-globusVersion=1
     

  This example defines the following required arguments:
  • Path to the Ninf-G installation directory
  • Path to the Globus Toolkit directory
  • Use Globus Ver.1 as a base toolkit
  All options to configure are documented in the below section or can be seen by running

   % ./configure --help 

  When using Globus Ver.1, --with-globusVersion=1 option must be specified. Version 2 is used as a default value of Globus Version.S
• Compile all components of the Ninf-G software by typing

   % make 

  Ninf-G uses a configure script generated by GNU autoconf to produce makefiles. If you have POSIX make program then the makefiles generated by configure will try to take advantage of POSIX make features. If your make is unable to process the makefiles while building you may have a broken make. Should make file during the build, try using GNU make.
• Install compiled files and the LDIF files onto the proper directory by executing as root or appropriate privileges.

   % make install 

• Register the host information by running the following command as a owner user of GLOBUS_LOCATION. It is usually a user globus.

  % cd ng/bin
  % ./server_install
  

• Add the information provider to the GRIS.
  • For Globus Ver.1:
    Add the following line to ${GLOBUS_DEPLOY_PATH}/etc/grid-info-resource.conf. This file maintains local resource information services provided by the GRIS which generate data based on information within the file.

     0 cat ${GLOBUS_DEPLOY_PATH}/var/gridrpc/*.ldif 

  • For GT2:
    
    • Add the following line to ${GLOBUS_LOCATION}/etc/grid-info-slapd.conf.

       include  ${GLOBUS_LOCATION}/etc/grpc.schema 

      The line should be put just below the following line.

       include  ${GLOBUS_LOCATION}/etc/grid-info-resource.schema 

    • Type the following command for restarting GRIS.

       % ${GLOBUS_LOCATION}/sbin/SXXGris stop 

       % ${GLOBUS_LOCATION}/sbin/SXXGris start 

• NOTES for dynamic linkage of the Globus shared libraries:

  
  The Globus dynamic linking libraries (shared libraries) must be linked with the Ninf-G stub executables. In order to enable this, set the shared library linkage path appropriately according to the system on which the Ninf-G stubs are installed. For example, this is done by adding the location of Globus libraries (${GLOBUS_LOCATION}/lib) to the environment variable ${LD_LIBRARY_PATH} of the Globus Gatekeeper spawning via inetd, or on Linux, add (${GLOBUS_LOCATION}/lib) in /etc/ld.so.conf.

Configure Options

Available options to be used for configuration can be listed by typing

 % ./configure --help 

The following is detailed information on the options to the configure script.

Generic Configure Options

Directory and file names

These options specify where Ninf-G objects will be placed.

Host type:

Features and packages:

In general, these options take the following forms.

�@