i’ve got the IIS and tomcat to communicate. the problem i face now is the syntax of the infoview url in xir2.
when i type http:///xir2 its getting redirected by the redirector to the following url
http:///xir2/logon/logon.do and hence i’m getting a
HTTP Status 404 - /xir2/logon/logon.do
type Status report
message /xir2/logon/logon.do
description The requested resource (/xir2/logon/logon.do) is not available.
this happens only from via iis but seems to work when i use the http://:8080/xir2/logon/logon.do shows the login screen but i want to use iis as the webserver and tomcat as the app server.
can someone tellme what should be done so that the iis - tomcat connector can understand this logon.do command and show the login screen.
the mapping is controlled by the workers2.properties, so can you paste a copy of yours here? I know that when I tried to set this up I also had to revert to testing with a stripped down server.xml (server-minimal.xml) to get it working. So…
paste a copy of the URI section from workers2.properties so we can check it.
try backing up your server.xml and renaming server-minimal.xml to server.xml. Or if you want to hack around with your existing server.xml look for the AJP 1.3 connector parameter (which is commented out by default in the BOE Tomcat)
thanks rod. have you tried to use single signon nt authentication. the document mentions we need to modify web.config but that is only for iis asp version. do you have any idea what needs to be modified for nt authentication for jsp version.
thanks again Rod and also for the link. even the bo document mentions about iis and no mention of nt authentication even though it works beautifully in ver 6.x where i’ve implemented in couple of clients with iis and tomcat combination and seamless nt authentication. i don’t know why they changed it in xir2. if it can work in 6.x don’t know why they did it.
Can you point me as to where I can obtain the “Jakarta Connector for IIS”? We also use apache because of Performance Manager. We put in a case with BO and their documentation has a link to download the software from Apache, however, the link does not contain the file they want us to download
Can you point me as to where I can obtain the “Jakarta Connector for IIS”? We also use apache because of Performance Manager. We put in a case with BO and their documentation has a link to download the software from Apache, however, the link does not contain the file they want us to download
I have followed this post and basicly saw two approaches to enabling SSO to work with Tomcat.
The first approach, from architecture standpoint, seems to be ‘cleaner’, it invovles using asp pages to get a token from IIS and passing it to jsp onthe tomcat side. But it ‘may’ have some performance issues.
The other involves setting up some redirector in IIS to allow it to direct any servet/JSP requests to tomcat. It sounded more efficient and requires much more effort to set up and has many grey areas on how the end product will look like. (at least for myself)
I went down the second path and configured the Tomcat and IIS bridge, I was able to access the jsp-examples on Tomcat through IIS as the following: http://infoview/jsp-examples instead of http://infoview:8080/jsp-examples. Our reasoning for using tomcat is that webi interactiver viewer only comes in the Java flavor, but we still like to use IIS as it allows sso. so my question are, when you use the bridge,
Would you simply use IIS for authenticating a user and use tomcat for everything else?
or
Would you use IIS for everything except the part that is not supported under .NET, in my case, webi interactive viewer. If so, when a user logges in to infoview.NET, would a session also get created on tomcat side. Is this done automatically or through custom coding. Can someone provide an example of their workers2.properties file so I can see whether I misunstood the whole thing.
I have followed this post and basicly saw two approaches to enabling SSO to work with Tomcat.
The first approach, from architecture standpoint, seems to be ‘cleaner’, it invovles using asp pages to get a token from IIS and passing it to jsp onthe tomcat side. But it ‘may’ have some performance issues.
The other involves setting up some redirector in IIS to allow it to direct any servet/JSP requests to tomcat. It sounded more efficient and requires much more effort to set up and has many grey areas on how the end product will look like. (at least for myself)
I went down the second path and configured the Tomcat and IIS bridge, I was able to access the jsp-examples on Tomcat through IIS as the following: http://infoview/jsp-examples instead of http://infoview:8080/jsp-examples. Our reasoning for using tomcat is that webi interactiver viewer only comes in the Java flavor, but we still like to use IIS as it allows sso. so my question are, when you use the bridge,
Would you simply use IIS for authenticating a user and use tomcat for everything else?
or
Would you use IIS for everything except the part that is not supported under .NET, in my case, webi interactive viewer. If so, when a user logges in to infoview.NET, would a session also get created on tomcat side. Is this done automatically or through custom coding. Can someone provide an example of their workers2.properties file so I can see whether I misunstood the whole thing.
Any luck? I receive the following message "Service Temporary Unavailable!
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Are you getting this error message all the time you try to access it or it is intermittent?
Please check Jakarta redirector logs if you have enabled logging feature.
This log file will give clear picture of what is wrong with Tomcat or ISAPI redirector.
We intend to use IIS for authentication and then just pass the user through the java login screen and into Infoview.
We have a custom ASP page that creates the logon token and redirects to http://:8080//InfoViewApp/logon/start.do
The issue we have run into is that we can not redirect to http://:8443//InfoViewApp/logon/start.do
Our SSL cert is at the virtual IP of the server and once the redirect call is made, there should ideally be just unencrypted data until it hits IIS which would then encrypt and pass on to the browser, but so far … no success.
We have tried using the isapi redirector but nothing there too.