Hi Tauf, I had faced a similar problem in the past. Upwards of 30 mailboxes across different departments. We did have just one email engine configured for all of them, but ran into large latency since it would go through them all serially, meaning that mailboxes with 1 or 2 unread messages could take a really long time to arrive since the email engine goes through each one serially, and there would be some high volume 'bulk' type email boxes; pretty much what you are describing.
Here are a bunch of performance tips to speed up email processing in general. This may help significantly with your issue. https://communities.bmc.com/docs/DOC-18514 However, if it is still not good enough for your customers, and you want to get the best possible throughput, (i.e. process in parallel) yes you can install multiple email engines on a single server in seperate directories or install multiple on a seperate server or even a set of servers. You want to determine how to dothis based on available memory and cpu for each server, but in your case with just two incoming email inboxes, two email engine instances on the same machine should be fine. I would avoid putting email engine as a service in a server group if you do this, and also recommend keeping email startup seperate from arsystem startup. After installing, and before starting it, you need to edit the emaildaemon.properties for each instance to tell it which mailboxes it is responsible for. I think the installer will ask you for your target arserver name during install, but the emaildaemon.properties also holds this information. com.remedy.arsys.emaildaemon.Mailboxes= If you run multiple email engines for a single server, this setting specifies which mailboxes this email engine should process. The value should contain comma-separated mailbox names. If the value is empty, the email engine processes all of the mailboxes configured for the server. If the value is not empty, the email engine processes the specified mailboxes only. HTH Thanks Randeep On Thu, Jun 19, 2014 at 7:34 PM, Grooms, Frederick W < [email protected]> wrote: > Just use the one Email Engine and put multiple mailboxes in the Email > Configuration form. On Startup the engine reads the configuration and sets > up the necessary threads. > > I don't think there is a way for an Email Engine to specify which > mailboxes it will process (You can specify which servers, but I don't think > you can go any deeper than that so it is an all-mailboxes on the server or > none). > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Tauf Chowdhury > Sent: Thursday, June 19, 2014 6:11 PM > To: [email protected] > Subject: Re: Multiple incoming email boxes > > Right, but my question is more on the how to set it up on the server > itself or if I should use multiple servers each with it's own instance of > the email engine. That's where I'm fuzzy and the documentation isn't there > either. > > Sent from my iPhone > > -----Original Message----- > > On Jun 19, 2014, at 6:18 PM, "Grooms, Frederick W" wrote: > > > > If you set up separate inbound mailboxes, each mailbox should have its > own threads > > > > Fred > > > > -------- Original message -------- > > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Tauf Chowdhury > > Sent: Thursday, June 19, 2014 4:53 PM > > To: [email protected] > > Subject: Re: Multiple incoming email boxes > > > > ** > > Thanks Shawn. Let me elaborate further on the issue. > > Right now, there's a single email address. This email is receiving both > user requests and also what we call "bulk requests" from event management > systems etc... So what is happening now is that the bulk requests which are > high in number are being processed ahead of the user requests because of > the order that they come in. This is leading to the user experiencing a > delay in their ticket being generated. That is the crux of the issue that > we are trying to figure out the best approach to. Logically, we thought > that sending the bulk requests to a separate email address/mailbox and > processing them separately would help. That is why I am trying to set up > multiple boxes. > > > > -------- Original message -------- > > On Thu, Jun 19, 2014 at 4:27 PM, Pierson, Shawn wrote: > > ** > > The easiest way to do it is that I have distribution lists with just the > inbound Remedy email account, and filter the incoming emails based on those. > > > > For example, I may have [email protected] and > [email protected] as two distribution lists that both contain > only the [email protected] account. When an email to either of those > are sent in (where you have to look at not just the To: line but the CC: > line), Remedy has RBE rules to process them and create an Incident with a > Template for the Server team, Service Desk, or whatever. Since inbound > email uses Outlook profiles it seems like it might be kind of tricky or at > least less stable to set up multiple instances on a single server so I’ve > never gone with that approach. > > > > Thanks, > > > > Shawn Pierson > > Remedy Developer | Energy Transfer > > > > -------- Original message -------- > > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Tauf Chowdhury > > Sent: Thursday, June 19, 2014 3:22 PM > > To: [email protected] > > Subject: Multiple incoming email boxes > > > > ** > > All, > > What is the best way to configure the email engine on the server side? I > know you can set up multiple inbound email records in the Email config form > but I'm more interested on the server side. Do I have to have multiple > email engine services installed on the same box? Can I install the email > engine on 2 separate servers? > > Thanks.. > > > > > > -- > > Tauf Chowdhury > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
