Complete one of the following tasks to update the device.xml file:
Option 1 (only for BlackBerry Enterprise Server 4.0.x to 4.1.x)
To download the updated device.xml and vendor.xml files, complete the following steps:
- Right-click the link for each of the following websites and select Save Target As or Save Link As.
- Save the files to C:\Program Files\Common Files\Research In Motion\AppLoader.
Note: On Windows® 64-bit servers, the path will be as follows: C:\Program Files (x86)\Common Files\Research In Motion\AppLoader.
-
No BlackBerry® Enterprise Server Services need to be stopped or restarted after replacing the device.xml and/or vendor.xml files.
Option 2
Download and install the most recent version of BlackBerry Device Software that is authorized from the wireless service provider's website or from www.blackberry.com.
Note: Installing BlackBerry Device Software on the same computer that is hosting the BlackBerry Enterprise Server can automatically overwrite the device.xml file. The device.xml file that is bundled with the BlackBerry Device Software is up to date at the time the software was created and might not be the highest available version.
Option 3 (only for BlackBerry Enterprise Server 5.0 to 5.0 SP3)
The BlackBerry Administration Service automatically connects to the Internet using a secure connection to the BlackBerry.com website to download the latest device.xml and vendor.xml files every hour.
If the BlackBerry Administration Service Application Server (BAS-AS) log is set to debug, you will see the below log lines ten minutes past the hour:
(10/20 08:10:00:031):{EJB-Timer-3[target=jboss.j2ee:service=EJB3,jar=100basServerManagementServer.jar,name=TimerManagerBean]} [com.rim.bes.bas.softwareconfigurationmanager.SoftwareConfigurationManagerBean] [DEBUG] [BBAS-200] {u=SystemUser, t=3273} Enter bean SoftwareConfigurationManagerBean.retrieveExternalXMLLocal
(10/20 08:10:00:031):{EJB-Timer-3[target=jboss.j2ee:service=EJB3,jar=100basServerManagementServer.jar,name=TimerManagerBean]} [com.rim.bes.bas.traitmanager.TraitManagerBean] [DEBUG] [BBAS-200] {u=SystemUser, t=3274} Exit bean TraitManagerBean.findTraitLocal: 'result='https://www.blackberry.com/Desktop/Download/XML/Vendor.xml''
(10/20 08:10:00:031):{EJB-Timer-3[target=jboss.j2ee:service=EJB3,jar=100basServerManagementServer.jar,name=TimerManagerBean]} [com.rim.bes.bas.traitmanager.TraitManagerBean] [DEBUG] [BBAS-200] {u=SystemUser, t=3275} Exit bean TraitManagerBean.findTraitLocal: 'result='https://www.blackberry.com/Desktop/Download/XML/Device.xml''
Note: The URLs for Device.xml and Vendor.xml are case sensitive for everything that follows www.blackberry.com (ie: ...blackberry.com/Desktop/Download/XML/Vendor.xml) and if the case is changed, the files will not be accessible.
- BlackBerry® Enterprise Server
If the software is sent to a local connected BlackBerry smartphone using a remote BlackBerry Manager. The same file versions of the vendor.xml and device.xml must be used on the computer that is using the remote BlackBerry Manager.
This can be resolved by updating the device.xml and vendor.xml files located in C:\Program Files\Common Files\Research In Motion\AppLoader.
Out of date device.xml and vendor.xml files on a workstation running BlackBerry Desktop Software 6.0 can result in no prompts for upgrades for smartphones when the correct device software is installed or failure to recognize new models of smartphones. This can be due to blocking of the automatic update of the files by a proxy server
Disclaimer
By downloading, accessing or otherwise using the Knowledge Base documents you agree:
(a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and
(b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.
Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.