Article

Problem

When trying to access eGuide from the BlackBerry Browser, you are presented with a WML exception as the BlackBerry gets identified as a WAP/WML browser.

Solution

Modify the eguide.cfg file to add the BlackBerry User Agent and force it to use text/html content instead of defaulting to WML.

Example

In order to complete this, you must edit the User Agent section in the eguide.cfg file. Below is an example of a User Agent that is defined by default in the eguide.cfg file.

Templates.UserAgent.3.id=*ProxiNet*
Templates.UserAgent.3.interface=simple

This above statement is pointing to a "template interface=simple" which, if you look further down in the configuration file, forces the content to be displayed as text/html.

Templates.Interface.4.id=simple
Templates.Interface.4.contentType=text/html

If you copy the above User Agent values and modify them to detect the BlackBerry Browser it will allow the BlackBerry to render the page in HTML correctly.

For example:

Templates.UserAgent.3.id=*ProxiNet*
Templates.UserAgent.3.interface=simple
Templates.UserAgent.4.id=*BlackBerry*
Templates.UserAgent.4.interface=simple

You will need to increment the number after UserAgent. to identify this as a seperate User Agent. After doing this you will need to restart Apache/Tomcat in order have eGuide read the new configuration file.

Note: Any help or links to how to locate the eguide.cfg on Netware vs Linux and a link to restarting Apache on Netware/Linux would be appreciated!

Environment

This was tested against eGuide 2.1.x running on OES SP1, but it should also work with eGuide running on any OS platform.