class TMonaLisaWriter: public TVirtualMonitoringWriter

 Create MonaLisa write object.

 Creates a TMonaLisaWriter object to send monitoring information to a
 MonaLisa server using the MonaLisa ApMon package (libapmoncpp.so/UDP
 packets). The MonaLisa ApMon library for C++ can be downloaded at
 http://monalisa.cacr.caltech.edu/monalisa__Download__ApMon.html,
 current version:
 http://monalisa.cacr.caltech.edu/download/apmon/ApMon_cpp-2.0.6.tar.gz

 The ROOT implementation is primary optimized for process/job monitoring,
 although all other generic MonaLisa ApMon functionality can be exploited
 through the ApMon class directly (gMonitoringWriter->GetApMon()).

 Monitoring information in MonaLisa is structured in the following tree
 structure:
 <farmname>
    |
    ---> <nodename1>
              |
              ---> <key1> - <value1>
              ---> <key2> - <value2>
    ---> <nodename2>
              |
              ---> <key3> - <value3>
              ---> <key4> - <value4>

 The parameter monid is equivalent to the MonaLisa node name, for the
 case of process monitoring it can be just an identifier to classify
 the type of jobs e.g. "PROOF_PROCESSING".
 If monid is not specified, TMonaLisaWriter tries to set it in this order
 from environement variables:
 - PROOF_JOB_ID
 - GRID_JOB_ID
 - LCG_JOB_ID
 - ALIEN_MASTERJOB_ID
 - ALIEN_PROC_ID

 The parameter montag is equivalent to the MonaLisa farm name, for the
 case of process monitoring it can be a process identifier e.g. a PROOF
 session ID.

 The parameter monserver specifies the server to whom to send the
 monitoring UDP packets. If not specified, the hostname (the port is
 a default one) is specified in the environment variable APMON_CONFIG.

 To use TMonaLisaWriter, libMonaLisa.so has to be loaded.

 According to the fact, that the deepness of the MonaLisa naming scheme
 is only 3 (<farm><node><value>), a special naming scheme is used for
 process monitoring. There is a high-level method to send progress
 information of Tree analysis (# of events, datasize).
 To distinguish individual nodes running the processing, part of the
 information is kept in the <value> parameter of ML.
 <value> is named as:
    <site-name>:<host-name>:<pid>:<valuetag>
 <site-name> is taken from an environment variable in the following order:
 - PROOF_SITE
 - GRID_SITE
 - ALIEN_SITE
 - default 'none'
 <host-name> is taken from gSystem->Hostname()
 <pid> is the process ID of the ROOT process

 Example of use for Process Monitoring:
   new TMonaLisaWriter("BATCH_ANALYSIS","AnalysisLoop-00001","lxplus050.cern.ch");
 Once when you create an analysis task, execute
   gMonitoringWriter->SendInfoUser("myname");
   gMonitoringWriter->SendInfoDescription("My first Higgs analysis");
   gMonitoringWriter->SendInfoTime();
   gMonitoringWriter->SendInfoStatus("Submitted");

 On each node executing a subtask, you can set the status of this subtask:
   gMonitoringWriter->SendProcessingStatus("Started");
 During the processing of your analysis you can send progress updates:
   gMonitoringWriter->SendProcessProgress(100,1000000); <= 100 events, 1MB processed

   gMonitoringWriter-SendProcessingStatus("Finished");
   delete gMonitoringWriter; gMonitoringWriter=0;

 Example of use for any Generic Monitoring information:
   TList *valuelist = new TList();
   valuelist->SetOwner(kTRUE);
   // append a text object
   TMonaLisaText *valtext = new TMonaLisaText("decaychannel","K->eeg");
   valuelist->Add(valtext);
   // append a double value
   TMonaLisaValue* valdouble = new TMonaLisaValue("n-gamma",5);
   valuelist->Add(valdouble);
   Bool_t success = SendParameters(valuelist);
   delete valuelist;

 option:
 "global": gMonitoringWriter is initialized with this instance

 Cleanup.

 Sends a <status> text to MonaLisa following the process scheme:
    <site> --> <jobid> --> 'status' = <status>
 Used to set a global status for a groupjob, e.g.
 a master-job or the general status of PROOF processing.

 Sends the <user> text to MonaLisa following the process scheme:
    <site> --> <jobid> --> 'user' = <user>

 Sends the description <jobtag> following the processing scheme:
    <site> --> <jobid> --> 'jobname' = <jobtag>

 Sends the current time to MonaLisa following the processing scheme
    <site> --> <jobid> --> 'time' = >unixtimestamp<

 Send the procesing status 'status' to MonaLisa following the
 processing scheme:
    <site> --> <jobid> --> 'status' = <status>
 Used, to set the processing status of individual subtaks e.g. the
 status of a batch (sub-)job or the status of a PROOF slave
 participating in query <jobid>

 Send the procesing progress to MonaLisa.

 Send the fileopen progress to MonaLisa.
 If openphases=0 it means that the information is to be stored
 in a temp space, since there is not yet an object where to attach it to.
 This is typical in the static Open calls.
 The temp openphases are put into a list as soon as one is specified.

 If thisopenphasename=0 it means that the stored phases (temp and object)
 have to be cleared.

 Send the parameters to MonaLisa.

 Set MonaLisa log level.

 Print info about MonaLisa object.