Welcome to WebmasterWorld Guest from 184.108.40.206
I have one external static IP address and am using Apache as the web server. My app server is weblogic 8.1.
What I have set up is...
Physical server exposed through DMZ with static IP to the outside world. This is where apache is running.
On this machine I vmware running with a VM which has my app server and DB.
I currently having everything working... www.mydomain.com and demo.mydomain.com both hit the webserver and direct traffic to my app server sat on the VM.
What I now need to do is introduce another VM also running Weblogic 8.1 and another sub domain (demo2.mydomain.com).
So then I'll have Apache in the DMZ on the host machine. demo.mydomain.com routed through to VM1 and demo2.mydomain.com through to VM2.
For anyone not familiar with VMware basically think of it as two physical separate app servers sat on your internal network VM1 = 192.168.1.2 and VM2 = 192.168.1.3.
Iíve tried a few different things within the HTTPd.config file, to try and achieve this, however, so far Iíve failed to get it working.
Does anyone know how I can do this, or what terminology I should use in google to get to the answer?
Thanks a lot!
What I think you are asking is you want one HTTP server with mydomain.com and subdomain1.mydomain.com pointing to one VM app server 1. Then you want another subdomain2.mydomain.com pointing to VM app server 2.
First question is, is the app on VM Server 1 and app on VM server 2 webprograms? or are they local programs that can have DMZ Router route to differnt ports and have a script in your website to redirect to the appropriate internal IPs
What version of Apache are you running?
here is some doc info from apache 2.2 which may help you, Vhost or virtual host may be your answer.
you can also try a good .htaccess file to do your redirecting.
Another option is to have a script wrote and embedded in mydomain.com that will redirect to differnt IPs.
I am trying to do exactlly as you stated...
one external IP address, with two internal IP address. Each on the internal IP addresses will be running weblogic, DB, App etc...
Essentially both installation are exactlly the same, but the way the app will be used is different. So demo.mydomain.com is for one use (demo's believe it or not ;) ) and then test.mydomain.com for... well I rekon you can guess...
I'm using Apache 2.0.59
When you say a 'good .htaccess file' what do you mean by good, and where can I get a good starting point from?
Thanks again for your help with this... going to have a read through the link you put up now...