Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.
An Explanation of GroupWise Wireless 1.1
GroupWise Wireless 1.1
GroupWise 5.5 Enhancement Pack
NOVELL GROUPWISE WIRELESS 1.1 ARCHITECTURE - SIMPLE EXPLANATION
GroupWise Wireless is a free add-on available at:
GroupWise Wireless leverages your already installed GroupWise 5.5 Enhancement Pack WebAccess. If GroupWise users have already been given rights to GroupWise WebAccess, then they will be able to access GroupWise wireless after a simple install of GroupWise Wireless. GroupWise Wireless leverages the same architecture of GroupWise WebAccess for HTML browsers, by adding new templates for HDML (Handheld Device Markup Language). When the GroupWise WebAccess Servlet running on your web server detects that a device is using HDML, it merges GroupWise message information into HDML templates, rather then the HTML templates.
HDML is an HTML like standard written to be used on devices, such as cellphones. The basic tags of HDML are <HDML> and </HDML>. The HDML language is written to accommodate the smaller size and functionality of handheld devices such as cellphones. The HDML standard was written by a company called Unwired Planet. Unwired Planet has since become PHONE.COM and now OPENWAVE.COM. OPENWAVE.COM not only made the HDML standard, but in the U.S. most of the phones that have microbrowsers use the OPENWAVE.COM HDML browser.
Although OPENWAVE.COM owns the U.S. cellphone browser market, another standard called WAP or WML will most likely take over the U.S. cellphone market in the very near future. The WML standard is not as feature rich as HDML, but it is an open Internet standard. This will ultimately provide end-users more choices to getting their handheld devices connected to the Internet.
UNDERSTANDING GROUPWISE WIRELESS INSTALLATION
When GroupWise Wireless gets installed, the following additions/changes are made to the existing GroupWise 5.5 Enhancement Pack WebAccess installation:
1. Three of the web server's GroupWise WebAccess resource files are replaced. They are: JAVA\BIN\NJGWAP.JAR and JAVA\BIN\NJWEB.JAR and JAVA\SERVLETS\COM\NOVELL\WEBACCESS\WebAccessServlet.class. These are the GroupWise WebAccess servlet files that are now capable of supporting the default HTML templates and the new HDML templates. Once GroupWise Wireless 1.1 has been installed these files are dated 8/30/2000.
The NJGWAP.JAR is the GroupWise Provider/Service. It is the component responsible for handling GroupWise requests in WebAccess.
The NJWEB.JAR file contains "generic" web code. This includes browser detection, file uploading support, browser detection, and rendering functionality.
The WebAccessServlet.class file handle all WebAccess requests from browsers. The request is then routed to a provider/service (in this case NJGWAP). The resulting data is then merged and routed back to the browser.
2. The new GroupWise HDML template files are installed to the web server. They are located in the newly created HDML directory. This directory is found at the following path on the web server that houses GroupWise WebAccess:
3. The web server's NOVELL\WEBACCESS\WEBACC.CFG is modified to include information regarding the HDML templates that the GroupWise WebAccess Servlet can use.
1. The installation should have prompted you to unload the web server. The web server must be restarted. NOTE: The GWINTER process does not need to be restarted. (My experience installing this at customer sites has been that you must re-boot the entire NetWare server to which you install GroupWise Wireless. It seems like there's something with the Novell Servlet Gateway that requires this.)
2. From an HDML device, such as a cellphone with a microbrowser enter the URL to your web server with the "/servlet/webacc" location specified. For example: "http://email.acme.com/servlet/webacc".
3. You should be prompted for a GroupWise userid and password.
4. If this doesn't work, see the troubleshooting section.
1. Make sure that GroupWise WebAccess works, when you access it from a regular computer browser such as Netscape. Hit the very same site that you are trying to hit from your cellphone. If WebAccess isn't working from a regular browser, it won't work for your cellphone. Troubleshoot this problem before going any further with the cellphone. Novell's support site, https://support.novell.com is a great place to start.
2. Check the webserver, make sure that the installation of GroupWise Wireless went well. Look at the installation section earlier in this document for even more information on what happens during the installation. For example look for the JAVA\BIN\NJGWAP.JAR and JAVA\BIN\NJWEB.JAR and JAVA\SERVLETS\COM\NOVELL\WEBACCESS\WebAccessServlet.class files. Are they dated 8/30/00 or later? How about the WEBACC.CFG, does it have the 6 lines needed to support HDML templates?
3. See if your GroupWise WebAccess seems to be able to dish out HDML. Here's a test to perform. From your computer's browser enter the following URL (subsituting your own Internet domain) NOTE: case is important, make sure that "U" in "User" is in uppercase.
Most browsers will prompt you to save file, because your browser cannot understand the file which is in HDML formatting. Some browsers will display a very simple screen with the following text:
User Id: Novell GroupWise
4. If you've proven that your WebAccess servlet is dishing out HDML from step 3 above, then it's time to use a Phone Emulator. Go to http://www.openwave.com. Go to the development pages, sign up to get developer access and download the PHONE.COM's cellphone emulator. Get the UP.
From the phone emulator. On the "GO" line, enter the URL: http://email.acme.com/servlet/webacc. If you can get your phone emulator to work, this isn't perfectly conclusive that you can use your cellphone to access GroupWise Wireless. With the phone emulator you are still not using the cellphone provider's HDML gateways.
If you can't get your phone emulator to work against your GroupWise WebAccess, do a test. See if it will work against the following HDML page:
If this does not work, then you are probably dealing with some kind of a proxy or firewall problem.
5. Does your server use SSL? Are you sure that your SSL certificate has not expired? Many Netscape Web Server's certificates expired on the last day of 1999. Your web browser will generally not catch this problem, but your cellphone provider's HDML gateway will. See the following URL, for more information:
6. Are you sure that your cellphone service provider supports the SSL certificate you are using? For instance, as of the writing of this document in September 2000, AT&T's Pocknet service only trusts Verisign certificates..