Virtual Host Addressing in Oracle9iAS

Hi,
We have Oracle9iAS 9.0.2.3 installed on Windows-2000 (SP-4) OS. Both the Instances of Oracle9iAS i.e INFRA & Mid-Tier is installed on the same machine. Our applications developed in Forms/Reports9i is deployed successfully on Mid-Tier and working OK over web with URL:: http://<Host IP>:7779/<app_name>/myprog.html
[HTTP server running on Port 7779, <app_name> is application delployed in our OC4J Instance & myprog.html is first page which opens by above URL is kept in its relevant directory of deployed application]
Now, i want to create a Virtual Host Address for my application that is running by HTTP Server in Mid-Tier Instance so that above URL could be avoided and intutive name can be given for the URL. I do not wish to give IP, Port etc. in URL for opening my applicaiton deployed on Mid-Tier. I wish to open like IGFL.XEXP.COM (The relevant DNS entry is already placed in Main Domain Controller machine, which will redirect to this HOST).
I checked the documents on Metalink and followed the DocID: Note: 231351.1. I followed the steps of configuraiton without webcache setup, but this is not working properly and i am unable to trace it...Why so.?? Here, i am specifying my customized document root directory instead of AS default directory.
Can anyone give me steps how to do it or help me identifying what i am missing. People claim that it works, but i do not hv any idea and doing it for the first time. You help is needed....Expecting your response.
Regards,
Kamesh Rastogi
Indo Gulf - Jagdishpur

Sounds like you just want the URL to not have the port listed? If so, just change the listen port in the httpd.conf file or change it in Web Cache (if you are using Web Cache).
Plus, you need to register a DNS entry in your DNS server to map the IP address to a name. You don't need to do anything in 9iAS for this part.

Similar Messages

Virtual Host on WebLogic Server 5.1

I need to configure my weblogic server 5.1 on windows 2000 server to make a virtual
host address.
How I can do it ????
Thanks a lot for any help.
Bye

Hi Andy,
I think a good approach for you would be to use a proxy server --
browser -> proxy that supports virtual hosting -> WebLogic
Use a proxy which supports virtual hosting, and which can have a separate
certificate bound to each virtual host.
That way you can do SSL between the browser and the proxy, and you can
have the proxy do cleartext to WebLogic.
This situation gets around WebLogic's limitation of allowing only one
certificate per instance of the server.
You could also use 5.1 as the proxy in the following manner:
Run 3 instances of Weblogic, each as a proxy server, each bound to a
different IP address and DNS name, having its own certificate --
one instance for aaa.com, another for bbb.com, and a third for ccc.com
Then have each of these three instances of WebLogic proxy to your "app
server" instance of WebLogic on the backend.
Hope this makes sense.
Joe Jerry
Andy Walker wrote:
Hello,
I am tasked with implementing a virtual hosting situation that must
use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
and https://www.ccc.com all having separate IPs. These URLs must
forward the request to the same WebLogic Server instance. The problem
is each URL must have its own certificate while WLS 5.1 only uses one
certificate per instance.
I was thinking about using a proxy server such that all three Web
servers that would host the URLs would be sent to a proxy server which
would redirect to the WLS 5.1 instance.
My questions are, would this be feasible using WLS 5.1 as the Web
Server and again WLS as the App Server? How secure is this
arrangement? Is it preferable to use another vendor's software as the
WebServer(IPlanet, Apache)

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

Oracle9iAS R2 - Virtual Hosts with Portal and SSO with OIDDAS application

Hi!
I have installed a the machine with name minsk.discover.local. The machine have installed Infrastructure and Portal. The instalation is sucessfull and i work fine. But i have publish Portal to WEB with name intranet.discover.com.br. The Oracle describe:
1 - Create the virtual hosts in SSO and PORTAL - OK
2 - run ptlasst to create SSO Partners Applications - OK
After this steps iwork fine with Portal and SSO, but when i click in portlet to create user to access the application OIDDAS, the Portal redirect to login page of SSO in address mct.com.br, the internal name, when then name not responde in the internet.
I need a help!!!!
Marcio Mesti

I just spoke to the Oracle App server admins, the two servers in question are clustered.
So my question changes slightly to:
What is the best way to install and configure a webgate for clustered Oracle App servers with mulitple virtual hosts, that are residing behind a load balancer (Traffic Manager)?
Thanks,
Andy

