Emails In HtmlDB

Hi all,
Can any one tell me how can we start MS Outlook when we click field on Oracle Html Db Application
Thanks
alaa
[email protected]

Assuming the emp table has a column containing the email address for the corresponding employee, you could use this query to acomplish what you are asking for:
SELECT '<a href="mailto:' || email || '">' || ename || '</a>' person_name,
hiredate, sal
FROM emp
Denes Kubicek

Similar Messages

Sending email from HTMLDB - what happens after submit?

I have read the "How To" document on sending email from HTMLDB but it is very vague on what is suppose to happen after submitting the process. After I submit the process that calls HTMLDB_MAIL.SEND, how do I track down what is suppose to happen? How do I debug it? All it mentions is that the job is stored in a queue somewhere until DBMS_JOB pushes the queue? Which USER_JOBS table am I suppose to see the job in? What is the job suppose to look like? How do I know the email has been sent? How do I check that the mail is posted correctly each time? Where do error messages go if the email is not sent? Where is there doco on changing the SMTP_HOST_ADDRESS and PORT settings?
help
Paul Platt

You can call
HTMLDB_MAIL.PUSH_QUEUE('smtpservername,port);
after sending your mail.Is there an easy way to call HTMLDB_MAIL.PUSH_QUEUE and get it to use the SMTP parameters defined for the HTMLDB installation, rather than having to specify them again in the code.
The DBMS_JOB entry used to push the mail uses:
wwv_flow_platform.get_preference('SMTP_HOST_ADDRESS')
but this is not a public package.
Thanks
Roger

Email an HTMLDB page

Our managers do not want to have to navigate to the program I have created in order to review data. Instead, they want me to configure it so that when their admin is in the program, the page they are on is emailed to them (It is full of charts/graphs). I have read all about configuring email but can I send a page, not a link but an actual page?
Thanks in advance!

You are kidding, right? Instead of getting a email containing a link to the desired information, your managers have asked you to send each person the full page as an attachment? That would be so inefficient. As long as the application has the proper authentication schemes so that clicking on the link takes them directly to the page with the charts/graphs, that should be sufficient. Sounds like a candidate for a Dilbert strip!
[Sorry, couldn't resist, I don't mean to make light of your request]

Sending email and get delivery notification

Hi,
I want to send an email from HTMLDB and I see that the HTMLB mail package also use the utl_smtp package to implement this function. So I write a store procedure to send email with the help of utl_smtp and it works. Additional to every send I want a delivery confirmation to the sender adress, because it is very important to see, which mails weren't delivered. I've searched for an parameter to set and found these syntaxes in the "PL/SQL Packages and Types Reference".
UTL_SMTP.MAIL (
c IN OUT NOCOPY connection,
sender IN VARCHAR2,
parameters IN VARCHAR2 DEFAULT NULL);
UTL_SMTP.RCPT (
c IN OUT NOCOPY connection,
recipient IN VARCHAR2,
parameters IN VARCHAR2 DEFAULT NULL)
RETURN reply;
UTL_SMTP.RCPT (
c IN OUT NOCOPY connection,
recipient IN VARCHAR2,
parameters IN VARCHAR2 DEFAULT NULL);
The following statement stay in the Reference for the description of "parameters":
parameters The additional parameters to RCPT command as defined in Section 6 of [RFC1869]. It should follow the format of "XXX=XXX (XXX=XXX ....)".
I read a little bit about SMTP in RFC1869 and I write change the statements:
utl_smtp.mail(mail_conn,sender);
utl_smtp.rcpt(mail_conn,recipient);
to:
utl_smtp.mail(mail_conn,sender, 'NOTIFY="SUCCESS,FAILURE"');
utl_smtp.rcpt(mail_conn,recipient, 'NOTIFY="SUCCESS,FAILURE"');
I get now the following syntax error: "ORA-29279: SMTP permanent error: 501 Syntax Error"
I tried also the statement without success:
utl_smtp.mail(mail_conn,sender, 'NOTIFY=SUCCESS,FAILURE');
utl_smtp.rcpt(mail_conn,recipient, 'NOTIFY=SUCCESS,FAILURE');
What can I do to get this delivery confirmation. E.g. in Outlook is possible to set this as option for emails before you send it. Any ideeas?
Thanks!
Serban Vettori

Hi,
I read at first parts of RFC 1869 (stands in your documentation) but it doesn't help me too much because it wasn't a concrete example there. The best adress is the RFC1891 "SMTP Delivery Status Notifications", that contains a lot of examples like:
MAIL FROM:<[email protected]> RET=HDRS ENVID=QQ314159
<<< 250 ok
RCPT TO:<[email protected]> NOTIFY=FAILURE \ORCPT=rfc822;[email protected]
<<< 550 error - no such recipient
RCPT TO:<[email protected]> NOTIFY=SUCCESS,FAILURE \ORCPT=rfc822;[email protected]
<<< 250 recipient ok
DATA<<< 354 send message, end with '.'
(message goes here)
.<<< 250 message received
QUIT<<< 221 bye
Your documentation is realy good but in this case wasn't really helpful. If you implement a function it were nice to document any input parameter. The user have to read several other documents to get ONE parameter! I personally don't like this. Perhaps there are other users which are really exalted to see such cross references.
Here is the right syntax for this problem:
utl_smtp.rcpt(conn, recipient, 'NOTIFY=SUCCESS,FAILURE')
You get in this way delivery notifications on succeded and failed messages. If you just want to get a delivery success notification just assign the input variable "parameters" with this value: 'NOTIFY=SUCCESS'. There is also a third possible value you can choose: "DELAY". This mean "notify me, if there is an email sending delay".
Best regards,
Serban Vettori

Instant message alert

Hello,
I am trying to create a HTML Db application which uses 'instant messaging'.
What I would like the database to do is when certain actions take place (e.g. A users submits a document or amends a document or deletes a document from a table), I would like to be able to send an alert out to certain groups of people (dependant on the action that has taken place). The recipients would see a popup box on their screen which would inform them of what has taken place and provide a link to the HTML Db application.
Is this possible in HTML Db?
Any help much appreciated.

Simon,
If I understand you right, you want to be able to send out an instant message instead of an email from HTMLDB. To send an email HTMLDB leverages the database SMTP client implementation and the SMTP protocol. Database exposes the SMTP client API to HTMLDB as a PL/SQL procedure (UTL_SMTP). There is no UTL_IM. So the solution to your problem lies in creating your own stored procedure in the database to send an IM.
I know each vendor had a proprietary protocol for instant messaging. You cannot add AOL or MSN messenger users into your yahoo messenger or vice versa !! (Pardon my ignorance if this is not true). Now a days I see third party instant messengers like ICQ that seem to work with MSN, yahoo, etc - I have not use one myself - which suggests that it is worth an effort to find more about the protocols. Once you have the information you can use UTL_TCP/external procedure/java procedure in the database to create a stored procedure to send IM.
Somebody had suggested using windows net send or unix wall. That can be implemented as external proc, saving you the time to research IM, but it will not work well in a mixed environment (unix servers and windows desktop).
In short HTMLDB email feature is a wrapper around database UTL_SMTP. Database does not have any IM client implementation. You will have to create your own.

Problem using reset_pw to change password

When sending out emails from HTMLDB using wwv_flow_fnd_user_api.reset_pw to change passwords HTMLDB used the email of the user as the from user. Our SMTP server will only allow valid users to send emails!
As a work-around we're updating the P_FROM column in WWV_FLOW_MAIL_QUEUE to a valid user if the email is stuck in the queue and then pushing then queue.
Anybody have a better solution?
Oracle, will you fix this "BUG"? and allow the from user to be specified as an optional parameter?
BTW: Many of the other email features are locked down in the email packages provided with HTMLDB. Could we get access to reply-to, error-to, from, and other email standard parameters?

Michael,
I might be missing something, but you say "our SMTP server will only allow valid users to send emails". So if your SMTP server has this limitation, is not a null From message header also an invalid e-mail address?
I just tried a test using the UTL_SMTP package (which is employed by HTML DB). I initiated a message to an SMTP server which did not validate the From field and it went through. I did a second message, identical to the first one with a bogus From address, and sent it to another SMTP server and it was rejected with "SMTP permanent error: 553 5.5.4 zzzz... Domain name required for sender address zzzz". I believe this error message is coming back from the SMTP server, it is not an Oracle creation.
On a separate note, if this is the reset password functionality and you are 1) using the same address for the "To" and the "From", and 2) this is the e-mail address that the user will received their reset password, if the e-mail address is bogus in the first place, how would the user ever receive this e-mail?
Joel

