This section provides information for helping .NET client mobile device users set up to use Unwired Accelerator. Use Mobile Web Studio to set up an account for each user, and supply the following information to the user:
Location of downloads – each user must install the .NET Compact Framework, ASA for CE, and Unwired Accelerator .NET client on his or her mobile device. Develop a process for making the version and location information available to users.
User Name – the user name for the profile,
such as masuper.
Password – the password for the profile,
such as m8super.
Server – the server and domain on which
the Unwired Accelerator server is running, such as lab2k.sybase.com.
Port – the port used to access the Unwired
Accelerator server, such as 4040.
RID – the default resource identifier (RID)
for the account, such as 21 for Unwired
Accelerator.
Each user must install the following software on a Windows mobile PDA:
.NET Compact Framework
ASA for Windows CE
Unwired Accelerator 7.0 .NET client
Install the .NET Compact Framework 1.0 Service Pack 3 on your device. You may want check to see whether the required .NET Compact Framework is already installed. If it is not installed, download the Service Pack from the Microsoft Web site and install it.
Checking the .NET Compact Framework version
In this step, verify the Service Pack installed on your mobile device. Skip this procedure if you already know you need to install .NET Compact Framework 1.0 SP3 on your device.
Open the File Explorer application on the device.
Browse to the \Windows folder.
Locate and click once on the file cgacutil. If there is no cgacutil file, the .NET Compact Framework is not installed.
A pop-up window displays the version number of the installed .NET Compact Framework. Use the information below to determine which version or versions of the .NET Compact Framework is installed.
Version number |
Software version |
|---|---|
1.0.2268.0 |
.NET Compact Framework 1.0 RTM |
1.0.3111.0 |
.NET Compact Framework 1.0 SP1 |
1.0.3226.0 |
.NET Compact Framework 1.0 SP2 Recall |
1.0.3227.0 |
.NET Compact Framework 1.0 SP2 Beta |
1.0.3316.0 |
.NET Compact Framework 1.0 SP2 Final |
1.0.4177.0 |
.NET Compact Framework 1.0 SP3 Beta |
1.0.4292.0 |
.NET Compact Framework 1.0 SP3 |
2.0.4037.0 |
.NET Compact Framework 2.0 (part of VS2005 CTP May) |
2.0.4135.0 |
.NET Compact Framework 2.0 (part of VS2005 Beta 1) |
2.0.4317.0 |
.NET Compact Framework 2.0 (part of VS2005 CTP November) |
2.0.4278.0 |
.NET Compact Framework 2.0 (part of VS2005 CTP December) |
2.0.5056.0 |
.NET Compact Framework 2.0 (BETA 2) |
2.0.5238.0 |
.NET Compact Framework 2.0 Release |
If you do not see version 1.0.4292.0 or higher, install .NET Compact Framework Service Pack 3.
You may see multiple version numbers in the pop-up window, meaning
that multiple CFs are installed, such as CF 1 and CF 2. This is acceptable,
as long as 1.0.4292.0, the version number for .NET Compact Framework
1 Service Pack 3, is included in the list of installed versions.
Downloading .NET Compact Framework Service Pack
3
In this step, download the Service Pack from the Microsoft download Web site to your PC. Skip this procedure if .NET Compact Framework SP3 is installed on your mobile device.
Navigate to:
http://www.microsoft.com/downloads/details.aspx
?FamilyId=A5A02311-194B-4C00-B445-F92BEC03032F&
displaylang=en
Review the download instructions on the Microsoft Web site.
Download the Service Pack to your PC, according to the instructions.
Installing .NET Compact Framework Service Pack
3
In this step, download the Service Pack from your PC to your mobile device, and install the Service Pack on the mobile device. Skip this procedure if .NET Compact Framework SP3 is installed on your mobile device.
Use ActiveSync to connect your mobile device to your PC.
On your PC, with your mobile device connected, run the Service Pack installer. The installer detects your device operating system, copies the appropriate configuration file to your device, and installs it.
If the device already has this version of the .NET Compact Framework installed, this prompt displays:
Microsoft .NET Compact Framework is already installed. Reinstall?
Click Cancel and proceed to “Installing ASA for Windows CE” to install the database. Or, click OK to reinstall.
If you continue with the installation, and if a memory card is plugged into your mobile device, you may be prompted to select the installation destination for the .NET Compact Framework.
Select the device memory as the installation destination,
not the memory card.
Install the Adaptive Server Anywhere for Windows CE (ASA for CE) database on your mobile device. The database is used for persistent storage of system and mobile application data.
The CABinet (CAB) file for ASA for CE is located in:
$SYBASE/tomcat/webapps/onepage/PocketPC
If you cannot access the Unwired Accelerator file system, or if you are WiFi-enabled, you can obtain the CAB file at:
http://hostname.domain:port/onepage/PocketPC/
To install a CAB file into any folder other than the
default destination, use a CAB file installer, such as the freeware
tool CabInstl, that allows you to browse for a CAB file, then select
where to install it.
CabInstl is available from http://s-k-tools.com/util.html (or go directly to http://s-k-tools.com/freeware/cabinstl.zip to obtain the downloadable zip file). The zip file includes three versions of the tool—English, German, and Russian. Other similar tools are available on the Internet.
If you are using CabInstl, manually create the folders to which you want to extract the CAB file content, before you unpackage the CAB file.
Installing ASA for CE
In this step, install ASA for CE on your mobile device. Since the CAB file is quite large (about 9MB), you may want to use ActiveSync to copy the file from Unwired Accelerator to the mobile device. Skip this procedure if ASA for CE is already installed on your device.
Use ActiveSync to connect your mobile device to your PC.
Use File Explorer to navigate to $SYBASE/tomcat/webapps/onepage/PocketPC.
Explore the mobile device and copy the asa_ce.ARM.30.CAB file to the device.
Use File Explorer on the device to browse to where you placed the asa_ce.ARM.30.CAB file.
Tap on asa_ce.ARM.30.CAB once to start the installation.
If you have a memory card plugged into the device, you may be prompted to install the database to the device or the memory card. Optimally, select the device memory as the installation destination for faster runtime performance.
However, if your device is running low on storage space, you can select the memory card.
On Windows Mobile 2003 devices, create the destination
folder on the memory card, \Storage Card\Program
Files\Sybase\ASA9, then use the CAB
installer to extract the files into this folder.
On Windows Mobile 5, the operating system is designed to create the destination folder automatically.
In this step, install the Unwired Accelerator .NET client on your mobile device. The client is used to synchronize with the Unwired Accelerator server.
Installing the .NET client
Use ActiveSync to connect your mobile device to your PC.
Use File Explorer to navigate to $SYBASE/tomcat/webapps/onepage/PocketPC.
Copy the UnwiredAcceleratorClient_PPC.ARMV4.CAB file to the mobile device.
Use File Explorer on the device to browse to where you placed the UnwiredAcceleratorClient_PPC.ARMV4.CAB file.
Tap on UnwiredAcceleratorClient_PPC.ARMV4.CAB once to start the installation.
If you have a memory card plugged into the device, you may be prompted to install the database to the device or the memory card. Sybase recommends that you install to device memory for optimal runtime performance.
If you do install to memory card, performance will be
very slow, since the .NET client frequently accesses the ASA database,
and file access on the memory card is slower than file access on
the main device memory.
To install to a memory card on Windows Mobile 2003 devices, create the destination folder on the memory card, \Storage Card\Program Files\Sybase\ASA9, and then use the CAB installer to extract the files into this folder.
On Windows Mobile 5, the operating system is designed to create the destination folder automatically.
