Has anyone ever created an internal website for the BB users to navigate to and install 3rd party applications for there devices. I am wanting to create an internal webpage for my end users to navigate to so they can install the 3rd party software if they need it right away so they don't have to wait for me to push it. I have create a small webpage on the IIS dir on the BES server and pointed it to the alx and cod files but this does not work. any ideals

On our Intranet we have an area called 'Libraian' where many documents are hosted (SOP's, DOP's, requst forms, directories, etc).

I created a simple Word document that contains install links and instructions some of the more popular (free) 3rd party apps (Beyond411, BBWeather, Google Maps, etc).

Then I updated the 'Home Page' link in the IT Policy to point to this document.

Works like a charm. Best thing is it is available to every device as soon as it is activated.

Ummm isn't this one of the main purposes for the Web Desktop Manager?

The links I'm providing in my document at the OTA links. I don't have the actual files anywhere.

We allow 3rd party app downloads, so this works for us.

How are you links setup? do they point to the alx file or cod files. What gives the BB user the prompt to download the alx file to install the application

OTA downloads through a browser typically use JAD files actually. Which are basically web versions of an ALX file.

so do you create an html page that has a hyperlink that points to a container that has a jad file and then your BB users can open up the interpage click on the hyperlink and install the software from there ??

It's a simple Word document, with embedded hyperlinks. That simple.

I type the word 'HERE', highlight the word, click Insert/Hyperlink, and put the OTA download link.

I don't have the jad files anywhere on our network.

I am wanting to point to JAD files that live on a network share internally. Has anyone done this instead of using the web desktop manager

We have this setup so that users can download OTA to their devices.

All you need is the HTML page and link to the JAD file. You will also need the COD file which contains the main program you want to install. I also have the ALX file in there too, but I don't think it is necessary for OTA installation.

I remember having to modify/create the JAD file myself to get this all to work for programs that I didn't have a JAD already created for OTA installation.

Here is the JAD for Reuters installation:
Manifest-Version: 1.0
RIM-COD-Module-Name: xpeclient
RIM-COD-Module-Dependencies: net_rim_cldc,net_rim_os
MIDlet-Jar-Size: 329101
MIDlet-1: Reuters Wireless Delivery System Client, ch/techop/excalibur/xpe/blackberry/resources/icon.gif,
RIM-COD-Creation-Time: 1142498547
MIDlet-Jar-URL: xpeclient.jar
RIM-COD-URL: xpeclient.cod
RIM-COD-SHA1: 0a fd 46 c4 41 36 97 60 31 f3 2d f0 25 13 8f 17 f5 b5 1a af
RIM-COD-Size: 173200
MicroEdition-Configuration: CLDC-1.1
MIDlet-Version: 1.2.1
MIDlet-Name: xpeclient
MIDlet-Vendor: Reuters PLC
MicroEdition-Profile: MIDP-2.0

To get the RIM-COD-SHA1 value I had to run:
fciv.exe -sha1 -add {filename}
Can't remember where I got fciv.exe from though.

Hope this helps.

Mark