HTMLDB/APEX - Email notification problem

Email notification is not sent AUTOMATICALLY to the user's email address when 'reset password' functionality is used or the administrator changes the password.
I managed to do that by drilling down to Home> Manage Service> Manage Mail Queue and pressing 'Send All Mail'. Is there a way to get it automated?

Once your mail request has been submitted try pushing the queue using apex_mail.push_queue(). The default wait time is going to be 10 or 15 minutes if set up to do so.
You can also take a look at this link and see if it helps:
http://www.oracle.com/technology/products/database/application_express/howtos/howto_workflow.html
Cheers,
Mike
Message was edited by:
Mike C

Problem with htmldb 2 (Sorry APEX)!

I installed htmldb 2 on a windows XP, Oracle 10gR1 (which has enhanced by companion CD downloaded form Oracle's site). Everything went OK but when I want to connect to it by this url: http://localhost:7777/pls/htmldb it takes my username,pass but says:
"Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Oracle-HTTP-Server/1.3.28 Server at localhost Port 7777"
I noticed many differences between my installed Apache and documents of htmldb. I run a 9.0.4.0.0 Apache server and the dads.conf and httpd.conf are as following:
# ============================================================================
# mod_plsql DAD Configuration File
# ============================================================================
# 1. Please refer to dads.README for a description of this file
# ============================================================================
# Note: This file should typically be included in your plsql.conf file with
# the "include" directive.
# Hint: You can look at some sample DADs in the dads.README file
# ============================================================================
Alias /i/ "E:\oracle\product\10.1.0\Companion\Apache\Apache\images/"
<Location /pls/htmldb>
SetHandler pls_handler
Order deny,allow
Allow from all
AllowOverride None
PlsqlDatabaseUsername HTMLDB_PUBLIC_USER
PlsqlDatabasePassword @BI+fAonVS+7xU8G04irVINWznM6s+A9fuQ==
PlsqlDatabaseConnectString chagh
PlsqlDefaultPage htmldb
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDocumentPath docs
PlsqlDocumentProcedure wwv_flow_file_mgr.process_download
PlsqlAuthenticationMode Basic
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
</Location>
# Based upon the NCSA server configuration files originally by Rob McCool.
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://www.apache.org/docs/> for detailed information about
# the directives.
# 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.
# After this file is processed, the server will look for and process
# E:\oracle\product\10.1.0\Companion\Apache\Apache/conf/srm.conf and then E:\oracle\product\10.1.0\Companion\Apache\Apache/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
# 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 "E:\oracle\product\10.1.0\Companion\Apache\Apache" will be interpreted by the
# server as "E:\oracle\product\10.1.0\Companion\Apache\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.
### Section 1: Global Environment
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
# ServerType is either inetd, or standalone. Inetd mode is only supported on
# Unix platforms.
ServerType standalone
# 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.
ServerRoot "E:\oracle\product\10.1.0\Companion\Apache\Apache"
# PidFile: The file in which the server should record its process
# identification number when it starts.
PidFile logs/httpd.pid
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this. But if yours does (you'll know because
# this file will be created when you run Apache) then you must ensure that
# no two invocations of Apache share the same scoreboard file.
ScoreBoardFile logs/httpd.scoreboard
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order. The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults. You can have the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf
# Timeout: The number of seconds before receives and sends time out.
Timeout 300
# SendBufferSize: controls setsockopt() call made to set send buffer size on
# all sockets. Default OS value on most Windows platforms is too small.
# Larger values can help if the average page size served by OHS is
# large (~64 k)
SendBufferSize 16384
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
KeepAlive On
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
MaxKeepAliveRequests 100
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
KeepAliveTimeout 15
# Apache on Win32 always creates one child process to handle requests. If it
# dies, another child process is created automatically. Within the child
# process multiple threads handle incoming requests. The next two
# directives control the behaviour of the threads and processes.
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies. The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources. On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For Win32, set this value to zero (unlimited)
# unless advised otherwise.
# NOTE: This value does not include keepalive requests after the initial
# request per connection. For example, if a child process handles
# an initial request and 10 subsequent "keptalive" requests, it
# would only count as 1 request towards this limit.
MaxRequestsPerChild 0
# Number of concurrent threads (i.e., requests) the server will allow.
# Set this value according to the responsiveness of the server (more
# requests active at once means they're all handled more slowly) and
# the amount of system resources you'll allow the server to consume.
ThreadsPerChild 50
# Server-pool size regulation. Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to
# handle the current load, plus a few spare servers to handle transient
# load spikes (e.g., multiple simultaneous requests from a single
# Netscape browser).
# It does this by periodically checking how many servers are waiting
# for a request. If there are fewer than MinSpareServers, it creates
# a new spare. If there are more than MaxSpareServers, some of the
# spares die off. The default values are probably OK for most sites.
#MinSpareServers 5
#MaxSpareServers 20
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#MaxClients 150
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#Listen 3000
#Listen 12.34.56.78:80
# BindAddress: You can support virtual hosts with this option. This directive
# is used to tell the server which IP address to listen to. It can either
# contain "*", an IP address, or a fully qualified Internet domain name.
# See also the <VirtualHost> and Listen directives.
#BindAddress *
# 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.
# Please read the file README.DSO in the Apache 1.3 distribution for more
# details about the DSO mechanism and run `apache -l' for the list of already
# built-in (statically linked and thus always available) modules in your Apache
# binary.
# Note: The order in which modules are loaded is important. Don't change
# the order below without expert advice.
# Example:
# LoadModule foo_module libexec/mod_foo.dll
LoadModule mime_magic_module      modules/ApacheModuleMimeMagic.dll
LoadModule mime_module          modules/ApacheModuleMime.dll
LoadModule dbm_auth_module     modules/ApacheModuleAuthDBM.dll
LoadModule digest_auth_module     modules/ApacheModuleAuthDigest.dll
LoadModule anon_auth_module      modules/ApacheModuleAuthAnon.dll
LoadModule cern_meta_module      modules/ApacheModuleCERNMeta.dll
LoadModule digest_module      modules/ApacheModuleDigest.dll
LoadModule expires_module      modules/ApacheModuleExpires.dll
LoadModule headers_module      modules/ApacheModuleHeaders.dll
LoadModule proxy_module      modules/ApacheModuleProxy.dll
LoadModule speling_module      modules/ApacheModuleSpeling.dll
LoadModule status_module      modules/ApacheModuleStatus.dll
LoadModule info_module          modules/ApacheModuleInfo.dll
LoadModule usertrack_module      modules/ApacheModuleUserTrack.dll
LoadModule vhost_alias_module     modules/ApacheModuleVhostAlias.dll
LoadModule agent_log_module     modules/ApacheModuleLogAgent.dll
LoadModule referer_log_module     modules/ApacheModuleLogReferer.dll
LoadModule perl_module      modules/ApacheModulePerl.DLL
LoadModule fastcgi_module      modules/ApacheModuleFastCGI.dll
LoadModule onsint_module      modules/ApacheModuleOnsint.dll
LoadModule wchandshake_module     modules/ApacheModuleWchandshake.dll
ClearModuleList
AddModule mod_so.c
AddModule mod_onsint.c
AddModule mod_mime_magic.c
AddModule mod_mime.c
AddModule mod_access.c
AddModule mod_auth.c
AddModule mod_negotiation.c
AddModule mod_include.c
AddModule mod_autoindex.c
AddModule mod_dir.c
AddModule mod_cgi.c
AddModule mod_userdir.c
AddModule mod_alias.c
AddModule mod_env.c
AddModule mod_log_config.c
AddModule mod_asis.c
AddModule mod_imap.c
AddModule mod_actions.c
AddModule mod_setenvif.c
AddModule mod_isapi.c
AddModule mod_vhost_alias.c
AddModule mod_log_referer.c
AddModule mod_log_agent.c
AddModule mod_auth_anon.c
AddModule mod_auth_dbm.c
AddModule mod_auth_digest.c
AddModule mod_cern_meta.c
AddModule mod_digest.c
AddModule mod_expires.c
AddModule mod_headers.c
AddModule mod_proxy.c
AddModule mod_speling.c
AddModule mod_info.c
AddModule mod_status.c
AddModule mod_usertrack.c
AddModule mod_perl.c
AddModule mod_fastcgi.c
AddModule mod_wchandshake.c
<IfDefine SSL>
LoadModule ossl_module      modules/ApacheModuleOSSL.DLL
</IfDefine>
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
ExtendedStatus On
### Section 2: '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.
# Port: The port to which the standalone server listens. Certain firewall
# products must be configured before Apache can listen to a specific port.
# Other running httpd servers will also interfere with this port. Disable
# all firewall, security, and other services if you encounter problems.
# To help diagnose problems use the Windows NT command NETSTAT -a
Port 7777
Listen 7777
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents.
ServerAdmin [email protected]
# ServerName allows you to set a host name which is sent back to clients for
# your server if it's different than the one the program would get (i.e., use
# "www" instead of the host's real name).
# Note: You cannot just invent host names and hope they work. The name you
# define here must be a valid DNS name for your host. If you don't understand
# this, ask your network administrator.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address (e.g., http://123.45.67.89/)
# anyway, and this will make redirections work in a sensible way.
# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your
# machine always knows itself by this address. If you use Apache strictly for
# local testing and development, you may use 127.0.0.1 as the server name.
ServerName localhost
# 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 "E:\oracle\product\10.1.0\Companion\Apache\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
# permissions.
<Directory />
Options FollowSymLinks
AllowOverride None
</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 "E:\oracle\product\10.1.0\Companion\Apache\Apache\htdocs">
# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
# Note that "MultiViews" must be named explicitly --- "Options All"
# doesn't give it to you.
Options Indexes FollowSymLinks MultiViews
# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options", "FileInfo",
# "AuthConfig", and "Limit"
AllowOverride None
# Controls who can get stuff from this server.
Order allow,deny
Allow from all
</Directory>
# UserDir: The name of the directory which is appended onto a user's home
# directory if a ~user request is received.
# Under Win32, we do not currently try to determine the home directory of
# a Windows login, so a format such as that below needs to be used. See
# the UserDir documentation for details.
<IfModule mod_userdir.c>
     UserDir "E:\oracle\product\10.1.0\Companion\Apache\Apache\users\"
</IfModule>
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#<Directory /home/*/public_html>
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# </Limit>
# <LimitExcept GET POST OPTIONS PROPFIND>
# Order deny,allow
# Deny from all
# </LimitExcept>
#</Directory>
# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index. Separate multiple entries with spaces.
<IfModule mod_dir.c>
DirectoryIndex index.html
</IfModule>
# AccessFileName: The name of the file to look for in each directory
# for access control information.
AccessFileName .htaccess
# The following lines prevent .htaccess files from being viewed by
# Web clients. Since .htaccess files often contain authorization
# information, access is disallowed for security reasons. Comment
# these lines out if you want Web visitors to see the contents of
# .htaccess files. If you change the AccessFileName directive above,
# be sure to make the corresponding changes here.
# Also, folks tend to use names such as .htpasswd for password
# files, so this will protect those as well.
<Files ~ "^\.ht">
Order allow,deny
Deny from all
</Files>
# CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each
# document that was negotiated on the basis of content. This asks proxy
# servers not to cache the document. Uncommenting the following line disables
# this behavior, and proxies will be allowed to cache the documents.
#CacheNegotiatedDocs
# UseCanonicalName: (new for 1.3) With this setting turned on, whenever
# Apache needs to construct a self-referencing URL (a URL that refers back
# to the server the response is coming from) it will use ServerName and
# Port to form a "canonical" name. With this setting off, Apache will
# use the hostname:port that the client supplied, when possible. This
# also affects SERVER_NAME and SERVER_PORT in CGI scripts.
UseCanonicalName On
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
<IfModule mod_mime.c>
TypesConfig conf/mime.types
</IfModule>
# DefaultType is 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
# 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.
# mod_mime_magic is not part of the default server (you have to add
# it yourself with a LoadModule [see the DSO paragraph in the 'Global
# Environment' section], or recompile the server and include mod_mime_magic
# as part of the configuration), so it's enclosed in an <IfModule> container.
# This means that the MIMEMagicFile directive will only be processed if the
# module is part of the server.
<IfModule mod_mime_magic.c>
MIMEMagicFile conf/magic
</IfModule>
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
HostnameLookups Off
# 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 "|E:\oracle\product\10.1.0\Companion\Apache\Apache\bin\rotatelogs logs/error_log 43200"
# LogLevel: Control the number of messages logged to the error.log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# Alternate "common" format to use when fronted by webcache:
# LogFormat "%{ClientIP}i %l %u %t \"%r\" %>s %b %h" common_webcache
# When webcache is forwarding requests to OHS, %h becomes the IP of
# the originating webcache server and the real client IP is stored
# in the ClientIP header. The common_webcache format can be used
# in place of the common format when using webcache but with one
# important caveat: if clients are capable of bypassing webcache
# then it is possible to spoof the client IP by manually setting
# the ClientIP header so the %h field should be monitored in such
# an environment. Another alternative to specifying the ClientIP
# header directly in a LogFormat is to use the "UseWebCacheIp"
# directive:
# UseWebCacheIp On
# When this is specified, %h is derived internally from the ClientIP
# header and the access log format does not need to be modified.
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# 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 "|E:\oracle\product\10.1.0\Companion\Apache\Apache\bin\rotatelogs logs/access_log 43200" common
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#CustomLog logs/referer.log referer
#CustomLog logs/agent.log agent
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog logs/access.log combined
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
ServerSignature On
# 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.
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
<IfModule mod_alias.c>
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL. So "/icons" isn't aliased in this
# example, only "/icons/"..
Alias /jservdocs/ "E:\oracle\product\10.1.0\Companion\Apache\Jserv\docs/"
Alias /javacachedocs/ "E:\oracle\product\10.1.0\Companion\javacache\javadoc/"
Alias /icons/ "E:\oracle\product\10.1.0\Companion\Apache\Apache\icons/"
Alias /i/ "E:\oracle\product\10.1.0\Companion\Apache\Apache\images/"
<Directory "icons">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
<IfModule mod_perl.c>
     Alias /perl/ "E:\oracle\product\10.1.0\Companion\Apache\Apache/cgi-bin/"
</IfModule>
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname 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/ "E:\oracle\product\10.1.0\Companion\Apache\Apache\cgi-bin/"
# "E:\oracle\product\10.1.0\Companion\Apache\Apache/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "E:\oracle\product\10.1.0\Companion\Apache\Apache\cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
</IfModule>
# End of aliases.
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Format: Redirect old-URI new-URL
# Directives controlling the display of server-generated directory listings.
<IfModule mod_autoindex.c>
# FancyIndexing is whether you want fancy directory indexing or standard
# Note, add the option TrackModified to the IndexOptions default list only
# if all indexed directories reside on NTFS volumes. The TrackModified flag
# will report the Last-Modified date to assist caches and proxies to properly
# track directory changes, but it does not work on FAT volumes.
IndexOptions FancyIndexing
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*
AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core
AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
DefaultIcon /icons/unknown.gif
# AddDescription allows you to place a short description after a file in
# server-generated indexes. These are only displayed for FancyIndexed
# directories.
# Format: AddDescription "description" filename
#AddDescription "GZIP compressed document" .gz
#AddDescription "tar archive" .tar
#AddDescription "GZIP compressed tar archive" .tgz
# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
# HeaderName is the name of a file which should be prepended to
# directory indexes.
# If MultiViews are amongst the Options in effect, the server will
# first look for name.html and include it if found. If name.html
# doesn't exist, the server will then look for name.txt and include
# it as plaintext if found.
ReadmeName README
HeaderName HEADER
# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing. Shell-style wildcarding is permitted.
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
</IfModule>
# End of indexing directives.
# Document types.
<IfModule mod_mime.c>
# AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
AddEncoding x-compress Z
AddEncoding x-gzip gz tgz
# AddLanguage allows you to specify the language of a document. You can
# then use content negotiation to give a browser a file in a language
# it can understand.
# Note 1: The suffix does not have to be the same as the language
# keyword --- those with documents in Polish (whose net-standard
# language code is pl) may wish to use "AddLanguage pl .po" to
# avoid the ambiguity with the common suffix for perl scripts.
# Note 2: The example entries below illustrate that in quite
# some cases the two character 'Language' abbriviation is not
# identical to the two character 'Country' code for its country,
# E.g. 'Danmark/dk' versus 'Danish/da'.
# Note 3: In the case of 'ltz' we violate the RFC by using a three char
# specifier. But there is 'work in progress' to fix this and get
# the reference data for rfc1766 cleaned up.
# Danish (da) - Dutch (nl) - English (en) - Estonian (ee)
# French (fr) - German (de) - Greek-Modern (el)
# Italian (it) - Korean (kr) - Norwegian (no)
# Portugese (pt) - Luxembourgeois* (ltz)
# Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cz)
# Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja)
# Russian (ru)
AddLanguage ar .ar
AddLanguage da .dk .da
AddLanguage nl .nl
AddLanguage en .en
AddLanguage et .ee
AddLanguage fi .fi
AddLanguage fr .fr
AddLanguage de .de
AddLanguage el .el
AddLanguage es .es_ES .es
AddLanguage he .he .iw
AddLanguage hu .hu
AddCharset ISO-8859-8 .iso8859-8
AddLanguage it .it
AddLanguage ja .ja
AddCharset ISO-2022-JP .jis
AddLanguage ko .ko
AddLanguage kr .kr
AddCharset ISO-2022-KR .iso-kr
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddCharset ISO-8859-2 .iso-pl
AddLanguage pt .pt
AddLanguage pt-br .pt_BR .pt-br
AddLanguage ltz .lu
AddLanguage ca .ca
AddLanguage sk .sk
AddLanguage sv .sv
AddLanguage th .th
AddLanguage tr .tr
AddLanguage cz .cz .cs
AddLanguage ro .ro
AddLanguage ru .ru
AddLanguage zh-cn .zh_CN
AddLanguage zh-tw .zh_TW
AddCharset Big5 .Big5 .big5
AddCharset WINDOWS-1251 .cp-1251
AddCharset CP866 .cp866
AddCharset ISO-8859-5 .iso-ru
AddCharset KOI8-R .koi8-r
AddCharset UCS-2 .ucs2
AddCharset UCS-4 .ucs4
AddCharset UTF-8 .utf8
# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
<IfModule mod_negotiation.c>
LanguagePriority ar en da nl et fi fr de el it ja ko kr no pl pt pt-br ro ru ltz ca es sk sv th tr zh-cn zh-tw zh-cn
</IfModule>
# AddType allows you to tweak mime.types without actually editing it, or to
# make certain files to be certain types.
# For example, the PHP 3.x module (not part of the Apache distribution - see
# http://www.php.net) will typically use:
#AddType application/x-httpd-php3 .php3
#AddType application/x-httpd-php3-source .phps
# And for PHP 4.x, use:
#AddType application/x-httpd-php .php
#AddType application/x-httpd-php-source .phps
AddType application/x-tar .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 command (see below)
# If you want to use server side includes, or CGI outside
# ScriptAliased directories, uncomment the following lines.
# To use CGI scripts:
#AddHandler cgi-script .cgi
# To use server-parsed HTML files
#AddType text/html .shtml
#AddHandler server-parsed .shtml
AddType text/xml xbl
AddType text/x-component htc
# Uncomment the following line to enable Apache's send-asis HTTP file
# feature
#AddHandler send-as-is asis
# If you wish to use server-parsed imagemap files, use
#AddHandler imap-file map
# To enable type maps, you might want to use
#AddHandler type-map var
</IfModule>
# End of document types.
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
# MetaDir: specifies the name of the directory in which Apache can find
# meta information files. These files contain additional HTTP headers
# to include when sending the document
#MetaDir .web
# MetaSuffix: specifies the file name suffix for the file containing the
# meta information.
#MetaSuffix .meta
# Customizable error response (Apache style)
# these come in three flavors
# 1) plain text
#ErrorDocument 500 "The server made a boo boo.
# n.b. the single leading (") marks it as text, it does not get output
# 2) local redirects
#ErrorDocument 404 /missing.html
# to redirect to local URL /missing.html
#ErrorDocument 404 /cgi-bin/missing_handler.pl
# N.B.: You can redirect to a script or a document using server-side-includes.
# 3) external redirects
#ErrorDocument 402 http://some.other_server.com/subscription_info.html
# N.B.: Many of the environment variables associated with the original
# request will not be available to such a script.
# Customize behaviour based on the browser
<IfModule mod_setenvif.c>
# The following directives modify normal HTTP response behavior.
# The first directive disables keepalive for Netscape 2.x and browsers that
# spoof it. There are known problems with these browser implementations.
# The second directive is for Microsoft Internet Explorer 4.0b2
# which has a broken HTTP/1.1 implementation and does not properly
# support keepalive when it is used on 301 or 302 (redirect) responses.
BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
# The following directive disables HTTP/1.1 responses to browsers which
# are in violation of the HTTP/1.0 spec by not being able to grok a
# basic 1.1 response.
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0
</IfModule>
# End of browser customization directives
# Allow server status reports, with the URL of http://servername/server-status
# Change the ".your_domain.com" to match your domain to enable.
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from localhost localhost localhost
</Location>
# Allow remote server configuration reports, with the URL of
# http://servername/server-info (requires that mod_info.c be loaded).
# Change the ".your_domain.com" to match your domain to enable.
#<Location /server-info>
# SetHandler server-info
# Order deny,allow
# Deny from all
# Allow from .your_domain.com
#</Location>
# There have been reports of people trying to abuse an old bug from pre-1.1
# days. This bug involved a CGI script distributed as a part of Apache.
# By uncommenting these lines you can redirect these attacks to a logging
# script on phf.apache.org. Or, you can record them yourself, using the script
# support/phf_abuse_log.cgi.
#<Location /cgi-bin/phf*>
# Deny from all
# ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi
#</Location>
# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#<IfModule mod_proxy.c>
# ProxyRequests On
# <Directory proxy:*>
# Order deny,allow
# Deny from all
# Allow from .your_domain.com
# </Directory>
# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block
# ProxyVia On
# To enable the cache as well, edit and uncomment the following lines:
# (no cacheing without CacheRoot)
# CacheRoot "E:\oracle\product\10.1.0\Companion\Apache\Apache\proxy"
# CacheSize 5
# CacheGcInterval 4
# CacheMaxExpire 24
# CacheLastModifiedFactor 0.1
# CacheDefaultExpire 1
# NoCache a_domain.com another_domain.edu joes.garage_sale.com
#</IfModule>
# End of proxy directives.
### Section 3: Virtual Hosts
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
# Please see the documentation at <URL:http://www.apache.org/docs/vhosts/>
# for further details before you try to setup virtual hosts.
# You may use the command line option '-S' to verify your virtual host
# configuration.
# Use name-based virtual hosting.
#NameVirtualHost *
#NameVirtualHost 12.34.56.78:80
#NameVirtualHost 12.34.56.78
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#<VirtualHost *>
# ServerAdmin [email protected]
# DocumentRoot /www/docs/dummy-host.example.com
# ServerName dummy-host.example.com
# ErrorLog logs/dummy-host.example.com-error_log
# CustomLog logs/dummy-host.example.com-access_log common
#</VirtualHost>
#<VirtualHost default:*>
#</VirtualHost>
SetEnv PERL5LIB "E:\oracle\product\10.1.0\Companion\perl\5.6.1\lib:E:\oracle\product\10.1.0\Companion\perl\site\5.6.1\lib"
<IfModule mod_perl.c>
# Perl Directives
# PerlWarn On
# PerlFreshRestart On
# PerlSetEnv PERL5OPT Tw
# PerlSetEnv PERL5LIB "E:\oracle\product\10.1.0\Companion\perl\5.6.1\lib:E:\oracle\product\10.1.0\Companion\perl\site\5.6.1\lib"
PerlModule Apache
# PerlModule Apache::Status
PerlModule Apache::Registry
# PerlModule Apache::CGI
# PerlModule Apache::DBI
# PerlRequire
<Location /perl>
SetHandler perl-script
PerlHandler Apache::Registry
AddHandler perl-script .pl
Options +ExecCGI
PerlSendHeader On
</Location>
# <Location /perl-status>
# SetHandler perl-script
# PerlHandler Apache::Status
# order deny,allow
# deny from all
# allow from localhost
# </Location>
</IfModule>
#Protect WEB-INF directory
<DirectoryMatch /WEB-INF/>
Order deny,allow
Deny from all
</DirectoryMatch>
# Setup of FastCGI module
<IfModule mod_fastcgi.c>
Alias /fastcgi/ "E:\oracle\product\10.1.0\Companion\Apache\fastcgi/"
ScriptAlias /fcgi-bin/ "E:\oracle\product\10.1.0\Companion\Apache\Apache\fcgi-bin/"
<Directory "E:\oracle\product\10.1.0\Companion\Apache\Apache\fcgi-bin">
     AllowOverride None
     Options None
     Order allow,deny
     Allow from all
     SetHandler fastcgi-script
     <IfModule mod_ossl.c>
     SSLOptions +StdEnvVars
     </IfModule>
</Directory>
</IfModule>
# Include the configuration for Apache JServ 1.1
#include "E:\oracle\product\10.1.0\Companion\Apache\Jserv\conf\jserv.conf"
# Setup of oprocmgr module.
# This directive identifies each remote apache instance that will be
# sending requests to processes (e.g., JServs), managed by local Apache
# instances. This directive is used by the local process manager to share
# routing information with remote apache instances via non-SSL HTTP messages.
# The directive is repeated for each remote apache instance that will be
# sending requests. The ProcNode directive that refers to the local apache
# instance will be ignored, but may be supplied to facilitate uniformity
# in configuration across apache instances. Arguments to the ProcNode must
# be sufficient to reach the remote instance of apache via non-SSL HTTP
# messages. It is not considered an error if the remote apache instance is
# unreachable, as no assumption is made about the starting order or
# availability of apache instances.
# Syntax: ProcNode <hostname> <port>
# Example: ProcNode abc.com 7777
<IfModule mod_oprocmgr.c>
<Location /oprocmgr-service>
SetHandler oprocmgr-service
Order deny,allow
Deny from all
Allow from localhost localhost localhost
</Location>
<Location /oprocmgr-status>
SetHandler oprocmgr-status
Order deny,allow
Deny from all
Allow from localhost localhost localhost
</Location>
</IfModule>
# Include the mod_oc4j configuration file
include "E:\oracle\product\10.1.0\Companion\Apache\Apache\conf\mod_oc4j.conf"
# Include the mod_dms configuration file
include "E:\oracle\product\10.1.0\Companion\Apache\Apache\conf\dms.conf"
# Loading rewrite_module here so it loads before mod_oc4j
LoadModule rewrite_module      modules/ApacheModuleRewrite.dll
# Include the SSL definitions and Virtual Host container
include "E:\oracle\product\10.1.0\Companion\Apache\Apache\conf\ssl.conf"
# Include the mod_osso configuration file
#include "E:\oracle\product\10.1.0\Companion\Apache\Apache\conf\mod_osso.conf"
# Include the Oracle configuration file for custom settings
include "E:\oracle\product\10.1.0\Companion\Apache\Apache\conf\oracle_apache.conf"
------------------------------------------------------------------------------------------------------------------

Firstly, there's no such thing as Apache 9.3, there's Apache 1 (and subversions) and Apache 2 (and subversions). Your error message -
Oracle-HTTP-Server/1.3.28Shows you're using Apache 1.3.28
Secondly, I'm confused by your comment -
I do not have Apache 9.3 or higher but I think oracle should offer this in its companion CDOracle does offer the Apache server, if you're saying you didn't get it from Oracle then where did your Apache server come from?
Thirdly, I notice from your config file -
ErrorLog "|E:\oracle\product\10.1.0\Companion\Apache\Apache\bin\rotatelogs logs/error_log 43200"That you're piping the logs through rotatelogs, are you sure the logfiles haven't just been renamed?

Display image in email

I would like to be able to add an image (the firm logo) in the body of an apex/htmldb email, and have it shown in the email and not be blocked by Outlook. Is this possible? Thanks, Jan

Hi Gopi,
Thanks for your reply.
when i open the email in outlook, i am getting 'If there are problems with how this message is displayed, click here to view in a web browser'. So when i view in browser(IE) on clikc of this link, the email opened from the temporary internet files(AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.Outlook\54AMMRVF\email (4).mht)
Here i am able to see the image.
Suppose if i forward this email to my gmail and opening in a browser, this time i cant see the image. i am getting only the blank space there.

ORA-01403: no data found when calling a web service from HTMLDB

I am working through Section 6 How to Implement a Web Service of the HTML DB 2 Day Developer tutorial. I can get the first example to work but not the second one. I am able to add the web reference and create the form and report. However, when I run the page and click submit, I get ORA-01403: no data found.
When I test the service, this is what shows in the Message Request:
<?xml version='1.0' encoding='UTF-8'?><SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Header><namesp1:Header xmlns:namesp1="http://www.xignite.com/services/"><namesp1:Username xsi:type="xsd:string"></namesp1:Username><namesp1:Password xsi:type="xsd:string"></namesp1:Password><namesp1:Tracer xsi:type="xsd:string"></namesp1:Tracer></namesp1:Header></SOAP-ENV:Header><SOAP-ENV:Body><namesp1:ListFuturesByExchange xmlns:namesp1="http://www.xignite.com/services/"><namesp1:Exchange xsi:type="xsd:string">NYMEX</namesp1:Exchange></namesp1:ListFuturesByExchange></SOAP-ENV:Body></SOAP-ENV:Envelope>
Nothing shows in the Message Response.
I have also tried to call a simple web service that I created in .NET. It exhibits the same behavior. I am able to add the reference and create the form. But when I click the submit button, I get ORA-01403: no data found.
Windows 2000
HTMLDB 2.0.0.00.49
Oracle9i 9.2.0.6.0
Any help will be greatly appreciated.

I'm having a similar problem!, Although, distressing as it is to observe the lack of response this thread has had for 9 months, I'm still seeking help here!
I created a web service reference according to the following WSDL : "http://OgAppExpress:[email protected]:5555/invoke/OgAdminUtils.pub:WSDL_HLR" (operation name="getSubscriberInfoByMSISDN") and a form on that web service, all of which went very nicely. But! When I ran the form, inserted the value ("3546933599") into the parameter and pressed submit.... => "ORA-01403: no data found"
The debug action displays very limited information and sheds no light on the problem :( Multiple attempts, on recreating the project from scratch, have resulted in the same utter failure! Needless to say, this nulls the affect of my Prozac proscription....
Is there anybody out there who can help me and defend APEX's reputation?

HTMLDB 1.6 load_de.sql bug ?

I installed HTMLDB 1.6 as an upgrade to the one on the companion CD.
Since my native language is german, I like to have HTMLDB speaking german language with me. So I opened sqlplus as sys with sysdba privs, altered the session schema to FLOWS_010600 and started the Language update via @load_de.
after some working statements I got the following error message and the installation stops:
Error page=4316.4003 item="F4000_P4316_VALIDATION_TYPE" id="22211144053.4003"
declare
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "SYS.OWA_UTIL", line 325
ORA-06512: at "SYS.HTP", line 1322
ORA-06512: at "SYS.HTP", line 1397
ORA-06512: at "SYS.HTP", line 1689
ORA-06512: at "FLOWS_010600.WWV_FLOW_API", line 3191
ORA-01461: can bind a LONG value only for insert into a LONG column
ORA-06512: at line 69
Any hints ?
cu Pete

Peter,
I believe there's a bug lurking in HTML DB somewhere. Your situation is identical to the one described in:
Re: Installation Error 1.6
The odd thing is, we have been unable to reproduce it (loading with NLS_LANG german_germany.al32utf8 works just fine). I also asked a couple colleagues in Germany if they've had any difficulty, and they have never encountered this.
If you would be so kind, could you please let me know the following information:
1) The database version you are using
2) The operating system (name and version)
3) Your database character set
4) The version and operating system of SQL*Plus you're using (in the event you're doing this installation remotely)
If you feel uncomfortable posting this on OTN, could you please just e-mail this info to [email protected]?
Thanks in advance for any assistance you can provide.
viele GrÃ¼Ãe,
Joel

