Hi, Previous answer is already very complete, but you could go a little further if you have some time : - create a supervision form - create a dummy approval process - create an escalation that executes a "new details" command for this process every X minutes - if you find the generated signature, close it; else, send an alert
On Mon, Sep 10, 2012 at 10:29 AM, patchsk <vamsi...@gmail.com> wrote: > ** > Unlike email engine, approval server is not a separate service, so you > cannot monitor a service or a tcp port. > It is built in as a plugin. The components involved are approval plugin, > dispatcher, application pending entries. > The way approval server works is remedy workflow creates an entry in the > Application Pending form when it needs approval server to do something. > There is a separate daemon called the dispatcher. > The dispatcher looks at the entries in the application pending form and it > invokes the respective plugins to process the request. The entries have a > field called category, which tells what plugin that it needs to invoke. > Once the dispatcher processes the request the application pending entry gets > deleted. > In an ideal scenario there should not be any entries in the application > pending. > So you can monitor the data in this table at sql level or remedy api level > and if there are records older than certain time threashold that is your > alert that something is not working right in the system. > The way to restart approval server is when armonitor started initially there > is a .lck file created in the logs folder.This file contains the approval > process id. > You can have a shell program to kill that process and delete the .lck file > and armonitor will automatically restarts approval server. > > On Sunday, September 9, 2012 11:01:45 PM UTC-7, Rob van Eerd wrote: >> >> Hi, >> >> Like mentioned in this topic about a hanging E-Mail Engine >> (http://listserv.rbugs.com/cgi-bin/wa.exe?A2=ind1209&L=ARSLIST&D=0&P=101940) >> we're occassionally experiencing similar behaviour with our Approval Server. >> We already restart our processes once a week, but that may not be enough. >> >> While looking for a real solution, we could implement somekind of monitor >> which can alert us on moments the Approval Server doesn't do what it's >> supposed to do or restart the approval server process itself. >> >> Anyone any ideas on what to monitor? >> >> We're running SRM 7.6.00 on an ARS 7.5.00 Linux environment (Oracle >> database). >> >> Thanks for any ideas. >> >> Regards, >> Rob. >> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
