[Date Prev] [Date Next] [Prev in Thread] [Next in Thread] [Date Index] [Thread Index]

Re: IIS Issue



A few options:


-  If you are not using IIS you could disable it and configure Tomcat for port 80 instead of 8080.

-  If you need IIS you could setup isapi_redirect with Tomcat to use IIS.

-  You can also setup a redirect to have http://yourserver:8080 to go to http://youruniqueurl


Brian



From: ARSList <arslist-bounces@arslist.org> on behalf of Brian Gillock <arslist2009@gmail.com>
Sent: Monday, March 5, 2018 8:52:39 AM
To: ARSList
Subject: Re: IIS Issue
 
Uncomment the 8080 connector in Tomcat's server.xml config.

On Mon, Mar 5, 2018 at 3:38 AM, Roy, Prakash <Prakash_Roy@bmc.com> wrote:

Hi Christian,

 

We need to understand your deployment architecture as below:

 

1)     Is there any reverse proxy server/load balancer configured?

2)     How many midtiers are configured?

3)     How many apps server’s configured and whether any apps side load balancer exists?

4)     If there is any RSSO configured?

5)     If there is single midtier which you are trying to access directly, does that machine host the IIS server too that works as a reverse proxy server?

6)     If the 5th point above is correct, does it mean that the IIS server is configured on port “80” which is the default port for http request?

 

 

If there is already port “80” configured for application other than midtier on the same machine then, midtier cannot be accessed using default port “80”. Midtier has to have some unique port configured for e.g “8080” to access it directly. You need to check the server.xml for the port configured for midtier.

 

Thanks,

Prakash

 

 

 

From: ARSList [mailto:arslist-bounces@arslist.org] On Behalf Of Smerz, Christian
Sent: 25 January 2018 21:10
To: arslist@ARSLIST.ORG
Subject: IIS Issue

 

Hi everyone,

We have upgraded our test system to 9.1.4  We have upgraded the RSSO component as well.  We cannot get to the midtier server with the direct URL, we are prompted with a domain login (assume this is coming from IIS) and cannot proceed.  If we add a port (:8080) to the FQDN it will work.  I’m hoping someone may have come across something similar and I’m just missing the easy fix.

 

Regards,

Christian Smerz

 



This message (including any attachments) is confidential and intended for a specific individual and purpose. If you are not the intended recipient, please notify the sender immediately and delete this message.


--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist




--
Brian Gillock

 
DISCLAIMER: The information contained in this e-mail and its attachments contain confidential information belonging to the sender, which is legally privileged. The information is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are notified that any disclosure, copying, distribution or action in reliance upon the contents of the information transmitted is strictly prohibited. If you have received this information in error, please delete it immediately.