92prodapache.htm

Debian中文参考手册,系统介绍了Debian系统

</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="TB-TblBody">
<A NAME="pgfId-766204"></A>mod_usertrack</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="TB-TblBody">
<A NAME="pgfId-766206"></A>User tracking using Cookies.</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="TB-TblBody">
<A NAME="pgfId-766208"></A>mod_vhost_alias </P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="TB-TblBody">
<A NAME="pgfId-766210"></A>Support for dynamically configured mass virtual hosting.</P>
</TD>
</TR>
</TABLE>
<P CLASS="BP-Body">
<A NAME="pgfId-764390"></A>Any other Oracle Apache Modules that are included in Oracle HTTP Server are provided &quot;as is&quot; without warranty or support of any kind.  Apache Modules from any source other than Oracle, including the Apache Software Foundation or a customer, will not be supported by Oracle.</P>
<P CLASS="BP-Body">
<A NAME="pgfId-764391"></A>In addition, Oracle will only provide technical support for problems that can be reproduced with an Apache configuration consisting only of supported Oracle Apache Modules.</P>
</DIV>
<DIV>
<H3 CLASS="H2-Head2">
<A NAME="pgfId-764393"></A>7.1 Building mod_perl DBI/DBD-Oracle and Apache::DBI</H3>
<P CLASS="BP-Body">
<A NAME="pgfId-764394"></A>To build, install, and test mod_Perl DBI/DBD-Oracle and Apache::DBI for the Solaris platform, follow these steps:</P>
<ol CLASS="LN1" TYPE="1">
<li CLASS="LN1" TYPE="1" VALUE="1">
<a NAME="764395"></a>Verify that the following software is available in
your environment:</li>
<dd CLASS="LSI">
<a NAME="764396"></a>C compiler Sun SparcWorks version 5.0</dd>
<dd CLASS="LSI">
<a NAME="766532"></a>GNU Make GNU Make version 3.77</dd>
<dd CLASS="LSI">
<a NAME="766533"></a>Perl Perl version 5.005_03</dd>
<li CLASS="LN1" TYPE="1" VALUE="2">
<a NAME="764397"></a>Verify that your PATH environment variable is set
correctly to locate the required software.</li>
<li CLASS="LN1" TYPE="1" VALUE="3">
<a NAME="764401"></a>Install Oracle HTTP Server from your product CD. This
version has mod_perl 1.2.4 built in. However, this install does not include
the following modules:</li>
<dd CLASS="LSI">
<a NAME="764402"></a>Apache::DBI</dd>
<dd CLASS="LSI">
<a NAME="766523"></a>Perl DBI</dd>
<dd CLASS="LSI">
<a NAME="766524"></a>Perl DBD-Oracle</dd>
<li CLASS="LN1" TYPE="1" VALUE="4">
<a NAME="764406"></a>Create a symbolic link from your Oracle HTTP Server
Apache install directory to /usr/local/apache. For example:</li>
<pre CLASS="CE1"><a NAME="764407"></a>prompt> ln -s /private1/ORA1/Apache /usr/local/apache
<a NAME="764408"></a></pre>
<li CLASS="LN1" TYPE="1" VALUE="5">
<a NAME="764409"></a>Set your PATH environment variable to pick up the
correct Perl binaries. For example:</li>
<pre CLASS="CE1"><a NAME="764410"></a>prompt> setenv ORACLE_HOME /private1/ORA1
<a NAME="764411"></a>prompt> setenv PATH ${ORACLE_HOME}/Apache/perl/bin:${PATH}
<a NAME="764412"></a></pre>
<a NAME="764413"></a>
<p CLASS="BP1">Note: There are other methods, which include setting the
<br>LD_LIBRARY_PATH and PERL5LIB environment variables, that make mod_perl
DBI/DBD-Oracle work. The scope of these steps is limited to one method
that has been tested and verified by Oracle.
<li CLASS="LN1" TYPE="1" VALUE="6">

