Install

Install from source files

The easy install procedure from source files is as follow. Note this example uses "bash" instead of "csh" or "tcsh".

 $ ./configure
 $ make

Then, you become the root.

 $ su -
 # make install

As a result, the OmniRPC software is installed on the default directory ("/usr/local/omrpc"). If you want to change the install directory, you can specify another install directory.

 $ ./configure --prefix /path/to/install

After installation, add "/path/to/install/bin" to the PATH environmental value.

• bash

   $ export PATH=$PATH:/path/to/install/bin
  

• csh or tcsh

   % setenv PATH "$PATH:/path/to/install/bin"
  

Install with the Globus Toolkit library

To compile OmniRPC with Globus Toolkit, the globus-makefile-header program, which is attached to Globus Toolkit, is needed. And, OmniRPC requires a library which supports pthread (such as gcc32dbgpthr, gcc32pthr).
Input the following to build OmniRPC with the Globus Toolkit library.

 $ ./configure --enable-globus

At this time, the Globus Toolkit path is set to the value of ${GLOBUS_LOCATION}, and the path to Grid Packaging Toolkit(GPT) is set to the value of ${GPT_LOCATION}.

If you want to specify a path to Globus Toolkit or to GPT, you should add some options.

 $ ./configure --enable-globus --with-globusDir=/path/to/globus --with-gtpDir=/path/to/gpt

Install Test

To test the installation, proceed as follows. Before testing, you should move "OmniRPC/test" directory. And, in each test, you should move the directories s which are written by number. To obtain more detailed information of the test program, especially if you encounter trouble with program testing, add the command option "--debug", if some trouble on program testing.

1. stub_test

To generate the stub program and test the "local-exec-test" program, move the subdirectory (omrpc_stub_test) and type in "make" to compile the program.

 % make

To test the stub program

 % local-exec-test

Next, we should register the stub information. In registration, we have to create the directory (${HOME}/.omrpc_registry).

 % mkdir ~/.omrpc_registry
 % make reg_stub

2. exec_test:

We test stub activation on a remote node. Especially, we test APIs (OmniRpcExecRemote, OmniRpcExecCall) which enable remote execution. First, we input "make" to compile the program.

 % make

To test the OmniRpcExecRemote API, <stub_directory> is a stub directory on which we compile procedure 1. We must describe <stub_directory> as an absolute path.

 % remote_exec_test1 <host> <stub_directory>

In a similar manner, test OmniRpcExecCall API.

 % remote_exec_test2 <host> <stub_directory>

3. call_test:

You should check Remote Procedure Call's API(OmniRpcCall, OmniRpcCallByHandle). Create the host file(hostfile.xml). You can get more detailed information about creating hostfile.xml from hostfile.txt.

    ~/.omrpc_registry/hosts.xml
    <OmniRpcConfig>
    <Host name="localhost"/> 
    </OmniRpcConfig>

Check OmniRpcCall API.

    % rcp-call-test1 

Check OmniRpcCallByHandle API.

    % rpc-call-test2 <host>

Check OmniRpcModuleInit, OmniRpcCall API.

    % rpc-call-test3

Check OmniRpcAsync, OmniRpcWaitAll API.

    % rpc-async-test1

The install test is finished.