3.6 Running the Sample
In real life, you will want applications on remote boxes. You can see how to do this in the
Deployment section.
However, just to see something running, we will use Eclipse.
There is an Eclipse deployment generated by default - so even though we haven't modelled any deployment information, it is there waiting for us.
You can either run or debug the applications. This display is from Run / Debug Configurations...:
The application can be started in any order, but we tend to start them in the logical order which is:
- UtilityPU
- CongestionZoneProcessor
- DVLA
- RoadUsers
If you build and run this sample straight out of the box,
it will use the shipped "Generate Log Level", which is "Detailed Debug". This will have two consequences:
- This is the most detailed level of logging/tracing and copious amounts of logging will be generated - every entry and exit is logged.
- This will use the centralised logging service once initialisation is complete.
You will see the Utility PU seeming to stop logging: this is because the logging has gone to the logging service.
On Windows, look for a file like
C:\log_YYYYMMDD_hhmmss.txt.
For more information, see the section on the logging service.
To tone down the "Generate Log Level", go to the Preferences page, Generate Time Settings.
To see objects going in and out of the space, either start up the GigaSpaces UI or look at the centralised logger.
|
