Apache Listener on OAS 4.08

i can't install and run apache properly as a third-party listener on oas 4.08. Apache seems to start, but the red-flag indicates that it isn't running.
what should i do with libapadp.so? docs say i should link it when i build apache. how do i do that?

Hello.
I've got the same problem, this is how far I've gotten:
[root@thor conf]# httpd
[Thu Aug 24 22:58:11 2000] [warn] Loaded DSO modules/ndwfapd.so uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI)
[root@thor conf]#
I've figured that I must recompile apache with:
./configure prefix=/path/to/install/apache enable-rule=SHARED_CORE
What about extra modules that come with the standard Mdk rpm? What switches is the mandrake rpm compiled with?
I'm too worried about wrecking my apache installation.
Basically my question is:
How do I recompile and get apache working with the least differentiation from the standard mdk rpm that came with Mandrake 7.1 but including support for my additional module (for Oracle Application Server)?
C.

Similar Messages

  • Apache listener

    Hello to all
    I have compiled Apache 1-3-1 with the timely indications
    of the release notes and is compiled without mistakes and starts
    httpd without problems , in the file srm.conf have put the
    adecuate alias directives but when I attempt to accede to
    directories such as http://server/ows-doc/ , I obtain message of
    not found.
    It is accurate to modify something of WRB?.
    The take-off sequence that I use is
    dbstart
    lsnrctl start
    owsctl start wrb
    apachectl start
    I have observed that to execute owsctl start admin and owsctl
    start www , they start the web server Spyglass in the ports 8888
    and 81. Must start them also and to effect a redirect? When I
    use oracle web listener (Spyglass) operates correctly. What is
    wrong?
    null

    Robin Jackson (guest) wrote:
    : I was excited to see that an Apache listener was supported
    : in 3.0.2. However, the wlextreg program is giving me a core
    : dump. Any ideas?
    : I have the ows_module loaded in apache and the aliases
    : defined correctly. But there is ABSOLUTELY no documentation
    : about setting up external Listeners (or am I missing
    : something?).
    : Has anybody else had a problem with wlextreg?
    : How can I rebuild/reinstall just this module?
    : BTW its GREAT to see Oracle move in this direction, including
    : Apache integration!
    : TIA
    : Rob
    I am having the same problem with wlextreg and was wondering if
    there is any fix for it. Have rebuilt apache properly, just need
    to know how to register it with OAS.
    null

  • While installation, Apache listener configuration for 9ias at window screen

    Hi,
    I installed 8.1.7 enterprise edition oracle on windows 2000 and also removed IIS from windows .
    While installing 9IAS Minimal edition , the problem i get is that
    apache listener configuration for 9ias at windows screen doesnt splashes..
    However , complete successfully message coming ...
    But there is no Http Server or any 9ias product installed actually
    What is wrong here ?
    thanks in advance
    Regards,
    Defne

    Hi,
    I installed 8.1.7 enterprise edition oracle on windows 2000 and also removed IIS from windows .
    While installing 9IAS Minimal edition , the problem i get is that
    apache listener configuration for 9ias at windows screen doesnt splashes..
    However , complete successfully message coming ...
    But there is no Http Server or any 9ias product installed actually
    What is wrong here ?
    thanks in advance
    Regards,
    Defne

  • Apache Listening port

    Is there anyway to change the listening port for the default website without messing up the server app??  I have a program that need to run on port 80 for ease of use, however lion listens on all ports because of the default website.    
    Thanks in advance,
    Jeremy

    you'd have to edit /etc/apache2/httpd.conf
    find the section: 
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    <IfDefine !MACOSXSERVER>
    Listen 80
    </IfDefine>
    and change from port 80 to whatever it is you desire
    will have to restart apache after you save the changes

  • Switching from XDB to Apache listener

    I am running Oracle 10gXE which installs Oracle http Serer and uses XMLDB's listener XDB on port 8080.
    I am also running Apache as an http server that listens to port 80.
    Is it possible to configure Oracle 10gXE to use Apache's listener?
    I need to use Apache (not XDB) so I am not looking at solutions that tell me how to reconfigure XDB to listen to port 80. (I know hoe to use dbms_xdb.sethttpport('80') )
    Thanks for your help.
    Edited by: user524482 on Aug 9, 2009 1:45 PM

    Hi
    Have you try use Apache reverseproxy ?
    Br, Jari

  • Registering Apache 1.3.4 with OAS 407 on RedHat Linux 5.2

    Hi,
    Has anybody tried or succeeded in registering Apache 1.3.4 with
    Oracle Application Server 4.0.7 running on RedHat Linux 5.2?
    We're having trouble registering Apache as an External Web
    Listener for OAS. Applying the correction for step #2 under
    registering Apache servers also hasn't given us any success in
    rebuilding Apache.
    Has anybody encountered the error message below when compiling
    the Apache 1.3.4 to work with OAS after updating the EXTRA_LIBS
    in Apache CONFIGURATION File with the value given on the
    documentation.
    The Error Message
    Using config file: Configuration
    Creating Makefile
    + configured for Linux platform
    + setting C compiler to gcc
    + setting C pre-processor to gcc -E
    + checking for system header files
    + adding selected modules
    + doing sanity check on compiler and options
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_log_error_old'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_palloc'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_internal_redirect'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `gMimeTypesFile'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_log_printf'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_setup_client_block'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_destroy_sub_req'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_get_basic_auth_pw'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_listeners'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_sub_req_lookup_file'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_pstrdup'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `gImplName'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_table_add'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_get_remote_host'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_signal'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_send_http_header'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ows_module'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_should_client_block'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_rwrite'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_table_set'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `ap_get_client_block'
    /home/oracle/ows/4.0/lib/libapadp.so: undefined reference to
    `alias_module'
    make: *** [dummy] Error 1
    ** A test compilation with your Makefile configuration
    ** failed. This is most likely because your C compiler
    ** is not ANSI. Apache requires an ANSI C Compiler, such
    ** as gcc. The above error message from your compiler
    ** will also provide a clue.
    Aborting!
    Your comments or suggestions are most welcome.
    Thanks,
    --Edsel
    null

    Hi ,
         First of all please check availability of your OS + DB requiremnts whether it is supported by SAP or not.You can check this at Product Availability Matrix at ::
    http://service.sap.com/pam
         If this support for your environment i.e.RedHat Linux 5.2 with Oracle 10G then be informed that after starting sapinst in step create database it will prompt you for installing your oracle DB. So open a new window & install your databse ,do the patching of your DB & then continue with sapinst after successfull installation of oracle.Rest of details sapinst will prompot you during instal;lation.
        Hope this will guide you for your query.
    Thanks..
    Mohit

  • Generic Apache calling OAS for pl/sql pages

    I have a generic apache 2.2 set up using SSL and everything works fine. We are calling OAS v10.1.2 for pl/sql pages. This works fine. Now we want to use SSL certificates. The certificates are correct for the generic apache, but when I call the pl/sql it doesn't work. 
    1.  If we have SSLVerifyclient OPTIONAL on the apache 2.2 the call to pl/sql is correct and the certificate is generated, but not for the pages on the apache 2.2. server.
    2. If we remove SSLVerifyclient OPTIONAL on the apache 2.2 the ssl certificate is correct for the pages on the apache 2.2 but not for the pl/sql pages form the OAS.
    Where should the ssl certificate come from for the OAS pl/sql? The OAS server or the generic apache server?

    You should post your question on the OTN (Oracle Technology Network) discussion forum.: www.technet.oracle.com. There is an iAS section where you can post questions on oas.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Tomh:
    Hi all,
    I am working on a e-commece portal site.
    Can anyone share experiences on the best configurations for running PL/SQL web applications. I'm about to deploy a production Web OLTP application developed completely with PL/SQL (8.1.5), and would like to know which of the following would be the most reliable and best performance option:
    o WebDB listener + Oracle 815
    Can WebDB give us high performance?
    o OAS listener 4.0.8.1 + OAS 4.0.8.1 + Oracle 815
    Is this the best choice?
    o Apache listener + OAS 4.0.8.1 + Oracle 815
    Any input appreciated. I think it would be useful for all people reading this list to hear some feedback...
    Thanks!
    Tomh.
    <HR></BLOCKQUOTE>
    null

  • Apache Web Services Listener not starting after bouncing application

    Can some one please help? I am runnng 11.5.10.2 on Solaris.
    ==========
    Problem:
    ==========
    I can not start my Apache Web Services Listener via ADSTRTAL.SH (log filed saved with 0 (zero) bytes – so no results to look at).
    I also tried to start it using the adapcctl.sh start as the applmgr user and I get the same error as adstrtal.sh.
    I ran apachectl configtest and got “Bus Error”
    ==========
    Question:
    ==========
    How do I fix this problem (bus error and get Apache listener to run)?
    -OR-
    Where do I go to edit this file and is it the http.conf file?

    Problem solved, disk drive was full.

  • Troubles with iAS modplsql (for Apache HTTP Listener)

    I discovered a harmful problem using
    modplsql for Apache Web Listener
    When i try to upload bylary files to table
    browser shows me error "invalid week day"
    table structure created correctly (i doublechecked it) as described in manual
    What i am doing wrong
    Is there any possibility to log actions
    performed by module ?

    They start just fine, but when we try to open the website, it just hangs at a >certain moment. Webcache is doing nothing, and we can see that Apache is trying to >process the request. This sounds like a configuration problem. To do what you want, you need to make sure 3 things happen:
    1. Web cache listens on Port 80 on the machine that it runs, say wc-host.
    2. Apache listens on Port 7778 on the machine that it runs, say apache-host. wc-host and apache-host may or may not be the same machine.
    3. Web Cache is told that when it has a cache miss, it should talk to Apache at apache-host:7778.
    It sounds like you did 1 and 2, but 3 is not done correctly. You can access Apache directly, which means 2 is done. To verify that 1 is done, try to connect to wc-host at port 80, say by a telnet command on Unix or Windows "telnet wc-host 80". If webcache is listening there, the telnet command should start and wait for you to type anything. Then, to verify if Web Cache knows where to find Apache, try give that telnet command an simple HTTP request by typing "GET / HTTP/1.0" and then two hit enter twice. Or, you could use the browser to access "http://wc-host:80/", but then the problem is IE tends to wait a long time even if Web Cache is not listening on that host and port, so it's a little hard to tell what is really going on. If you don't get anything back, then 3 is not done right.
    To fix 3, check this document http://otn.oracle.com/docs/products/ias/doc_library/90200doc_otn/caching.902/a95404/setup.htm#1011459. In fact, in this document, figure 6-2 shows an example of changing the default Web Cache listening port from 7777 to 80 and keep Apache listening on 7778. That might be exactly what you are trying to do.

  • Running OAS plsql toolkit in HTML DB

    Hi, we currently have a lot of code written using the OAS plsql toolkit, running on an Oracle 8.1.6 database. These are primarily pages that are hosted on the internet.
    I was wondering could be migrate this plsql code to Oracle 10G, dispense with the now outdated OAS altogether and use the new features of HTML DB to run the plsql pages, without really any alteration.
    Does Oracle 10G allow us to put these pages onto the web using the Apache listener.
    Has anyone else done this?

    You can't "run" the PL/SQL pages with HTML DB. What you will find is that you can throw away 90% of your code used for UI and keep the queries used for reports and any SQL or PL/SQL used for DML.
    HTML DB will handle all of the UI, session state, report sorting and pagination, and form fields. I strongly encourage you (if you have not already) to write a few reports and play with the built-in column-heading sorting, pagination, and templates before you start this process. The reason I say this is that time after time, I see people faced with your exact task trying to hold on to their pl/sql htp.p's for reports. It takes them a while to see the light, and when they do, they wonder why they've been fighting it.
    asktom.oracle.com and think.com both went through this. It's amazing how much more you can focus on the content of the app and adding new functionality when you don't have to worry about the stuff HTML DB takes care of for you. Just try it out on htmldb.oracle.com, you'll get what I'm saying in no time.
    Good luck,
    Tyler

  • Conversion to 9ias from OAS

    We are putting together a migration/conversion strategy for
    moving to 9ias from OAS and need to know if we can install 9ias
    on the same server as OAS without any issues, then once we have
    moved users to this, remove the OAS from the App Server?

    I also posted this on the Metalink forum and did get a response
    back:
    You can certainly install 9ias and OAS on the same box. You need
    to be aware that the www listener of OAS uses Port 80 which is
    the same port that 9ias tries to use for Apache. You will want
    to change the www listener to something else. In addition, it is
    not recommended that you use the same database for OAS and 9ias
    because they use different pl/sql toolkit. You should use a
    different database for 9ias.

  • Problem with JMX Remote Port - JBoss & Apache on same machine

    Hi,
    I have a server which hosts Apache that uses mod_jk to pass requests to three Tomcat instances. Apache listens to port 80.
    I want to install a different application on the same machine that runs on JBoss. Foreseeing the problem with port numbers, I got a different IP address (Let's say IP2, and original IP for Apache is IP1) on the same machine to run JBoss application. I changed HTTP Connector configuration in server.xml to add "address=IP1:8080" for Tomcat, "address=IP2:8080" for JBoss. I also modified Apache Listen directive in httpd.conf from "Listen 80" to "Listen IP1:80".
    Now when I try to start JBoss server by running run.bat, I get below error.
    Can any one please suggest how can I resolve this port conflict? Is there even a way to resolve it? As JAVA_HOME can point to a single location and both JBoss & Apache use it?
    Thanks.
    ===============================================================================
      JBoss Bootstrap Environment
      JBOSS_HOME: C:\jboss
      JAVA: C:\Java\jdk1.6.0_01\bin\java
      JAVA_OPTS: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=
    9004 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.aut
    henticate=false  -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.
    client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
      CLASSPATH: C:\Java\jdk1.6.0_01\lib\tools.jar;E:\jboss\bin\run.jar
    ===============================================================================
    Error: Exception thrown by the agent : java.rmi.server.ExportException: Port alr
    eady in use: 9004; nested exception is:
            java.net.BindException: Address already in use: JVM_Bind
    Press any key to continue . . .

    What's running on JMX port without the Jboss running ?
    Seems that u have something it.
    Btw, try to discover how to bind JMX of portal to IP2, not to IP1 or to global Ip.

  • Apache as reverse proxy - 400 Bad request

    Hi all,
    I'm configured apache as reverse proxy according to this blog:
    The Reverse Proxy Series -- Part 3: Apache as a reverse-proxy
    When I try to navigate http://testcomp/irj I get "400 - Bad request"
    See exception;
    <i>Message : User Guest, IP address
    Cannot parse the http request. Http error response [400 Bad Request] will be returned. Request is [Host: sapportal:50000
    Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, /
    Accept-Language: en,he;q=0.5
    Accept-Encoding: gzip, deflate
    User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727)
    Max-Forwards: 10
    Via: 1.1 localhost
    X-Forwarded-For: 10.0.0.4
    X-Forwarded-Host: 10.0.0.6
    X-Forwarded-Server: localhost
    Connection: Keep-Alive
    GET /irj HTTP/1.1
    Host: sapportal:50000
    Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, /
    Accept-Language: en,he;q=0.5
    Accept-Encoding: gzip, deflate
    User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727)
    Max-Forwards: 10
    Via: 1.1 localhost
    X-Forwarded-For: 10.0.0.4
    X-Forwarded-Host: 10.0.0.6
    X-Forwarded-Server: localhost
    Connection: Keep-Alive
    com.sap.engine.services.httpserver.exceptions.HttpIllegalArgumentException: Incompatible field content in the MIME header.
         at com.sap.engine.services.httpserver.lib.headers.MimeHeaderField.parse(MimeHeaderField.java:364)
         at com.sap.engine.services.httpserver.lib.headers.MimeHeaders.init(MimeHeaders.java:504)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.initialize(RequestAnalizer.java:196)
         at com.sap.engine.services.httpserver.server.Client.initialize(Client.java:84)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:143)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Severity : Error
    Category :
    Location : com.sap.engine.services.httpserver
    Application :
    Thread : SAPEngine_Application_Thread[impl:3]_32
    Datasource : 9332850:C:usrsapPD9JC00j2eeclusterserver0logdefaultTrace.trc
    Message ID : 000C29EFE9A300570000002D00000B9000043A81D3311894
    Source Name : com.sap.engine.services.httpserver
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : 5359e85066e411dcbf6b000c29efe9a3
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives :
    Resource Bundlename :
    Session : 2
    Source : com.sap.engine.services.httpserver
    ThreadObject : SAPEngine_Application_Thread[impl:3]_32
    Transaction :
    User : Guest</i>
    The lines I added to http.conf
    <i>#Enable reverse-proxying
    ProxyVia on
    ProxyTimeout 600
    #disable forward-proxying
    ProxyRequests Off
    #proxy /irj both ways
    ProxyPass /irj http://sapportal:50000/irj
    ProxyPassReverse /irj http://testcomp/irj
    #proxy /logon both ways
    ProxyPass /logon http://sapportal:50000/logon
    ProxyPassReverse /logon http://testcomp/logon</i>
    I tried with apache version 2.2.3 & 2.0.59 with no success.
    My J2EE/Portal version is 6.17.
    Since this is a testing environment the two computers are under the same workgroup (no domain).
    If I naviagte directly to the portal (without the reverse proxy) everything is working.
    How can I solve it?
    Regards,
    Omri

    Hi Jakub,
    Thanks for the answer.
    It's not working for me...
    I'm attaching my httpd.conf file.
    Also, what apache version do you use?
    Can you send me your post your httpd.conf file?
    Thanks,
    Omri
    httpd.conf
    This is the main Apache HTTP server configuration file.  It contains the
    configuration directives that give the server its instructions.
    See <URL:http://httpd.apache.org/docs/2.2/> for detailed information.
    In particular, see
    <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    for a discussion of each configuration directive.
    Do NOT simply read the instructions in here without understanding
    what they do.  They're here only as hints or reminders.  If you are unsure
    consult the online docs. You have been warned. 
    Configuration and logfile names: If the filenames you specify for many
    of the server's control files begin with "/" (or "drive:/" for Win32), the
    server will use that explicit path.  If the filenames do not begin
    with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
    with ServerRoot set to "c:/apache" will be interpreted by the
    server as "c:/apache/logs/foo.log".
    NOTE: Where filenames are specified, you must use forward slashes
    instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
    If a drive letter is omitted, the drive on which Apache.exe is located
    will be used by default.  It is recommended that you always supply
    an explicit drive letter in absolute paths, however, to avoid
    confusion.
    ThreadsPerChild: constant number of worker threads in the server process
    MaxRequestsPerChild: maximum  number of requests a server process serves
    ThreadsPerChild 250
    MaxRequestsPerChild  0
    ServerRoot: The top of the directory tree under which the server's
    configuration, error, and log files are kept.
    Do not add a slash at the end of the directory path.  If you point
    ServerRoot at a non-local disk, be sure to point the LockFile directive
    at a local disk.  If you wish to share the same ServerRoot for multiple
    httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "c:/apache"
    Listen: Allows you to bind Apache to specific IP addresses and/or
    ports, instead of the default. See also the <VirtualHost>
    directive.
    Change this to Listen on specific IP addresses as shown below to
    prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
    #Listen 12.34.56.78:80
    Listen 80
    Dynamic Shared Object (DSO) Support
    To be able to use the functionality of a module which was built as a DSO you
    have to place corresponding `LoadModule' lines at this location so the
    directives contained in it are actually available before they are used.
    Statically compiled modules (those listed by `httpd -l') do not need
    to be loaded here.
    Example:
    LoadModule foo_module modules/mod_foo.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    #LoadModule auth_digest_module modules/mod_auth_digest.so
    #LoadModule authn_anon_module modules/mod_authn_anon.so
    #LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authn_file_module modules/mod_authn_file.so
    #LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule autoindex_module modules/mod_autoindex.so
    #LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule cgi_module modules/mod_cgi.so
    #LoadModule dav_module modules/mod_dav.so
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    #LoadModule deflate_module modules/mod_deflate.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule env_module modules/mod_env.so
    #LoadModule expires_module modules/mod_expires.so
    #LoadModule file_cache_module modules/mod_file_cache.so
    #LoadModule headers_module modules/mod_headers.so
    LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule include_module modules/mod_include.so
    #LoadModule info_module modules/mod_info.so
    LoadModule isapi_module modules/mod_isapi.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule mime_module modules/mod_mime.so
    #LoadModule mime_magic_module modules/mod_mime_magic.so
    <b>LoadModule proxy_module modules/mod_proxy.so</b>
    #LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    #LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    #LoadModule proxy_connect_module modules/mod_proxy_connect.so
    <b>LoadModule proxy_http_module modules/mod_proxy_http.so</b>
    #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule negotiation_module modules/mod_negotiation.so
    #LoadModule rewrite_module modules/mod_rewrite.so
    LoadModule setenvif_module modules/mod_setenvif.so
    #LoadModule speling_module modules/mod_speling.so
    #LoadModule status_module modules/mod_status.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule userdir_module modules/mod_userdir.so
    #LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule vhost_alias_module modules/mod_vhost_alias.so
    #LoadModule ssl_module modules/mod_ssl.so
    'Main' server configuration
    The directives in this section set up the values used by the 'main'
    server, which responds to any requests that aren't handled by a
    <VirtualHost> definition.  These values also provide defaults for
    any <VirtualHost> containers you may define later in the file.
    All of these directives may appear inside <VirtualHost> containers,
    in which case these default settings will be overridden for the
    virtual host being defined.
    ServerAdmin: Your address, where problems with the server should be
    e-mailed.  This address appears on some server-generated pages, such
    as error documents.  e.g. [email protected]
    ServerAdmin @@ServerAdmin@@
    ServerName gives the name and port that the server uses to identify itself.
    This can often be determined automatically, but we recommend you specify
    it explicitly to prevent problems during startup.
    If your host doesn't have a registered DNS name, enter its IP address here.
    ServerName localhost:80
    DocumentRoot: The directory out of which you will serve your
    documents. By default, all requests are taken from this directory, but
    symbolic links and aliases may be used to point to other locations.
    DocumentRoot "c:/apache/htdocs"
    Each directory to which Apache has access can be configured with respect
    to which services and features are allowed and/or disabled in that
    directory (and its subdirectories).
    First, we configure the "default" to be a very restrictive set of
    features. 
    <Directory />
        Options FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
        Satisfy all
    </Directory>
    Note that from this point forward you must specifically allow
    particular features to be enabled - so if something's not working as
    you might expect, make sure that you have specifically enabled it
    below.
    This should be changed to whatever you set DocumentRoot to.
    <Directory "c:/apache/htdocs">
    Possible values for the Options directive are "None", "All",
    or any combination of:
      Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    Note that "MultiViews" must be named explicitly --- "Options All"
    doesn't give it to you.
    The Options directive is both complicated and important.  Please see
    http://httpd.apache.org/docs/2.2/mod/core.html#options
    for more information.
        Options Indexes FollowSymLinks
    AllowOverride controls what directives may be placed in .htaccess files.
    It can be "All", "None", or any combination of the keywords:
      Options FileInfo AuthConfig Limit
        AllowOverride None
    Controls who can get stuff from this server.
        Order allow,deny
        Allow from all
    </Directory>
    DirectoryIndex: sets the file that Apache will serve if a directory
    is requested.
    <IfModule dir_module>
        DirectoryIndex index.html
    </IfModule>
    The following lines prevent .htaccess and .htpasswd files from being
    viewed by Web clients.
    <FilesMatch "^\.ht">
        Order allow,deny
        Deny from all
    </FilesMatch>
    ErrorLog: The location of the error log file.
    If you do not specify an ErrorLog directive within a <VirtualHost>
    container, error messages relating to that virtual host will be
    logged here.  If you do define an error logfile for a <VirtualHost>
    container, that host's errors will be logged there and not here.
    ErrorLog logs/error.log
    LogLevel: Control the number of messages logged to the error_log.
    Possible values include: debug, info, notice, warn, error, crit,
    alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    The following directives define some format nicknames for use with
    a CustomLog directive (see below).
        LogFormat "%h %l %u %t \"%r\" %>s %b \"%You need to enable mod_logio.c to use %I and %Oi\" \"%{User-Agent}i\"" combined
        LogFormat "%h %l %u %t \"%r\" %>s %b" common
        <IfModule logio_module>
          LogFormat "%h %l %u %t \"%r\" %>s %b \"%i\" \"%{User-Agent}i\" %I %O" combinedio
        </IfModule>
    The location and format of the access logfile (Common Logfile Format).
    If you do not define any access logfiles within a <VirtualHost>
    container, they will be logged here.  Contrariwise, if you do
    define per-<VirtualHost> access logfiles, transactions will be
    logged therein and not in this file.
        CustomLog logs/access.log common
    If you prefer a logfile with access, agent, and referer information
    (Combined Logfile Format) you can use the following directive.
        #CustomLog logs/access.log combined
    </IfModule>
    <IfModule alias_module>
    Redirect: Allows you to tell clients about documents that used to
    exist in your server's namespace, but do not anymore. The client
    will make a new request for the document at its new location.
    Example:
    Redirect permanent /foo http://www.example.com/bar
    Alias: Maps web paths into filesystem paths and is used to
    access content that does not live under the DocumentRoot.
    Example:
    Alias /webpath /full/filesystem/path
    If you include a trailing / on /webpath then the server will
    require it to be present in the URL.  You will also likely
    need to provide a <Directory> section to allow access to
    the filesystem path.
    ScriptAlias: This controls which directories contain server scripts.
    ScriptAliases are essentially the same as Aliases, except that
    documents in the target directory are treated as applications and
    run by the server when requested rather than as documents sent to the
    client.  The same rules about trailing "/" apply to ScriptAlias
    directives as to Alias.
        ScriptAlias /cgi-bin/ "c:/apache/cgi-bin/"
    </IfModule>
    "c:/apache/cgi-bin" should be changed to whatever your ScriptAliased
    CGI directory exists, if you have that configured.
    <Directory "c:/apache/cgi-bin">
        AllowOverride None
        Options None
        Order allow,deny
        Allow from all
    </Directory>
    Apache parses all CGI scripts for the shebang line by default.
    This comment line, the first line of the script, consists of the symbols
    pound (#) and exclamation followed by the path of the program that
    can execute this specific script.  For a perl script, with perl.exe in
    the C:\Program Files\Perl directory, the shebang line should be:
       #!c:/program files/perl/perl
    Note you mustnot_ indent the actual shebang line, and it must be the
    first line of the file.  Of course, CGI processing must be enabled by
    the appropriate ScriptAlias or Options ExecCGI directives for the files
    or directory in question.
    However, Apache on Windows allows either the Unix behavior above, or can
    use the Registry to match files by extention.  The command to execute
    a file of this type is retrieved from the registry by the same method as
    the Windows Explorer would use to handle double-clicking on a file.
    These script actions can be configured from the Windows Explorer View menu,
    'Folder Options', and reviewing the 'File Types' tab.  Clicking the Edit
    button allows you to modify the Actions, of which Apache 1.3 attempts to
    perform the 'Open' Action, and failing that it will try the shebang line.
    This behavior is subject to change in Apache release 2.0.
    Each mechanism has it's own specific security weaknesses, from the means
    to run a program you didn't intend the website owner to invoke, and the
    best method is a matter of great debate.
    To enable the this Windows specific behavior (and therefore -disable- the
    equivilant Unix behavior), uncomment the following directive:
    #ScriptInterpreterSource registry
    The directive above can be placed in individual <Directory> blocks or the
    .htaccess file, with either the 'registry' (Windows behavior) or 'script'
    (Unix behavior) option, and will override this server default option.
    DefaultType: the default MIME type the server will use for a document
    if it cannot otherwise determine one, such as from filename extensions.
    If your server contains mostly text or HTML documents, "text/plain" is
    a good value.  If most of your content is binary, such as applications
    or images, you may want to use "application/octet-stream" instead to
    keep browsers from trying to display binary files as though they are
    text.
    DefaultType text/plain
    <IfModule mime_module>
    TypesConfig points to the file containing the list of mappings from
    filename extension to MIME-type.
        TypesConfig conf/mime.types
    AddType allows you to add to or override the MIME configuration
    file specified in TypesConfig for specific file types.
        #AddType application/x-gzip .tgz
    AddEncoding allows you to have certain browsers uncompress
    information on the fly. Note: Not all browsers support this.
        #AddEncoding x-compress .Z
        #AddEncoding x-gzip .gz .tgz
    If the AddEncoding directives above are commented-out, then you
    probably should define those extensions to indicate media types:
        AddType application/x-compress .Z
        AddType application/x-gzip .gz .tgz
    AddHandler allows you to map certain file extensions to "handlers":
    actions unrelated to filetype. These can be either built into the server
    or added with the Action directive (see below)
    To use CGI scripts outside of ScriptAliased directories:
    (You will also need to add "ExecCGI" to the "Options" directive.)
        #AddHandler cgi-script .cgi
    For type maps (negotiated resources):
        #AddHandler type-map var
    Filters allow you to process content before it is sent to the client.
    To parse .shtml files for server-side includes (SSI):
    (You will also need to add "Includes" to the "Options" directive.)
        #AddType text/html .shtml
        #AddOutputFilter INCLUDES .shtml
    </IfModule>
    The mod_mime_magic module allows the server to use various hints from the
    contents of the file itself to determine its type.  The MIMEMagicFile
    directive tells the module where the hint definitions are located.
    #MIMEMagicFile conf/magic
    Customizable error responses come in three flavors:
    1) plain text 2) local redirects 3) external redirects
    Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    EnableMMAP and EnableSendfile: On systems that support it,
    memory-mapping or the sendfile syscall is used to deliver
    files.  This usually improves server performance, but must
    be turned off when serving from networked-mounted
    filesystems or if support for these functions is otherwise
    broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    Supplemental configuration
    The configuration files in the conf/extra/ directory can be
    included to add extra features or to modify the default configuration of
    the server, or you may simply copy their contents here and change as
    necessary.
    Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    Multi-language error messages
    #Include conf/extra/httpd-multilang-errordoc.conf
    Fancy directory listings
    #Include conf/extra/httpd-autoindex.conf
    Language settings
    #Include conf/extra/httpd-languages.conf
    User home directories
    #Include conf/extra/httpd-userdir.conf
    Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    Various default settings
    #Include conf/extra/httpd-default.conf
    Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    Note: The following must must be present to support
          starting without SSL on platforms with no /dev/random equivalent
          but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    <b>ProxyPreserveHost On
    ProxyVia on
    ProxyTimeout 600
    #disable forward-proxying
    ProxyRequests Off
    #proxy /irj both ways
    ProxyPass /irj http://sapportal:50000/irj
    ProxyPassReverse /irj http://sapportal:50000/irj
    #ProxyPassReverse /irj http://testcomp/irj
    #proxy /logon both ways
    ProxyPass /logon http://sapportal:50000/logon
    ProxyPassReverse /logon http://sapportal:50000/logon
    #ProxyPassReverse /logon http://testcomp/logon</b>

  • Apache Hangs after 1.0.2.1 upgrade

    I've upgraded to iAS 1.0.2.1 from 1.0.2 on NT. The apache listener comes up okay on startup. When I try to access a portal configuration though the browser just hangs until it times out. There is no error message returned to me. This behavior exists when trying to connect to a portal 3.0.7 install that worked under the old 1.0.2 install as well as a fresh 3.0.8 portal install that I created with the new Portal Configuration Wizard.
    The behavior is such that when I try to access the portal page the disk drive cranks and the CPU spikes for about 5 seconds and then it just sits there. If the database is not running I get an error message so the inital call is probably making some sort of DB contact, however no Portal Homepage. Any suggestions are very welcome.null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Michael Rinebold ([email protected]):
    I just upgraded from 1.0.2.0 and have the same issue. So I uninstalled the 1.0.2.0 instance and did a fresh install and it still hangs trying to get to the public home page. All of the config pages work ok.
    What is up with this?
    msr<HR></BLOCKQUOTE>
    I logged a tar with Oracle support and it turned out my problem was with duplicate entries in the zone.properties file. Here is the fix from Oracle Support.
    I see serveral duplicate entries in the zone.properties. The following are the lines that have duplicates. Check to see if I missed any and then remove the duplicates. After that bounce the http listener.
    repositories=D:\Oracle\iSuites\Apache\Jserv\servlets\Parallel.jar
    repositories=D:\Oracle\iSuites\Apache\Jserv\servlets\ChartServlet.jar
    repositories=D:\Oracle\iSuites\Apache\Jserv\servlets\AppLoader.jar
    servlet.page.code=oracle.webdb.page.ParallelServlet
    servlet.chart.code=oracle.webdb.chart.ChartServlet
    servlet.apploader.code=oracle.webdb.apploader.AppLoaderServlet
    servlet.ojsp.code=oracle.jsp.JspServlet
    null

  • 9iAS 1.0.2.1 Apache dies with httpd.pid overwritten

    Hi,
    I am running 9iAS 1.0.2.1(minimun install) on Linux 6.2 EE with Oracle 8.1.7.0.1. I am not able to start Apache. The error_log shows that httpd.pid was overwritten. There are no other error logs. Has anybody seen this problem? The Apache listener that came with the database runs fines(it is on a different port).
    Thanks,
    Matthew

    We had the same problems. I found on the 9iAS CD another Apache. I just copied the binaries and modules over to the Apache directory of 9iAS and got it to work with this.

Maybe you are looking for