Nearcode

 

Example Name:                              ncdxml_js.htm

 

Language:                                       HTML & Javascript

 

API type:                                           XML CGI

 

API component filename:            mcxquery.exe

 

Environment:                                  Internet Explorer

 

 

What does it do?

 

Demonstrates calling the XML version of the CGI client and processing the resulting XML using javascript. The page is dynamically updated to display the results.

For an ambiguous results, it displays a clickable list of place names. Clicking one submits another search with the qualified place name as input.

For a successful results, it displays a  clickable list of nearest locations. Clicking one shows the location on a map.

 

This example is designed to work with the Nearcode Libraries pool.

 

 

Could be used as a starting point for:

 

Store Finder website showing a list of nearest stores.

The use of XML means this could be part of an AJAX solution.

 

 

Where to find the example code:

 

After running the setup from the Nearcode CD to install the client APIs you will find these examples installed (by default) in:

 

C:\Program Files\Capscan\SDK\Nearcode Client API\CGI\Examples

 

If you have installed to another location you will need to change the path where necessary.

 

 

What each file does:

 

File name                                         What does it do?

 

ncdxml_js.htm                                    Prompt for a query to submit to mcxquery.exe. Updates the page with the results.

 

 

Preparing to run the example:

 

Please make sure that you have installed the Capscan Pool Manager and that it is up and running.

 

 

Running the example:

 

1.       Make sure mcxquery.exe is in cgi-bin.

 

2.       Make sure the Libraries pool is set in the local spider.ini file.

 

3.       Copy ncdxml_js.htm to the document root folder of the web server (wwwroot in IIS).

 

4.       Open a web browser and enter http://themachinename/ncdxml_js.htm.  Where “themachinename” is the name of the machine that has the HTML page in its document root.

 

 

Trouble-shooting and hints:

 

1.       If you are running on a LAN make sure that the Capscan Pool Manager is running correctly.  To do this you can use the Pool Manager Admin application that is installed along with the Capscan Pool Manager.

 

2.       If you are using a firewall make sure that it is not blocking this example or the Capscan Pool Manager.  By default the Capscan Client/Server uses port 27920 for sending and receiving data.

 

3.       For more hints and tips please see the SDK bookshelf documentation.