<a NAME="764414"></a>Download the following modules from http://www.cpan.org/modules/by-module:</li>
<p>
<p CLASS="BP1">DBI version 1.15
<p CLASS="BP1">DBD-Oracle version 1.0.6
<p CLASS="BP1">Apache::DBI version 0.87
<li CLASS="LN1" TYPE="1" VALUE="7">
<a NAME="764416"></a>Unpack the DBI package and follow the README instructions
carefully to build, test, and install the module.</li>
<li CLASS="LN1" TYPE="1" VALUE="8">
<a NAME="764417"></a>The DBD-Oracle module expects enough Oracle software
available (such as $ORACLE_HOME/lib, $ORACLE_HOME/rdbms/lib, etc.) to build
the driver successfully. Make sure that the following information is available
in your environment:</li>
<ol CLASS="LA2" TYPE="a">
<li CLASS="LA2" TYPE="a" VALUE="1">
<a NAME="764418"></a>Set the ORACLE_HOME environment variable to point
to a valid Oracle HTTP Server install or an Oracle database install (for
example, 8.1.6, 8.1.7, etc.).</li>
<li CLASS="LA2" TYPE="a">
<a NAME="764422"></a>Set the ORACLE_SID environment variable to point to
a valid Oracle SID.</li>
<li CLASS="LA2" TYPE="a">
<a NAME="764423"></a>Verify that the LD_LIBRARY_PATH environment variable
points to the libclntsh.so. This can be done by setting $ORACLE_HOME/lib
in the LD_LIBRARY_PATH environment variable.</li>
<li CLASS="LA2" TYPE="a">
<a NAME="764424"></a>If you are using National Language Support (NLS),
make sure that you set the ORA_NLS and ORA_NLS33 environment variables
to avoid ORA-01019 errors.</li>
<li CLASS="LA2" TYPE="a">
<a NAME="764425"></a>Optionally set the ORACLE_USERID environment variable
(the tests will use scott/tiger by default).</li>
<p>&nbsp;</ol>
<li CLASS="LN1" TYPE="1" VALUE="9">
<a NAME="764426"></a>Unpack the DBD-Oracle package and follow the README
instructions carefully to build, test, and install the module.</li>
<li CLASS="LN1" TYPE="1" VALUE="10">
<a NAME="764427"></a>Unpack the Apache::DBI package and follow the README
instructions carefully to build and install the module. There are no tests
available for this module yet. This step will install the Apache AuthDBI.pm
and DBI.pm modules.</li>
<li CLASS="LN1" TYPE="1" VALUE="11">
<a NAME="764428"></a>Edit $ORACLE_HOME/Apache/Apache/conf/httpd.conf as
follows:</li>
<p>
<p CLASS="BP1">Uncomment the following line (remove the pound sign that
is prepended):
<pre CLASS="CE1"><a NAME="764430"></a>PerlModule Apache::DBI
<a NAME="764431"></a></pre>
<a NAME="764432"></a>
<p CLASS="BP1">This allows the use of Apache::DBI's persistent database
connections. For more information, read the Apache::DBI README instructions,
specifically the section on Examples.
<br><a NAME="764433"></a>
<p CLASS="BP1">Note: httpd.conf is the main Apache server configuration
file. Be sure to understand the instructions at the beginning of this file.