Primary Key in subject line of email

I'm sending emails from my application and I want the Primary Key or the number that is being generated to be in the suject line of the email...
I have the following code, but nothing is showing up in the subject line besides TEST EMAIL- NEW PTA NOTIFICATION :
The P1091_PTA_ID is the primary key that I'm trying to send in the email and its not showing up in the body or the subject line...
DECLARE
l_body CLOB;
v_empl_email_addr varchar2(200);
v_empl_email_addr2 varchar2(200);
BEGIN
l_body := 'An PTA has been created. Please log into the database at http://dvlp01.bhti.com:7777/pls/htmldb to continue processing.'||utl_tcp.crlf||'Your PTA number is :'||to_char(:P1091_PTA_ID)
v_empl_email_addr := '[email protected]'||','||'[email protected]'||','||'[email protected]'||','||'[email protected]';
v_empl_email_addr2 := (:P1091_USER_ID);
htmldb_mail.send(
p_to => v_empl_email_addr,
p_from => v_empl_email_addr2,
p_body => l_body,
p_subj => 'TEST EMAIL - New PTA Notification -'||to_char(:P1091_PTA_ID));

Maybe try seomthing like this -
p_subj => 'TEST EMAIL - New PTA Notification -'||:P1091_PTA_ID||' created';
I changed the variable format, and added literals at the end, just for checking.

