Targets Using Virtual Hosts Show A "Down" Status in OEM 10gR2

Hello all. I have two databases (10.2.0.2 and 9.2.0.7) that are each using virtual hostnames in a clustered environment. These databases have been verified to be up and running and their respective listeners are up as well. In the Monitoring Configuration for each of these databases, the information for the virtual hostname is entered, and the connection and configuration is successful.
But when I view either of the databases in the list of targets, the status is shown as "Down". If I click on the database name, a "Internal Error has occured. Check the log file for details." error is returned.
Both of these databases are running on Solaris 9 and the OEM versions are as follows:
Enterprise Manager 10g OMS Version 10.2.0.2.0
Enterprise Manager 10g AS Control Version 10.2.0.0
Enterprise Manager 10g Agent Version 10.2.0.2.0
I'm aware that there is a documented bug in OEM 10gR1 regarding this issue, but I'm curious if there is a way to configure the target in R2 to return a correct status when using a virtual hostname or IP address? Thanks in advance for your help!

It is perfectly possible to use a virtual hostname or virtual ip in monitoring configuration of Listener. However, in the monitoring configuration of the database, the "Listener Machine Name" is provided and has to be the virtual ip.
Have a look at $OMS_HOME/sysman/log/emoms.trc as you receive the Internal Error.
Regards,
Martin

Similar Messages

How to Install an APO Livecache on Windows Using Virtual Host Names

Hi,
How to Install Live Cache on windows using Virtual Host names?
we are using SCM 4.0 with live cache build 7.4.3 on two differnt servers.
I have checked the Live cache CD (7.4.3) is with setup.cmd, where as it need use command sapinst.exe SAPINST_USE_HOSTNAME=Virtual hostname.
Please advise.
Thanks
Anil

a possible workaround (that I have no tested) is to temporarily name your server with the same of the virtual name, install. when completed, rename server to original name.
This is not a proven method, but it might work.

Problem getting db connection when using virtual hosts / tomcat / apache

Hello,
I have servlets that use a connection pool to query an oracle database. When running Tomcat 5.5 stand-alone, everything works fine. But the same servlets do not work when running them on a server tomcat and apache integrated with jk and using virtual hosts. The problem is the connection pool, because servlets not using the pool also work fine.
Does anybody have any idea why this is happening?
Thank you.
Logan

Hi Saish,
Thank you for helping.
Try connecting with the machinen's IP, if this is a viable strategy for you (meaning the database IP is not dynamically assigned).I'm not sure how to do this. Here is a copy of my context.xml:
<Context path="" docBase="" debug="0">
<Resource name="jdbc/CraigsList" auth="Container"
type="javax.sql.DataSource" username="craigslist" password="xxxxxx"
driverClassName="oracle.jdbc.driver.OracleDriver"
url="jdbc:oracle:thin:@localhost:1521:GRI"
maxActive="8" maxIdle="4"/>
</Context>
Does this help?
Thanks.

AP showing down status in WLC

hi,
I have cisco wlc 4404 and access point 1242AG A-K9
when I try to connect ap to WLC, it is showing me down status
when i take hyperterm of AP, one of the radio interface status showing me as administratively down.

hi,
Interface                  IP-Address      OK? Method Status                Prot
ocol
Dot11Radio0                unassigned      NO unset up                    up
Dot11Radio1                unassigned      NO unset administratively down down
FastEthernet0              172.16.10.100   YES other up                    up
yes, there are other APs that are in A domain, but the model number is different 1242AG N-K9
and I am facing problem with 1242AG A-K9

Virtual Host Number

How many virtual hosts can i have in WebLogic Web Server?
I need more than 100.000, is it possible?
Thank's