Changing Hyper-V host and cluster virtual IP addresses to new subnet/VLAN

I have a 2 node Hyper-V 2012 R2 failover cluster, managed by System Center Virtual Machine Manager 2012 R2, and I would like to change the IP addresses of the hosts and the cluster, in order to move them to a new subnet and VLAN. The existing and new subnets
are able to route to each other so all hosts will still be able to communicate throughout the parts of the process where they may be on separate subnets. There is also a dedicated cluster heartbeat network on its own subnet and VLAN that I am not altering
in any way.
The 2 hosts are configured with 4 nics in a team, with dedicated virtual interfaces for each of the following:
-Live Migration
-Cluster Heartbeating
-Host management/general traffic (the cluster virtual IP address is also on the same subnet as these interfaces).
It is the host management/general traffic addresses that I want to change. The interfaces were created and configured with the Add-VMNetworkAdapter, New-NetIPAddres and Set-VMNetworkAdapterVlan commands.
Please advise if the following process is correct:
1) Evacuate all the VMs from the first host to be changed and put it in maintenance mode.
2) Use Set-VMNetworkAdapter to change the name of the interface (the current name refers to the VLAN it's on)
3) Use Set-NetIPAddress to change the IP address and gateway of the interface as appropriate
4) Use Set-VMNetworkAdapterVlan to set the VLAN ID
5) Take the host out of maintenance mode and move all VMs off the other host
6) Repeat above steps on the other host
I know that I will then need to change the cluster virtual IP address, but I have no idea how to do this or where to look for that setting. Please advise!
Cheers.

Hi new_guise,
For changing cluster node's IP address please refer to the link below :
https://support.microsoft.com/kb/230356?wa=wsignin1.0
For changing VIP please refer to this article :
http://blogs.technet.com/b/chrad/archive/2011/09/16/changing-hyper-v-cluster-virtual-ip-address-vip-after-layer-3-changes.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Virtual Hosts, lookupd and loopback address

For days I've been trying to install and configure MySQL, phpMyAdmin and virtual hosts, but I just seem to be digging myself a deeper hole. I decided to focus on virtual hosts first and learned how to modify my httpd.conf, hosts and NetInfo files, only to discover that I also have to modify something called lookupd, which I can't even find.
I posted a rather detail query at http://discussions.apple.com/thread.jspa?messageID=4232285#4232285
and received this reply:
[QUOTE]I'm not real sure it applies to virtual domains, but if you want your local machine to redirect URLs to a local domain you need to set up lookupd. . . . As it is, your browser is not even finding Apache because you have no DNS server. As an expedient alternative most people use the loopback address with a custom port number, but you are more demanding than that.[/QUOTE]
Maybe you should repost in the UNIX section and use a better subject line. This is pretty geeky stuff.[/QUOTE]
So is it true that I've been beating my brains out when there's a simpler method involving a loopback address with a custom port number? If so, can someone tell me how to do it or direct me to a tutorial? If, instead, I have to modify this lookupd file, how do I find it? I can't find it with Spotlight, and I haven't been able to locate it with TextWrangler yet.
Thanks!

You should ask this question at http://discussions.apple.com/forum.jspa?forumID=735&start=0

Problem with DNS and/or Virtual Host (works from inside, not from outside)

I am running several web sites (as virtual hosts) successfully on one Xserve (192.168.200), which are accessible internally and from the Internet (via forwarding port 80 on our firewall).
Now I am trying to add another web site (newmini.domain.com), which however is running on a Mac mini (also on the same subnet as the Xserve) at 192.168.100. What I did is make an additional entry under the Xserve's DNS for the domain (domain.com) (+ Machine..., pointing to 192.168.0.100). (I also made the necessary changes to the Mac mini's httpd and hosts configuration--no problem there).
Now, here's the strange thing: All computers on the subnet, whose DNS points to the Xserve, can see and browse newmini.domain.com fine. No problem. The computers ask the Xserve for the IP of the host in question, the Xserve says, "192.168.100", the request goes to the Mac mini, and it serves the web site as expected.
But this doesn't happen if the request comes from the Internet. Instead of seeing the Mac mini, the client sees the default web site of the Xserve... So it appears that somewhere, the virtual host part of the HTTP request is lost between our firewall and the Xserve.
Any ideas? Thanks.

