I see the 4 am.. If you have CD (configuration discovery - formally marimba) you may want to run that at 5am. AIE will run for hours.
On Thu, Dec 3, 2009 at 11:41 AM, Shyam Attavar <atta...@sbcglobal.net>wrote: > ** > Good point Tauf, > We are running everything based on events except one which is time based - > at 4 AM every morning. > -- > Shyam > > ------------------------------ > *From:* "Chowdhury, Tauf" <tauf.chowdh...@frx.com> > *To:* arslist@ARSLIST.ORG > *Sent:* Thu, December 3, 2009 5:10:02 AM > > *Subject:* Re: Adding AIE process to armonitor.conf > > ** > > Also, keep in mind if you have any Data Exchanges that run on interval, > they will most likely kick off when the service is started. So you would > want to take into consideration of doing this during peak usage of the > production environment. > > > > *T**auf** **C**howdhury** **|** **F**orest** **L**aboratories**, **I**nc.* > ** > > Analyst, Service Management > > Mobile:646.483.2779 > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arsl...@arslist.org] *On Behalf Of *Joe DeSouza > *Sent:* Thursday, December 03, 2009 3:37 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Adding AIE process to armonitor.conf > > > > ** > > Whats your OS??? > > > > If it is Windows, you can have the Windows Services manager to restart the > process after it dies. The Services manager has options to do a task after a > process dies one of them which is to restart it.. > > > > If you are on UNIX you could write a cron job to check the process at > intervals when a AIE schedule has to run, and if not found to restart it.. > > > > Or you could write a cron job to stop the process at a anticipated time > when there will be no AIE job running and to automatically start just before > an AIE process is about to be triggered.. > > > > Joe > > > ------------------------------ > > *From:* Shyam Attavar <atta...@sbcglobal.net> > *To:* arslist@ARSLIST.ORG > *Sent:* Thu, December 3, 2009 1:34:36 AM > *Subject:* Adding AIE process to armonitor.conf > > ** > > Dear Listers, > > We are seeing an issue with the AIE process dying from time to time and we > would like to add this to armonitor.conf, so that the process can be > restarted without any manual intervention. We are currently running only a > single instance of AIE on the same box running AR Server. I am not sure if > this is even recommended. I was wondering if any of you have done this. If > so, what are the things we need to watch out for? > > Any insight is really appreciated. > > Thanks, > -- > Shyam > > > > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ > ------------------------------ > This e-mail and its attachments may contain Forest Laboratories, Inc. > proprietary information that is privileged, confidential or subject to > copyright belonging to Forest Laboratories, Inc. This e-mail is intended > solely for the use of the individual or entity to which it is addressed. If > you are not the intended recipient of this e-mail, or the employee or agent > responsible for delivering this e-mail to the intended recipient, you are > hereby notified that any dissemination, distribution, copying or action > taken in relation to the contents of and attachments to this e-mail is > strictly prohibited and may be unlawful. If you have received this e-mail in > error, please notify the sender immediately and permanently delete the > original and any copy of this e-mail and any printout. > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ > -- Patrick Zandi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
