¿ÏÀü Ãʺ¸ Àä..
Ä¡¸¦ ´Ù Çߴµ¥ 6)¹ø °úÁ¤ Å×½ºÆ®½Ã apexec.pl ÆÄÀÏÀ» ÀÚ²Ù ´Ù¿î ¹Þ´Â âÀÌ ¶ß³×¿ä.7)µµ ¸¶Âù°¡ÁöÀ̱¸¿ä.
¼³Á¤µµ ´Ù ÇÑ °Í °°Àºµ¥.. ¾î¶»°Ô ÇØ¾ß ÇÏÁÒ? (¼³Á¤µµ ¼³¸í Á» ºÎŹµå·Á¿ä)
´ÙÀ½Àº ÀνºÅç °¡À̵å°í ¼Ò½º ¾ÐÃàÆÄÀÏ ¿Ã¸³´Ï´Ù. ±×·³ ºÎŹµå¸®°Ú½À´Ï´Ù.


1) Download and unzip the distribution file.

After extracting the zip file, you should find the following files inside:

license.txt - Software License Agreement

readmefree.txt - Basically a pointer to this online product documentation

aftemplate.html - Sample template file. Template files are HTML pages that have the <A!RESULTS> placeholder tag that Foundation replaces with the remote content results.

apexec.pl/apexec.cgi - The Foundation Exec file. The main "entry" file for all Foundation scripts. This is a perl script that invokes all the rest of the program files. This is the only file that needs the first line set to point to perl, correct file permissions set, and this is the file that all your URLs will point to. This file will should never need to be updated. Both .pl and .cgi versions are distributed. Some web servers require that cgi scripts end with .cgi, while others need them to end with .pl

apexecutive.apl - The Foundation Executive file. This is the shared common "guts" of the Foundation products.

ap_freesearch.apl module file.

2) Configure the apexec.pl/apexec.cgi file.

The first line must be correctly set to point to your perl executable. Under NT, this is usually unnecessary. The rest of the options in this file are described briefly in the file as comments. The most important setting to get things working is the "$ap_scriptpath" variable. This is usually fine as is, but if your web server doesn't execute CGI scripts with the current directory set to the cgi directory, it might need to be changed to a full system path, without a trailing "/" sign.

3) Upload the apexec.pl/apexec.cgi, apexecutive.apl, aftemplate.html and the ap_freesearch.apl file to your cgi-bin directory.

Make sure and use ascii mode in your FTP program to properly transfer these files.

4) Set the permissions on apexec.pl/apexec.cgi to 755.

CGI scripts need to have permissions set to 755. Most FTP programs allow you to change the file permissions. Under NT, you don't need to perform this step.

5) Create a directory called "apcache" under the script directory.

Set the permissions of this directory to 777. This is the directory that Foundation will store results in between requests for better performance.

6) Test the script install.

You can test the installation of the script files by loading this url:
http://yourdomain.com/cgi-bin/apexec.pl?command=version
Where yourdomain and cgi-bin are appropriate for your hosting situation, and apexec.pl is substituted with apexec.cgi if necessary. The page that loads should be headed with "Anaconda! Command Output", and should list 2 Anaconda modules and their respective versions and dates.


7) Test the script functionality.

You can test the functionality of the script files by loading this url:
http://yourdomain.com/cgi-bin/apexec.pl?etype=freesearch&search=????
Where yourdomain and cgi-bin are appropriate for your hosting situation, and apexec.pl is substituted with apexec.cgi if necessary. The search=??? should be replaced with the search terms you want to look for ("search=thailand" will do a search on thailand)


Direct Links

You can link to Foundation directly by putting hyperlinks into your pages that pass in hardcoded values for "etype" and "search".
http://yourdomain.com/cgi-bin/apexec.pl?etype=freesearch&search=eqypt
This url will do a search for sites on eqypt.

http://yourdomain.com/cgi-bin/apexec.pl?etype=freesearch&search=eqypt
This url will do a search for sites on eqypt.


Search Forms

You can also perform a search using a form.
<FORM ACTION="/cgi-bin/apexec.pl" METHOD="GET">
Search: <INPUT TYPE=TEXT NAME=search SIZE=20 VALUE="">
<INPUT TYPE=HIDDEN NAME=etype VALUE="freesearch">
<INPUT TYPE=SUBMIT VALUE="Search">
</form>


Templates:

A template is an html page that is used by Foundation to display the results of searches. Most people will want to use a page from their site as a template, in order to insert the search results directly into the site. This will give the impression of a totally integrated search, with the overall look and feel of your pages.
Note: Your template file needs to be named ending with .html, .htm, or .shtml for security reasons.


In order to configure a template, you need to 1) tell Foundation how to find the template, and 2) put the correct Anaconda results tags in the template as a placeholder.


Tell Foundation how to find the template:

Foundation can either load a template from a file, or it can fetch one using a URL. The URL method is convienent when a site is generated dynamically using another CGI process, ASP, Cold Fusion, etc. However, it does result in a second hit to the web server, so it should only be used if necessary.
There are many ways to tell Foundation what template file to use, only *one* of these methods is necessary:

Set $ap_parm{template} in apexec.pl to the name of your template file. Foundation will look in the script directory for the template file. You can also set $ap_parm{templatedir} if you want to place the template in a different place.

Set $ap_parm{templateurl} in apexec.pl - Foundation will fetch the template from this url using HTTP.

Pass in a template filename using a url variable. Passing this: "template=filename.html" sets the template, "templatedir" can also be passed in this way. You can use a hidden form input field if you have a search form pointing to Foundation.


Setting the search results location in the template:

You simply place one of the following tags in the template file, in the location where you want Foundation to insert the search results.
<A!RESULTS>
<ANACONDARESULTS>
(or the older)
<!-- ANACONDARESULTS -->