It's not going to.
You say you've setup port forwarding on the firewall. Port forwarding only cares about the port number (80). It knows nothing about the nature of the request (e.g. the hostname that the web request is for). Therefore all extenal connections on port 80 get sent to the XServe. The newmini doesn't see the traffic at all.
If you only have a single public IP address you can only forward port 80 traffic to a single machine. Your options are to either use a different port number, or configure the XServe to proxy the connection to the mini (so now the traffic goes router -> XServe -> Mini -> XServe -> router), although that might not do what you want since it still places load and dependencies on the XServe.

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).

How to create and access a Virtual Host on the J2EE WAS?

Hello, I have searched through the Forums and help.sap.com and found a lot of information on how to set up a Virtual Host on the J2EE server but am having issues with it working.
The goal is to provide a simple virtual host on the J2EE Portal server to host some static image and HTML files. Previously I had stored these files in the standard publicly accessible SAP J2EE folder location /usr/sap/<SID>/JCxx/j2ee/cluster/serverx/apps/sap.com/com.sap.engine.docs.examples/servlet_jsp/_default/root/. This location is resolved to when using the URL <host>:50000 for example.
The main issue here is that during Portal support pack applications this folder gets wiped out and we have to remember to save off any custom files and folders in this location and replace them.
I would like to create a virtual host to store these static files (i.e., branding-image.jpg, etc...).
I have run through the process of creating the virtual host both using Visual Administrator and <host>:50000/nwa but am not able to get the virtual host name to resolve properly.
The following are the steps that I have taken. Let's assume the standard SAP portal (i.e., xSS, etc...) is running properly on <host>:50000.
1. create virtual host via Visual Administrator/NWA called 'sapwebserver1' by using the Create Host option (takes on the attributes of the 'default' standard virtual host)
2. change the root directory for this virtual server to a custom folder at E:/tmp/mimes (where E:/usr is where the J2EE files are all installed), no start files were set up and nothing else was changed in the new virtual host record, no permissions were changed on the /tmp/mimes folder from whatever the default Windows user permissions are normally set, I am using a local Windows administrator account but I have not seen any reference in the help files or the examples that indicate that any specific permissions updates need to be made on the virtual host root folder
3. restarted the J2EE server as well as the HTTP Provider service
4. before updating the company DNS, I wanted to test this locally on the server and so have updated the server's local HOSTS file with a <host IP address> sapwebserver1 entry
5. from that server I can ping the sapwebserver1 virtual host name and it resolves properly to the machine's physical IP address
According to all of the documentation and examples I have seen I should now be able to (from that server) launch a browser and access the static files in the virtual host by referring to http://sapwebserver1:50000/branding-image.jpg for example. This is not working and the browser just brings up a Cannot display the web page error in IE. By referring to the virtual host name sapwebserver1:50000 it's supposed to hit the J2EE server and based on the host name sapwebserver1 realize that it should resolve to the root directory E:/tmp/mimes. This is not happening. Just as a test I have created a copy of the 'default' virtual host and called it sapwebserver2, updated the local HOSTS file for this entry, and tried to see if that would work like the 'default' host. My expectation was that http://sapwebserver2:50000 would behave the same was as http://<host>:50000 but it too fails to resolve just like the sapwebserver1 virtual host refernce.
Would anyone happen to have any pointers on what to do next? I just want a simple virtual host to be able to serve up some static images and files.
Thanks for any insight or assistance you might be able to provide here.
Graham

This defeats the purpose of trying to centralize SAP-related web resources on the SAP server. Typically IIS/Apache or other non-SAP servers are under the control of IT and not the SAP BASIS group.
We simply would like to have a centralized location to store static web files so that they are not overwritten during Portal support pack applications.

How to set up Virtual Hosts in Apache (OS X Server 10.9)

I want to host more than one website on my mac mini with OS X Server 10.9
1.) I edited /etc/apache2/httpd.conf for uncommenting the include line:
# Virtual hosts
Include /private/etc/apache2/extra/httpd-vhosts.conf
2.) I edited /etc/apache2/extra/httpd-vhosts.conf and added:
<VirtualHost *:80>
    ServerName cammino-al-dente.net
    ServerAlias www.cammino-al-dente.net
    DocumentRoot "/Library/Server/Web/Data/Sites/cammino-al-dente.net"
    ErrorLog "/private/var/log/apache2/cammino-al-dente.net.com-error_log"
    CustomLog "/private/var/log/apache2/cammino-al-dente.net-access_log" common
    ServerAdmin [email protected]