Thank you Eric,
Do you know who can help me more??
Jacques
"Eric Gross" <[email protected]> wrote:
Ahh.. I think I do understand the problem at hand here.
Definitely more complicated doing it the way I proposed when I think
about
it this way.
I am now unsure!
Wish I could be of more assistance here.
Regards,
Eric
"jacques" <[email protected]> wrote in message
news:[email protected]...
Eric,
I understand your explanation, but i need one more information.
How do i configure my webserver intended to forward all requests(including root
folder, subfolders and files) to a certain Servlet that will try locatethe file
requested on the file system and return it back, if succeeded, to theclient.
Examples:
jacques.mysite.com
jacques.mysite.com/test
jacques.mysite.com/test/a.htm (this includes the gif below)
jacques.mysite.com/test/gifs/a.gif
Note that a single html file that has 10 <img src> tags will generate10
new requests
to the webserver->servlet. Got it?
Regards,
Jacques
"Eric Gross" <[email protected]> wrote:
I'm not sure on the way it would work, but I am assuming that this
way
would
be more efficient than having that many virtual servers setup.
I was just presenting an alternate idea. As for the servlet processing
the
request. It would just have to analyze the host part of the domainand
do
some logic based on that. Not sure you would need to do a redirect.
It
really all depends on what you want to do. Lot of factors involved.
Yes, in the zone file at the DNS Server you can specifiy *.mysite.com
IN
A 1.2.3.4 and that will resolve all subdomains of mysite.com to1.2.3.4,
even multiple levels down.
For linking based on the host part of the domain, you can parse forthe
host
and do logic based on that to determine where the directory is.
Regards,
Eric
"jacques" <[email protected]> wrote in message
news:[email protected]...
Eric,
Answering your questions:
I will have 1 IP address for all "virtual hosts/virtual servers".
I can use wildcards dns and have a Servlet, but is it the better
choice?
Can you briefly describe how this Servlet works (redirect requestor
not)?
The webserver verifies host header on receive a request, my servletwill
make
the same thing again.
Double-checking: "Anything that ends with .mysite.com will be set
to
a
unique
IP address. Is this the wildcard dns?". If so, my problem is how
to
tell
the webserver
to separate the existing URLs into separated folders, as shown:
http://eric.mysite.com --> /usr2/mysite/allsites/eric
http://jacques.mysite.com --> /usr2/mysite/allsites/jacques
http://jacques.mysite.com/photos --> /usr2.../jacques/photos
The question is how to tell the webserver to link, base on the
hostheader,
the
request to the right folder (on file system).
I can use a Servlet to redirect requests but i need show the correcturl
in field
address on client browser (jacques.mysite.com/photos), i don´t knowif
this will
happen using a servlet.
Thank´s
"Eric Gross" <[email protected]> wrote:
I'm assuming that you are going to be using 1 IP address for all
those
virtual hosts? If so, then can't you use wildcard dns? Then maybehave
a
servlet parse the first part of the domain? I'm just taking a
shot
in
the
dark here, but maybe if you described how your application is goingto
use
those domains or subdomains, we could perhaps provide more insight.
Regards,
Eric
"jacques" <[email protected]> wrote in message
news:[email protected]...
Kummar,
I really need more than 100000.
Another thing that i need is create a virtual host dynamically.
How
can i
do that
in WebLogic Server (Web Server)? Have i a command line to do
this?
I am developing a application like "www.tripod.com".
First i thought use a Servlet to redirect my requests, but webservercan
do that
automatically using virtual hosts.
Thank´s a lot.
Sorry by my english.
Kumar Allamraju <[email protected]> wrote:
Unlimited..
BTW, do you really need 100000?
jacques wrote:
How many virtual hosts can i have in WebLogic Web Server?
I need more than 100.000, is it possible?
Thank's

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 hosts all redirect to first in list - Snow Leopard Server

I know this is something that's been talked about here before, but I don't see the answer that's making it work for me.
Basically, I am trying to use virtual hosts in a pretty standard fare way. I'm just making a bunch of subdomains: wiki.mysite.com, client1.mysite.com, client2.mysite.com, you get it.
All of these resolve fine, but they're all showing wiki.mysite.com (the first in the list in Server Admin). If I reorder the list, I get whatever's first. I do not have a * in the aliases section of any of these sites.
Can anyone help?

Server manager and workgroup manager in some cases (apache) reads and writes out to files, so you can check if SM is doing the right thing by apache if you go to the actual files in /etc/apache2/sites and check what is there...
i DID have this behavior and fixed it by putting something in the alias part of server manager - i guess it is worth a try and you can always take it out again.

Hiding the Port in a Virtual Host/Server-name Alias

