Welcome to Port3101.org : Your BES Connection Mark forums read | View Forum Leaders
Port3101.org : Your BES Connection



Reply
LinkBack Thread Tools Display Modes
How to use BES 5.0.2 with MDS + Bloomberg Mobile
 
  #1 (permalink)  
Old 08-17-2010, 03:30 PM
RLT RLT is offline
BES Activated
 
Join Date: Aug 2010
Posts: 6
Default How to use BES 5.0.2 with MDS + Bloomberg Mobile

Hi all,

I've just setup the BlackBerry Enterprise Server (BES 5.0.2) with Mobile Data Services (MDS) and now I need to rollout the Bloomberg Mobile software to a couple of our users but I have a few doubts:

Do I need to install MDS Runtime?

I think we have 4 methods to do it.

1 – Download and install the Bloomberg Mobile in the phone;
2 – Using the Desktop Manager – give the application;
3 - Using the “How to create a software configuration to wirelessly deliver third-party applications to a BlackBerry smartphone”
KB03748 - How to wirelessly deploy third-party applications to BlackBerry smartphones
for the 5.0 is in KB03748-How to create a software configuration to wirelessly deliver third-party applications to a BlackBerry smartphone
4 – Using the MDS, do have Bloomberg MDS Gateway?

Or 5 only using MDS

The Bloomberg I´m trying to install is from Bloomberg Mobile
Download Bloomberg on BlackBerry for installing with BES 5.0 or later

Thanks in advance
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 08-18-2010, 10:45 PM
BES Expert
 
Join Date: Mar 2009
Posts: 106
Default

MDS Runtime is an older product meant for custom in-house applications built with MDS studio. It is no longer supported. So, No you do not need it.

To delpoy Bloomberg, just grab the BES 5 zip file and create a software configuration for it. Looks like you have the KB articles to do that already.
Reply With Quote
  #3 (permalink)  
Old 08-19-2010, 05:10 PM
RLT RLT is offline
BES Activated
 
Join Date: Aug 2010
Posts: 6
Default

Hi hooper, thanks for reply.

I have done the software configuration, the job have done well with 1 minute, but none of the blackberrys didn't get the application...

All IT policy's at blackberrys phone are by default, do I have to turn on/off of them?

How can I troubleshooting this kind of issue ? in the phone is possible?

At BES Server in "SRVXXX_POLC_01_20100819_0001" I don't see anything wrong.

Thanks one more time.
Reply With Quote
  #4 (permalink)  
Old 08-19-2010, 05:40 PM
BES Expert
 
Join Date: Mar 2009
Posts: 106
Default

Have a look at some of these tutorials:
BlackBerry Administration Service

Did you assign the software config to a group or user?
Reply With Quote
  #5 (permalink)  
Old 08-30-2010, 03:24 PM
RLT RLT is offline
BES Activated
 
Join Date: Aug 2010
Posts: 6
Default

Hi, its applied to a user.

The job run well, but no APP on the Phone.

I also try with google maps.

Log LABBES01_BBAS-AS_01_20100830_0002.txt

Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(Unknown Source)
at com.rim.bes.basplugin.monitoring.net.BMSConnection.getClientSocket(BMSConnection.java:185)
at com.rim.bes.basplugin.monitoring.net.BMSConnection.getSocket(BMSConnection.java:212)
at com.rim.bes.bms.peer.AbstractPeerConnection.<init>(AbstractPeerConnection.java:144)
at com.rim.bes.basplugin.monitoring.net.BMSConnection.<init>(BMSConnection.java:91)
at com.rim.bes.basplugin.monitoring.net.BMSProxy._invokeCall(BMSProxy.java:484)
... 93 more


