Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
View Interest List Message Details
<< Back to Search Results

Date: 12/12/2006
From: matt@newatlanta.com
Subject: Re: [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in
And here is another possible solution for SE ISAPI:

Create another IIS Website besides the Default Website, and configure it 
to respond only to requests that use "a.com" as the host.
Move the SE Filter to be on that 1 website only.
Keep your BEA component on the Default website.

Then requests that use a.com will go to the a.com website which will 
have SE ISAPI hooked into it.
And requests that any other hostname will go to the Default Website 
which does not have SE ISAPI hooked into it.

This solution would not require you to define your own ServletExec 
Virtual Servers, or to make any other SE-specific configurations.

Matt McGinty
Software Engineer
New Atlanta Communications, LLC
http://www.newatlanta.com 



matt@newatlanta.com wrote:

> Sounds like you have already moved the SE filter from the global level 
> down to the level of a particular website.
> If so, then that means you essentially have 2 brands of servlet engine 
> fighting for who gets to serve requests to 2 different webapps.
>
> Part of the problem is that you are using the exact same context path 
> (a single forward slash) for each webapp.
> That's OK to do, so long as you use the hostname to distinguish 
> between them.
>
> But by default, SE is configured to handle all requests (no matter 
> what the hostname).
>
> You could use 2 different context paths for each of your 2 webapps.
> Of course you'd couldn't use a single forward slash as the       
context 
> path of *any* webapp in either brand of servlet/jsp engine since that 
> would match all requests, causing all requests to go that engine.
>
> So you could use /se as the context path for your SE webapp.
> Then you could use /bea as the context path for your BEA webapp.
>
> Or you could use SE AS instead of SE ISAPI, editing the 
> webadapter.properties file as I mentioned earlier.
> Or you could use SE ISAPI but do this:
>
>  1. create a new SE Virtual Server (done via the SE admin UI) which 
> handles requests that use a.com as the hostname.
>  2. undeploy your app from SE's Virtual Server named                  
"default" (i.e. 
> the Default Virtual Server).
>  3. redeploy your app under the SE Virtual Server that you created in 
> #1 above (you must do this via it's own Admin UI, which
>      would be accessed using http://a.com/servletexec/admin
>  4. You'd also need to remove the default app that's deployed    
inside 
> the SE Virtual Server named "default" since it's context
>     path is a single forward slash.
>
> You may also find this posting to be helpful:
>
>                                                                            
http://www.newatlanta.com/c/products/servletexec/self_help/archiveSearch/detail?
page=1&messageId=99222
>
>Matt McGinty
>Software Engineer
>New Atlanta Communications, LLC
>http://www.newatlanta.com 
>
>
>
> sudhir.mehta@wipro.com wrote:
>
>>
>>                                                                        
------------------------------------------------------------------------
>>
>> Subject:
>> RE: [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in
>> From:
>> <sudhir.mehta@wipro.com>
>> Date:
>> Wed, 13 Dec 2006 03:19:57 +0530
>> To:
>> <servletexec-interest@newatlanta.com>
>>
>> To:
>> <servletexec-interest@newatlanta.com>
>>
>>
>>Hi Matt,
>> 
>>Thanks for your reply but i have the following problem:
>> 
>>Both applications are on the same level "Default Web Site".   
So i need to configure both the filters at the "Default Web Site"     
Level only
>>Is there any other way - some configuration in Servlet Exec?
>>We are using SE ISAPI
>> 
>>Regards,
>>Sudhir Mehta
>>
>>________________________________
>>
>>From: servletexec-interest-owner@newatlanta.com on behalf of            
matt@newatlanta.com
>>Sent: Wed 12/13/2006 2:54 AM
>>To: servletexec-interest@newatlanta.com
>>Subject: Re: [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in
>>
>>
>>By default, when SE is installed against IIS, the ServletExec Filter    
(an ISAPI Filter) gets placed at the global "websites" level within   
IIS.
>>This means that the SE filter gets invoked for all requests (all        
hostnames... i.e. all IIS websites).
>>If you wish the SE filter to only come into play for 1 particular IIS   
website (and not others) then:
>>
>> If you are using SE ISAPI:
>> Remove the SE Filter from the global level of IIS, and then add it at  
the level of your 1 particular IIS website.
>> You may do this for exactly 1 IIS website.
>>
>> If you are using SE AS:
>> Leave the SE Filter where it is (the global level of IIS), and simply  
edit the webadapter.properties file
>> to change "...hosts=all"  to "...hosts=a.com".
>> That way requests will only be routed to your SE AS instances when the 
host header in the request is "a.com".
>>
>>Matt McGinty
>>Software Engineer
>>New Atlanta Communications, LLC
>>http://www.newatlanta.com 
>>
>>
>>sudhir.mehta@wipro.com wrote: 
>>
>>	Hi,
>>	 
>>	I have a IIS 6.0 Web Server. I have the following installed on it:
>>	 
>>	1. Servlet Exec 5.0
>>	2. BEA Web Logic - IIS Proxy Plug-in
>>	 
>>	We have deployed a application "a" to be served by Servlet   
Exec 5.0 For eg: http://a.com/a.jsp
>>	Another application "b" is deployed in Web Logic which we    
access through IIS - http://b.com/b.jsp
>>	 
>>	But when we access the URL http://b.com/b.jsp, Servlet Exec tries to   
locate and execute the JSP and gives 404 error.
>>	 
>>	Can we do some configurations in Servlet Exec, so has to not serve the 
web logic application.
>>	 
>>	Your help will be highly appreciated.
>>	 
>>	Regards,
>>	Sudhir Mehta
>>
>>The information contained in this electronic message and any            
attachments to this message are intended for the exclusive use of the           
addressee(s) and may contain proprietary, confidential or privileged            
information. If you are not the intended recipient, you should not disseminate, 
distribute or copy this e-mail. Please notify the sender immediately and        
destroy all copies of this message and any attachments. 
>>
>>WARNING: Computer viruses can be transmitted via email. The recipient   
should check this email and any attachments for the presence of viruses. The    
company accepts no liability for any damage caused by any virus transmitted by  
this email.
>>
>>www.wipro.com
>>	
>>
>>  
>>
>>------------------------------------------------------------------------

>>
>>
>>The information contained in this electronic message and any            
attachments to this message are intended for the exclusive use of the           
addressee(s) and may contain proprietary, confidential or privileged            
information. If you are not the intended recipient, you should not disseminate, 
distribute or copy this e-mail. Please notify the sender immediately and        
destroy all copies of this message and any attachments. 
>>
>>WARNING: Computer viruses can be transmitted via email. The recipient   
should check this email and any attachments for the presence of viruses. The    
company accepts no liability for any damage caused by any virus transmitted by  
this email.
>> 
>>www.wipro.com
>>

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
 <meta content="text/html;charset=ISO-8859-1"                      
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Verdana">And here is another possible solution for  
SE ISAPI:<br>
<br>
Create another IIS Website besides the Default Website, and configure
it to respond only to requests that use "a.com" as the                
host.<br>
Move the SE Filter to be on that 1 website only.<br>
Keep your BEA component on the Default website.<br>
<br>
Then requests that use a.com will go to the a.com website which will
have SE ISAPI hooked into it.<br>
And requests that any other hostname will go to the Default Website
which does not have SE ISAPI hooked into it.<br>
<br>
This solution would not require you to define your own ServletExec
Virtual Servers, or to make any other SE-specific configurations.<br>
</font>
<pre class="moz-signature" cols="72">Matt McGinty
Software Engineer
New Atlanta Communications, LLC
<a class="moz-txt-link-freetext"                                   
href="http://www.newatlanta.com">http://www.newatlanta.com</a>
; </pre>
<br>
<br>
<a class="moz-txt-link-abbreviated"                                
href="mailto:matt@newatlanta.com">matt@newatlanta.com</a>    
wrote:
<blockquote cite="mid457F2DB7.6060201@newatlanta.com"              
type="cite">
 <meta content="text/html;charset=ISO-8859-1"                      
http-equiv="Content-Type">
 <title></title>
 <font face="Verdana">Sounds like you have already moved the SE 
filter
from the global level down to the level of a particular website.<br>
If so, then that means you essentially have 2 brands of servlet engine
fighting for who gets to serve requests to 2 different webapps.<br>
 <br>
Part of the problem is that you are using the exact same context path
(a single forward slash) for each webapp.<br>
That's OK to do, so long as you use the hostname to distinguish between
them.<br>
 <br>
But by default, SE is configured to handle all requests (no matter what
the hostname).<br>
 <br>
You could use 2 different context paths for each of your 2 webapps.<br>
Of course you'd couldn't use a single forward slash as the context    
path
of *any* webapp in either brand of servlet/jsp engine since that would
match all requests, causing all requests to go that engine.<br>
 <br>
So you could use /se as the context path for your SE webapp.<br>
Then you could use /bea as the context path for your BEA webapp.<br>
 <br>
Or you could use SE AS instead of SE ISAPI, editing the
webadapter.properties file as I mentioned earlier.<br>
Or you could use SE ISAPI but do this:<br>
 <br>
&nbsp;1. create a new SE Virtual Server (done via the SE admin UI) which
handles requests that use a.com as the hostname.<br>
&nbsp;2. undeploy your app from SE's Virtual Server named              
"default" (i.e.
the Default Virtual Server).<br>
&nbsp;3. redeploy your app under the SE Virtual Server that you created in
#1 above (you must do this via it's own Admin UI, which<br>
&nbsp;&nbsp;&nbsp;&nbsp; would be accessed using <a          
class="moz-txt-link-freetext"
href="http://a.com/servletexec/admin">http://a.com/servletexec/admi
n</a><br>
&nbsp;4. You'd also need to remove the default app that's         
deployed inside
the SE Virtual Server named "default" since it's                 
context<br>
&nbsp;&nbsp;&nbsp; path is a single forward slash.<br>
 <br>
You may also find this posting to be helpful:<br>
 <br>
 <a class="moz-txt-link-freetext"
href="http://www.newatlanta.com/c/products/servletexec/self_help/archiveSea
rch/detail?page=1&amp;messageId=99222">http://www.newatlanta.com/c/p
roducts/servletexec/self_help/archiveSearch/detail?page=1&amp;messageId=9922
2</a><br>
 </font>
 <pre class="moz-signature" cols="72">Matt McGinty
Software Engineer
New Atlanta Communications, LLC
<a class="moz-txt-link-freetext"                                   
href="http://www.newatlanta.com">http://www.newatlanta.com</a>
; </pre>
 <br>
 <br>
 <a class="moz-txt-link-abbreviated"
href="mailto:sudhir.mehta@wipro.com">sudhir.mehta@wipro.com</a&g
t; wrote:
 <blockquote
cite="mid7F24577C3B4C0F4191E30AC8036159784358D4@BLR-EC-M
BX01.wipro.com"
type="cite"><br>
   <hr size="4" width="90%"><br>
   <table class="header-part1" border="0"                
cellpadding="0"
cellspacing="0" width="100%">
     <tbody>
       <tr>
         <td>
         <div class="headerdisplayname" style="display:       
inline;">Subject:
         </div>
RE: [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in</td>
       </tr>
       <tr>
         <td>
         <div class="headerdisplayname" style="display:       
inline;">From:
         </div>
         <a class="moz-txt-link-rfc2396E"
href="mailto:sudhir.mehta@wipro.com">&lt;sudhir.mehta@wipro.com
&gt;</a></td>
       </tr>
       <tr>
         <td>
         <div class="headerdisplayname" style="display:       
inline;">Date:
         </div>
Wed, 13 Dec 2006 03:19:57 +0530</td>
       </tr>
       <tr>
         <td>
         <div class="headerdisplayname" style="display:       
inline;">To: </div>
         <a class="moz-txt-link-rfc2396E"
href="mailto:servletexec-i
nterest@newatlanta.com">&lt;servletexec-i
nterest@newatlanta.com&gt;</a></td>
       </tr>
     </tbody>
   </table>
   <table class="header-part2" border="0"                
cellpadding="0"
cellspacing="0" width="100%">
     <tbody>
       <tr>
         <td>
         <div class="headerdisplayname" style="display:       
inline;">To: </div>
         <a class="moz-txt-link-rfc2396E"
href="mailto:servletexec-i
nterest@newatlanta.com">&lt;servletexec-i
nterest@newatlanta.com&gt;</a></td>
       </tr>
     </tbody>
   </table>
   <br>
   <pre wrap="">Hi Matt,

Thanks for your reply but i have the following problem:

Both applications are on the same level "Default Web Site". So i need 
to configure both the filters at the "Default Web Site" Level only
Is there any other way - some configuration in Servlet Exec?
We are using SE ISAPI

Regards,
Sudhir Mehta

________________________________

From: <a class="moz-txt-link-abbreviated"
href="mailto:servletexec-interest-o
wner@newatlanta.com">servletexec-interest-o
wner@newatlanta.com</a> on behalf of <a
class="moz-txt-link-abbreviated"                                      
href="mailto:matt@newatlanta.com">matt@newatlanta.com</a>
Sent: Wed 12/13/2006 2:54 AM
To: <a class="moz-txt-link-abbreviated"
href="mailto:servletexec-interest@newatlanta.com">servletexec-i
nterest@newatlanta.com</a>
Subject: Re: [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in


By default, when SE is installed against IIS, the ServletExec Filter (an ISAPI  
Filter) gets placed at the global "websites" level within IIS.
This means that the SE filter gets invoked for all requests (all hostnames...   
i.e. all IIS websites).
If you wish the SE filter to only come into play for 1 particular IIS website   
(and not others) then:

If you are using SE ISAPI:
Remove the SE Filter from the global level of IIS, and then add it at the level 
of your 1 particular IIS website.
You may do this for exactly 1 IIS website.

If you are using SE AS:
Leave the SE Filter where it is (the global level of IIS), and simply edit the  
webadapter.properties file
to change "...hosts=all"  to "...hosts=a.com".
That way requests will only be routed to your SE AS instances when the host     
header in the request is "a.com".

Matt McGinty
Software Engineer
New Atlanta Communications, LLC
<a class="moz-txt-link-freetext"                                   
href="http://www.newatlanta.com">http://www.newatlanta.com</a>
; 


<a class="moz-txt-link-abbreviated"                                
href="mailto:sudhir.mehta@wipro.com">sudhir.mehta@wipro.com</a&g
t; wrote: 

Hi,
 
I have a IIS 6.0 Web Server. I have the following installed on it:
 
1. Servlet Exec 5.0
2. BEA Web Logic - IIS Proxy Plug-in
 
We have deployed a application "a" to be served by Servlet Exec 5.0   
For eg: <a
class="moz-txt-link-freetext"                                         
href="http://a.com/a.jsp">http://a.com/a.jsp</a>
Another application "b" is deployed in Web Logic which we access      
through IIS - <a
class="moz-txt-link-freetext"                                         
href="http://b.com/b.jsp">http://b.com/b.jsp</a>
 
But when we access the URL <a class="moz-txt-link-freetext"
href="http://b.com/b.jsp">http://b.com/b.jsp</a>, Servlet    
Exec tries to locate and execute the JSP and gives 404 error.
 
Can we do some configurations in Servlet Exec, so has to not serve the web      
logic application.
 
Your help will be highly appreciated.
 
Regards,
Sudhir Mehta

The information contained in this electronic message and any attachments to     
this message are intended for the exclusive use of the addressee(s) and may     
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should    
check this email and any attachments for the presence of viruses. The company   
accepts no liability for any damage caused by any virus transmitted by this     
email.

<a class="moz-txt-link-abbreviated"                                
href="http://www.wipro.com">www.wipro.com</a>


 </pre>
   <pre wrap=""><hr size="4"                       
width="90%">

The information contained in this electronic message and any attachments to     
this message are intended for the exclusive use of the addressee(s) and may     
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should    
check this email and any attachments for the presence of viruses. The company   
accepts no liability for any damage caused by any virus transmitted by this     
email.

<a class="moz-txt-link-abbreviated"                                
href="http://www.wipro.com">www.wipro.com</a></pre>
 </blockquote>
</blockquote>
</body>
</html>

Message Thread
Date Subject Author
12/12/2006 Re: [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in matt@newatlanta.com
12/12/2006 RE: [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in sudhir.mehta@wipro.com
12/12/2006 Re: [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in matt@newatlanta.com
12/12/2006 Re: [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in matt@newatlanta.com
12/12/2006 [ServletExec] Servlet Exec and IIS - BEA Proxy Plug-in sudhir.mehta@wipro.com
<< Back to Search Results


   
company media information terms of use privacy policy contact us