I need some guidance/help with the HTTP Server in AS 10g. We have several new Portal sites with a mix of forms, reports, and pl/sql server pages. We wish to make these services available from the internet via an aliased hole in the firewall.
We have our public alias of Alias.CompanyWebsite.com mapped to the server-name, but we'd like to get the alias mapped to servername:port. I've tried to get this set up using virtual hosts in the HTTP server, but I'm having no luck. I'm also having trouble finding documentation on how to this.
Is there a way to hide the server-name and port number via a virtual host (alias) in HTTP Server and/or Web Cache? If so, how do you accomplish this?
Thanks,
Josh

Usually it is like this:
outside name: www.acme.com
oudside port: 80
inside name: inside.acme.local
inside port: 7778 (if you have a seperate machine for the middle tier)
In the Webcache you'll need a site
www.acme.com with port 80
and an origin server
inside.acme.local with port 7778
Then create a site-to-server mapping from www.acme.com to inside.acme.local
If your firewall listens to another name or does something with the ports you need to change the site accordingly.
cu
Andreas

Virtual hosts in apache defaults to first host

On my MacMini I have set up apache to use virtual hosts I and use a mounted USB drive to host the sites (in my case /Volumes/Work1/www as root). I have configured 3 sites and switch on the subdomain (in my case and in order in the virtual hosts file: hbc1.helsted.net, consulting.helsted.net, store.helsted.net).
On the MacMini I have inserted the urls in the hosts file to point at localhost for two of the entries and all work beautifully on the MacMini for those two. Anywhere else (and from the MacMini on the one not in the hosts file) the system defaults to the first entry in the virtual hosts config file (as the documentation says it will if the url is not recognized) which is displayed in the browser and which has entries in the log file.
After some time the server occasionally refuses to serve the pages and I get a 403 error (access denied). Again not on the MacMini with the hosts file entries. Looking at the error log from apache in that case it appear that it has got the full url served as it is in the log file.
Restarting the web share removes the 403 error (until next time).
Any hints on how to to resolve my two issues?