<li CLASS="LN1" TYPE="1" VALUE="12">
<a NAME="764434"></a>Now you are ready to test your persistent connection.
As an example, perform the following to test the connection via your startup.pl:</li>
<ol CLASS="LA2" TYPE="a">
<li CLASS="LA2" TYPE="a" VALUE="1">
<a NAME="764435"></a>Add this line to your httpd.conf file:</li>
<pre CLASS="CE2"><a NAME="764436"></a>PerlRequire &lt;absolute path to ApacheDBI's startup.pl script>
<a NAME="764437"></a></pre>
<li CLASS="LA2" TYPE="a">
<a NAME="764438"></a>Modify the startup.pl connect call, such as:</li>
<pre CLASS="CE2"><a NAME="764439"></a>Apache::DBI->connect_on_init('dbi:Oracle:',"scott/tiger", '');
<a NAME="764440"></a></pre>
<li CLASS="LA2" TYPE="a">
<a NAME="764441"></a>Restart your Oracle HTTP Server:</li>
<pre CLASS="CE2"><a NAME="764442"></a><tt>prompt> $ORACLE_HOME/Apache/Apache/bin/apachectl </tt>stop
<a NAME="764443"></a><tt>prompt> $ORACLE_HOME/Apache/Apache/bin/apachectl start</tt>
<a NAME="764444"></a></pre>
<li CLASS="LA2" TYPE="a">
<a NAME="764445"></a>Check Oracle HTTP Server logs to verify that connections
were obtained correctly.</li>
<p>&nbsp;</ol>
<a NAME="764446"></a>
<p CLASS="BP1">Tip: If Oracle HTTP Server logs report that the ORACLE_HOME
environment variable is not set, try adding this line to your httpd.conf
file:
<pre CLASS="CE1"><a NAME="764447"></a>PerlSetEnv ORACLE_HOME "&lt;absolute path to Oracle Home>"
<a NAME="764448"></a></pre>
<a NAME="764449"></a>
<p CLASS="BP1">Another sample Perl script to test the connection is:
<pre CLASS="CE1"><a NAME="764450"></a>##### Perl script start ######
<a NAME="764451"></a>use DBI;
<a NAME="766554"></a>print "Content-type: text/plain\n\n";
<a NAME="764452"></a>$dbh = DBI->connect("dbi:Oracle:", "scott/tiger", "") ||die&nbsp;
$DBI::errstr;
<a NAME="764453"></a>$stmt = $dbh->prepare("select * from emp order by empno")|| die&nbsp;
$DBI::errstr;
<a NAME="764454"></a>$rc = $stmt->execute() || die $DBI::errstr;
<a NAME="764455"></a>while (($empno, $name) = $stmt->fetchrow()) { print "$empno
<a NAME="764456"></a>$name\n"; }
<a NAME="764457"></a>warn $DBI::errstr if $DBI::err;
<a NAME="764458"></a>die "fetch error: " . $DBI::errstr if $DBI::err;
<a NAME="764459"></a>$stmt->finish() || die "can't close cursor";
<a NAME="764460"></a>$dbh->disconnect() || die "cant't log off Oracle";
<a NAME="764461"></a> ##### Perl script End ######</pre>
</ol>


<H3 CLASS="H2-Head2">
<A NAME="pgfId-764462"></A>7.2 mod_plsql Requirement</H3>
<P CLASS="BP-Body">
<A NAME="pgfId-764463"></A>To use the mod_plsql module against a given back-end database, you need to manually install the Oracle PL/SQL Web ToolKit (OWA PL/SQL packages) on the back-end database. The OWA PL/SQL packages should be installed into the SYS database schema; make sure that you have only one installation of the OWA PL/SQL packages. Note that existing Oracle Application Server (OAS) customers upgrading to the Oracle HTTP Server have an older version of these packages that must be replaced. </P>
<P CLASS="BP-Body">
<A NAME="pgfId-764469"></A>For more information, see Using the PL/SQL Gateway in the Oracle HTTP Server Documentation Library. Or, you can access the online documentation available at http://hostname.domain:port/pls/admin_/title.htm.</P>
</DIV>
<DIV>
<H3 CLASS="H2-Head2">
<A NAME="pgfId-764471"></A>7.3 Restoring Oracle Application Server OWA Packages</H3>
<p CLASS="BP">When you install the new mod_plsql OWA packages, it places
them in the SYS database schema. This can create problems with Oracle Application
Server applications using the PL/SQL cartridge. If you experience these
problems and want to continue to use your Oracle Application Server PL/SQL
cartridge applications, you must recreate the synonyms that reference the
Oracle Application Server OWA packages.
<br><a NAME="764473"></a>
<p CLASS="BP">To create these synonyms on the origin database machine:
<ol CLASS="LN1" TYPE="1">
<li CLASS="LN1" TYPE="1" VALUE="1">
<a NAME="764474"></a>Connect to the origin database as the SYS user in
SQL*Plus.</li>
<li CLASS="LN1" TYPE="1" VALUE="2">
<a NAME="764475"></a>Run the following commands in SQL*Plus. This drops
all of the OWA public synonyms created during the Oracle HTTP Server installation
process.</li>
<pre CLASS="CE1"><a NAME="764479"></a>drop public synonym OWA_CUSTOM;
<a NAME="764480"></a>drop public synonym OWA_GLOBAL;
<a NAME="764481"></a>drop public synonym OWA;
<a NAME="764482"></a>drop public synonym HTF;
<a NAME="764483"></a>drop public synonym HTP;
<a NAME="764484"></a>drop public synonym OWA_COOKIE;
<a NAME="764485"></a>drop public synonym OWA_IMAGE;
<a NAME="764486"></a>drop public synonym OWA_OPT_LOCK;
<a NAME="764487"></a>drop public synonym OWA_PATTERN;
<a NAME="764488"></a>drop public synonym OWA_SEC;
<a NAME="764489"></a>drop public synonym OWA_TEXT;
<a NAME="764490"></a>drop public synonym OWA_UTIL;
<a NAME="764491"></a>drop public synonym OWA_INIT;
<a NAME="764492"></a>drop public synonym OWA_CACHE;
<a NAME="764493"></a>drop public synonym WPG_DOCLOAD;
<a NAME="764494"></a></pre>
<li CLASS="LN1" TYPE="1" VALUE="3">
<a NAME="764495"></a>Connect to the "<tt>oas_public</tt>" OWA package installation
schema.</li>
<li CLASS="LN1" TYPE="1" VALUE="4">
<a NAME="764496"></a>Ensure that the user schema has "<tt>CREATE PUBLIC
SYNONYM</tt>" privileges. If it does not, then grant these privileges to
the user schema before continuing with the next step.</li>
<li CLASS="LN1" TYPE="1" VALUE="5">
<a NAME="764497"></a>Run the following commands in SQL*Plus. This recreates
the OWA public synonyms so that they reference the Oracle Application Server
OWA packages.</li>
<pre CLASS="CE1"><a NAME="764498"></a>create public synonym OWA_CUSTOM for OWA_CUSTOM;
<a NAME="764499"></a>create public synonym OWA_GLOBAL for OWA_CUSTOM;
<a NAME="764500"></a>create public synonym OWA for OWA;
<a NAME="764501"></a>create public synonym HTF for HTF;
<a NAME="764502"></a>create public synonym HTP for HTP;
<a NAME="764503"></a>create public synonym OWA_COOKIE for OWA_COOKIE;
<a NAME="764504"></a>create public synonym OWA_IMAGE for OWA_IMAGE;
<a NAME="764505"></a>create public synonym OWA_OPT_LOCK for OWA_OPT_LOCK;
<a NAME="764506"></a>create public synonym OWA_PATTERN for OWA_PATTERN;
<a NAME="764507"></a>create public synonym OWA_SEC for OWA_SEC;
<a NAME="764508"></a>create public synonym OWA_TEXT for OWA_TEXT;
<a NAME="764509"></a>create public synonym OWA_UTIL for OWA_UTIL;
<a NAME="764510"></a>create public synonym OWA_INIT for OWA_CUSTOM;
<a NAME="764511"></a>create public synonym OWA_CACHE for OWA_CACHE;
<a NAME="764512"></a>create public synonym WPG_DOCLOAD for WPG_DOCLOAD;</pre>
</ol>
<a NAME="764518"></a>

<H3 CLASS="H2-Head2">
<A NAME="pgfId-764518"></A>7.4 Oracle Demo Certificates Replacement</H3>
<P CLASS="BP-Body">
<A NAME="pgfId-764519"></A>Oracle Demo certificates (that is, dummy certificates) are included with the HTTP Server build so that the server may be tested in a non-production mode. Before going to production mode, you MUST replace the Oracle Demo certificate with a real certificate.</P>
</DIV>
<DIV>
<H3 CLASS="H2-Head2">
<A NAME="pgfId-766879"></A>7.5 Preserving Changes to Oracle HTTP Server Configuration on Re-installation in Same Oracle Home</H3>
<P CLASS="BP-Body">
<A NAME="pgfId-766890"></A>Be sure to save copies of httpd.conf, jserv.conf, zone.properties, and any Oracle HTTP Server configuration files that you have changed. Depending upon how you re-install Oracle9<i>i</i>
 Release 2 into the same Oracle home, existing configuration files may be overwritten with the newly installed files.</P>
</DIV>
<DIV>
<H3 CLASS="H2-Head2">
<A NAME="pgfId-764522"></A>7.6 New SSL Certificate Required</H3>
<P CLASS="BP-Body">
<A NAME="pgfId-764523"></A>A new SSL certificate will need to be acquired from Verisign to upgrade from Oracle Application Server (OAS) 4.0.8.2 to Oracle HTTP Server, due to the Spyglass to Apache conversion for listeners.</P>
</DIV>
<DIV>
<H3 CLASS="H2-Head2">
<A NAME="pgfId-764527"></A>7.7 OPENSSL Command -CONFIG Option Requirement</H3>
<P CLASS="BP-Body">
<A NAME="pgfId-764528"></A>The <EM CLASS="CodeInline">
openssl</EM>
 command to create a certificate request or certificate requires the <EM CLASS="CodeInline">
-config</EM>