BlackBerry Forums Support Community

BlackBerry Forums Support Community (http://www.blackberryforums.com/)
-   General 8300 Series Discussion - Curve (http://www.blackberryforums.com/general-8300-series-discussion-curve/)
-   -   Deploying apps through the BES (http://www.blackberryforums.com/general-8300-series-discussion-curve/92245-deploying-apps-through-bes.html)

Gavsta 08-26-2007 04:57 AM

Deploying apps through the BES
 
Is there a good hw to anywhere that will show me how to do this?

prudent89 08-26-2007 07:43 AM

The BES Admin Guide is fairly straight forward in walking you through this.

Freedom Keyboard did a very good step by step on this.
BES Security changes - Powered By Kayako SupportSuite

Here are their instructions minus the screen shots, just modify them for the software that you're working with:

Creating a Software Configuration and applying a control policy for the Freedom Universal Keyboard.
The following instructions were put together from instructions sent by Research In Motion along with excepts from the BlackBerry Enterprise Server for Microsoft Exchange Version 4.0 Handheld Management Guide, our own notes, and screen shots from our BES server.
BlackBerry Enterprise Server for Microsoft Exchange version 4.0 Handheld Management Guide
1) Setup third-party applications (Wireless connection).
1. Create an applications folder in Program Files\Common Files\Research In Motion\Shared\
2. Create a subfolder under the Program Files\Common Files\Research In Motion\Shared\applications\”directory for each third-party application”. Copy the handheld installation files (.ALX & .COD*) files to this directory.
You need to create a directory for each configuration (For example c:\program files\common files\research in motion\shared\applications\bluetooth keyboard).
3. Index the applications** by specifying the loader /index command from the command prompt. [See command below: ]
Go to: C:\Program Files\Common Files\Research In Motion\Apploader Type the command: Loader.exe /Index
* The .ALX and .COD files for both 4.1 and 4.2 can be can be downloaded from .ALX and .COD files for 4.1 and 4.2 - Powered By Kayako SupportSuite
**When you run Loader.exe you will not get any confirmation that it has run. This is normal.
2) Share Handheld Software and upgrade tools.
1. Verify that the handheld upgrade software is installed in <drive:>\Program Files\Common Files\Research In Motion as described above.
2. Share <drive:>\Program Files\Common Files\Research In Motion.
3. Set the permission attributes to Read-only.
3) Setting up the software configuration.
a) Open the BlackBerry Manager software on the BES server.
b) Select “Blackberry Domain” from the left hand side and click the Software Configuration tab.
c) Click Add New Configuration.
d) Fill out the Handheld Software Configuration Screen.
i) Enter a name for the new configuration
ii) Optionally fill in a configuration description
iii) Enter the Handheld Software Location in standard UNC format:
Press the “Change” button to browse to the location of the files, be sure to point to “My Network Places,” then Entire Network, drill down to the shared \Program Files\Common Files\Research In Motion. Then click OK.
*NOTE: Do not go further then selecting the “Research in Motion” Folder.
e) Expand Application Software, and you see your third-party applications.
f) As shown below, for each third-party application change the Delivery column to Wireless or Wireline (normally this should be Wireless).
g) Click on the Policies button and then click the New button.
h) From the Application Control Policy window, change the Event Injection to Allowed and make sure Disposition is set to Required
i) Click OK to accept the changes.
j) Make sure the Policy you created it assigned to the Application Software and Click OK.
4a) Assign a software configuration to a user
1) On the left hand panel select Servers then select your BES Server.
2) Click the Users tab on the right.
3) Select the user you wish to apply the software configuration to from the list on the right.
4) Click Device Management in the bottom panel and then Click Assign Software Configuration
5) Select the Software Configuration that you just created and press Ok
4b) Assign a software configuration to a group
You can also assign the software configuration to a group.
1) Expand User Groups under Blackberry Domain on the left panel.
2) Select the User group you wish to apply the software configuration to.
3) On the right hand panel select the Group Configuration tab and click Device Management to expand.
4) Click Assign Software Configuration select the Software Configuration that you just created and press “Ok”
*Note: Depending on settings the new software configuration may not be pushed to the handheld right away.
5) Trouble Shooting and other BES settings.
Other Settings:
Below is a list of other settings that can stop the keyboard from working. With the default BES settings most of these should be ok if the BES is using the default settings but if you are experiencing any issues please check these settings first.
IT Policy Settings.
There are two main areas within the IT Policy which most commonly effect the software configuration for the keyboard. These are the “Security Policy Group” and “Bluetooth Policy Group”.
To access the IT Policy:
1) Click on “BlackBerry Domain” from the Explorer View on the Left. On the Right select the “Global” tab and then click on “Edit Properties”.
2) In the “Global Properties” window that pops up select “IT Policy” from the list on the left.
3) Click on the “…” button on the right panel next to “IT Policies”.
4) On the Window that pops up highlight the policy that applies to the keyboard user and click on properties or create a new policy.
Policy Settings:
Under the “Security Policy Group” check that: Disallow Third Party Application Downloads is set to False Allow Third Party Applications to Use Serial Port is set to True
Under the “Bluetooth Policy Group” check that:
Disable Bluetooth is set to False Disable Paring is set to False
Disable Serial Port Profile is set to False
Disable Discoverable Mode is set to False
Require Password for Enabling Bluetooth Support is set to False
Require Password for Discoverable Mode is set to False
Other Application Control Policy settings.
In the Application Control Policy (where you set event injection to allow) there are also a number of other settings that could effect the keyboard if they have been changed from the default. These are:
Disposition is set to Required
Bluetooth Serial Profile is set to Allowed
General Trouble Shooting.
Q) I have checked all of the above but the software configuration is still not being pushed to the user.
A) Make sure that the delivery method in the software configuration is set to wireless. Also make sure the user does not already have the driver software installed and double check all the settings in the section above. It can take up to 4 hours for the software configuration to be pushed out. Also make sure that you have the right drivers set in the software configuration for the user. The btkbd42 .alx and .cod files are for the newer 4.2 BlackBerry’s (such as the Curve, Pearl, etc). The btkbd41 .alx and .cod files are for the older 4.1 BlackBerry’s.
Q) I have checked all the settings on the BES and the policy is still not being pushed out, the hand held device is a:
BlackBerry 8700 Series
BlackBerry Pearl 8100 smartphone
BlackBerry 8800 smartphone
BlackBerry 8300 Curve smartphone
A) There is an issue with the BES not having the Hardware ID for the newer devices. Please see knowledge base article KB04693 on the Research in Motion website (link below)
BlackBerry Search Results
Q) I have triple checked all of the settings on the BES and the policy is still not being pushed out, now what?
A) The BES software does sometimes seem to have problems with pushing out a software configuration, especially if you have ever had the software configuration disposition set to disallowed. If you have checked all the above settings and the policy is still not being pushed out then try remove the software configuration and policy and renaming the directory where you saved the .alx and .cod files to. Then recreate the software configuration. If this still does not push the software out then double check that you have assigned it to the correct user (select the user and at the bottom of the right hand panel it will show you what software configuration is assigned to them). If it is assigned and it says it is installed or that an install is required then install the drivers directly on the BlackBerry using the desktop manager and the .alx file in the shared folder on the BES. It is important that you use the exact same .alx file as you specified in the software configuration.
Q) The software has pushed out to the user but when they try to install it they are getting errors.
A) As above make sure you are pushing the right software version to the right handheld. Also double check the settings above, especially the Disallow third party applications setting in the IT Policy.
Q) The software has installed on the handset and keystroke injection is now set to allow but when I try to turn the keyboard on it says the Bluetooth is turned off.
A) On the hand set make sure that Bluetooth is turned on. If it is then double check the Bluetooth Policy Settings in the main IT Policy (As above) and make sure that Bluetooth Serial Profile is set to Allowed in the software configuration.
Q) Everything seems to be set up ok but when I try to connect the keyboard it just comes up with connecting but never actually connects.
A) This can sometimes happen if the pairing has become corrupt (especially if there have been a lot of attempts to connect the keyboard with an incorrect software configuration). Following the steps below on the handheld will resolve the problem.
Note: These steps are for the Freedom Universal Keyboard. The procedure is the same for the Freedom Original and Freedom BlackBerry but in these cases ignore the reference to switching the keyboard to SPP mode and just turn the keyboard on.
1) Remove the batteries from the keyboard (this clears its memory).
2) On the BlackBerry run the "Bluetooth Keyboard" software and if asked enter your "Unlock Code
2a)If you have not already generated your unlock code you will need to visit the site below: www.freedominput.com/unlock.html
3) You should see two tick boxes. One saying "Activate Keyboard" and another saying "Reconnection" make sure that both of these are NOT ticked.
4) Exit the software and on the BlackBerry main menu go to "Options" (depending on the model this may also be called "Settings").
5) In the Options Menu go to "Bluetooth".
6) If you see KEYBOARD on the list highlight it, open the menu and select "Delete Device".
7) Put the batteries back in the keyboard and switch it to "SPP Mode" (put the little switch to the left).
8) On the BlackBerry go back to "Options" and then "Bluetooth".
9) Open the menu and select "Add Device"
10) The BlackBerry should now search for and find the keyboard. Once it is found select it from the list. When asked for the Passkey enter 0000
11) Once it is paired you should see the keyboard on the list. Highlight it, open the menu and select "Device Properties".
12) Make sure that "Trusted" is set to "Yes", "Encryption" is set to "Enabled" and that under "Services:" it says "SPP Slave". Exit and save any changes you made.
13) Run the "Bluetooth Keyboard" software. Tick the "Activate Keyboard" check box. The "keyboard status" should change to "Connecting" and then say "Connected".
14) Once it says "Connected" tick the "Reconnection" check box and try using the cursor keys on the keyboard to move down to the keyboard test box. 15) Try typing in the test box. The keyboard should now be connected and working.

Gavsta 08-26-2007 08:26 AM

Hi,

Thats straightforward enough - I have created two apps to be pushed, Google Maps and Mobireader.

How can you tell its actually working ???

Inphektion 08-26-2007 08:33 AM

In the bes you can "update software configuration check status" which will show either "up to date", "install required", "upgrade required" , etc for the users software. when you first push it out you should see install required. After anywhere from 5 minutes to 4 hours it should say "up to date" and then it should be on the handheld.


All times are GMT -5. The time now is 09:29 PM.

Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.