Iis – Java application server behind IIS 7.5 on Windows Server 2008

iisiis-7.5javawindows-server-2008

I have a Java application server (GlassFish, indeed, but the problem is the same for any other application server, I guess), running on port 8080. And I have IIS 7.5 listening on port 80 as by default configuration.

I want to avoid people typing the port because it's unprofessional. So I want that when somebody types

http://myserver

the traffic is directed to IIS. And this is how it already works now. But I also want that when somebody types

http://myserver/java

the traffic is directed to port 8080 and consequently my GlassFish splash screen is displayed. If I have deployed an application on GlassFish under context root app1, typing

http://myserver/java/app1

should access the application.

How can I do this? I have tried with adding some rules with the URL Rewrite utility from IIS7.5 UI, but this shows the port after the rule has rewritten the url, and I want to avoid it.

Best Answer

It might be easier if you can use a sub-domain for the java app like http://java.myserver/. Then you could do something like the following, though I'm not familiar with GlassFish but I assume you can configure it to listen on a certain IP address like with TomCat. If you want to use port 80 for both apps you need IIS to listen on IP Address A and GlassFish to listen on IP Address B. Then use DNS to point myserver to IP A and java.myserver to IP B.

Then follow these steps: http://www.fredmastro.com/post/Restrict-IIS-to-listen-only-on-X-IP-Address-Allowing-you-to-co-run-with-TomCatApache-on-port-80-with-IIS-on-port-80.aspx

Basically limit IIS to only listen on IP A and not bind IP B. So that GlassFish can bind it to port 80.

Open a command prompt as an administrator

Show which IP Address IIS is listening/binding too with this command.

netsh http show iplisten

Then limit IIS to listen/bind certain IP address with this command

netsh http add iplisten xxx.xxx.x.x

Reboot the server (You could try restarting http service but that doesn’t always show up in services and it’s a pain. Easier to reboot).

Related Solutions

Iis – Windows 7 IIS 7.5 ASPX Pages Hang IIS in Application migrated from IIS6

I finally figured it out. There was a 3rd party DLL in the project called safileup.dll that was being used to upload files on the application. Removing that file from the bin directory fixed my hanging issues.

The dll in question was softartisans fileup. We will be discontinuing use of this add on.

IIS 7.5 folder and web site permissions

If you've created the website using the usual IIS7.5 out-of-the-box defaults then your "test website" will have had an application pool created for it as well.

The default identity that the site will execute requests as is ApplicationPoolIdentity. ApplicationPoolIdentity is a special synthesised account that is created on the fly and represents the identity of your site's application pool.

You state:

physical path has "IIS AppPool\DefaultAppPool" read and execute

This would explain why you're getting the 500.19 error. Unless you assigned the site to the "DefaultAppPool" application pool this permission won't be doing anything useful.

You need to assign the ApplicationPoolIdentity of the site (at least) read and execute permissions. To do this execute the following from the command line:

icacls <path_to_site> /grant "IIS APPPOOL\<app_pool_name>"(CI)(OI)(M)

Where <app_pool_name> is the name of the application pool that was created for your test site. You can find its name by executing:

appcmd list app /site.name:"<your site name>"

This will return something like and displays the name of your site's application pool (which ApplicationPoolIdentity is named after:

APP "test site/" (applicationPool:test site)

Best Answer

Related Solutions

Iis – Windows 7 IIS 7.5 ASPX Pages Hang IIS in Application migrated from IIS6

IIS 7.5 folder and web site permissions

Related Topic