1. Managing JIMS SYSTEM SERVICE
All JIMS service parameters are stored in /etc/jims/jims-service.conf file. There is only one configuration parameter – jims.agent.mlet.url which should be set to point to HTTP URL where monitoring modules (JAR files with SystemInformation, SNMP and NetworkMetrics MBeans) are available.
This parameter should be set in form: jims.agent.mlet.url=http://host.domain:7701.
This part of exercise should be performed on CE, because it manages the JIMS service directly.
Running JIMS monitoring service commands:
Tab 1 JIMS cg-jims-service commands
Before starting JIMS Manager application /etc/jims/jims-client.conf file should be configured. There should be set jims.manager.sg.url parameter to point to URL where SOAP Gateway is running (in form http://host.domain).
Running JIMS Manager application requires:
· changing to $JIMS_HOME/bin directory
· executing ./cg-jims-manager
Fig. 1 Main window of JIMS Manager application
Fig. 1 shows the main window of JIMS Manager application. On the left hand side there is a list of monitored stations (their JMX addresses). JIMS Manager refreshes this list every certain period of time. The thread refreshing the list can be started and stopped manually. We can also refresh the list on demand. The more advanced functionality of JIMS Manager allows user to load custom MBeans from earlier defined HTTP server, deploy them or remove, what can be useful during development or administration.
Fig. 2 MBean Server user interface – monitored MBeans attributes
Fig. 2 shows details of particular MBean Server. Left panel contains names of registered MBeans. By clicking on one of them and selecting an attribute from attributes tree there can be displayed value of each parameter of monitored station. There are also (of course available through all other applications) other system MBeans like RmiConnectorServer, MLetService, that are accessible through this interface.
Diagrams on Fig. 3, Fig. 4 and Fig. 5 visualize monitored parameters. There are charts of CPU usage like idle time, user time and system time during last period of time, file systems utilizations and memory usage, respectively. Each diagram refreshes itself every period of time. Due to CPU load on machine that renders these diagrams, there is an option to disable visualization and use only text information provided by SystemInformation and SNMPMirror MBeans.
Fig. 3 MBean Server user interface – CPU usage visualization
Fig. 4 MBean Server user interface – file systems utilization visualization
Fig. 5 MBean Server user interface – memory statistics
All client configuration parameters are saved in /etc/jims/jims-client.conf configuration file. There is only one parameter to set in jims-client.conf file, used both by cg-jims-client and cg-jims-manager application: jims.manager.sg.url. This is the http URL to server, where SOAP Gateway is installed and running and should be in the form: http://host.domain.
Running CLI client application requires:
· changing to $JIMS_HOME/bin directory
· executing ./cg-jims-client args
Currently there is only one argument for cg-jims-client – IP address of host to which latency is measured. For example: ./cg-jims-client 126.96.36.199. IP addresses can be obtained through the JIMS Manager application.
Results of executing cg-jims-client script are shown below.
Listing. 1 Running CLI JIMS client application
Listing. 1 shows data obtained through the CLI interface. Shown results are only example of
parameters that can be delivered by JIMS. First line show command line to be executed – name of script and IP address of WN to which latencies are measured from all other WNs.
Second line shows current version of JIMS client - v.1.4.
Next there is time stamp – current time in [millis] from 1 Jan 1970 and below there are IP addresses of all monitored stations, User Times (hundreds of second that CPU spent on user tasks), ICMP latency from current host to host specified in the command line, UDP latency and throughput measured using UDP protocol.