Tuesday 25 June 2013

Static Agents Vs Dynamic Agents in Blackberry Enterprise Server

Static Agents:

You can create separate Mailbox Agents for those special, important VIP users on your Blackberry Server so even if a Mailbox Agent worker thread gets blocked and a Mailbox agent is unresponsive they can still get mail delivered. Note that a new mailbox agent is like a new MAPI connection so you don’t want to create a lot of them because you BES server will become unresponsive.

The steps to assign a static mailbox agent on BES 5.0 are:

Log into the BlackBerry Administration Service web console.
Expand User under the BlackBerry Solution Management.
Click Manage Users.
Search for the desired BlackBerry smartphone user and click on their display name.
Click on Component information in the user view.
Click on Edit user.
Set Turn on static mailbox agent to Yes.
Enter a number between 200 and 399 in the Mailbox agent ID field.
Click Save all.

This procedure might be useful when BlackBerry smartphone user accounts are on a remote Microsoft® Exchange Server that has network latency issues. Assigning these BlackBerry smartphone users to a static agent can reduce the impact of network latency on BlackBerry smartphone user accounts on local Microsoft Exchange servers.

This is a temporary solution to consider while the network latency issues are addressed.

Note: If assigning multiple static agents, each one will initiate a new BlackBerryAgent.exe process and a new CalHelper.exe process on the BlackBerry Enterprise Server. These processes will use hardware resources and may cause performance issues on the BlackBerry Enterprise Server.

Dynamic Agents:

Each BES will start up by default 5 dynamic mailbox agents with SQL, each mailbox agent has a maximum of 100 MAPI threads and a maximum of 5 threads per pool. So about 500 users per agent.

Refer the blog for more info


No comments:

Post a Comment