- more examples

diff --git a/org.glite.jp.client/doc/README.jpimporter b/org.glite.jp.client/doc/README.jpimporter
index 74f5ec2..a5629db 100644 (file)
--- a/org.glite.jp.client/doc/README.jpimporter
+++ b/org.glite.jp.client/doc/README.jpimporter
@@ -23,7 +23,7 @@ For LB dumps, there is another utility, which parses common LB dump files
 message describing the location, destination etc. to local directory. This
 message directory should be obviously monitored by the jpimporter again.
 
-lb_dump_exporter usage: lt-lb_dump_exporter [option]
+lb_dump_exporter utility usage: lt-lb_dump_exporter [option]
         -h, --help              Shows this screen.
         -d, --dump <file>       Dump file location.
                                 File generated by the glite-lb-purge
@@ -35,12 +35,6 @@ lb_dump_exporter usage: lt-lb_dump_exporter [option]
                                 Directory, where should be stored the message
                                 describing the file upload (read by jpimporter)
 
-For the sandbox files, you should use the JP client API to create messages for
-jpimporter. The function glite_jpimporter_upload_files() do the job. It takes
-one ore more files and create one tarball. Then everything works like with
-LB dumps. There is an example utility in org.glite.jp.client/examples/jpps_upload_files.c
-(staged as glite-jp-primary-upload_files).
-
 jpimporter daemon usage: glite-jp-importer [option]
         -h, --help         displays this screen
         -k, --key          private key file
@@ -60,5 +54,61 @@ jpimporter daemon usage: glite-jp-importer [option]
                            Specifies the time interval for which the process
                            JobRegistration/FileUpload sleeps after the unsuccessful
                            scan (find no new messages)
+Examples:
+
+So, for the job registration and dump upload from the LB server, you should run the
+LB server like this:
+./glite_lb_bkserverd -c <hostcert> -k <hostkey> -S /var/tmp/purge -D /var/tmp/dump -J /tmp/lb_server_jpreg
+
+(Whenever the job is registered to the LB server, the message for jpimporter
+is stored in the /tmp/lb_server_jpreg directory.)
+
+Then you should run the jpimporter daemon on the same host:
+./glite-jp-importer -k <hostcert> -k <hostkey> -p jpps.server.address:8900 -r /tmp/lb_server_jpreg -d /tmp/lb_server_jpdump
+
+(Every job registration anounced in /tmp/lb_server_jpreg directory will be sent
+to the JP PS at the address jpps.server.address:8900.)
+
+According the dump files - on the same host should be periodicaly ran the
+glite-lb-purge utility. (Usually started by cron) Let say, that it stores the
+LB dump file /var/tmp/purge/dump_file.
+
+Then you should run (most likely in the same cron job)
+./lb_dump_exporter -d /var/tmp/purge/dump_file -s /var/tmp/dumps_per_job -j jpps.server.address:8900 -m /tmp/lb_server_jpdump
+
+(Then there is created a set of LB dump file - one per job - and according to them
+lb_dump_exporter will also notify the glite-jp-importer)
+
+
+
+
+For the sandbox files, you should use the JP client API to create messages for
+jpimporter. The function glite_jpimporter_upload_files() do the job. It takes
+one ore more files and create one tarball. Then everything works like with
+LB dumps.
+
+There is an example utility in org.glite.jp.client/examples/jpps_upload_files.c
+(staged as glite-jp-primary-upload_files).
+
+The glite_jpimporter_upload_files funftion prototype:
+
+int glite_jpimporter_upload_files(
+            /* JP client context.
+             * stores the error code/description
+             * user can set default JP PS address there and
+             * LB directory for jpimporter announcements
+             */
+        glite_jpcl_context_t ctx,
+
+            /* JobId
+             */
+        const char *jobid,
+            /* File list. Stored in the array of string.
+             * Last item has to be NULL
+             */
+        const char **files,
+            /* Location of the user proxy file
+             */
+        const char *proxy);