Virtual Hosts configuration in JServ.conf

I was trying to configure virtual hosts in the Jserv.conf file like this:
NameVirtualHost 138.1.104.151
# directives for vhost1
<VirtualHost 138.1.104.151:10001>
ServerName gsyang-lap.xyz.com
<IfModule mod_jserv.c>
ApJServDefaultHost gsyang-lap.xyz.com
ApJServProperties "C:\ORCL\ias\Apache\Jserv\conf\jserv_1.properties"
ApJServLogFile "C:\ORCL\ias\Apache\Jserv\logs\mod_jserv_1.log"
</IfModule>
</VirtualHost>
# directives for vhost2
<VirtualHost 138.1.104.151:10002>
ServerName gsyang-lap.us.oracle.com
<IfModule mod_jserv.c>
ApJServDefaultHost gsyang-lap.xyz.com
ApJServProperties "C:\ORCL\ias\Apache\Jserv\conf\jserv_2.properties"
ApJServLogFile "C:\ORCL\ias\Apache\Jserv\logs\mod_jserv_2.log"
</IfModule>
</VirtualHost>
After I saved the file and tried to stop/restart the Apache server, I got any warning, saying:"NameVirtualHosts 138.1.104.151 has not virtual hosts". Any idea as to how to fix this problem? Thanks in advance.
Sunny

Hi,
This seems to be a SO error more than an IAS error.
Have you tried stopping the iAS Server and looking for and old process still running?
It may not be a problem with the file open limit, but may be the one it is trying to user is still in use by and old process.
Carlos

Similar Messages

Webdav/virtual host configuration problem

