[Slippery]

Hey all, I need to allow Blackberry Application Control for the Event Injector API for a Shasta bluetooth keyboard. Can anyone give me some direction?

BES= GroupWise, ver. 4.0.2.20

I need to know where I have to set the permission for this device. I can't find anything that says Blackberry Application Control on the BB manager, or BES server config. Do I have to setup a software policy, and if I do how do I go about it? I have been pretty lucky with my users not needing to much other than their email and I have been able to figure out much of the BES administration on my own but here I am stumpped...any help will be appreciated. Thanks,
Slip

[shaqinsactown]

Install the software first somewhere that the BES can point to.
Then you have to allow it in the software configuration
Then I believe an IT policy has to allow for event injection from that software config

[edonin]

Shaqinsactown's reply is pretty right on. However, once you create the software configuration in Handheld Tool Mgr, you'll need to create an application control policy for the allowance of event injection and apply the ACP to your keyboard software configuration.

[|||||||]

BlackBerry Search Results

And apply SP5a for your BES.

Edit: updated link

[Slippery]

Update...thanks for the help...still not working but...I tried to apply the new software config and I had problems. Here is what happened.

I created a new folder in C:\program files\common files\research in motion\shared called applications.

inside this folder I added a folder called 'shasta keyboard' and copied the .alx and .cod files for the keyboard there.

then I shared the research in motion folder as read only for everyone. (all of this is on the BES)

when I then went to the software configuration and tried to add one, I could browse to this folder but it would not attach to anything inside so the button stayed grey.

Does anyone know why it is not picking up the driver files?

I also ran loader.exe /index from the command prompt to index the app.

[mrc7928]

Originally Posted by Slippery

Update...thanks for the help...still not working but...I tried to apply the new software config and I had problems. Here is what happened.

I created a new folder in C:\program files\common files\research in motion\shared called applications.

inside this folder I added a folder called 'shasta keyboard' and copied the .alx and .cod files for the keyboard there.

then I shared the research in motion folder as read only for everyone. (all of this is on the BES)

when I then went to the software configuration and tried to add one, I could browse to this folder but it would not attach to anything inside so the button stayed grey.

Does anyone know why it is not picking up the driver files?

I also ran loader.exe /index from the command prompt to index the app.

From what I understand, the permissions of the Shasta Keyboard folder should be Read & Execute, List Folder Contents and Read permissions delegated to authenticated users. Try that, rerun the loader /index command and see if it created PkgDBCache.xm and specification.pkg files and let us know.

[Slippery]

Originally Posted by mrc7928

From what I understand, the permissions of the Shasta Keyboard folder should be Read & Execute, List Folder Contents and Read permissions delegated to authenticated users. Try that, rerun the loader /index command and see if it created PkgDBCache.xm and specification.pkg files and let us know.

I have the PkgDBCache.xml...not xm (does this matter?) and specification.pkg in the folder but still get the grey button. The permissions are taken care of because I just gave full control to everyone for that folder to see if it is a permission thing...it does not seem to be. I feel like I am missing something and have run the loader /index several times. Thanks for the help and I'll try any other ideas you have.

[mrc7928]

Sorry, meant to type .xml, but left the l off the end.

All you should have to do now is add a new configuration, name it and point it to the location that the software. The Shasta Kyb software should then show up in your list of applications and you should be able to check the box next to it. Once that is done, you create a policy to allow the injector API and assign that policy to the software install.

When you click to add a new software configuration, do you see the Shasta application under applications? What button is showing as greyed out? At this point in the install, it appears that the loader worked correctly, so running it again will do no good.

[Slippery]

OK...now I am cookin' with Gas...I have the unc in there and have checked the Shasta Keyboard and applied the policy (shasta keyboard). In the policy it asks for the internal domains and external domains I want to establish connections with...what is this?

[Slippery]

Now it is working...I applied the software config to the handheld and waited a few minutes for the sync and it is good to go. Thanks for everything.

BTW, I did not have anything in the domain fields and it worked fine.

Slip

[GovBerry]

I'm trying to setup an application in Handheld config. I've read this thread hoping it would help. But I don't get the PkgDBCache.xml and specification.pkg files once I run apploader. ( My enviornment is Exchange)

Any ideas

[|||||||]

Double and triple check the folder names, the spelling is probably off

[GovBerry]

I'm new to this so...

I may have misread the instructions but I had to install one of the Handheld applications on the server THEN i was able to view the applications I was trying to setup.

[|||||||]

Originally Posted by GovBerry

I'm new to this so...

I may have misread the instructions but I had to install one of the Handheld applications on the server THEN i was able to view the applications I was trying to setup.

Here is the article you want to follow: BlackBerry Search Results