aspose file tools*
The moose likes BEA/Weblogic and the fly likes Weblogic Production Env Setup Newbie Problem 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 "Weblogic Production Env Setup Newbie Problem" Watch "Weblogic Production Env Setup Newbie Problem" New topic
Author

Weblogic Production Env Setup Newbie Problem

casey graves
Greenhorn

Joined: Dec 18, 2001
Posts: 1
Hi
I am a newbie with regards to WebLogic Setup in a "production" type environment.
I have an application on a Windows NT Server that builds fine and is viewable internally (behind the firewall) but is causing me problems when it is viewed outside the firewall.
The application is at 10.1.1.24/appname internally. We have the default port set to 80. We set an outside ip up and mapped port 80 requests to the internal ip. Since the 10.1.1.24/appname is the home page for a Domain.com, we setup a virtual host to not require the user to enter domain.com/appname to get to the home page. For some reason, when a user from outside tries to access the application, I get a http 403 error, access forbidden. Is their a setting I need to tweak in the config.xml file or in the web.xml file?
Any and all help would be appreciated
Thanks
Casey
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16145
    
  21

There's 2 ways to work what you are describing. One is via Network Address Translation (NAT). This simply allows users on the other side of the wall to share an external IP gateway, and can't be used for inbound requests, since every host on the other side has the same external IP address and there's no way for the external requester to know or specify which host will get the request. That could get a "403" if the request went to some other host that wasn't feeling cooperative.
More properly, you should have been set up with a proxy server. In this case, the external request goes to the proxy server, which rewrites it and forwards it to the WebLogic Server. Check the WebLogic log to see what the rewritten request looked like.
It's possible that WebLogic may object to the source IP, but I don't recall any options offhand that would result in a 403. Also, when running under a demo license, the total number of IPs that WLS will accept input from is limited.


Customer surveys are for companies who didn't pay proper attention to begin with.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Weblogic Production Env Setup Newbie Problem