Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
The moose likes BEA/Weblogic and the fly likes weblogic10 & IIS5. Issue setting up the proxy server. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "weblogic10 & IIS5. Issue setting up the proxy server." Watch "weblogic10 & IIS5. Issue setting up the proxy server." New topic
Author

weblogic10 & IIS5. Issue setting up the proxy server.

Rajesh Unnithan
Greenhorn

Joined: Feb 20, 2009
Posts: 22
Hi ,

I am facing an issue with IIS5.0 & weblogic10. I am new with IIS &webapps. Please help me to resolve the issue
We have an ear deployed in weblogic10 in a server box. And we have a windows2000 server where IIS5 is running. I am using the Microsoft IIS proxy plugin to try to redirect the entire request to the wl app server via IIS.
I have the following ?’s.
I followed the steps mentioned in this following link. I got confused with certain things mentioned in the document
http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/plugins/isapi.html#wp100492
Q1  Do we need to have IIS & Wl server running in the same box.
Q2  In the above link step 1 says copy the issproxy.dll to a directory accessible to IIS. Since in my case they both are running in different box, shall I copy it in to the box where IIS is running?
Q3  Step 2 talks about proxiying by file extension & step3 talks about proxying by path. Which one should I use for a simple ear application.
Q4  What is the URL I need to use to hit the IIS, so that it will redirect the request to the appropriate? For example, my weblogic server is running @ http://10.100.xxx.xxx:8001/app/index.jsp. To hit this URL, in IIS how should I send the request?

I know some of the questions looks pretty silly, I am new to this IIS stuff. Please help me to understand these stuff.

Appreciate your help.

Deepak Bala
Bartender

Joined: Feb 24, 2006
Posts: 6662
    
    5

I have not personally hooked up IIS with weblogic, but I know some of the high level steps that you need to take and have worked with this setup before, so I ll try to help.

Do we need to have IIS & Wl server running in the same box.


Not necessary

In the above link step 1 says copy the issproxy.dll to a directory accessible to IIS. Since in my case they both are running in different box, shall I copy it in to the box where IIS is running?


That should make sense

Step 2 talks about proxiying by file extension & step3 talks about proxying by path. Which one should I use for a simple ear application.


It depends on what you want to do. If you are sure that http://your_domain.com/application/* needs to be redirected to weblogic, do that. Else if you want *.jsp to be redirected to weblogic, take that approach.

What is the URL I need to use to hit the IIS, so that it will redirect the request to the appropriate? For example, my weblogic server is running @ http://10.100.xxx.xxx:8001/app/index.jsp. To hit this URL, in IIS how should I send the request?


Find the IP of the IIS server and simply replace that in the URL above, removing the port number of course. I am assuming here that IIS operates on port 80.

I know some of the questions looks pretty silly, I am new to this IIS stuff. Please help me to understand these stuff.


The concepts are pretty similar to hooking up an apache web server with say a tomcat server. With weblogic you can perform a marriage with IIS using the ISAPI dll. Don't fret you can do it


SCJP 6 articles - SCJP 5/6 mock exams - More SCJP Mocks
Rajesh Unnithan
Greenhorn

Joined: Feb 20, 2009
Posts: 22
Thanks Deepak,

I will try out the same and update you the results.

Appreciate your help.

Rajesh Unnithan
Greenhorn

Joined: Feb 20, 2009
Posts: 22
Sorry for late in responding. I was busy with some other works. I successfully configured it and I am able to connect to the weblogic server. I am facing a new issue now. All the request proxies from IIS to weblogic takes a lot of time to load the page. If I am directly accessing application the request is served with in few seconds, where as if I am getting the request through IIS, its taking more than 3 min to get a response back n load the page. Is it because I am missing some kind of setting in IIS or weblogic?

I am using IIS5 in a win2000 server & weblogic 10 running in a win XP box. There were no firewall issues or anything like tht.

Could you please let me know if I am missing some configuration here?
Deepak Bala
Bartender

Joined: Feb 24, 2006
Posts: 6662
    
    5

Rajesh Unnithan wrote:Sorry for late in responding. I was busy with some other works. I successfully configured it and I am able to connect to the weblogic server. I am facing a new issue now. All the request proxies from IIS to weblogic takes a lot of time to load the page. If I am directly accessing application the request is served with in few seconds, where as if I am getting the request through IIS, its taking more than 3 min to get a response back n load the page. Is it because I am missing some kind of setting in IIS or weblogic?

I am using IIS5 in a win2000 server & weblogic 10 running in a win XP box. There were no firewall issues or anything like tht.

Could you please let me know if I am missing some configuration here?


3 minutes !!! Thats crazy. Is IIS able to talk with weblogic seamlessly ? Any logs indicating timeouts or a possible network problem between IIS and weblogic. Are they both on the same machine. What is the ping between the machines ? Check the logs anyway since it might reveal some clues.

Congrats on setting the system up
Rajesh Unnithan
Greenhorn

Joined: Feb 20, 2009
Posts: 22
Thanks for the replay.

I could figure out the issue, there was a network deplay happening in one route, that was causing the issue. Now its working fine. thanks a lot for your help.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: weblogic10 & IIS5. Issue setting up the proxy server.