Starting EHPI for virtual Host

Hi All,
Can you help me with how to start the EHPI with the virtual host name.
Thanks in Advance
Anthony

Hi,
The main thing in cluster is to use one Hostname during the Upgrade.
Please use the physical hostnames in the profiles also and the UPG
should run till the end.
The EHPI needs an instance named with the usual DVEBMGS format.
The upgrade
should run on the same host as the central instance.
Please check the SAP notes:
96317 Host names during R/3 upgrade, tips & tricks
962955 Use of virtual TCP/IP host names
Regards,
Aidan

Similar Messages

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

Multiple IP vs Same IP multiple port for virtual hosts

Anyone have any recommendations or experience in setting up a virtual host that has a listener for each site?
The issue is when I have to restart a single site, I have to restart them all, because they are installed under the same listener/server.
I need a setup where I can install and manage each website (on the same box) on it's own listener/server instance so re-starting one site doesn't effect another.

Add a service in the Network preference pane. Select the network interface you want; e.g., Ethernet. Configure as desired. Apply and test.

Mod_rewrite not working for virtual host nor .htaccess

I've been tearing my hair out trying to implement mod_rewrite on my Leopard Server. I have finally been able to get mod_rewrite to log what it does, but that has only shown that it DOES periodically respond to a /server_status request from the server itself, but any request to the virtual host (which is otherwise working) does not result in mod_rewrite being 'triggered.' I've tried all the usual suspects, in just about every permutation and combination:
1) .htaccess in all its guises and Override All;
2) RewriteEngine On;
3) http.conf, the virtual xxxx_80_virtualhostname.com.conf;
4) Options All -Includes -ExecCGI +MultiViews -Indexes +FollowSymlinks;
5) other less credible ideas gleaned from the Apple discussions and the web.
If I had to summarise the effect, it's that
a) mod_rewrite is on (as shown by the regular /server_status entries in the rewrite.log);
b) xxxx_80_virtualhostname.com.conf is read when the virtual host is turned on (because the site is active and can be turned off, at will);
c) any mod_rewrite and Options entries in the vistual host xxxx_80_virtualhostname.com.conf seem to be being studiously ignored, even though the .conf file is being read and used.
This part of http.conf is what seems to turn on the logging:
<IfModule mod_rewrite.c>
     RewriteEngine On
     RewriteLog /private/var/log/apache2/rewrite.log
     RewriteLogLevel 9
</IfModule>
Here's the section of xxxx_80_virtualhostname.com.conf:
<Directory "/Library/WebServer/com.VirtualHostName">
     AllowOverride All
     <IfModule mod_dav.c>
          DAV Off
     </IfModule>
     Options All -Includes -ExecCGI +MultiViews -Indexes +FollowSymlinks
</Directory>
<IfModule mod_rewrite.c>
     RewriteEngine On
     RewriteLog /private/var/log/apache2/rewrite.log
     RewriteLogLevel 9
     RewriteRule ^/Tom.html$ /Mary.html [R]
     RewriteCond %{REQUEST_METHOD} ^TRACE
     RewriteRule .* - [F]
