Title: Lbi - Updating Infosets
Description: Using a batch file to update infosets
mtom5 - October 12, 2007 06:42 PM (GMT)
Using LBI ver 9.0.2 - trying to follow Lawson's procedure to update Infosets daily using a .bat file which is run by the Windows Scheduler on the LBI server. We can get the individual infosets to update using the following syntax:
Java ExecURL "http://ourserver/lsn/QueueAction?command=update-infoset&id=1033&key=-1533005439">>SampleSchedulerServlet.log
But when we try to update group or update all using the following it does
not update the Infosets:
Java ExecURL "http://ourserver/lsn/QueueAction?command=update-all">>SampleSchedulerServlet.log
Does anyone have this Update All url working??
Thanks
Mtom5 :bye:
mnye - October 12, 2007 08:34 PM (GMT)
First off, I would highly recommend NOT using Update All.
Can you post the output results. Should be in the same directory called SampleSchedulerServlet.log
mnye - October 12, 2007 08:55 PM (GMT)
ah yes, i forgot about that. Because Update-All is so powerful, you have to be authenticated to the SN inorder for that URL to work. The ExecURL servlet doesnt do any authentication.
Again though, I dont think you want to Update-All, its easy but highly inefficient and if there are any errors in any of the infosets this can crash your tomcat instance.
I suggest creating separate bat file for each Grouping of InfoSets at most.
Let me know if I can provide further info.
hth,
matt
mtom5 - October 30, 2007 01:12 PM (GMT)
Now am using the URL for UPDATE GROUP and it is working without problems. Here is the content of the file:
@echo off
Setlocal
Set CLASSPATH=.;%CLASSPATH%
echo =======================================>>SampleSchedulerServlet.log
echo %date% %time%>>SampleSchedulerServlet.log
echo =======================================>>SampleSchedulerServlet.log
Java ExecURL "http://<OUR SERVER>/lsn/QueueAction?command=update-namespace&id=Procurement&key=994787686">>SampleSchedulerServlet.log
mnye - October 30, 2007 04:59 PM (GMT)
if you want to get really fancy you can 4 variables; LogName, Command, ID and Name. Then place those vars in the appropriate places in the bat file. Then all you have to do is pass the variable values to the bat file from a kron job or Scheduled Task. This eliminates the need for multiple bat files.
just a though.