Exactly. This MT would be for a select (*trainable*) few. If they were following a URL from an email they would end up hitting the main MT (actually a DNS alias for a load balanced VIP of main MTs).
There is no real harm in them using the main MT other than their session will time out and they will encounter a message saying they are connected from another machine, allowing them to override. One option would be to have a filter that monitors the AR System Email Messages form to look for emails with "http://web/arsys/";. If a MT URL is being sent then look up the recipient to see if they should get the special MT. If they use the special MT REPLACE web with web1. Jason On Thu, Mar 10, 2011 at 1:41 PM, Pargeter, Christie :CO IS <cparg...@lhs.org > wrote: > ** > If you did the multiple MT servers with different timeout value how would > you handle the emails that come from the application server? Would they all > say http://web/arsys/forms/ars/form even if you had web for most people > and web1 for say your Help Desk? > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Jason Miller > *Sent:* Tuesday, March 08, 2011 1:06 PM > *To:* arslist@ARSLIST.ORG > > *Subject:* Re: Session timeout on Midtier > > ** Another option would be to have another Mid-Tier server with a different > timeout value. We were planning on doing what Joe suggested for our service > desk but recently have been kicking around the idea of a dedicated MT with a > much longer timeout for them. > > > Of course they need to know how to get to their own MT vs. what the rest of > the enterprise uses as well as we have not worked out a way to enforce only > the appropriate people are using this MT (wish there was a $MTSERVER$ > keyword in AR). Worst case we can do it at the web server level to filter > traffic. > > Jason > > Jason > > On Tue, Mar 8, 2011 at 12:36 PM, Joe Martin D'Souza <jdso...@shyle.net>wrote: > >> ** >> >> Bola, >> >> Create workflow on forms where it should not timeout, to auto run a dummy >> transaction before the timeout happens.. This would mean a overhead on those >> clients by way of active links running on intervals running a dummy modify >> or create transaction to a dummy form.. Permit this workflow to run only >> when members of the groups that need this are logged in.. >> >> That would be the quickest and dirtiest and perhaps the only way of doing >> it... >> >> Cheers >> >> Joe >> >> *From:* Oyefeso, Bola <boyef...@dpscs.state.md.us> >> *Sent:* Tuesday, March 08, 2011 3:33 PM >> *Newsgroups:* public.remedy.arsystem.general >> *To:* arslist@ARSLIST.ORG >> *Subject:* Session timeout on Midtier >> >> ** >> >> Does anyone know how to make the session not to timeout for some groups on >> Middtier? >> >> >> >> Bola Oyefeso >> _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ >> > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
