Distributing Your Application: 4 Setting Up a Web Server

To make Nokia 9000i Communicator software packages available on a web site, the web site administrator will do some set-up work so that the server knows how to tag Add-On Software files. Each software package must be bundled up into an Add-On Software file--a special kind of archive.

Standard Add-On Software files will have a . AOS suffix, and should be identified by the MIME-type application/x-nokia-9000-communicator-add-on-software . Exactly how this is set up depends upon your server software. NCSA's httpd daemon may use a file called mime.types , to which you would add a line reading

			application/x-nokia-9000-communicator-add-on-software 							aos

Once the server has been set up correctly, each software package needs to be bundled up into an Add-On Software file.

Pack the package descriptor file and all files in the software package into one tar archive file. (This is done using the tar program. Tar is a standard Unix program; there is a public domain DOS tar program. The host-file-location lines in the package description file should describe locations within the tar file's directory structure.) The . INS file must be in the top level directory of the tar file so that it may be found. Read your tar documentation to find out how to create the archive. An appropriate invocation for one version of tar might be:

tar cvf santa2.aos santa2.ins santa2/santa2.geo

Give the tar file's filename the suffix . AOS so that it will be recognized as an Add-On Software file.
Put the file up on your web server.

Users of the Nokia 9000i Communicator using the WWW built-in application will be able to use WWW to install the software package from your site. The WWW program will download the Add-On Software file, extract the files from the archive, and put them into the proper directories as directed by the package description file.

GEOS SDK TechDocs |

3 Setting Up a PC Server