ControlAP Online Help

Pro

ControlAP Pro Architecture:

ControlAP Pro consists of a local hotspot gateway "ControlAP Plus" and a central authentication server that manges the local gateway as well as remote hotspots running ControlAP Pro. The authentication server also integrates billing with an external Internet Merchant (e.g. PayPal) and needs to be accessible tby the Internet merchant for payment notifications. Preferably a static IP or domain name or using a Dynamic IP service (e.g. no-ip.com).

Below are general configuration topics that will refer to the Hotspot Operator, for more details refer to:

The hotspot operator web based administration is available at:

https://[ip address]/hotspotadmin

Default username is admin default password is controlapadmin

--> ControlAP Pro Hotspot Operator Guide <--

For the local hotspot web administrator (as with all editions):
https://[ip address]:8090/admin (http for AP edition)

For help on basic network settings see help docs for the basic edition:
http://controlap.com/help

Configuring ControlAP Pro's Billing System:

www.paypal.com

payments.verisign.com

secure.authorize.net

Configuring to use a different database server:

To connect and use a different database, edit the configration files found in mediatracker/conf/mediatracker/localhost. See the 2 xml files there that include references to what to change to configure a different database driver.

Included example shows how to connect to a MySQL database:
Comment out (use ) the references to the existing database driver and database url and uncomment the lines referring to MySQL Also edit the username and password to access the database. The database name is specified in the url, database name is "hotspot". Create this database and give it a username/password. Tables will be created by ControlAP upon startup.

A driver for Microsoft SQL is included and drivers for Posgres SQL, Oracle, and most database servers are also available.
How to revert to ControlAP Standard or Plus:

ControlAP Administrator Advanced Properties

Web Authentication Server

Web Authentication Server Login check

ControlAP Plus Help

Advanced Topics:
- Setting up a custom SSL certificate for use with ControlAP
- Advanced Database Usage (generating custom reports):
- Special note when using with AP editions of ControlAP Plus (how to run on alternate port other than 443 (https) or add another port):
  The default port is 443 for SSL (https), if you'd like to also support port 80 or use a different http port, e.g. 81 (if already running a localhost hotspot it requires 80) than edit mediatracker/conf/server.xml and uncomment the section indicating http port. This is actually required for login check URL for ControlAP Plus running in the AP (Linksys). If running a local hotspot, then you have to use a port other than 80, e.g. 81 and add this to the login check url at the AP running Plus. the web auth URL (actual login URL users see) will still remain as port 443 unless you do not wish to use https.
- Supporting Additional Merchants
  (web based instant notifcation Internet merchants only):

payments.verisign.com

secure.authorize.net.

response

approved

amount

(

)

Customizing pages separately for each remote hotspot:

As each unique remote hotspot running ControlAP Plus connects to ControlAP Pro, the unique 5 digit hotspot id (the default is 97010 which is the universal code using the default look and feel), the default pages are copied at run time by ControlAP Pro in the hotspot folder to create seperate pages for each hotspot based on the hotspot id. e.g. index.jsp gets copied to index12345.jsp. The general look and feel (namely, header/title, message, logo) can be all customized from the hotspot operator web inteface for each hotspot entered into the database using the hotspot operator. If any additional manual editing of the pages is desired, than you can also do that by editing the individual pages generated, e.g. editing index12345.jsp for hotspot id 12345.

As with manually editing all web pages, *.jsp pages, take care to not edit code using the <% %> tags as these are used for navigation and centralized customization unless you really have to or do not desire to use the hotspot operator for customizing the web pages. These jsp pages (Java Server Pages) can be edited in editors such as DreamWeaver that acknowledge jsp tags.