| Red Hat Docs > Manuals > Red Hat Applications > |
|
Before installing WAF, several other pieces of software need to be installed and configured.
JDK 1.3.1 — on Linux, the IBM JDK is recommended and is available online at:
http://www.ibm.com/developerworks/java/jdk |
A RDBMS, either:
Oracle 8i or 9i, Standard Edition
Oracle 9.0.1 — installation instructions for Linux are available online at:
http://otn.oracle.com/docs/products/oracle9i/doc_library/901_doc/A90352-02/html/toc.htm |
Note, you must be a registered user to access this information:
http://technet.oracle.com |
At a minimum, you will need the Oracle client libraries (for UNIX, this option is available during installation; on MS Windows® it is called the Oracle Windows Client) if you are connecting to a remote Oracle installation. If you do not have an Oracle installation, you will need to install the Oracle database as well.
PostgreSQL 7.2.2 or later, available online at:
http://www.postgresql.org |
Additionally, you will need the the PostgreSQL JDBC driver, available online at:
http://jdbc.postgresql.org/ |
We recommend using Red Hat Database, v2.0, which can be reviewed online at
http://www.redhat.com/software/database/ |
and is available for download online at:
http://www.redhat.com/apps/download |
A Servlet container that supports Servlet 2.3, such as Apache Tomcat 4.x, available online at
http://jakarta.apache.org/tomcat/ |
or Resin 2.1.x, which is available at:
http://www.caucho.com |
If you intend on developing with WAF, you will also need:
Ant 1.5, available at:
http://jakarta.apache.org/ant/ |
JUnit 3.8, a regression testing framework, available at:
http://www.junit.org |
RPMs for JUnit are available online at:
http://www.jpackage.org |
Web Application Framework needs a valid Oracle username and password during an Oracle installation in order to install and run properly. The user should have full privileges on its schema, which can be spread across one or more tablespaces. In addition, make sure your version of Oracle is configured as follows:
UTF-8 character set
Minimum 8KB db blocksize
Intermedia, if you need full-text search capabilities
Although you can install the WAF with the Oracle Thin driver, there are some known issues with the way Oracle's thin driver handles LOBs. It is highly recommended to use the OCI driver instead.
Most likely, the Oracle JDBC driver will be already in place at:
${ORACLE_HOME}/jdbc/lib/classes12.zip |
This is also the default value offered by the installation program when configuring the location of the Oracle JDBC driver, assuming that at least the Oracle client library is available and that ORACLE_HOME is set accordingly. If this file does not exist, you must install it. You can download the Solaris drivers from http://technet.oracle.com; the classes12.zip included with the Solaris drivers works on Linux as well.
The OCI driver depends on native Oracle client libraries which must be properly set via LD_LIBRARY_PATH.
Make sure that the user running the servlet conatiner has read access to the Oracle JDBC driver and client libraries.
To get the Thin JDBC driver to work, the target Oracle machine (for example, the one you are connecting to) must have its listener enabled for TCP connections, even if the WAF and Oracle installations are on the same host. If the OCI driver is an option (see above), you could use the OCI driver to eliminate the need for the TCP listener.
Install the Oracle 9i client according to the instructions provided by Oracle. Also see the Oracle 9i installation hints for Red Hat Linux 7.2 online at:
http://www.idevelopment.info/data/DBA_tips/DBATIP_53.shtml |
A number of the commands for installation and day-to-day development assume that the Oracle environment has been setup for all users on the machine. This can be trivially accomplished by creating the file /etc/profile.d/oracle.sh as follows (you will need to correct the paths to match your local installation):
export ORACLE_HOME=/u00/app/oracle/product/9.0.1
export NLS_LANG='AMERICAN_AMERICA.UTF8'
export PATH=$PATH:$ORACLE_HOME/bin
if [ -z $LD_LIBRARY_PATH ]
then
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib
else
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib
fi |
 | Note |
|---|---|
If you are connecting to a local Oracle instance and you are not connecting via the listener, you must make sure ORACLE_SID is set in your environment as well. Normally this happens automatically during installation. |