Chapter 3. Configuration
Prev     Next

.

Chapter 3. Configuration

Table of Contents

3.1. Configuration
3.1.1. Files
3.1.2. Man pages
3.2. Ports
3.3. Verifying the configuration
3.4. JIMS resource utilization

3.1. Configuration

3.1.1. Files

Before starting JIMS, there should be set JAVA_HOME environmental variable: 

$export	JAVA_HOME=/opt/java1.5

The variables can be put into /etc/default/jims or /etc/java/java.conf file, which are both "sourced" during JIMS startup. Example configuration of /etc/default/jims is shown below: 

export JAVA_HOME=/opt/java1.5

Configuration files are placed in $JIMS_HOME/jims/etc directory. It is necessary to configure only one file site.cfg.

The GW and HTTP environment variable should be set to the value that is returned by the 'hostname' command. The GW tells JIMS which agent is the 'master' agent, and the HTTP variable tells JIMS whether to start the HTTP service with the repository of modules. The repository is used by the agent (and potentially other agents) to load the modules from remote location. In our case the repository is located on the same node as the JIMS agent is started.

We can verify the operation of HTTP server and the JMX WS connector after JIMS startup by issuing the telnet command for the target host and following ports (respectively for HTTP repository and the JMX WS connector): 

$telnet access	7701
$telnet access	7702

We can also use the browser to check whether the service has started successfully: http://access:7701 http://access:7702/jims-jmxws

3.1.2. Man pages

In order to read man pages for JIMS, we have to set the MANPATH environmental variable: 

$export	MANPATH=$MANPATH:$JIMS_HOME/share/man

Having the MANPATH set correctly, we have the following man pages available: 

$man jims-agent
$man jims-manager
$man jims-cli

3.2. Ports

  1. JIMS uses UDP/7707/224.224.224.224 for discovery of other agents in local cluster. This port does not have to be open for the external world (outside the cluster) and it can concern only private address space in the cluster. In systems configured by iptables we can use following command (for node with IP w.x.y.z): 
    $iptables -A INPUT -s w.x.y.z/255.255.255.0 
-d 224.224.224.224 -i eth0 -p udp -j ACCEPT
    Important notice: allowing UDP in general is not enough - the procedure above is required because it is required to allow UDP multicast traffic explicite.
  2. In order to register discovered nodes in local cluster, JIMS uses also TCP/7707/unicast connections from CE to itself and (potentially) all WNs. This port also does not have to be open for the outside world.
  3. In order to connecto to JIMS from the outside world, and for the proper operation of the JIMS P2P subsystem (discovery of all computing elements), there has to be open also the TCP/7702/unicast port. In JIMS P2P subsystem, the initial sites, that have to exist before any other agents are started, are configured in the $JIMS_HOME/share/java/jims-gateway-3.0.0.jar/newGDS.properties file. By default, the file contains the CYFRONET's address of ce.i2g.cyf-kr.edu.pl. However, it can be set to any other host or to the chosen set of other initial hosts. The newGDS.properties file included in the JAR has to be configured before an agent is started (the JAR is then copied to the HTTP repository and then its copy is downloaded).
  4. JIMS also uses TCP/7701 to operate as a repository of modules. In default configuration (where all variables, i.e. the GW and the HTTP point to the hostname of CE), all agents started on all CEs act as repositories of modules, that is why there is a need to have this port open for the CE (itself) in order to download monitoring modules.
  5. For measurement purposes, JIMS pathload module uses two ports (one TCP and one UDP) configured in pathload-base-3.0.0.jar/pathload.prop file (by default: tcp_port=55001, udp_port=55002).

3.3. Verifying the configuration

We can verify the configuration by connecting to JIMS system using the commandline console. Assuming that 10.0.128.9 is the public IP of access node with JIMS agent up and running, we can test the configuration as follows: 

$jims-cli
JIMS CLI v. 3.0.0, type "help" for help
JIMS>connect 10.0.128.9
Connection prepared for: 10.0.128.9
JIMS>list
[01] 10.0.128.1
[02] 10.0.128.9
JIMS>cpu
TIME/CPU0,1,... USER NICE IDLE SYSTEM [hs/s]:
[01] 10.0.128.1: 2[0 2] 0[ 0 0]2051[1028 1023] 3[0 3]
[02] 10.0.128.9: 2[7 14] 0[ 0 0] 198[ 93 86] 0[0 0]
JIMS>quit

3.4. JIMS resource utilization

JIMS resource utilization depends on number of requests per second. Tests for recently used JMX WS (JSR262) connector have not been performed yet.

Prev     Next
Chapter 2. Installation  Home  Chapter 4. User guide