|
Prior to installation of webace you
should have installed perl5.005 or later, CGI.pm (should come as a part of perl
package), GD.pm
and a WWW server (such as apache). Installation of webace requires 3 components:
gifaceserver, Aceclient and webace itself. The first will
not need to be done each time and the second may only
need doing once:
 gifaceserver |
You must be running the current
gifaceserver on your acedb database. Download binary for
your architecture from directory
ftp://ftp.sanger.ac.uk/pub/webace/gifaceserver
and replace your current
binary if you are running an out of date version.
See http://webace.sanger.ac.uk/webace/setup.html for instructions on setting up the server if
you are using an aceserver for the first time.
| Aceclient |
Aceclient needs to be installed into
your copy of perl. Download from
ftp://ftp.sanger.ac.uk/pub/webace/aceclient
and follow install instructions. This
probably only needs to be done once.
| webace |
If you ever had webace installed you
will notice the difference:
- all cgi scripts
go to cgi-bin/WebAce directory on your web
server, not strait into cgi-bin as it used to be.
- webace release
contains two different files: webace_cgi.tar and webace_htdocs.tar.gz
- webace cache
directory doesn't have to be in htdocs anymore.
To install webace :
- Download webace_cgi.tar.gz and webace_htdocs.tar.gz from
http://www.graingenes.org/Webace2K/
- Move
webace_cgi.tar.gz into web server cgi-bin directory (for
example /export/home/WWWserver/cgi-bin), unzip and untar it.
gzip -d
-c webace_cgi.tar.gz | tar xvf -
- You will find new
directory WebAce in cgi-bin. All cgi webace scripts
are located in this WebAce directory.
- Move webace_htdocs.tar.gz into webserver htdocs directory (/export/home/WWWserver/htdocs),
gzip -d
-c webace_htdocs.tar.gz | tar xvf -
- New htdocs/webace directory will appear.
This directory contains html help files and
several Java and JavaScript files.
Now you've got
everything and it's time for the configuration part.
To configure webace:
- Register you AceDB
database in cgi-bin/WebAce/acelib/dbinfo. You must supply
following information about your database:
- database
name - name of a database how you want it
to be appear in webace header.
- server IP
- your web server IP address
- port -
port which is used by gifaceserver
- data
directory - absolute path to a database
acedb directory
- homepage
URL - your database home page URL
- cache
directory - absolute path to a directory
(which you have to create first) where
webace will write cache files.
- Make changes in cgi-bin/WebAce/acelib/hostinfo.pl file.
The main configuration
part is done.
Now what you can do:
- to
create custom "main" webace
page
You can write two
files: body1.html and body2.html and put them into the
database wspec
directory.
These files replace everything before layout
table and after
Wildcards. For more
explanation see file examples.
- if
you don't see layout table on
the "main" webace page
If there is no
layout table on the main webace page it means you
have to create wspec/layout.wrm.
|