RMCS Install and Config

The RMCS service is hosted for the eMinerals project on the NGS and will later be extended for use by all NGS users. A description of what RMCS does can be found here. These pages document how to install client tools and configuration data needed by users of the service.

Upgrading to NGS hosted RMCS Service.

If you previously were using another RMCS server you will need to change the URL settings in ~/.rmcs/rmcs.config to


and in ~/.rcommands/rcommands.config to


Remember that you will need ~/.rmcs/rmcs.config , ~/.rcommands/rcommands.config and ~.srb/.MdasEnv (and .MdasAuth on NW-grid machines) setup on every host you will be submitting to. E.g. for "preferredGridList = ngs2", this means all sites of the NGS available to RMCS (see the MCS Grid Hosts list)

The metadatamanager web portal is located at


or an alternative interface is available here


You will also need to recompile or install v0.3.0 Rcommands/Rgem client tools for your local client as documented below. All original username/passwords and database entries have been ported from the old server.

Initially both eMinerals and NGS SRB collections are supported but users are recommended to migrate data to the NGS SRB collections and switch both their .MdasEnv and .MdasAuth settings to NGS SRB. Note that RMCS requires the presence of both files even if using GSIAuth (which otherwise does not require .MdasAuth). If using GSIAuth the contents of .MdasAuth can be a junk password rather than your real SRB password if .MdasEnv contains "AUTH_SCHEME 'GSI_AUTH'". The rmcs server also needs to be updated when you switch, please inform the server administrators by email to the NGS helpdesk.

Grid hosts available for RMCS Jobs.

Details of available grid hosts (needed for .mcs input files) can be found here MCS Grid Hosts . This list is updated daily. Note you must have been granted access to these separately before submiting a job.

RMCS Client Commands Installation.

Example RMCS Client Config file

( ~/rmcs/rmcs.config ).

username = RMCS Username> password = RMCS password> cacertdir = /etc/grid-security/certificates myproxyusername = proxy=myproxy.grid-support.ac.uk url=https://fs6.ngs.rl.ac.uk:8443/axis/services/rmcs

Note that when using rmcs_submit etc. the commands will prompt for the myproxy password of the proxy uploaded to the "proxy=" server set in rmcs.config, as below:

[ngs0123@ngs ]$ rmcs_submit -i myjob.mcs -n "My Job Name" Enter MyProxy password: Submitted new job with jobID: 30375

The username associated with the proxy is taken from the 'myproxyusername' in the config file. The default if using the command line 'myproxy-init' command would be the local unix id (ngs0123 in the above example), so users should be careful to ensure the usernames match. However proxies uploaded using one of the java myproxy upload tools must use the local unix id ('ngs0123' in this example) of the user who will run 'rmcs_submit' as the 'username' and the prompted password as was entered for the 'Grid PassPhrase' for example in the picture below.

MyProxyUpload Username Screen

RCommands/RGem Client Installation (v 0.3.0).

The v0.2.2 Rcommands were merged with the Rgem service and client code to create the 0.3.0 service and client code. 0.3.0 is installed on the NGS hosted RMCS service and you must use 0.3.0 clients to interact with it. 0.2.2 Rcommands client tools will not work.

A tarball for the 0.3.0 client tools is available, it contains everything you need including the latest gSOAP (2.7.10) library and an installer script. The installer script compiles both gSOAP and the Rcommands and can install them if needed. Installation is as follows:

  • Download tarball

wget http://www.ngs.ac.uk/applications/rcommands-0.3.0.tar

  • Unpack tarball

[user@machine]# tar -xvf rcommands-0.3.0.tar

  • Edit the install.sh

[user@machine]# cd ClientTools [user@machine]# vi install.sh

Update the following lines especially if you are not root and are installing for your own login account.

.... rcommands_instdir=/usr/local .... # Setup the client if required #mkdir -m 700 ~/.rcommands #cp config/rcommands.config ~/.rcommands #chmod 600 ~/.rcommands/rcommands.config exit 0

[user@machine]# ./install.sh

  • Test the installation

Edit ~/.rcommands/rcommands.config and update username, password, cacertdir fields, then upload a certificate proxy to the myproxy server using your method of choice.

[user@machine]# Rinit [user@machine]# Rls

Rcommands/ Rgem Client Config file

All grid hosts on which you want to run jobs on, submitted through RMCS must have the file ~/.rcommands/rcommands.config which should have unix 600 permissions set as below. You will also need this file on any host on which you want to run any of the Rcommands or Rgem commands.

[user@machine]# chmod 600 ~/.rcommands/rcommands.config

The file should contain:

username = RMCS username> password = RMCS password> cacertdir = /etc/grid-security/certificates http_proxy=myproxy.grid-support.ac.uk url=https://sc2.esc.rl.ac.uk:8443/axis/services/rcommands

The items username, password should have your RMCS username and password. The cacertdir may be different on each grid host it is installed on, although it is traditionally as above. The directory must contain the files for the UK eScience Root and UK eScience CA X509 certificates. These are usually the files: 367b75c3.0 (http://ca.grid-support.ac.uk/pub/certs/367b75c3.0) 98ef0ee5.0 (http://ca.grid-support.ac.uk/pub/certs/98ef0ee5.0) adcbc9ef.0 (http://ca.grid-support.ac.uk/pub/certs/adcbc9ef.0) 8175c1cd.0 (http://ca.grid-support.ac.uk/pub/certs/8175c1cd.0). Contact the local admin for grid host if this directory does not contain these 4 files.

The http_proxy is the url for the myproxy server. To use the Rcommands you must have a valid certificate proxy uploaded on this server and its life must be long enough so that it is still valid when the rmcs job completes and when you want to run any of the Rcommands.

The url is the same for all installations of the Rcommands for the NGS hosted eMinerals RMCS service.

Topic revision: r1 - 19 Jan 2009 - RobAllan
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback