Deploying on a Target Device
Applications are delivered to target hardware in the form of a Symbian Installation System (.sis) file. A .sis file is a single compressed archive file, containing all of the files required for installation, plus optional information about the installation process. The Symbian Installation System provides a simple and consistent user interface for installing applications, data or configuration information onto devices based on Symbian OS. Developers (or end users) install components, packaged in .sis files.
Production of .sis files can be performed using the interactive sisar tool provided with the Series 60 SDK. Sisar packages all the application files into one .sis file for ease of installation onto target hardware. Alternative methods for producing installation files are described in Chapter 2.
Everything required to make an installation (.sis) file is provided with the example HelloWorld projectunder the \install folder. In this example project we will use a special installation package source file called HelloWorld.pkg and a tool from Symbian called makesis.exe.
Building a SIS Install File
After building the armi release version of the HelloWorld application, as described above, you need to package up the application components into an installation package (.sis) file. Open a command prompt and navigate to the SDK folder for the HelloWorld project. Change to the \install folder, then build the .sis file by typing:
A successful build will produce an output message such as "Created helloworld.sis". The installation package (.sis) file will have been created in the \install folder. Now you need to transfer it to the device, as described in the next section.
SIS File Installation
You may choose among three potential installation options, depending on the device you are using, and other facilities available to youfor example, whether you have access to a PC with infrared or Bluetooth capability, or access to appropriate software based on Symbian Connect (Nokia PC Suite, for example, or a branded equivalent provided by the device manufacturer):
Installation through the invocation of a .sis file located on a PC, with subsequent application installation on to the Series 60 device through an infrared or Bluetooth session between the PC and the target device, established via software such as Symbian Connect.
Installation by transfer of a .sis file through OBEX (OBject EXchange), over infrared or Bluetooth, from another device such as a PC, Symbian OS phone or any OBEX-enabled device. This process will be managed via the Messaging application, which intercepts the file attached to the messagewhen you open up the message, it will automatically start the application installation process on the phone.
Alternatively, .sis files can be sent as email attachments. Application installation is again managed via the Messaging application on the phone. When you open the message, it will automatically start the installer.
The first two options depend on establishing a connection between your development PC and the Series 60 device. The device manufacturer typically supplies suitable communications software, and you will need to refer to the specific instructions supplied with the connection software.
After installation a much-reduced version of the .sis file remains on the Series 60 device to control the uninstallation of the application, if required, using the application "Manager." This reduced .sis file contains only the information required to uninstall the application and is typically very much smaller than the original file.
Often the original .sis file may still exist on the device, if it was delivered as a message attachment and the original message has not been deleted from the Messaging application's Inbox folder.
Running on a Target Device
Transfer the helloworld.sis file provided to the target hardware, using one of the methods described above. After the transfer you will be offered the chance to install the application on the device. To run the application follow the procedure outlined in "Locating and Running the Application" earlier in this chapter. You will be reassured to find that locating and running the application on a target device is identical to the process on the emulatorwith one small difference: the application will not be located in an "Other" folder.