Thanks for the reply, my vhosts config file contains the following (note that the viewer in the forum browser removes the initial #es on the comment lines):
# Virtual Hosts
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
# Please see the documentation at
# <URL:<a class="jive-link-external-small" href="http://">http://httpd.apache.org/docs/2.2/vhosts/>
# for further details before you try to setup virtual hosts.
# You may use the command line option '-S' to verify your virtual host
# configuration.
# Use name-based virtual hosting.
NameVirtualHost *: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>
ServerAdmin [email protected]
DocumentRoot "/Volumes/Work1/www/hbc1"
ServerName hbc1.helsted.net
ErrorLog "/private/var/log/apache2/hbc1.helsted.net-error_log"
CustomLog "/private/var/log/apache2/hbc1.helsted.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot "/Volumes/Work1/www/consulting"
ServerName consulting.helsted.net
ErrorLog "/private/var/log/apache2/consulting.helsted.net-error_log"
CustomLog "/private/var/log/apache2/consulting.helsted.net-access_log" common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot "/Volumes/Work1/www/store"
ServerName store.helsted.net
ErrorLog "/private/var/log/apache2/store.helsted.net-error_log"
CustomLog "/private/var/log/apache2/store.helsted.net-access_log" common
</VirtualHost>
<Directory /Volumes/Work1/www>
Options Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>
Message was edited by: skhelsted

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

Wiki and virtual hosts

Is there any way to limit the visibility of group wikis when using virtual hosts? Let me explain...
We have two public sub-domains that map to two virtual hosts on a single Leopard server box:
site1.example.com
site2.example.com
Each site has it's own wiki that is up and running just fine.
The problem is when we visit
site1.example.com/groups
we see the wikis for both site1 and site2 listed. When we click site1 we get through to the site1 wiki. When we click site2, we get a file not found error. The opposite happen when we visit site.example.com/groups.
What I'd really like is for site1.example.com/groups to only list the site1 wiki and site2.example.com/groups to only list the site2 wiki.
Is this possible?

I managed to do this by a 'cheap and nasty' method!
The group listing is created by the file
/usr/share/wikid/lib/appletemplates/grouplisting.xsl
it is the ONLY xsl file that cannot be overridden by a custom wikitheme, but it can be edited.
Within this file you will find an unordered list,
<ul class="contentlist">
</ul >
if you replace this by
<ul class="contentlist">
<script type="text/javascript">
if(location.hostname=='www.foobar1.com'||location.hostname=='foobar1.com')
document.write('<li><a href="http://www.foobar1.com/groups/group_name1/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title1A website that ...</a></li>');
document.write('<li><a href="http://www.foobar1.com/groups/groupname2/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title2Another website </a></li>');
document.write('<li><a href="http://www.foobar1.com/groups/groupname3/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title3A final website .</a></li>');
else if(location.hostname=='www.foobar2.com'||location.hostname=='foobar2.com')
document.write('<li><a href="http://www.foobar2.com/groups/group_name4/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title4 The Home site of </a></li>');
document.write('<li><a href="http://www.foobar2.com/groups/group_name5/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title5An online t;/span></a></li>');
else
document.write('<li><a href="http://www.foobar3.info/groups/group_name6/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title6 The Home site .</a></li>');
document.write('<li><a href="http://www.foobar3.info/groups/group_name7/"><img src="/collaboration/images/group.jpg" alt="" width="32" height="32"/>title7A wiki for .</a></li>');
</script>
</ul>
Save and restart the webserver from within serveradmin and it should appear.
OK, so it doesn't automatically respond to new groups as you create them but it's easily updated and, if you follow the instructions from a thread I started on wiki_entry tags you COULD update it from within an admin wiki
I don't claim it's pretty, or that it will survive apple's update once they have sorted out their inability to cope with virtual hosting, but it works.

Http tunnelling not working with virtual host

Hi,
We have recently migrated our application from OC4J server to the Weblogic 11g server. There is one EJB client module which connects using t3 protocol. We are trying to use Http Tunneling for it. The server setup consists of two machines (machine1.global.com and machine2.global.com) in clustered mode. A virtual host cbs.global.com is configured to load balance across the above 2 two machine. Also Apache HTTP Server plugin is used for handling the web tier.
For enabling tunneling, we have checked the 'Enable HTTP Tunneling' check box in the server. Also in the Httpd.conf file, we have added a block for
<Location /HTTPClnt>
SetHandler weblogic-handler
</Location>
If we give the initial context url as http://machine1.global.com:7005 or http://machine2.global.com, then it is working fine. But when we give the virtual host names - http://cbs.global.com or http://cbs.global.com:7005, it is not working. This application needs to be accessed outside the company network, so we cannot directly give the machine names and have to make it work using virtual host.
Please advise whether any other settings need to be done for enabling the tunnelling for virtual hosts.
Highly appreciate your help in this regard.
Best Regards,
Jaison
Edited by: user13152776 on Aug 29, 2011 7:00 PM

Thanks Peter for the reply.
We are having multiple managed servers configured to multiple ports - 7003, 7005, 7007, etc. Please find below the mod_wl_ohs.conf file
# NOTE : This is a template to configure mod_weblogic.
LoadModule weblogic_module "${ORACLE_HOME}/ohs/modules/mod_wl_ohs.so"
# This empty block is needed to save mod_wl related configuration from EM to this file when changes are made at the Base Virtual Host Level
<IfModule weblogic_module>
# WebLogicHost <WEBLOGIC_HOST>
# WebLogicPort <WEBLOGIC_PORT>
# Debug ON
# WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/weblogic.log
# MatchExpression *.jsp
# Dev Cluster Configuration - Port 7003
<Location />
SetHandler weblogic-handler
WebLogicCluster nooslux050d.gl.2wglobal.com:7003,nooslux051d.gl.2wglobal.com:7003
Debug ON
WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/devcluster.log
MatchExpression *
</Location>
<Location /intApp>
SetHandler weblogic-handler
WebLogicCluster nooslux050d.gl.2wglobal.com:7003,nooslux051d.gl.2wglobal.com:7003
Debug ON
WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/devcluster.log
MatchExpression *
</Location>
# Ocean Cluster Configuration - Port 7005
<Location /CQS>
SetHandler weblogic-handler
WebLogicCluster nooslux050d.gl.2wglobal.com:7005,nooslux051d.gl.2wglobal.com:7005
Debug ON
WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/oceancluster.log
MatchExpression *
</Location>
# Websi Cluster Configuration - Port 7007
<Location /si>
SetHandler weblogic-handler
WebLogicCluster nooslux050d.gl.2wglobal.com:7007,nooslux051d.gl.2wglobal.com:7007
Debug ON
WLLogFile /app/oracle/middleware/user_projects/domains/base_domain/ClusterLogs/websicluster.log
MatchExpression *
</Location>
</IfModule>
Best Regards,
Jaison

2nd virtual host, and external Internet site

The first virtual host is setup for our internal users.
The plan is to setup a second virtual host for an external internet portal for customers.
Do I need a second SSL certificate, and second wallet ?
Should this run another IP and therefore need another NIC card in the application server host?

You can use Virtual Hosts in SAP systems to deliver a specific set of ICF services. In the same host:port running the WAS you can have multiple virtual hosts each delivering a set of ICF services.
Check this documentation
http://help.sap.com/saphelp_nw04/helpdata/en/85/5c543aa24b511ce10000000a11402f/frameset.htm
You use external aliases to give meaningful name for the running services. The external alias can be used to access the service.
Check this documentation
http://help.sap.com/saphelp_nw04/helpdata/en/78/9852bdc06b11d4ad310000e83539c3/content.htm
Hope this helps.
Thanks and Regards,
Prasanna Krishnamurthy

SSL virtual host with external hardware accelerator/LBR

Hi all,
We have an existing non-ssl site configured - http://abc.company1.com
We wish to add a new https site - https://xyz.company2.com - and terminate SSL at our hardware load balancer. But obviously keep our existing http site available.
However, we can't seem to get this to work. We added a new site to the Web Cache, registered it with sso, updated httpd.conf and iasconfig.xml with the new virtual host and ran ptlconfig.
Has anyone successfuly implemented a similar configuration?
Is it possible to have a mixture of http and https virtual hosts with SSL termination at the LBR?
Thanks in advance,
Andy

Yeah, in the app server admin guide for SSL configuration:
17.3.5 Enabling SSL in Virtual Hosts
You can use virtual hosts to deploy multiple Web sites on a single Oracle HTTP Server (for example, to make an application available over the HTTP protocol and the HTTPS protocol).
The Oracle Application Server Single Sign-On Administrator's Guide, section titled "Configuring mod_osso with Virtual Hosts" contains instructions on configuring an SSL virtual host to be protected by mod_osso. You cannot use name-based virtual hosting. You must use IP-based or port-based virtual hosting.
//This may be your problem - granted no symptoms were provided.

Real brain bender: virtual host or omni portlet issue? Take the challenge

We are having problems with a portal page that displays several omni portlets on several tabs. Here's the situation:
The page consists of 5 tabs, each representing a different demographic characteristic. On each tab there are four omni portlets. One omni porlet represents a selection list. The user makes a selection, which triggers an omni portlet event to pass the selection criteria to a page parameter. The other three omni portlets on the tab read the parameter value and retrieve data according to the selected parameter value.
Example: The user selects the Age tab and selects the link representing data for the Central Region. The omni portlet's event populates the page's "region" parameter with the value "Central." The other three portlets on the tab retrieve their respective data where region = 'Central'.
Since all the tabs on the page represent different demographic characteristics, the omni portlets on all the other tabs also perform their queries where region='Central' so that the user will see Central Region data displayed regardless of what tab they navigate to.
Also, when the user navigates to another tab and selects a different region, all the omni portlets on all the tabs perform their respective queries to capture data where region=<selected region>.
The page performs correctly until we configure a virtual host. In that case, when a user makes a selection of a particular county in one tab, the queries are performed but the page displays with a tab in view other than the one where the user made the selection.
Example: the user navigates to the Age tab and selects region='Central'. Then the user navigates to Gender tab and then Living Situation tab, viewing the results on each tab. Now the user returns to Gender tab and selects region='Western.' The portlets perform their queries and the page re-displays with the user on Living Situations tab, rather than Gender tab where the selection was made.
Obviously, we want the user to stay put on the tab in which they make their selection. I think it's a problem with the virtual host configuration. My DBA thinks it's a problem with the way the page is built. Has anyone else run into this kind of thing? Is there a trick to using Virtual Hosts?

Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

Targets Using Virtual Hosts Show A "Down" Status in OEM 10gR2

Similar Messages

Maybe you are looking for