Email with attachment - Urgent help required ..................... :(

Hi Great frnds,
I am in trouble and i need help from you guys.... :(
My problem is i want to edit RTF or doc (appriciate if I can edit PDF) file which I stored in DB and send it as email attachment.
Mean to say, i'll upload RTF or DOC file to apex DB . Its a kind of letter .
And if some conditions reached i need to edit that file ( need to put name , sex , address etc) and send it as an email attachment to that person.
And i dont know how to perform this task….....
I got one package but i m not able to use that for sending attachment , normal mails are working fine . Here is that link
http://www.oracle.com/technology/sample_code/tech/pl_sql/htdocs/Utl_Smtp_Sample.html
Can anybody help me on this ……………. L

Kalesh,
As a start you can check out the mail merge app at http://htmldb.oracle.com/pls/otn/f?p=18326:44:::::P44_ID:1682. It won't work with pdf's. As for sending email attachments google on demo_mail that gives you a base package that will send attachments. You can call it as follows...
create or replace procedure pdf_mail(
p_sender varchar2, -- sender, example: 'Me '
p_recipients varchar2, -- recipients, example: 'Someone '
p_subject varchar2, -- subject
p_text varchar2, -- text
p_filename varchar2, -- name of pdf file
p_blob blob -- physcial pdf file
) is
conn utl_smtp.connection;
i number;
len number;
BEGIN
conn := mail_pkg.begin_mail(
sender => p_sender,
recipients => p_recipients,
subject => p_subject,
mime_type => mail_pkg.MULTIPART_MIME_TYPE);
mail_pkg.begin_attachment(
conn => conn,
mime_type => 'application/pdf',
inline => TRUE,
filename => p_filename,
transfer_enc => 'base64');
-- split the Base64 encoded attachment into multiple lines
i := 1;
len := DBMS_LOB.getLength(p_blob);
WHILE (i < len) LOOP
IF(i + mail_pkg.MAX_BASE64_LINE_WIDTH < len)THEN
UTL_SMTP.Write_Raw_Data (conn,
UTL_ENCODE.Base64_Encode(
DBMS_LOB.Substr(p_blob, mail_pkg.MAX_BASE64_LINE_WIDTH, i)));
ELSE
UTL_SMTP.Write_Raw_Data (conn,
UTL_ENCODE.Base64_Encode(
DBMS_LOB.Substr(p_blob, (len - i)+1,i)));
END IF;
UTL_SMTP.Write_Data(conn, UTL_TCP.CRLF);
i := i + mail_pkg.MAX_BASE64_LINE_WIDTH;
END LOOP;
mail_pkg.end_attachment(conn => conn);
mail_pkg.attach_text(
conn => conn,
data => p_text,
mime_type => 'text/html');
mail_pkg.end_mail( conn => conn );
END;
Keep Smiling,
Bob R

How to pass variable from link in email into HTML DB

On our helpdesk application, we want to send emails to impacted customers, and have them click on a link in the email (that contains their ticket number) to get to a response form in HTML DB without having to copy and paste or re-enter that ticket number. How would I do this? At this point I don't know if the email will come from Outlook or from HTML DB.
Also, I see that there is a version of HTML DB for Windows machines. Does it interface with MS Exchange?
Thank you.

Hi,
I have a HR Incident Reporting HTMLDB application that sends details of assigned calls to the assignee's email account, detailing the issue and including a URL to the relevant page in the application.
When the user clicks on the URL (appears as a link in their email) they go straight into the relevant application page (via login screen).
We use lotus notes, but I see no reason Exchange would work in the same way.
Cheers,
Rob Chalton

How to attach a file to a mail using htmldb

Hi all,
can u help me how to attach a file in htmldb.
iam able to send a mail using the inbuilt package but unable to attach a file.
advance thanks in helping out.

The APEX_MAIL package doesn't support sending emails with attachments.
See Send E-Mail with attachment from HTML DB for some alternatives.

Emails In HtmlDB

Similar Messages

Maybe you are looking for