Introduction
Bombard is a tool to literally bombard Weblicht services, with the intention to check the reliability and performance of chains.
Usage
The distribution contains two scripts to use Bombard, bombard and bombard-summarize. bombard is used with a configuration in JSON format. For instance, if we have a configuration file my-services.json, the following command will start bombarding the configured chains and will write the results to my-services.out:
bin/bombard my-services.json my-services.out
The my-services.out is not very readable, since it contains individual results. The bombard-summarize command provides a summary of the results:
bin/bombard-summarize my-services.out
If you are still bombarding services, a nice way to get intermediate results is to let bombard-summarize refresh the results every *n* seconds. For instance, the following command will refresh the results every ten seconds.
bin/bombard-summarize 10 my-services.out
The examples/german-constituent.json file contains a longer example of a Bombard configuration. We will discuss a shorter fragment here:
{ "testcases": [
{
"name": "berkeley-larger",
"services": ["11858/00-1778-0000-0004-BA7B-4", "http://hdl.handle.net/11022/0000-0000-1CB2-8"],
"dataFilename": "/Users/ddekok/Desktop/silbersee.tcf",
"interval": "30 minutes",
"requestTimeout": "30 minutes"
}
}
In this configuration, there is only one test case. This test case is named 'berkeley-larger' (the name should be unique). This test case calls two PIDs sequentially, sending 'silbersee.tcf' to the first PID, and if processing was successful, to the second PID. It will do this every 30 minutes, with a request timeout of 30 minutes (if a service does not provide results in 30 minutes, we consider it to have failed).