</IfModule>
This is a variant of the .htaccess file:
RewriteEngine on
RewriteBase /
RewriteRule ^/Tom.html$ /MARY.html [R]
It makes no difference whether the RewriteBase is present in the .htaccess or the xxxx_80_virtualhostname.com.conf, or both.
No amount of pass-though [PT] or redirect [R] has any effect, either.
I do have Lasso 8.5 installed, but the developer says that Lasso should have no effect on the proper functioning of mod_rewrite.
mod_rewrite is working (i.e. it's on, as shown by the /server_status entries in the log and that the log is being updated), but it is also not working (in that no matter what I put into xxxx_80_virtualhostname.com.conf and/or .htaccess, there is no entry in the rewrite.log nor in the system logs).
Hence, I'm stumped. Any suggestions would be very, very welcome.

Never mind. I discovered that Server had created several versions of the virtual host .conf file in the sites folder (I've no idea why, when, or how it would do that). They all had different numbers and so were well hidden within the dozens of other .conf files. Once I a) found the right .conf file for the virtual host, and b) deleted the rest from the sites folder, my mod_rewrite code worked fine.
Hence, if you find that mod_rewrite is working, but not for a particular virtual host, make darn sure that there are no errant .conf files for the domain and, if there are, that you're editing the correct one.

How do I configure Apache for Virtual Hosts?

This is whatI've done so far: I have a static IP. I have a registered domain name that points to this IP. I've made my sites in iWeb. Set up my computer for Personal Web Sharing. I've used Smultron to edit the httpd.conf files per this tutorial : http://www.macminicolo.net/videos/ServerVideo6.mov. Still no luck. I can't access the site from the internet.
Can anyone shed some light ?

Hi Joe,
Se if this helps...
http://mark-kirby.co.uk/2008/setting-up-virtual-hosts-on-os-x-leopard/

Separate Wiki Data Stores for Virtual Hosts?

Is it possible to set different data stores to be used for the wikis associated with different sites (i.e. virtual hosts) on a Mac OS X Server (Snow Leopard)?
By default they are in "/Library/Collaboration/" and that is applied to ALL hosted sites.
My client would like a little more differentiation than that offered by user and/or group login.
Thanks in advance.
+*Geoff Heys*+

Ditto.
I noticed it when logged in as a user with permissions to a specific wiki on the server, and went to 'My Page', that updates from all the other wikis on the server are listed, in addition to the updates for the wiki I belong to. I can't get to them by clicking on the links, but they show up in the list. Makes it pretty hard to focus on your wiki, when you see updates from multiple other wikis listed.
It would seem like there must be a fix in the code for both the 'My Page' and the generic top-level '/groups', but I don't know the code structure well enough yet to figure out how/where to fix it.
Anyone else find a solution for this? I don't think I can roll out multiple domains/wikis on one server, if this behavior is present.

DNS settings for virtual host 10.6 server

We have just gone through a rebranding exercise, i.e. the company name has changed from 'mycompany' to our 'ourcompany'.
For various reasons we have decided to not rename our complete setup, but rather add a virtual host for our mail server including a second primary DNS zone for the new domain 'ourcompany'.
We are hosting our website externally, however since we added the second primary DNS zone incl. an A record (www) pointing to our external website hosts IP for 'ourcompany', workstations on our LAN can no longer access the website.
Running DIG for 'www.ourcompany.com.au' results in the correct A record IP address being shown, but it is still not showing in any browser – we also made sure we emptied our caches.
Although we thought this should work relatively easily, we are now totally confused as to the additional primary zones general settings... currently we allow zone transfer and provide an entry in the nameserver section.
Any ideas as to what might be going on here would be greatly appreciated.

Mr. Hoffman,
Than you very much for your reply - unfortunately, despite studying and testing your advice (incl. wesbite) we seem to not get much further.
Please find our comments inserted below...
MrHoffman wrote:
FWIW, both mycompany.com.au and ourcompany.com.au are real and registered domains; I'll presume they're not the domains you're migrating from or to. Accordingly, I'll use example.org for your old stuff, and example.com for your new stuff; the example domains are RFC-reserved for this usage.
Correct we are not using my bad example domains.
Each host should have one A record (and one AAAA record, if you have IPv6 active), and one of the more common errors in these migrations is setting up an A record for each new domain that might arrive; each host has one A (and possibly one AAAA) record, and that's the canonical name for that host. Externally, that'll probably be the latest name in any sequence (such as www.example.com), and all previous names (including www.example.org) will have CNAME entries.
To clarify do you mean the following: internally we should not have more than one A record for each host... i.e. one for example.org and one for example.com and presumably any other subdomains should be CNAME records?
2. externally we should change the A record for www.example.org to a CNAME record and create a new A record for www.example.com;
Internally (and here's why having a different domain inside is handy) use one of the old names; use example.org, for instance. This means you can use the public DNS services for the external web sites and resources; your internal DNS servers receive the requests for example.com hosts and go "duh, lemme ask somebody else for that", and that somebody else is the (public) DNS server your external DNS services for example.com hosts.
Exactly what we had initially done - basically we (naively) thought we could get away with only relying on external DNS translations... however that resulted in mail clients on our LAN loosing their connection every 5-10 minutes, thus we decided to setup another primary DNS zone which fixed that problem but created the other.
Please also note we have created a subdomain admin.example.com which properly resolves to the CMS backend - btw. from within this backend you can then preview the any page on the regular website with their non www. URLs.
Since the current setup resolves to the correct IP address I wonder if it could be a problem with the .htaccess rewrite rules the web developer has setup to remove the www. ... or is this too far fetched?
The usual trigger for not reaching the external A (or AAAA) records is either a stale cache on the particular client (for translations inside the Time To Live (TTL) values for the old DNS translations, or pending a local cache flush on each client), or (and this is more common) confusion over authoritative DNS servers; you have your internal DNS configured as authoritative for the new www.example.com domain, and also authoritative for the old www.example.org domain, and your external DNS is also authoritative for (probably) both domains. Internal requests get as far as the internal server, and get an authoritative translation (possibly being "no such host"), and don't go any further.
Safari & Firefox present with 'Server not found' errors.
So we are still stuck thus any further advice would be much appreciated.

Best Practices for Virtual Hosting

I am providing hosting for a few churches besides our own and had some question regarding best practices.
My primary domain say is churchhosting.com with an A record "mail.churchhosting.com" pointing to my static ip. It also has a MX record to "mail.churchhosting.com" and a PTR record set by my ISP to "mail.churchhosting.com".
For the other sites I am hosting say "church1.com" and "church2.com", should I set their MX record to "mail.churchhosting.com" or have an A record "mail.church1.com" pointing to my static ip with a MX record to "mail.church1.com." and likewise with the "church2.com" domain.
What would the best practice be and the potential problems that either might present with the server?

Am I doing this correctly? I want to know how many SSL certs I need under the following:
In a similar situation, I think. I have multiple virtual domains setup. For example, company.com, company1.com, company2.com.
Mail Services General Settings show the host name at company.com. All the company.com, company1.com and company2.com are listed under Advanced > Hosting as virtual domains.
All these domains are on a single IP address. The DNS is hosted at godaddy and all MX records for company.com, company1.com, and company2.com are '0 @ company.com'.
All the CNAME records for mail.company.com, mail.company1.com, and mail.company2.com point to "@" and all the A records point to the same IP address. There is only one server.
I think what this means is that I've set it up so that all mail.xxx.com is routed to mail.company.com for all virtual domains. I want to use SSL certs for mail. How many will I need under this arrangement? Is it just one for mail.company.com or is it 3, one for each virtual domain?
Thanks.

Set up reverse DNS for virtual mail hosting

I need a bit of server configuation advice.
I have a static IP and two public domains on a Snow Leopard server connected using NAT behind a firewall - with the necessary port forwarding to ensure all works.
1. abc.com is my primary domain on the server - server.abc.com
2. I have xyz.com set up as a virtual domain and also as a virtual mail host
This setup has worked well for a long time but I have found that emails to [email protected] are going missing. If I check my mx records using one of the web based tools it show an error on the reverse dns for server.xyz.com showing a reverse DNS of server.abc.com.
So the question - is it possible to have secondary 'virtual' DNS record on the server so reverse DNS works for the virtual mail host xyz.com? If not how do I handle the reverse DNS problem which i think is causing some external mail server to reject mail due to the inconsistency on the reverse DNS lookup?
Many thanks for any suggestions

SMTP requires a DNS A record.
A DNS A record is also known as a machine record.
A DNS A record inherently means that forward DNS and reverse DNS will match.
The forward translation translates the host name to the IP address.
The reverse translation translates the IP address to host name.
When the full translation produces the same host name, that's an A record.
DNS CNAME records are aliases, and are used for virtual hosts.
CNAME records inherently do not match the reverse DNS translations.
To get your configuration to work, your server must have an A record.
That means forward and reverse DNS will match.
Any of the virtual hosts within your mail server then all use an MX pointing at the A record host.
If you have your DNS hosted somewhere other than your ISP, then you'll need your ISP to set up a DNS PTR.
The DNS PTR is the reverse translation; address to name.
If you have your own DNS services within your network (as would be typical with a privately-addressed NAT'd network), set that up as a virtual host within SMTP.
Here is some related reading on external (public) DNS, as related to SMTP servers and such.

VIrtual host and reverse proxy FOR EBIZ R12.0.6

we have 4 dev EBIZ instances on a single hp_ux itanium server on which I have to setup one instance for virtual hosting and to work behind a reverse proxy .
any particular documents or steps for this.
Thanks
mn

we have 4 dev EBIZ instances on a single hp_ux itanium server on which I have to setup one instance for virtual hosting and to work behind a reverse proxy .
any particular documents or steps for this.Implementing Virtual Host, Concurrent Managers and EM DBconsole on Oracle Applications R12 [ID 603883.1]
Conc-System Node Name Not Registered After Fresh Install Using Virtual Name [ID 948644.1]
Is Auto Failover With Virtual Hostnames For Concurrent Processing Servers Supported In 11i Or R12? [ID 456540.1]
Case History: Implementing a Reverse Proxy Alone in a DMZ Configuration - R12 [ID 726953.1]
Oracle E-Business Suite R12 Configuration in a DMZ [ID 380490.1]
Thanks,
Hussein

Recipient_delimiter w/ virtual hosting?

All of my past OS X Server Mail installations have used local domains (not virtual hosting) until my most recent installation....
I generally setup amavisd.conf to deliver spam to a user+spam@ address.
Back to my most recent install. This is my first site running virtual hosting. The setup was done 'the Apple way' with the domains added in WorkGroup Manager (virtual hosts) and the full email address added to short names for each user.
I then enabled recipient_delimiter = + in main.cf and restarted postfix.
Mail addressed to [email protected] is rejected.
At minimum, even if the spam mailbox didn't exist, the mail should be delivered to [email protected]
I've set this up many times with local domains.
What am I missing for virtual hosting???
Jeff

Jeff,
you are absolutely right. My fault, should have made it clearer in the docs.
Reject-before-scan will not work with WGM style virtual domains.
- Reject-before-scan code. Does it require a postfix-style setup of virtual users?
postfix-style (actually, you can do sort of a "hybrid" setup, but it is not "clean" and can get messy, so let's stick to postfix-style).
Well, yes this topic is sort of drifting, but since its more of a private conversation between you and me.... no harm done. If we had done this via e-mail, no one else would have benefitted.
So while we are at it:
I'll edit my docs to make this clearer. The setting up virtual users tutorial was really meant for beginners who were afraid of terminal. Once somebody starts using postfix to it's full (or at least fuller) extent, the GUI has to go and anything but a basic config will cause problems when modified through the GUI (I know you know this, but I am writing it for the benefit of the unexperienced). Actually I am in the process of writing a documentation on what can be safely done with the GUI and what can't, but since time is precious I have no clue when I'll be done.
Coming back to your original issue. You need an advanced postfix setup, but want the end-user to be able to administer it. The best way would most likely be to re-compile postfix to include MySQL support and then have the user use postfixadmin. This not for the faint hearted, but you should have no problem with this.
Alternatively, if it is only one customer you need this for, you might as well configure everything to use postfix style virtual aliases and then write a shell script to help the end-user in adding aliases to /etc/postfix/virtual
To add an alias, use something along the lines of:
sudo echo [email protected] [email protected] >> /etc/postfix/virtual
to delete:
grep '[email protected]' /etc/postfix/virtual | sed "do your substitution here"
Obviously you could also create a GUI for editing /etc/postfix/virtual. Should be very simple to do.
Just a few thoughts. Pick the one you like best
Alex

Apache virtual host with OSX Server?

I have been running OSX Server for a while now, and just recently I decided to get McMyAdmin for my Minecraft server. The web client for McMyAdmin runs on port 8080, but I wanted it on port 80. I wanted to use it with my domain, so I just created a sub domain and pointed it to my server. The problem is that OSX Server apparently doesn't let me use port 80, even when websites are turned off. I decided to delete Server and just use plain apache. This worked until I realized that my website was only accessible locally. I have all the correct ports forwarded, etc. But I get the error:
Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.
when I try to connect from outside my network. This is probably just some simple thing I missed but it would be nice if someone could just point out what I did wrong here. Back to the point, I want to know how to run the proxy to my web client on port 8080 AND ALSO run OSX Server with or without apache virtualhost.
Thanks in advance,
Eamon

Web is stupidly easy - Apache has extensive support for multiple virtual hosts in a single server and will happily support as many domains/hostnames as you can throw at it.
Mail is a little trickier since it needs to hook into some kind of directory server to validate user addresses.
Mac OS X's Open Directory does support this, but it's a little cumbersome (basically every user has to exist in the main Open Directory domain as well as having a secondary email address(es) in the other domain(s).
This can get especially tricky when you have users with the same shortname in different domains - for example if you give [email protected] a secondary email address of [email protected] and you then get a new user [email protected], you can't give the third 'joe' the address 'joe' in Open Directory since that's already taken. This means he'll have to login using different credentials from his email address. Confused yet? You bet.
If you're prepared to eschew Open Directory you can just use Postfix's built-in support for virtual hosting, but it's a little more complex to setup and support and is entirely command-line based (i.e. there's no GUI for setting it up or supporting it).
So, for that reason you might be prepared to setup multiple virtual machines for each domain. It really depends on how much the domains are related (if at all).

Oracle VM 3 - only one virtual host accessible from the network (DELL R410)

Hi,
I have installed Oracle VM 3.0.3 and created the network for Virtual hosts. After installing two systems on the server only one is accessible from the network at a time. The second one is not.
Have no idea how e to enable the second host to reach a network.
Maby You have some idea?
Thanks,
Jarek

Hello!!
I'm not an expert but /OVS/Pool should be the directory naming of OVM 2.x, replaced by /OVS/Repositories/REPOS_ID in OVM 3.x
The "wierd directory name" it's the unique ID that OVM assigns to Repository, infact if you go to VM Manager in Repository tab and edit your current repository you will see this ID: 0004fb0000030000839f2d2faa5014c3
Under "0004fb0000030000839f2d2faa5014c3" folder, as you noticed, there are the classic folders ISO, VirtualDisk, VirtualMachine, etc. where files are placed.
I've never tried to import a pre-packaged template from Oracle but I would try importing it as an assembly from http/ftp! ;)
Hope this helps.
Greets!

DefaultWebApp on virtual host

The documentation for WLS 8.1 says the DefaultWebApp parameter for virtual hosts
is being
depricated, yet you are not allowed to add more than one web application to a
domain that
has a context root of /. Is there another way to code a default application for
a virtual host
that I am not aware of? What would the advantage of a virtual host be if you
can't assign a
default web application?

We do both.. physical gets installed on /opt and is just the agent & host target. Virtual is the db, listener, agent and virtual host. This way you can tell when a box that is not "active" is alerting or crashing and the virtual agent can contain the metrics and such set once and consistent. If you failover . you would have to rediscover/unblackout the db if you decided to discover it on the physical host.
Our environment is veritas cluster server .. sounds like you have perhaps more of a vmware type of environment.
Either way I would think you should go with the virtual agents.

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

Starting EHPI for virtual Host

Similar Messages

Maybe you are looking for