(08/30 17:52:46:968):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-11} [com.rim.bes.bas.commands.securitymanager.SecurityLogin] [INFO] [BBAS-1006] {unknown} Logged in user luis.gomes
(08/30 17:52:47:734):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-11} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=2, uc=1, o=0, t=48834} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 17:52:48:593):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-8} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=2, uc=1, o=0, t=49258} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 17:52:49:343):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-8} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=2, uc=1, o=0, t=49622} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 17:53:18:233):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=2, uc=1, o=0, t=50413} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 17:53:32:998):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=2, uc=1, o=0, t=51191} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 17:53:33:826):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=2, uc=1, o=0, t=51555} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 17:54:19:497):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-1} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=2, uc=1, o=0, t=53193} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 17:55:06:683):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-11} [com.rim.bes.bas.commands.securitymanager.SecurityLogin] [INFO] [BBAS-1006] {unknown} Logged in user admin
(08/30 17:55:17:495):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-1} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=54328} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 17:56:40:836):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-4} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=54838} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 18:07:53:437):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-4} [com.rim.bes.bas.commands.securitymanager.SecurityLogin] [INFO] [BBAS-1006] {unknown} Logged in user admin
(08/30 18:11:00:258):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=58419} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 18:11:04:883):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [tapestry.page.ComponentTemplateLoader] [WARN] Template for component ModifyUserInformation/modifyUserAuthenticatorBand does not reference embedded component: adminPasswordLabel.
(08/30 18:11:11:476):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=58836} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 18:13:23:274):{WorkManager(2)-508} [com.rim.bes.bas.reconciliationmanager.ReconciliationManagerBean] [INFO] [BBAS-1009] {u=SystemUser, t=59488} Reconciliation is running
(08/30 18:13:24:743):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=59701} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 18:19:49:283):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-14} [com.rim.bes.bas.commands.securitymanager.SecurityLogin] [INFO] [BBAS-1006] {unknown} Logged in user admin
(08/30 18:27:09:724):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=62078} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 18:27:25:349):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=63091} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 18:27:35:442):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=63795} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 18:27:45:208):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=64604} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 18:27:49:770):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=65077} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
(08/30 18:28:05:629):{http-labbes01.wifi.com.ca%2F192.168.255.232-443-2} [com.rim.bes.basplugin.mdss.MDSSManagerBean] [WARN] [ASMS-2023] {u=1, uc=-1, o=0, t=65781} findDeviceServiceAttributesLocal query device invalid deviceId parameter, com.rim.bes.bas.usermanager.UserDeviceNotFoundException: Message: '_queryDeviceStatus Could not queryDeviceStatus due to device not registered with MDS-IS. null', nested exception: 'null'
Reply With Quote
  #6 (permalink)  
Old 08-30-2010, 10:13 PM
BES Expert
 
Join Date: Mar 2009
Posts: 106
Default

Let us know what you see when you do the following. See screenshots for more info.

1. Goto a user you assigned a software configuration to, and click on that user's software configuration tab.
2. Then click on view resolved applications
3. Is anything listed?
4. If not, click on the other configured applications tab
5. You should see your app there if it was properly assigned to the user. Click on the eye icon to see why it didn't load.
Attached Thumbnails
How to use BES 5.0.2 with MDS + Bloomberg Mobile-8-30-2010-10-10-35-pm.png   How to use BES 5.0.2 with MDS + Bloomberg Mobile-8-30-2010-10-12-12-pm.png  
Reply With Quote
  #7 (permalink)  
Old 08-31-2010, 05:11 AM
RLT RLT is offline
BES Activated
 
Join Date: Aug 2010
Posts: 6
Default

Don't have anything listed, but the job was apply.

See this pictures.

Thanks one more time
Attached Thumbnails
How to use BES 5.0.2 with MDS + Bloomberg Mobile-1.jpg   How to use BES 5.0.2 with MDS + Bloomberg Mobile-2.jpg   How to use BES 5.0.2 with MDS + Bloomberg Mobile-3.jpg   How to use BES 5.0.2 with MDS + Bloomberg Mobile-4.jpg  
Reply With Quote
  #8 (permalink)  
Old 09-09-2010, 10:23 AM
RLT RLT is offline
BES Activated
 
Join Date: Aug 2010
Posts: 6
Default

The problem was solved.

Open Smartphones, Cell Phones & Smart Phones at BlackBerry.com in the firewall - Because the vendor.xml and device.xml dont update... dont start the process to send application to the phones.
Reply With Quote
  #9 (permalink)  
Old 09-13-2010, 10:44 PM
BES Expert
 
Join Date: Mar 2009
Posts: 106
Default

Quote:
Originally Posted by RLT View Post
The problem was solved.

Open Smartphones, Cell Phones & Smart Phones at BlackBerry.com in the firewall - Because the vendor.xml and device.xml dont update... dont start the process to send application to the phones.
This problem comes up quite a bit where the BES server does not have access to the internet. Not so much a firewall rule per se as it is still an outbound connection. You will often see this problem as well when looking for software updates in the BES. The BES needs access to the PAS servers to get the software patch info.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
T-Mobile UMA Certificates mitchberk Port 3101: The BES Admin Bar & Grill 4 03-12-2014 03:47 PM
KB04876 - Differences between BB Mobile Data Service and BB Mobile Data System hdawg Featured BlackBerry KB Articles 0 09-14-2009 09:48 PM
Port3101.org Blogs - Now Mobile Otto Port 3101: The BES Admin Bar & Grill 4 08-26-2009 09:38 PM
Port3101.org Blogs - Now Mobile Otto Site Suggestions & Information 0 08-01-2009 05:46 PM


All times are GMT -4. The time now is 02:46 AM.
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2018, vBulletin Solutions, Inc.


 

SEO by vBSEO 3.3.2 PL2