11-07-2008 05:45 PM
I am fairly new to the Blackberry development but I just finished my first Application using the Visual Studio 2008 plugin. The app connects to a web service and works great on the simulator.
Now it is time to publish it to our BES for Exchange server (ver 22.214.171.124). I have spent a couple days searching the forums to find the answers I need but have come up short.
There is a Mobile Data Service Properties option in the Blackberry Manager and the service is running. I can get to a webpage on ht++p://bes:8080 that says it is the Blackberry Mobile Data Service, Build 5 Build Version 126.96.36.199.
Now, when I use the MDS Publishing wizard, i change the url to the one above, test it and it works fine. When I click next, I get a "resource not found" error.
I cannot find any type of options to allow unsigned apps or anything of that sort in the blackberry manager.
I tried to publish an MDS runtime on our server and added my phone (8830 188.8.131.52) to the user list. Should BB MDS... be listed in Options->Advanced Options->Applications...
Solved! Go to Solution.
11-15-2008 08:16 PM
BESX 4.0.7 does not come with MDSS, which is required to push custom developed applications.
MDSCS = Mobile Data Services Connection Service which is required to browse using BlackBerry Browser (internal and external sites)
You require BESX 4.1 (which comes with MDSS, we recently renamed MDSS to MDSIS).
For more information feel free to review the following:
Also Feature and technical overview and Release Notes of BESX 4.1.6
Feel free to ask any questions.
11-17-2008 11:36 AM
Thanks for the reply.
After a week of messing around, I finally got my first blackberry app loaded onto my phone using MDS and BES 4.0.
First thing I tried to do was test getting MDS onto my phone with the Handheld configuration manager. I could not get this to install and I tried a few applications with no success. It turns out my 8830 was not in the device.xml file on the BES server. Just my luck to have a device not in the list. Anyway, after adding in the proper line and waiting 30 min (I changed the AppProvisioningPollInterval) I received the update. I also tried putting MDS Runtime 184.108.40.206 on a 8703 4.1 OS with no luck. I made a new alx file that was in my root app folder so I could install both 4.1 and 4.2 the same way 220.127.116.11 install is. I don't know why they changed that but it sure made it confusing.
Now that I had MDS runtime installed, I went after the MDS Upgrade. I ran the script in the install package to create a new Database and set the permissions on it. Then, I ran the install package and got MDS installed. I started the service using the admin tool and published an app to it. The app was listed but I could not see any devices in the device list. I had to configure the MDS Runtime on the device but no matter which address I put in the link it did not work. In the end, I added my connector, set a proxy and applied settings, disabled the proxy, reset the service and it worked. When I changed the download size limit for my connector, I had to set a proxy and apply, then remove it and apply and reset the service. This is the only way it would work.
Now, everything is working great and I have started to roll everything out.
My only other question is if there is any way to set the MDS Runtime path in a policy or does this have to be done manually.
03-28-2009 12:43 AM
I am also facing same problem while installing any MDS application on my BB through BES. I have gone through the given steps but i am not found my device in Registered Device list in BES. I also check in Device.xml my BB device name is there (9000 Bold) so need ur valuable support regarding the same.
Waiting for ur reply