``````````````````````````````` Other jFed software ``````````````````````````````` jFed features a number of other tools next to the jFed experimenter GUI. Overview ======== GUI tools --------- The jFed Connectivity Tester is part of the jFed Experiment GUI, but can be used without logging in to the actual GUI. So you do not need an account to use it. The Connectivity Tester is useful to debug connectivity problems. It runs a number of connectivity tests, and then shows a report. This report can also be saved to disk. The jFed Probe GUI is a tool for manually calling servers. Very low level calls can be made, and low level replies are visible. This tool requires knowledge of the communication APIs, and the tool itself is not a very user friendly GUI. It can be very valuable for testbed developers that wish to debug their server. The Automated Testing GUI: This tool is used to run tests scenarios on servers. This is only useful for server developers, and it is not a very user friendly GUI. It includes simple tests, such as veryfing if the ``GetVersion`` reply of an AM server is correct, and more complex tests, such as verifying if an AM can correctly provision a node, and if that node can be logged in to using SSH. The jFed Scanner GUI: The jFed configuration contains information on each server that jFed can communicate with. This tool is used to scan a server and automatically fill in this info. It is of interest to server developers, and users that which to use jFed with a server not known to jFed. The Bugreport Viewer GUI: Is a standalone viewer for the bugreports that the jFed Experimenter GUI sends. This is only of interest to the jFed developers. ClI tools --------- The jFed Probe CLI has the same functionality, but it is a CLI instead of a GUI. This tool too is not activly maintained, and not user friendly at all, even for a CLI. It can be useful for certain automation tasks. Contact the jFed authors if you think this tool is useful for you, or consider using `Geni's OMNI tool `_, or the jFed Experimenter CLI. The only advantage of the probe CLI over these tools is that it can send some m low level calls that the other tools cannot. An other alternative to using this CLI, is integrating the jFed library itself in you java project. The Automated Testing CLI: This is the CLI version of the the Automated Testing GUI The jFed Scanner CLI: A CLI tool related to the scanner GUI. This is no longer maintained. Software libraries ------------------ The jFed core library is a java library that is the is the core of all jFed tools. It is open source and can be used for server communication. The jFed RSpec library is a java library for RSpec parsing and manipulation. It is open source and can be used for RSpec manipulation. The jFed Test Assistant is a library that allows java software to use jFed easily in unit or integration tests. Fedmon ------ The Fedmon software suite powers ``_. This site monitors the status of servers in the Fed4Fire and Geni federation. This software is a seperate project that uses the automated testing library of the jFed software. The last version of jFed also depend on the `Fedmon Web API `_ which is part of Fedmon. .. include:: connectivity.rst .. include:: cli.rst