The sample configuration file "webcal.xml" is for the application WebCalendar. You can download WebCalendar from webcalendar.sourceforge.net

The configuration file contains following information

1)Transaction Information: 

	Transaction information is specified in the tag <transaction>. User can specify information about as one or more transactions. In the sample file there are 3 transactions Login, ViewEntry, WriteEntry. Main field in transaction is <url>, which contains the url of the transaction. For session based transaction there will be more than one url tags. One of them is main url which is to be profiled and other are used to maintain session. They should be in the same order as required for maintaining session. "count" attribute specifies how many times the url should be executed. The count should only be specified for other urls, not for main url. User can also specify method GET/POST as an attribute of the url, default is GET method.
	
	User can also specify a hierarchy of sequences. Sequeces are used so that different executions of a transaction can have different URL. The URl in the <url> tag can contain the sequence variable in the format ${variable-name}. Each execution of the URL will replace the ${variable-name}
by a different value.

2)Node Information:
	There should be a <NodeInfo> tag for each server that serves the transactions. In node information the server process and its machine address should be specified. In the port field we specify the port at which the daemon Autoprofiler is running. This should be same as the port specified while executing the daemon by the command ./prof -d <port>.

3) <farmer> tag
	Here we specify, which transactions are to be profiled in <usertransaction> field. Load-Generator is multi-threaded. The <executioncount> tag specifies how many times each thread should be executed.

4) <farm> tag
	count attribute specifies number of simultaneous users.