Hi folks,
I have a web server behind firewall, which redirects port 80 to my server's internal IP, 192.168.6.222. I did setup 3 virtual domains there:
blogs.domain.com at *
wiki.domain.com at *
dav.domain.com at *
each site has different root and dav site has its own realm set.
I just found that virtual domains are not working and dav.domain.com doesn't work at all. When I switch dav.domain.com to 192.168.6.222, it eats all connections and even for blogs site shows login sheet.
$ httpd -S
Processing config directory: /etc/httpd/sites/*.conf
Processing config file: /etc/httpd/sites/0000any_80blogs.domain.com.conf
Processing config file: /etc/httpd/sites/0001any_80wiki.domain.com.conf
Processing config file: /etc/httpd/sites/0002any_80dav.domain.com.conf
Processing config file: /etc/httpd/sites/virtualhostglobal.conf
VirtualHost configuration:
wildcard NameVirtualHosts and default servers:
*:80 is a NameVirtualHost
default server blogs.domain.com (/etc/httpd/sites/0000any_80blogs.domain.co.conf:3)
port 80 namevhost blogs.domain.com (/etc/httpd/sites/0000any_80blogs.domain.co.conf:3)
port 80 namevhost wiki.domain.com (/etc/httpd/sites/0001any_80wiki.domain.com.conf:3)
port 80 namevhost dav.domain.com (/etc/httpd/sites/0002any_80dav.domain.com.conf:3)

Hi Simon
You are not doing anything wrong. Setting up a virtual host has obviously
worked as you can access it. You still have to specify the port number as
it is not running on the standard port 80 that your browser assumes if you
do not explicitly state it.
regards
Nick
"Simon Pierre NOLIN" <[email protected]> wrote in message
news:3be7f4f1$[email protected]..
>
Hi!
I try to configure a virtual host but it doesn't work. I have create it(name=myVirtualHost,
virtual host names=gandalf.foo.com). I assigne it to my managed server(port 5021).
In the managed server i have a web application calls "rings". If i typethe url,
gandalf.foo.com/rings/login : 404 not found error. BUT if i usegandalf.foo.com:5021/rings/login
: it works.
Can someone explain me what i do wrong?
Regards
Simon Pierre NOLIN

Virtual Hosts - Configured but still not working -

I configured virtual hosts in my portal so that multiple companies can access there portal with their own domain name. It seems to work fine when i give the a direct link to the site. But some times the original server name is written back on the urls. For example, i am in www.abc.com/portal/page/portal/some_page and it will go back to www.original_server_name.com /pls/portal/page/portal while i am browsing. It doesn't do this for all of them. Is there something i need to set up??

Ok,
I reinstalled a new oracle portal from scratch and followed the virtual hosts guide by dannorris.com which stated that there where errors in the oracle documentation. After following the guide, the virtual hosts work when you go to the http://virtual_host_name.com. It sends you to the "Welcome to Oracle Application Server" page. However when you go and click the link that states
"To manage and monitor Oracle Application Server Portal, log on to Oracle Application Server Portal:
username: portal
password: ias_admin password specified during install"
it kicks you back to the original host name url. Any ideas??
I have multiple clients that need to login and see their domain names only and not the real server name.

Weblogic virtual host configuration

Hi,
Can anyone explain to me what is virtual host.
what is the significance and purpose of the same.
in what scenario should we configure a virtual host.
and what is the benefit of the same.
from the documentation i did not understand the concept.
Thanks in advance.

I think this page is pretty clear. Does this help?
http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/pagehelp/Corecorevirtualhosttabletitle.html
A virtual host is a set of host names to which WebLogic Server instances (servers) or clusters respond. When you use virtual hosting, you use DNS to specify one or more host names that map to the IP address of a server or cluster. You also specify which Web applications are served by each virtual host.

10.5.1 Broken Mail Server - virtual host configuration

Hi,
I have been trying to set up my mail server (new 10.5.1 build) to run with virtual hosts. I read pterobyte's tutorial ( Making Virtual Mail Users in OS X 10.4/10.5 Server) and implemented his suggested workarounds. However, it doesn't seem to have worked. I am now concerned that I have screwed things up beyond reprieve and need help to get it working again.
To give a start, I have included my postconf output below:
swallowtail:postfix serverconfig$ postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mapsrbldomains =
messagesizelimit = 10485760
mydestination = $myhostname,localhost.$mydomain,localhost,inovaplus.com
mydomain = inovaplus.com
mydomain_fallback = localhost
myhostname = swallowtail.inovaplus.com
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relayhost = mailfilter.fastnet.co.uk
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permit_mynetworks rejectrblclient sbl-xbl.spamhaus.org rejectrblclient zen.spamhous.org permit
smtpdpw_server_securityoptions = none
smtpdrecipientrestrictions = permitmynetworks,reject_unauthdestination,permit
smtpduse_pwserver = no
unknownlocal_recipient_rejectcode = 550
virtualaliasdomains = hash:/etc/postfix/virtual_domains
virtualaliasmaps = hash:/etc/postfix/virtual
virtualmailboxdomains = hash:/etc/postfix/virtual_domains
virtual_transport = lmtp:unix:/Volumes/Private/Mail/socket/lmtp

Same issue here. I am current on all system updates. I have noticed this with any photoshop cs3 jpeg file. When using "mail", attached photoshop jpeg files show up as a plain text document "What???" Using Automator produces the same results. I did not have this problem with 10.5.1. I can't mail out any photoshop jpeg files?!@%* I just got off the phone with apple tech support and they told me that Adobe has not yet updated their software to comply with Leopard. Come on. Cover flow in Leopard 10.5.2 is still not working with Adobe photoshop jpeg files either. They Still show up pixelated. Yes, I know the work around by going into photoshop/preferences/file handling/image previews: Never Save. Yea, sure that works, but that is something that not any Mac user should have to do. I have had more problems dealing with pictures on my Mac than my Pc by far. Anybody else? Solution? Better Operating System?

Tomcat Virtual Host Configuration on windows 2000

Dear Reader,
I am using Tomcat 4.1 with JDK1.4. Currently i have 3 projects.
The navigation for these is ....
http://localhost:9090/Shopping/
http://localhost:9090/Bank/
http://localhost:9090/Sample/
Now,
I need these links as
http://Shopping:9090 or www.shopping.com is local system....
http://bank:9090 or www.bank.com is local system....
http://Sample:9090 or www.sample.com is local system....
I am using Windows OS. Please Help
Advance Thanks.
Rengaraj.R

Also should have mentioned that to get the mappings for the individual web apps (/Shopping, /bank and /Sample) after the localhost portion you need to add a context file for each web app to the tomcat configuration files (location below).
The files will live in /tomcat/Conf/Catalina/localhost/"the name of your web app". As an example something like:
<Context crossContext="true" docBase="/var/webapps/mybankapp" path="/bank" reloadable="true">
</Context>
This is placed in a file called: bank.xml
Edited by: PaulOckleford on Jun 29, 2009 4:14 AM
Edited by: PaulOckleford on Jun 30, 2009 2:26 AM Wrong xml file name

Tomcat virtual host configuration

Next stupid question from me again.
I'm trying to configure my Tomcat to handle several websites. Both websites are going to be JSP/JAVA driven.
Currently I'm struggling to figure out how to tell Tomcat to use application for Host by default.
I'm doing the following:
<Host name="gnum.info" appBase="D:\Users\Alex\web.gnum.info" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false">
<Alias>www.gnum.info</Alias>
<Context path="gnum.info" docBase="" debug="0" reloadable="true" cookies="true" />
</Host>
I triend different variations from having NO <Context> included to
1. <Context path="gnum.info" docBase="" debug="0" reloadable="true" cookies="true" />
2. <Context path="gnum.info" docBase="gnum.info" debug="0" reloadable="true" cookies="true" />
I'm always ending up with empty response for "www.gnum.info" (you can see it yourself).
Typing "www.gnum.info/gnum.info" gets back with what I want to see.
BUT
I'd like to see it typing "www.gnum.info" without "/gnum.info"...
Could anybody tell me how to achieve that?

Hi Gnum,
Just change your context path to
<Context path="/" docBase="" debug="0" reloadable="true" cookies="true" />
note the "/" instead of "gnum.info"
Kevin

Configuring default web apps for virtual hosts

Hi,
This posting is meant save time for anyone trying to specify a default web app
for each of their virtual hosts (as opposed to specifying a default web app for
each of their wl servers). This applies to weblogic 6.1, on NT. (I haven't tried
this on other platforms).
If you are trying to use the admin console to do this, give up. It's not possible.
The "Virtual Host/Configuration" window lets you specify everything about that
vhost configuration EXCEPT a default web app. (The "Default Web Application" drop
down menu will always have only one option to choose from: "none").
Instead, shutdown your server, and edit your domain's config.xml file manually.
Attached is an example config file that specifies that the web app "kz" should
be the default web app for the vhost "wl.kz.com", and that the web app "kahuna"
should be the default web app for the vhost "www.kahuna.com".
Hope this helps,
Brian O'Donnell
Lead Developer, Learning Network
[config.xml]

Hi,
Is it possible to configure default web appls for virtual hosts
with Weblogic 6.0 on NT platform? I tried to configure the configure.xml as Brian
did, it doesnot work. I am just wondering if there's any other possible way to
do this.
Thanks.
Mei
"Brian O'Donnell" <[email protected]> wrote:
>
>
>
Hi,
This posting is meant save time for anyone trying to specify a default
web app
for each of their virtual hosts (as opposed to specifying a default web
app for
each of their wl servers). This applies to weblogic 6.1, on NT. (I haven't
tried
this on other platforms).
If you are trying to use the admin console to do this, give up. It's
not possible.
The "Virtual Host/Configuration" window lets you specify everything about
that
vhost configuration EXCEPT a default web app. (The "Default Web Application"
drop
down menu will always have only one option to choose from: "none").
Instead, shutdown your server, and edit your domain's config.xml file
manually.
Attached is an example config file that specifies that the web app "kz"
should
be the default web app for the vhost "wl.kz.com", and that the web app
"kahuna"
should be the default web app for the vhost "www.kahuna.com".
Hope this helps,
Brian O'Donnell
Lead Developer, Learning Network

The essential guide to DW cs4... by D. Powers: when from wamp to xampp+virtual host and having problems :(

Following the book in chapter 2 I think Ivé followed everything correctly, but have encluded all the things I've edited below.
I was using wamp with no problems but after trying to set up a virtual host and now using xampp im abit lost its probabsomething stupid but I can find the prob.
(This post is abit long and dragged out so I used some colour to try ease the reading..)
When I try to view a dynamic page in live view or in firefox I get the following error:
**when using:
<VirtualHost *:80>
DocumentRoot c:/xampp/htdocs
ServerName localhost
</VirtualHost>
result:
Access forbidden!
You don't have permission to access the requested object.     It is either read-protected or not readable by the server.
If you think this is a server error, please contact the webmaster.
Error 403
thegoodlife
2009/10/13 12:47:48 PM
Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0
*when using:
<VirtualHost *:80>
DocumentRoot c:/htdocs
ServerName localhost
</VirtualHost>
result:
Object not found!
The requested URL was not found on this server.          If you entered the URL manually please check your     spelling and try again.
If you think this is a server error, please contact the webmaster.
Error 404
thegoodlife
2009/10/13 12:32:58 PM
Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0
This is what I've done, blue indicating where I have or was meant to edit, red being the relivant context. (hope it helps )
1. Created a new folder called htdocs (C:\htdocs)
2. Changed the pathname to:
# 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:/htdocs"
and
# This should be changed to whatever you set DocumentRoot to.
<Directory "C:/htdocs">
3. Created vhosts folder; with a sub-folder called thegoodlife (C:\vhosts)
4. entered new vhost:
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host
127.0.0.1 localhost
127.0.0.1 dwcs4
127.0.0.1 thegoodlife
127.0.0.1 bin.errorprotector.com ## added by CiD
5.It says uncomment the command by removing the #, (Supplemental configuation.), but this is the origional file; already uncommented?
# Real-time info on requests and configuration
Include "conf/extra/httpd-info.conf"
# Virtual hosts
Include "conf/extra/httpd-vhosts.conf"
# Distributed authoring and versioning (WebDAV)
Include "conf/extra/httpd-dav.conf"
6.Set the permissions and changed the code as instructed, unsing (c:/xampp/htdocs) as advised.
# You may use the command line option '-S' to verify your virtual host
# configuration.
<Directory C:/vhosts>
Order Deny,Allow
Allow from all
</Directory>
# Use name-based virtual hosting.
##NameVirtualHost *:80
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
<VirtualHost *:80>
DocumentRoot c:/xampp/htdocs
ServerName localhost
</VirtualHost>
<VirtualHost *:80>
DocumentRoot c:/vhosts/dwcs4
ServerName dwcs4
</VirtualHost>
<VirtualHost *:80>
DocumentRoot c:/vhosts/thegoodlife
ServerName thegoodlife
</VirtualHost>
Then creating the site definition:
local root forlder: C:\htdocs\thegoodlife\
testing server folder: C:\vhosts\thegoodlife\
URL prefix: http://thegoodlife/
hope i've covered all area's where I could have gone wrong

Just one more thing - the description of what i did while first Kernel appeared:
Happened 2 days ago. Wasn't turning it off for like a day, only sleep mode by closing it. Worked fine all day, wasn't doing anything, except for checking mail 2-3 times and having windows 7 virtual machine opened but doing nothing, everything was going fine. Then closed it without turning off.
Opened 3-4 hours later, everything was working fine for 30 minutes of checking mail, then Kernel appeared. After that pretty much everything i did is described in part 1-5.
Note: all the time MBP was connected to internet via wifi, so updates to both MBP and virtual machine of all programs were possible.
I only shared downloads and desktop folders, so windows couldn't have access to system folder of Mac Os.
Hope this might help...Thanks again.

Virtual Hosts for Load Balancing

Hi all,
So I have two identical servers, that have SOA Suite installed pointing to the same database. (RHEL 4) I have configured the mod_oc4j.conf file for round robin, and then I created a virtual host on the httpd.conf file to point to the load balance hardware.
It worked! But with a slight issue. The Load Balance server is orasoaqa.tmpw.net:7777, which opens the main Application Server page. However, when I click on BPEL console, or ESB, it continues using the orasoaqa.tmpw.net:7777 virtual, which of course, breaks even trying to login.
What am I missing here? Here's the entry I added to mod_oc4j.conf:
Oc4jSelectMethod roundrobin:local
Here's the entry I added to the httpd.conf on server 1:
Port 7777
Listen 7777
NameVirtualHost XXX.XXX.XXX.XXX:7777
<VirtualHost orasoaqaapp101.ma.tmpw.net:7777>
ServerName orasoaqa.tmpw.net
ServerAlias orasoaqaapp101.ma.tmpw.net
Port 7777
</VirtualHost>
and on server 2:
Port 7777
Listen 7777
NameVirtualHost XXX.XXX.XXX.XXX:7777
<VirtualHost orasoaqaapp102.ma.tmpw.net:7777>
ServerName orasoaqa.tmpw.net
ServerAlias orasoaqaapp102.ma.tmpw.net
Port 7777
</VirtualHost>
Yes, the port for Application Server and the port on the Load Balancer are exactly the same, I hope this isn't the issue.
Any help would be greatly appreciated.
Thanks!
Message was edited by:
CooperHawkes

Seeing that you have an external load balancer available, you really should not be trying software load balancing. Windows NLBS is a software based load balancing and is not really dependent on the physical/virtual hosting of the OS. There are certain gotchas
w.r.t the NLB modes since they depend on network protocols such as arp, propagation of MAC addresses and usage of the MAC in the L2 routing tables of network devices.
You should be taking the help of the cloud service provider as ONLY they would have an understanding of their underlying networking infrastructure such as VLANS. addressing, routing rules and such.
You could also refer to the VMware support forum for KB's such as
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006580
Most importantly, NLBS is a base OS related service and you're more likely to get a response in the Windows Server Forum. In the specific case of BizTalk, the Windows NLB is only used for hosting the out of process services such as those associated with
HTTP/s Receive, orchestration published as schemas, web services (asmx) and/or WCF endpoints.
Regards.

Virtual Hosts Issues

I have a fresh install of Mac OS X 10.4 Server, and am having some problems setting up virtual hosts. I have 2 sites I'd like to host. Both are configured under the Sites tab of Web services. Both are pointing to different web folders. Both are using the same IP (the only IP this server has), and both are using port 80.
Regardless of which site I try to access, I always get the first sites default page. I've already checked to make sure it's not a caching issue, and I have turned on the vhostaliasmodule.
I've read through some old posts on this subject, but haven't found a solution that works yet. Any one know how to resolve this? Thanks!

Ha!
I finally figured it out.
In httpd.conf, at the end of the file there's a section stating to use all of the .conf files in the /etc/httpd/sites directory. Seemingly, Mac OS X Server sets up every site as a virtual host, and creates a .conf file for each site in this directory. The issue ended up being that the directive in http.conf was:
Include "/etc/httpd/sites/*.conf"
I removed the quotes and both of my virtual hosts are working now.
I don't know if this is a bug, or if there's supposed to be some other way to make this work.
Thanks for the help from all of you!

Virtual Hosts in Apache HTTP Server

How to configure virtual hosts in Apache HTTP Server httpd.conf file.
If I want to access my server with some other name(alias), how can I do this ?
Suggestions in this matter would be highly helpful.
Thanks
Vidhyut Arora

Following is a note explaining how to setup
Virtual hosts.
Hope this helps
Ranga
Note:70647.1
Subject: Apache Server Virtual Hosting
Last Revision Date: 07-JUN-2001
PURPOSE
This document discusses considerations for setting up virtual hosts on an
Apache machine, to include how to get the hostname working and how to
configure Apache.
SCOPE & APPLICATION
The information in this document is intended for those who manage multiple sites
using an Apache machine.
REFERENCES
First published in Apache Week issue 31 (6th September 1996)
Last update 20th September 1998
Using Virtual Hosts
Virtual Hosts let you run multiple independent Web sites on a single host with
a single Apache setup.
One of the most important facilities in Apache is its ability to run virtual
hosts. This is now the essential way to run multiple Web services - each with
different host names and URLs - that appear to be completely separate sites.
This is widely used by ISPs, hosting sites and content providers who need to
manage multiple sites but do not want to buy a new machine for each one.
Picking an IP address
There are two types of virtual hosts: IP-based and non-IP-based. The former is
where each virtual host has its own IP address. You must have a new IP address
for each virtual host you want to set up, either from your existing allocation
or by obtaining more from your service provider. When you have extra IP
addresses, you tell your machine to handle them. On some operating systems, you
can give a single ethernet interface multiple addresses (typically with an
fconfig alias command). On other systems, you must have a different
physical interface for each IP address (typically by buying extra ethernet
cards).
IP addresses are a resource that costs money and are increasingly difficult to
get, so modern browsers can now also use 'non-IP' virtual hosts. This
lets you use the same IP address for multiple host names. When the server
receives an incoming Web connection, it does not know the hostname that was used
in the URL. However, the new HTTP/1.1 specification adds a facility where the
browser must tell the server the hostname it is using, on the Host: header. If
an older browser connects to a non-IP virtual host, it does not send the Host:
header, so the server must respond with a list of possible virtual
hosts. Apache provides some help for configuring a site for both old and new
browsers.
Picking a Hostname and Updating the DNS
Having selected an IP address, the next stage is to update the DNS so that
browsers can convert the hostname into the right address. The DNS is the system
that every machine connected to the internet uses to find the IP address of host
names. If your hostname is not in the DNS, no one can connect to
your server (except by the unfriendly IP address).
If the virtual hostname you are going to use is under your existing domain,
you can just add the record into your own DNS server. If the virtual hostname
is in someone else's domain, you must get them to add it to their DNS
server files. In some cases, you want to use a domain not yet used on the
internet, in which case you must apply for the domain name from the
InterNIC and set up the primary and secondary DNS servers for it, before adding
the entry for your virtual host.
In any of these cases, the entry you need to add to the DNS is an address record
(an A record) pointing to the appropriate IP address. For example, say you want
the domain www.my-dom.com to access your host with IP address 10.1.2.3: you
must add the following line to the DNS zone file for my-dom.com:
www A 10.1.2.3
Now, users can enter http://www.my-dom.com/ as a URL in their browsers and get
to your Web server. However, it will return the same information as if the
machine's original hostname had been used. So, the final stage is to tell Apache
how to respond differently to the different addresses.
How Apache Handles Virtual Hosts
Configuring Apache for virtual hosts is a two-stage process. First, it needs
to be told which IP addresses (and ports) to listen to for incoming Web
connections. By default, Apache listens to port 80 on all IP addresses of the
local machine, and this is often sufficient. If you have a more complex
requirement, such as listening on various port numbers, or only to specific IP
addresses, then the BindAddress or Listen directives can be used.
Second, having accepted an incoming Web connection, the server must be
configured to handle the request differently, depending on what virtual host it
was addressed to. This usually involves configuring Apache to use a different
DocumentRoot.
Telling Apache Which Addresses to Listen To
If you are happy for Apache to listen to all local IP addresses on the port
specified by the Port directive, you can skip this section. However, there are
some cases where you want to use the directives explained here:
- If you have many IP addresses on the machine but only want to run a Web
server on some of them
- If one or more of your virtual hosts is on a different port
- If you want to run multiple copies of the Apache server serving different virtual
hosts
There are two ways of telling Apache what addresses and ports to listen to:
- Use the BindAddress directive to specify a single address or port
- Use the Listen directive to any number of specific addresses or ports
For example, if you run your main server on IP address 10.1.2.3 port 80, and a
virtual host on IP 10.1.2.4 port 8000, you would use:
Listen 10.1.2.3:80
Listen 10.1.2.4:8000
Listen and BindAddress are documented on the Apache site.
Configuring the Virtual Hosts
Having gotten Apache to listen to the appropriate IP addresses and ports, the
final stage is to configure the server to behave differently for requests on
each of the different addresses. This is done using <VirtualHost> sections in
the configuration files, normally in httpd.conf.
A typical (but minimal) virtual host configuration looks like this:
<VirtualHost 10.1.2.3>
DocumentRoot /www/vhost1
ServerName www.my-dom.com
</VirtualHost>
This should be placed in the httpd.conf file. You replace the text
10.1.2.3 with one of your virtual host IP addresses. If you want to specify a
port as well, follow the IP address with a colon and the port number
(example: 10.1.2.4:8000). If omitted, the port defaults to 80.
If no <VirtualHost> sections are given in the configuration files, Apache
treats requests from the different addresses and ports identically. In terms of
setting up virtual hosts, we call the default behavior the main server
configuration. Unless overridden by <VirtualHost> sections, the main server
behaviour is inherited by all the virtual hosts. When configuring virtual
hosts, you must decide what changes to make in each of the virtual
host configurations.
Any directives inside a <VirtualHost> section apply to just that virtual host.
The directives either override the configuration give in the main server, or
supplement it, depending on the directive. For example, the DocumentRoot
directive in a <VirtualHost> section overrides the main server's DocumentRoot,
while AddType supplements the main server's mime types.
Now, when a request arrives, Apache uses the IP address and port it arrived on
to find a matching virtual host configuration. If no virtual host matches the
address and port, it is handled by the main server configuration. If it does
match a virtual host address, Apache uses the configuration of that virtual
server to handle the request.
For the example above, the server configuration used is the same as the
main server, except that the DocumentRoot is /www/vhost1, and the
ServerName is www.my-dom.com. Directives commonly set in <VirtualHost>
sections are DocumentRoot, ServerName, ErrorLog and TransferLog. Directives
that deal with handling requests and resources are valid inside <VirtualHost>
sections. However, some directives are not valid inside <VirtualHost> sections,
including BindAddress, StartSevers, Listen, Group and User.
You can have as many <VirtualHost> sections as you want. You can
leave one or more of your virtual hosts being handled by the main server, or
have a <VirtualHost> for every available address and port, and leave the main
server with no requests to handle.
VirtualHost sections for non-IP Virtual Hosts
Non-IP virtual hosts are configured in a very similar way. The IP address that
the requests arrive on is given in the <VirtualHost> directive, and the
host name is put in the ServerName directive. The difference is that there
(usually) is more than one <VirtualHost> section handling the same IP address.
For Apache to know whether a request arriving on a particular IP
address is supposed to be a name-based requests, the NameVirtualHost directive
addresses for name-based requests. A virtual host can handle more than one
non-IP hostname by using the ServerAlias directive, in addition to the
ServerName.
null

FMS3 Linux and virtual host

Instaled FMS3 on my Linux box, but some strange things happen
with virtual host configuration:
1. add virtual host directory to /conf/_defaultRoot_ (just
making a copy of _defaultVHost_). It contains all needed files -
Application.xml and Vhost.xml with default settings
2. Restart the server
When I login into admin console, new vhost appears in the
list, but it's impossible to connect to it, or just restart it.
Permissions are ok.
Am I forgetting something?

I finnaly get it - FMS starts fmscore process for each vhost,
but after about 5-7 minutes of work every process quits. Logs don't
say anything, what can it be?
/opt/adobe/fms/fmscore -console -adaptor _defaultRoot_ -vhost
test.com -ap -conf /opt/adobe/fms/conf/Server.xml -name
_defaultRoot_:test.com:::
Adobe Flash Media Server (Core)Console mode.
Host: localhost IPv4: 127.0.0.1
Starting admin app on core (4651).
Core (4651) connecting to admin.
Core (4651) connected to admin.
Core (4651) connection to admin accepted.
Core (4651) sending register cmd to edge.
Core (4651) disconnected from edge.
Core (4651) disconnecting from admin.
Unloaded application instance admin

Struggling with Apache Virtual Hosts

Hi Folks,
I'm having trouble getting Apache virtual hosts to function
on my work PC.
PHP works. The PHP info page loads fine. I just can't get any
virtual hosts
to function. Get "Cannot find server or DNS Error."
The identical configuration on my home machine works fine.
Some details
below.
Windows HOSTS file:
127.0.0.1 localhost
127.0.0.1 mvhms
Apache 2.0 virtual host settings in httpd.conf file:
# Use name-based virtual hosting.
NameVirtualHost *:80
# Edited by Phil 3/15/2007
<VirtualHost *:80>
DocumentRoot c:/htdocs
ServerName localhost
</VirtualHost>
<VirtualHost *:80>
DocumentRoot c:/htdocs/mvhms
ServerName mvhms
</VirtualHost>
Any help greatly appreciated. Thanks.
Phil
Work PC is on a LAN
Windows XP Pro
Apache 2.0.59
PHP 5.1.6
Reference: PHP for Dreamweaver 8

Hi Bev,
I tried various local IP addresses with no luck.
However, I do think it may be a local LAN or HOSTS file
issue. If I remove
the proper references from my home HOSTS file, I get the
identical behavior
as my work machine.
Is there a Windows HOSTS file bypass or Group Policy setting
that our IT
department may have changed?
Phil
"bsoliman" <[email protected]> wrote in
message
news:etcioa$839$[email protected]..
> You're welcome, Phil.
>
> Hmmm, in that case then I'm stumped too. If the exact
same setup is
> working
> for you at home, then I have a sneaking suspicion that
it has something to
> do
> with being on a LAN. Unfortunately, that's just a gut
instinct and I
> couldn't
> tell you what the acutal problem might be. Hopefully
someone else will
> come
> along that can help you out.
>
> This is a total shot in the dark: Why not try changing
127.0.0.1 to your
> machine's IP address on the LAN? I'm obviously grabbing
at straws here,
> but I
> figure trying something (no matter how farfetched) is
better than sitting
> around feeling aggravated while waiting for help :-)
>

Apache-weblogic bridge problems with virtual hosting

Hi,
Can we set apache-weblogic bridge where apache webserver is configured
as virtual hosts and each Virtual Host is mapped to a WebLogic server
instance running on separate port ?
Please provide doc or reference or your comments if you have solved this
problem
Thanks
Shriniwas

The above comments notwithstanding, there's one outstanding line in your post that seems crucial:
Also if I type on my browser the name of another secondary (or virtual) domain name in the form http://domain2.com it brings the website hosted under the primary domain which is domain1.com. In case I type http://www.domain2.com than it works as it should and displays the website hosted under this domain name.
As far as Apache is concerned, 'domain2.com' and 'www.domain2.com' are completely separate entities. They have to be otherwise if all domain2.com traffic went to this site you'd never be able to host different sites within the domain (e.g. blogs.domain2.com, wiki.domain2.com, blah.domain2.com, etc.). In other words, there is no automatic relationship between a hostname and sub-records of that hostname.
So what's happening here is Apache is seeing a request for 'domain2.com' which does not match any of its configured virtual hosts, so it handles the request via the default site. If you request www.domain2.com this matches your virtual host configuration so Apache serves the alternate content.
The fix is simple - trivial, even - you just need to tell Apache all the hostnames that match this site - in this case if you've configured the site's primary address as 'www.domain2.com' and you want it to also respond to requests to 'domain2.com' then add 'domain2.com' to the list of Server Aliases in Server Admin.

Virtual Hosts configuration in JServ.conf

Similar Messages

Maybe you are looking for