This directory contains:

./gridbroker.jar  - A jar file containing GridBroker, GridSim v2.1, and
                    SimJava v1.2 classes.

  NOTE: No updates or improvements on GridBroker package since GridSim v2.1,
        hence, it is more stable under GridSim v2.1 and SimJava v1.2 release.

./doc     - GridBroker API
./example - A simple example on how to use GridBroker
./src     - A GridBroker source files

This application only works on GridSim version 2.1 and older.
DO NOT use gridbroker.jar with the latest version of gridsim.jar (see below).

===============================================================

FAQ

Q: How do you compile and run GridBroker application?

A: Similar to compile and to run GridSim. Instead of using gridsim.jar,
   you use gridbroker.jar. Inside this jar file, it contains GridBroker,
   GridSim and SimJava classes.

   Please do not use recent GridSim release jar file when running this broker
   (see the below question).

---------------------------------------------------------
Q: I have executed all gridsim examples. But while executing gridbroker
example, it gives following error after initializing gridsim:

Initialising...
Starting GridSim version 4.0
Entities started.
java.lang.IncompatibleClassChangeError
 at gridbroker.Broker.body( Broker.java:649)
 at eduni.simjava.Sim_entity.run(Sim_entity.java:603)


A: read the README.txt file.

./gridbroker.jar  - A jar file containing GridBroker, GridSim v2.1, and
                    SimJava v1.2 classes.
NOTE: No updates or improvements on GridBroker package since GridSim v2.1,
hence, it is more stable under GridSim v2.1 and SimJava v1.2 release.

You cant mixed up jars from different class versions.
That's why you have this error message.

---------------------------------------------------------
Q: I want to create a specific application. Is it necessary to build on top
   of GridBroker?

A: You are expected to develop an application on top of GridSim,
   instead of GridBroker. GridBroker is included to demonstrate the
   capability of GridSim in simulating the Grid environment and a
   Nimrod/G like deadline and budget constraint scheduling system.

---------------------------------------------------------
Q: The application generates the files: tracefile, stat.txt, g14.sched1,
   g14.sched2, g14.sched3, g14.sched31, g14.sched4, g14.sched5, g14.sched6.
   What are the meaning of these files?

A: These files contains statistical results of the simulation that are of
   interest to the GridSim user (ie. you).

   When running a GridBroker application, it will produce the following files:

        stat.txt -> created by GridSim class during GridSim.init() to create
                    a GridStatistics object for statistical purposes

        tracefile -> created by the SimJava package to trace every events
                     that are performed by SimJava, GridSim and GridBroker
                     during the simulation.

        g14.sched* -> All of these files are created by Broker class.
                      When we create an UserEntity object, it will
                      automatically creates a Broker object.

    Description on the g14.sched* files:
        g14.sched1 is about Gridlets finished report.
        g14.sched2 is about Gridlets processing expenses report.
        g14.sched3 is about Gridlets on resource report.
        g14.sched31 is about Gridlets committed for resource report.
        g14.sched4 is same as g14.sched1, however this file only
            displays the overall result or summary of g14.sched1 file.

        g14.sched5 is same as g14.sched2, however this file only
            displays the overall result or summary of g14.sched2 file.

        g14.sched6 is same as g14.sched3, however this file only
            displays the overall result or summary of g14.sched3 file.

    NOTE: Explanations about the content of each file are mentioned in
          GridBroker example section.

---------------------------------------------------------