Information Technology

Requirements

aMapApp3 has been designed and tested on a Linux system running the Apache web server only.

To add aMapApp3 to a web page you will need the following,

A basic understanding of creating html pages and specifically how to create and locate div tags on a page.

A basic understanding of paths on your server.  In particular, the you need to be able to construct relative paths between different locations on the server.

At least a minimal knowledge for how to write javascript.  This knowledge does not need to be very deep as most of the requirements will be illustrated on these pages.  However, you must be sufficiently acquainted with html page creation and scripting to be able to duplicate the examples.  If you need to add local modifications, your level of knowledge of either javascript or php or both will be higher.

Access to a database.  The aMapApp3 supports mySQL (http://dev.mysql.com/) and sqlite3 (http://www.sqlite.org/).  Check with your system administrator about what you have available and/or can have installed. If using mySQL, the mySQL server does not have to be on the same machine. Other databases are possible but they may require more coding.  We can make no definitive statements about how easily it would be use other databases.  We worked primarily with mySQL 5.0.8.  You should never need to access the database manually – aMapApp3 should handle all the database interfacing.

Access to xajax code (http://xajaxproject.org/) and the EXTjs library (http://www.extjs.com/). These are both available as free downloads for non-commerical use. Check the websites for usage limitations and rules.  Installation is relatively simple, but consult your system administrator.  Depending on where your administrator want to put them, they may have to do the install.  We recommend putting both somewhere that is accessible to any future application that may want to use them rather than hiding them away in personal web space. You will need to know where on the server they are located.  Most recently, aMapApp3  was written and tested with EXTjs version 3.3.1, but ran successfully with 3.0.3 and 2.2. Warning: we're currently have some problems with 3.3.1.  We think this is a problem with our installation of 3.3.1 but using 3.0.3 may be safer. It will not run with the version 4.  Version 3 is available at http://www.sencha.com/learn/legacy/Ext_Version_Archives. We developed and tested with version 0.5 of xajax.

A license key for Google Maps.  This is available at http://code.google.com/apis/maps/signup.html.   There are restrictions on the use of the free license and it is your responsibility to make sure that your use of Google maps meets the requirements. 

Php version 5 or better.  We haven’t tested with anything below 5.  Your system administrator may need to o install or upgrade your php version. Important: To upload large files, such as video files, your php must be configured properly.  Specifically, the upload_max_filesize and post_max_size values must be large enough for the largest file you will want to upload. Check with your systems administrator on the current settings of their values and on having them increased if necessary. Alternatively, you can set these values in a .htaccess file.  See the section on Searching Disks for more information.

The image viewer function requires that ImageMagick be installed on the server.  This is run as a system level command and does not need to be added to the php installation. ImageMagick is available at http://www.imagemagick.org/script/index.php.  If it isn't already installed on your server, see your system administrator.

You may need access to both aLogin2 and aBlog2 if you are going to use either the default authentication system or allow for any blogging.  If you aren't using aLogin2 you'll need to provide to modify some provided functions to hook into another authentication scheme.  See the section on authentication for more details.   If you aren't using the blogging features or anything from aLogin2, you don't need to have either installed on your system. You will not need to run the normal aLogin2 and aBlog2 setup since this is done automatically when you setup aMapApp3.  If using, you will need to know where they are located on your server.

Public and Private keys to the Recaptcha system for preventing robot account creation.  These are available at http://recaptcha.net/.  These wouldn't be needed if you don't use the new account creation feature contained in aLogin2 or if you are not concerned about preventing robot account creation.

Ability of create new directories on you server with the correct permissions.  What permissions you'll need will depend on what you are trying to do and how your server is setup.  You may need to work with the systems administrator on this, but the actions required are fairly simple.  aMapApp3 causes some files to be created when run so it must have permission to write into the appropriate locations and the directory that will contain the web application must exist.  See the section on Setup for more information.