Hi Raymond, I would agree with Cliff and the procedure he had listed.
Just another point: AlarmNotifier will run as a process and not service in background and would be initiated by process daemon, and you can stop it by killing the process. Also under $Specroot/Notifier it generates *.out log file and *.out.bak which are handy troubleshooting problems. Regards, Nikhil On Tue, Jan 13, 2009 at 2:21 PM, HUNGERFORD, CLIFF [AG/1000] < [email protected]> wrote: > Raymond, > > > > If you've renamed the Notifier process, and you want it to startup and > restart automatically, you'll need to call that out specifically in your > Partlist idb file. > > > > For example, I use a separate Notifier process for our Manufacturing sites > (AlarmNotifier-Mfg), and it uses a separate resource file (.alarmrc-mfg). > Here's my IDB file. I highlighted the syntax-specific lines that make it > work. > > > > PARTNAME;AlarmNotifier-Mfg; > > APPNAME;Alarm Notification Service Mfg; > > WORKPATH;$SPECROOT/Notifier; > > LOGNAMEPATH;$WORKPATH/NOTIFIER-Mfg.OUT; > > ADMINPRIVS;y; > > AUTORESTART;y; > > AUTOBOOTSTART;y; > > #STATEBASED;N; > > NUMPROCS;1; // one per host > > RETRYTIMEOUT;600; // 10 seconds > > #TICKETUSER;$USER; > > RETRYMAX;3; // 3 retries allowed > > STARTPRIORITY;30; > > SERVERPROCESS;y; > > #ENV;<var>=<value>; > > ARGV;$SPECROOT/Notifier/AlarmNotifier-Mfg<CSEXE> -r ".alarmrc-mfg"; > > > > I actually have three separate Notifiers running, all using different > resource files, configured similar to the example above, and they all start > up automatically and run in the background. Works very well. > > > > Hope this helps! > > > > Cliff > > > > *From:* Ferber, Raymond [mailto:[email protected]] > *Sent:* Tuesday, January 13, 2009 12:54 PM > *To:* spectrum > *Subject:* RE: [spectrum] port alarm policies > > > > We are running Spectrum 8.1 running OC & SpectroGraph on Windows 2003 & SS > on Linux 3.x. > > > > First venture into the Spectrum Alarm Notifier area, so let me document the > steps that were suggested to me by CA: > > > > 1. I created a new alarm notifier folder & copied the files from the > original notifier folder into that new folder. > > 2. I named the new folder and application (.alarmrc) the same. > > 3. Updated the paths for the set, update, & clear scripts to use the > new name & location. > > 4. Updated the set, update, & clear scripts to use > VARFORMAIL=NotificationData > > > 5. Using SpectroGraph from the OC selected the SANM Policy > Administrator > > 6. Created an Application & Alarm Notification Policy with the proper > criteria > > 7. Saved the files and associated them. > > 8. Now have a folder, application, & SANM Alarm Notification Policy by > the same name. > > 9. Testing the new SANM policy running from a OC command prompt > everything works as it should. > > 10. The problem is the command line task times out after a few hours > based on server settings. > > > > So the issue is….. How do I get this to run in the background on the OC > server? Or do I need to move this to the MLS? > > > > It was suggested that we create a new .idb file (again with the same name) > in the spectrum/lib/SDPM/partslist/newappname which we did, then cycled the > processd on the OC console. But that didn't seem to address the problem. > > > > Can someone share their experience in getting the new alarm notifier > process to run as a background task? > > > > > > *Thanks* > > > > *Raymond Ferber* > > *Technical Support Architect*** > > > > > > *402-777-1868 Office* > > *402-960-5126 Cell & Pager* > > > > > > - --To unsubscribe from spectrum, send email to [email protected] with > the body: unsubscribe spectrum [email protected] > > ------------------------------ > > *The information in this message may be proprietary and/or confidential, > and protected from disclosure. If the reader of this message is not the > intended recipient, or an employee or agent responsible for delivering this > message to the intended recipient, you are hereby notified that any > dissemination, distribution or copying of this communication is strictly > prohibited. If you have received this communication in error, please notify > First Data immediately by replying to this message and deleting it from your > computer. * > > > > - --To unsubscribe from spectrum, send email to [email protected] with > the body: unsubscribe spectrum [email protected] > > *This e-mail message may contain privileged and/or confidential > information, and is intended to be received only by persons entitled to > receive such information. If you have received this e-mail in error, please > notify the sender immediately. Please delete it and all attachments from any > servers, hard drives or any other media. Other use of this e-mail by you is > strictly prohibited.* > > *All e-mails and attachments sent and received are subject to monitoring, > reading and archival by Monsanto, including its subsidiaries. The recipient > of this e-mail is solely responsible for checking for the presence of > "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts > no liability for any damage caused by any such code transmitted by or > accompanying this e-mail or any attachment.* > > > - --To unsubscribe from spectrum, send email to [email protected] with > the body: unsubscribe spectrum [email protected] > > -- Nikhil Mehra "The only Constant in Life is CHANGE!" "Whether it is mainframe, client-server, distributed, grid or web services computing — none of it works without the network." --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
<<image001.png>>
