09-24-2012 03:34 PM
Today, our server side application does a HTTP Post to a pre-configured BES URL and is able to push an icon to a BB5,6 or 7 device without any issues. The server side application is not Java based and simply uses a HTTP Post to do the push. All is well and our clients are happy :-)
Now looking forward to BB10, it seems that things have gotten much more complex. The following is my understanding:
1. BES and MDS will not be applicable to BB10 devices since those devices will use the new BDS service. Will this service have an MDS-like interface so we can do a push to the relevant device?
1a. If not, how can we push to the BB10 device?
1b. Do we have to write some sort of Java server or can we continue to use simple HTTP Post like we are doing today with BB5,6 and 7?
Remember, I am only interseted in the BES sceanrio (corporate enterprise devices) and not BIS.
Solved! Go to Solution.
09-24-2012 04:56 PM
03-14-2013 04:05 PM
BlackBerry Enterprise Server 10 can be used to push to BlackBerry 10 devices. It will support existing push initiators and should not require any changes. The Push Service SDK 1.2 also has support to help you push via BES to BlackBerry 10 devices.
05-27-2013 10:41 AM - edited 05-27-2013 10:57 AM
I am struggling to get BES push in a BB10 app working, where the BB10 app is a migrated version of BBOS app.
"It will support existing push initiators and should not require any changes."
Obviously there are changes required at the BB10 end, and I can't get my head around them. Is there any documentation for this migration?
I have been through the pushCollector program, and even tried it on my Z10 - but when I start it after setting BES, I get error 10002 - which is basically saying there is a problem with the provider id. But according to the documentation, I should not need to specify one.
Any hints gratefully received....
BTW, the pushCollector program is running inside my Work perimeter, I have installed from BlackBerry World - Work.
Also I have replicated what i believe to the required functionality in my own Cascades application, and get the same error. I can confirm that it does connect to the push service and the log messages that come at that time do indicate that my application is running in the Work perimeter.
05-27-2013 05:31 PM
Discovered that if I remove the consumer push permission, "_sys_use_consumer_push", then it works to a point. I no longer get the 10002, and the sample connects to the Channel, as does my application. My client application gets the channel id returned which is the same as the device's PIN, which I guess makes sense.
However the server pushes to either application are ignored. I suspect we need some sort of different push configuration, or there is a parameter we are not specifying correctly, but nothing we are looking at is telling us there is a problem. We have looked at the MDS logs, they indicate the push has been delivered. But nothing shows up at the application end.
Any tracing hints would be appreciated.
05-28-2013 11:33 AM
Yes, the _sys_use_consumer_push permission should not be used for BES/enterprise pushes for BlackBerry 10.
Have you seen this forum thread?
You need to have a X-Wap-Application-Id header when you send out the push from your Push Initiator.
Let me know if you have any questions.
05-28-2013 08:18 PM
Seen that, and am investigating.
Am also following up on the information in here
Will let you know how i get on.
05-29-2013 09:41 AM
Great! I also just wanted to clear up one thing about not having to specify an application ID when you create a PushService instance for BES 10.
You don't have to specify one, because it uses a default one which I mention in the http://supportforums.blackberry.com/t5/BlackBerry-
If you don't specify one, it uses this rule for the application ID:
If you look at the BAR file itself for the app it would be in the META-INF/MANIFEST.MF file.
You basically would take the Package-Name entry and the Package-Id entry and combine them with a period in between.
Application package identifier = Package-Name + "." + Package-Identifier
You would then need to specify this value in your X-Wap-Application-Id header.
08-28-2013 11:52 PM