[slimbim]

Currently running BES 4.1 SP1 (along with some BES 4.0 servers).

I am trying to fully understand the message workflow... I always thought that every message goes through Blackberry Infrastructure (RIM's servers), but looking at the Message Workflow diagram recently, this is not true?

Livelink - Redirection

On the diagram, for BES, it shows the message flow as follows:
Messaging Servers --> BES --> Firewall --> Internet --> Wireless Network --> Blackberry devices

Or is RIM's infrastructure part of the "Internet" in teh workflow?

Thanks!

[|||||||]

RIM's infrastructure is part of the wireless network.

Edit: HAHA I just looked at the PDF, and Infrastructure is on the PIN to PIN diagram but not the BES email one.

[jibi]

Actually, the RIM infrastructure would be part of the Internet portion of the workflow. It really just depends on how you want to look at the Internet, as defined in the workflow. There is an encrypted connection between your firewall and the RIM infrastructure, but it's initiated over the Internet. There is also an encrypted connection between RIM's infrastructure and the carrier wireless networks, which is also initiated over the Internet (I believe). Here's the former diagram from 4.0.

[GSR]

what about pin to pin messages?

Is it true these are not encrypted?

If this is the case, do they still pass through the bes dispatcher(which encrypts them) to RIM to the cellular provider and finally to the handheld?

[jibi]

Originally Posted by GSR

If this is the case, do they still pass through the bes dispatcher(which encrypts them) to RIM to the cellular provider and finally to the handheld?

PIN messages don't touch the BES. They leave your handheld, travel over the carrier network, to RIM's infrastructure, back over the carrier network, to the other handheld. They are not encrypted.

The association of PIN messages to the BES are through peer-to-peer encryption (if set, you limit your users to sending PIN messages to other users within your BlackBerry domain) and through the disabling of peer-to-peer messages (a policy-enabled option). Neither of these options have any involvement in redirecting messages through the BES - only with pushing settings/policies to the handheld that alter the PIN messaging abilities on the handheld.

[GSR]

thanks Jibi, thats very well explained.

Does anyone have a similiar architecture diagram for the BES 3.6.

I need to compare the architecture, basically document what's different between the BES 3.6 and 4.1.

thanks

[slimbim]

So for BES implementation, all emails will go through RIM infrastructure correct? I've read somewhere that no emails are ever queued or stored anywhere once it leaves the BES. If this is the case, what happens when there is a problem with the RIM infrastructure or the wireless network? Do emails just get re-sent by BES when the message received/delivered confirmation is not received? I would assume the emails don't just get lost...

Thanks for all the information by the way

[jibi]

Yes, all emails originating from the BES or BIS are routed through the RIM infrastructure. In all honesty, I can't really remember what has happened in the past with these pending messages. There was an outage the other night, so maybe you can remember what happened? I'm wanting to say that any messages that were pending for me were not delivered, but perhaps they were (my BES servers never lost SRP connectivity during the maintenance outage).

[jibi]

Originally Posted by GSR

thanks Jibi, thats very well explained.

Does anyone have a similiar architecture diagram for the BES 3.6.

I need to compare the architecture, basically document what's different between the BES 3.6 and 4.1.

thanks

Look on page 24 of the Administration Guide (PDF page, not actual page). I seem to remember that I ripped a 4.1 diagram at some point, but I guess I never posted here. I'll do so tomorrow (today).

[GSR]

Is this an accurate architecture diagram for BES 3.6? it only has 4 components?

What about the blackberry dispatcher, messaging agent, sync service and policy service on 3.6? are these part of the blackberry enterprise server task?

Are these all new components in the BES 4.0/4.1?

any help will be much appreciated, thanks.

[|||||||]

Originally Posted by GSR

Is this an accurate architecture diagram for BES 3.6? it only has 4 components?

What about the blackberry dispatcher, messaging agent, sync service and policy service on 3.6? are these part of the blackberry enterprise server task?

Are these all new components in the BES 4.0/4.1?

Yes that is the diagram, the sync service didn't exist before 4.0 and the policy service didn't do a whole lot so it was all part of the BES service. 4.0 and later allow for more features but also more reliability because if one service fails the other usually will keep working.

[GSR]

Originally Posted by |||||||

Yes that is the diagram, the sync service didn't exist before 4.0 and the policy service didn't do a whole lot so it was all part of the BES service. 4.0 and later allow for more features but also more reliability because if one service fails the other usually will keep working.

thanks. What are you referring to when you say 'BES service'? Is this the 'blackberry enterprise server task' ? Does this mean the Policy service was part of the Blackberry enterprise server task?

Sorry for the daft questions, just need to get my head around the layout of BES 3.6.

[|||||||]

In BES 3.6 there was 4 services, MDS, BES, attachment and Database consistentcy

MDS and Attachment are obvious, database consistantcy was useless and the BES service did everthing else. This is the same as the BlackBerry Enterprise Server task.

[GSR]

Originally Posted by |||||||

In BES 3.6 there was 4 services, MDS, BES, attachment and Database consistentcy

MDS and Attachment are obvious, database consistantcy was useless and the BES service did everthing else. This is the same as the BlackBerry Enterprise Server task.

Brilliant!! Thanks... clears it all up for me.