</VirtualHost>
<VirtualHost *:80>
    ServerName sutterer.net
    ServerAlias www.sutterer.net
    DocumentRoot "/Library/Server/Web/Data/Sites/sutterer.net"
    ErrorLog "/private/var/log/apache2/sutterer.net-error_log"
    CustomLog "/private/var/log/apache2/sutterer.net-access_log" common
    ServerAdmin [email protected]
</VirtualHost>
3.) then I edited /etc/hosts/ to spoof my IP address to the domains:
127.0.0.1
localhost
127.0.0.1
cammino-al-dente.net
127.0.0.1
www.cammino-al-dente.net
127.0.0.1
sutterer.net
127.0.0.1
www.sutterer.net
255.255.255.255
broadcasthost
::1
localhost
fe80::1%lo0
localhost
Then I restarted Apache...But nothing happens :-(
I could reach my website cammino-al-dente.net only by using the Server Default-entry, chancing the entry to my cammino...-folder
Regards
Fred Mario

In the /etc/apache2/extra/httpd-vhosts.conf file check this line exists:
NameVirtualHost *:80
This solve same issue for me.
I hope it's help.

Virtual Hosts and Mod_JK

I setup two sites: madplanet.com and j-community.org. Both on all addresses and on port 80. The two domain names resolve to an external IP address. I configured Mod_JK correctly in the httpd.conf file.
Now I configured two workers in workers.properties each pointing to a different JBoss/Tomcat server. I added them to the workers list and finally added them manually to the appropriate XXXXany_90<domain name>.conf file in the sites directory which looks like this:
<VirtualHost *:80>
ServerName madplanet.com
ServerAdmin [email protected]
DocumentRoot "/Library/WebServer/Documents"
DirectoryIndex "index.html" "index.php"
CustomLog "/var/log/apache2/access_log" "%h %l %u %t \"%r\" %>s %b"
ErrorLog "/var/log/apache2/error_log"
ErrorDocument 404 /error/HTTPNOTFOUND.html.var
<IfModule mod_ssl.c>
SSLEngine Off
SSLCertificateFile "/etc/certificates/192.168.0.2.crt"
SSLCertificateKeyFile "/etc/certificates/192.168.0.2.key"
SSLCipherSuite "ALL:!ADH:RC4RSA:+HIGH:+MEDIUM:+LOW:!SSLv2:+EXP:eNULL"
</IfModule>
<IfModule mod_dav.c>
DAVLockDB "/var/run/davlocks/.davlockany80default"
DAVMinTimeout 600
</IfModule>
<IfModule modmemcache.c>
CacheEnable mem /
MCacheSize 4096
</IfModule>
<Directory "/Library/WebServer/Documents">
Options All -Includes -ExecCGI +MultiViews -Indexes
AllowOverride None
<IfModule mod_dav.c>
DAV Off
</IfModule>
</Directory>
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_METHOD} ^TRACE
RewriteRule .* - [F]
</IfModule>
<IfModule modproxybalancer.c>
<Proxy "balancer://balancer-group">
</Proxy>
</IfModule>
<IfModule mod_alias.c>
Alias "/collaboration" "/usr/share/collaboration"
Alias "/icons/" "/usr/share/httpd/icons/"
Alias "/error/" "/usr/share/httpd/error/"
Alias "/examples" "/Library/Tomcat/webapps/examples"
Alias "/macserver" "/Library/WebServer/Documents"
</IfModule>
<IfModule mod_jk.c>
JKMount / JBoss1
JKMount /* JBoss1
</IfModule>
Include /etc/apache2/httpd_users.conf
Include /etc/apache2/httpd_groups.conf
Include /etc/apache2/httpdteamsrequired.conf
LogLevel debug
ServerAlias *
</VirtualHost>
Still after the web service is started both domains delivery the same content (the one from madplanet.com) meaning that 'http://madplanet.com' and 'http://j-community.org' delivery the same web site. Using the web site port from Tomcat the j-community website comes up fine.
Any pointers?
Thanks - Andy

Your fatal flaw is the line:
ServerAlias *
This tells Apache that this virtual host matches all hostnames, so it doesn't matter what site the user tried to access, they will always get the output of this virtual host.
Remove this line and you should be fine.

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.

Setting up Virtual Hosts on a Snow Leopard Development Server

Hi Everybody,
I'm losing hair over this - I thought it would be simple!
I have set up a Mac Mini Server running SLS and would like to host multiple websites for development on the internal network. I require the websites to be stored anywhere on the server, not just in Library/WebServer/Documents/. Ideally, I would like to access them by example.com/mynewsite so I don't have to mess around with DNS.
Currently I'm setting up websites in the Server Admin Web panel but it just doesn't work. I've noticed the error log keeps looking for files located in the Library/WebServer/Documents/ folder even though I have specified a different folder.
What Am I missing? Does anybody know of a tutorial / guide to point out potential issues when setting up virtual hosts? I have checked Apple's guide but it doesn't really help me. Any pointers would be much appreciated!
Cheers

Sites is likely failing here because Sites is based on the DNS and on the HEAD command within the http stream; if the DNS does not match, you won't get to the host, and if the HEAD command doesn't match the entry in the site, then you'll either get the * wildcard or (if no *) you won't be transferred to the target Site.
Check the web server logs, as a start.
If you want to see how this stuff works at the protocol level, you could telnet to port 80 and toss a http 1.1 GET / command and see what you get back for a page.
Per [rfc2616|http://tools.ietf.org/html/rfc2616], this sequence looks like this:
+telnet www.example.com 80+
then:
+GET / HTTP/1.1+
+host: www.example.com+
followed by two presses of the return key, and where www.example.com is your target Site (virtual host) name.
Alternatives to using DNS and virtual hosts are port-based hosting (which is easy), and you can also use IP addresses to establish virtual hosts. The former is set up via the Sites stuff, with various other ports being used for the web servers. Ugly, but easy. The IP-based approach can get ugly fast, too.
If you get DNS going and aliases added, and all this goes away in a puff of greasy orange smoke.

Virtual IP address in Failover Cluster Manager

Dear All,
I want assign virtual IP address to cluster server windows 2012 but this Ip address is not given to physically.
i am creating host entry with ip address and hostname but i am not able to ping.
is there any way to ping this ipaddress?
i am only creating entry in host file.
Sunil
SUNIL PATEL SYSTEM ADMINISTRATOR

Hi SPKATEL,
Are you trying to add IP address resouces? You can refer the following simlar thread and KB:
How to add IP address for cluster resource name?
https://social.technet.microsoft.com/Forums/windowsserver/en-US/51e4dcda-ffde-4e55-b106-139e3b15188b/how-to-add-ip-address-for-cluster-resource-name
How to Create a Cluster Group with a Disk, IP Address, and Name Resource
http://msdn.microsoft.com/en-us/library/dd897474(v=bts.10).aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Network Load Balancing - Virtual MAC Address

Hi All,
I have environment that running 2 Exchange 2010 server with CASHT and join windows network load balancing as a node.
My question is,
If NLB service is restart, is it virtual MAC Address for NLB will change to new virtual MAC Address?
Thanks for response,
Best Regards,
Henry Stefanus

Hi Henry Stefanus,
The NLB work mechanism will not change whether what higher application we used and I am not very familiar with Exchange NLB architecture, may the following KB and article
may help you.
When you use the unicast method, all cluster hosts share an identical unicast MAC address. Network Load Balancing overwrites the original MAC address of the cluster adapter
with the unicast MAC address that is assigned to all the cluster hosts.
When you use the multicast method, each cluster host retains the original MAC address of the adapter. In addition to the original MAC address of the adapter, the adapter is
assigned a multicast MAC address, which is shared by all cluster hosts. The incoming client requests are sent to all cluster hosts by using the multicast MAC address.
Selecting the Unicast or Multicast Method of Distributing Incoming Requests
http://technet.microsoft.com/en-us/library/cc782694(v=ws.10).aspx
The related third party article:
Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 1
http://blog.morecoffeeany1.com/2010/03/19/building-nlb-exchange-2010-rtm-cas-ht-servers-hyper-v-%E2%80%93-part-1/
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Virtual Host Addressing in Oracle9iAS

Similar Messages

Maybe you are looking for