Redirecting https requests to two different weblogic servers using the Weblogic proxy and Apache2?

First, the must read resource for this is of course the official documentation : Installing and Configuring the Apache HTTP Server Plug-In (see also this previous answer for more links about the WLS 9 plugin).

First, the must read resource for this is of course the official documentation : Installing and Configuring the Apache HTTP Server Plug-In (see also this previous answer for more links about the WLS 9 plugin). As detailed in the section Configuring the Apache HTTP Server Plug-In, I'd define several IfModule, one for each application (clustered or not), and, indeed, several VirtualHost (which can include IfModule). There is an example in the documentation: # VirtualHost1 = localhost:80 DocumentRoot "C:/test/VirtualHost1" ServerName localhost:80 #... WLS parameter ... WebLogicCluster localhost:7101,localhost:7201 # Example: MatchExpression *.

Jsp MatchExpression *. Jsp PathPrepend=/test2 # VirtualHost2 = 127.0.0.2:80 DocumentRoot "C:/test/VirtualHost1" ServerName 127.0.0.2:80 #... WLS parameter ... WebLogicCluster localhost:7101,localhost:7201 # Example: MatchExpression *. Jsp MatchExpression *.

Jsp PathPrepend=/test2 #... WLS parameter ... Note that this is a Multiple IP-Based Virtual Hosts configuration (and not Name-Based as stated in the documentation). But this is actually good because this is exactly what you need when using SSL as you can't use name-based virtual hosts. Quoting Why can't I use SSL with name-based/non-IP-based virtual hosts?

From Apache's SSL/TLS Strong Encryption: FAQ The reason is very technical, and a somewhat "chicken and egg" problem. The SSL protocol layer stays below the HTTP protocol layer and encapsulates HTTP. When an SSL connection (HTTPS) is established Apache/mod_ssl has to negotiate the SSL protocol parameters with the client.

For this, mod_ssl has to consult the configuration of the virtual server (for instance it has to look for the cipher suite, the server certificate, etc. ). But in order to go to the correct virtual server Apache has to know the Host HTTP header field.To do this, the HTTP request header has to be read. This cannot be done before the SSL handshake is finished, but the information is needed in order to complete the SSL handshake phase.

Bingo! So, in the sampel above, modify the virtual hosts IP addresses and ports, the ServerName, adapt the IfModule to suit your needs (and set up DNS entries to point on the IPs) and there you go.

Thanks. Coincidentally, I'd found that document last night after I posted the question (my google-fu must have been weak before), but your confirmation that the approach is what I need is valuable. – Paul Jan 20 '10 at 8:29 @Paul You're welcome.

Glad you find it useful. Good luck. – Pascal Thivent Jan 20 '10 at 9:10.

I don't have any experience with weblogic, so maybe I'm missing something important. But this sounds like a straightforward application for apache's reverse proxy capability. Set up an apache instance serving https, and configure two locations as follows: LoadModule proxy_module modules/mod_proxy.

So LoadModule proxy_http_module modules/mod_proxy_http. So ProxyPass serverA:7001/app1" rel="nofollow">serverA:7001/app1 ProxyPassReverse serverA:7001/app1" rel="nofollow">serverA:7001/app1 ProxyPass serverB:8001/app2 ProxyPassReverse serverB:8001/app2.

I think the issue is the use of SSL. Otherwise, your solution would work. I also have to use the weblogic proxy, not just redirect (server1 and server2 are in fact weblogic clusters) – Paul Jan 19 '10 at 20:48.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.