IIS - Tomcat Redirect Problem

[#1]

I've set up an XI 3.1 SP2 deployment on Windows 2003 Enterprise. The requirement is to use IIS redirect to Tomcat because the company standard is to use an IIS plug-in for SSO (Entrust GetAccess). Tomcat is working, but after installing the Jakarta isapi_redirect.dll according to the instructions at http://tomcat.apache.org/connectors-doc/index.html, requests going to IIS (http://myserver.qa.domain.com/InfoViewApp/logon.jsp) result in the following error:

Page cannot be displayed HTTP 500 - Internal server error

from the log:

2010-03-14 17:58:50 W3SVC1 10.8.145.161 GET /InfoViewApp/logon.jsp - 80 - nnn.nn.nnn.nn Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.1;SV1;.NETCLR1.1.4322;.NETCLR2.0.50727;.NETCLR3.0.4506.2152;.NETCLR3.5.30729;InfoPath.1;MS-RTCLM+8) 500 0 87

I've gone over the redirect configuration and everything seems to be there. Any thoughts on how to troubleshoot/get this working?

[denis_konovalov · Accepted solution]

if you post your workers.properties file and connectors definiton from tomcat server.xml, we can try to figure this out.

[Former Member · Accepted solution]

Ok, here are the definitions.

*_workers.properties*_

1. workers.properties -

#

1. This file provides minimal jk configuration properties needed to

2. connect to Tomcat.

#

1. The workers that jk should create and work with

#

worker.list=wlb,jkstatus

#

1. Defining a worker named ajp13w and of type ajp13

2. Note that the name and the type do not have to match.

#

worker.ajp13w.type=ajp13

worker.ajp13w.host=localhost

worker.ajp13w.port=8009

#

1. Defining a load balancer

worker.wlb.type=lb

worker.wlb.balance_workers=ajp13w

#

1. Define status worker

#

worker.jkstatus.type=status

Connector definietion from server.xml

<!-- Define an AJP 1.3 Connector on port 8009 -->

<Connector enableLookups="false" port="8009" protocol="AJP/1.3" redirectPort="8443"/>

<!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->

<!-- See proxy documentation for more information about using this. -->

<!--

<Connector port="8082"

maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

enableLookups="false" acceptCount="100" connectionTimeout="20000"

proxyPort="80" disableUploadTimeout="true" />

Edited by: Cinghiale on Mar 15, 2010 5:51 PM

I can ping the web server ports 8080, 8009, and 80, but ports 8082 and 8443 fail. BUT, this same config is running in XI R2 production, and pinging ports 8082, 8443 fails there too.

[denis_konovalov · Accepted solution]

Try this :

1. workers.properties -

#

1. This file provides minimal jk configuration properties needed to

2. connect to Tomcat.

#

1. The workers that jk should create and work with

#

worker.list=ajp13w,jkstatus

#

1. Defining a worker named ajp13w and of type ajp13

2. Note that the name and the type do not have to match.

#

worker.ajp13w.type=ajp13

worker.ajp13w.host=localhost

worker.ajp13w.port=8009

#

1. Defining a load balancer

#worker.wlb.type=lb

#worker.wlb.balance_workers=ajp13w

#

1. Define status worker

#

worker.jkstatus.type=status

Also, do jsp-samples work at all thru IIS ?

[Former Member · Accepted solution]

Denis, tried your worker.properties but still got the HTTP 500.

I can reach jsp-examples through Tomcat, but not IIS.

FYI, we opened a case.

[denis_konovalov · Accepted solution]

If you can't reach jsp-examples thru IIS - it's not a BOE issue, it's an issue with connector configuration. Tomcat support will be a better option (if they have any).

Is IIS on the same box as Tomcat ?

What version of connector are you using ?

What files came with it ?

Is IIS configured per documentation ?

I'm sure there is an SAP Note on this as well with examples... have you tried searching ?

Edited by: Denis Konovalov on Mar 15, 2010 4:50 PM

[Former Member · Accepted solution]

Correct, it wasn't a BOE issue. It turns out that the isapi_redirect.dll was never registered. The symptom was that there was never anything in the isapi.log file. Nothing was being redirected, resulting in those HTTP 500 errors. The key was to use an old copy of the Tomcat connector (in our case we used JK 1.2.14.exe), one that used an install program to build the folders, worker files and actually register the connector. We had previously copied a .dll from the Apache site, and although it appeared to be working (we got the green arrow in the isapi filter tab) it wasn't.

Tim and Denis,thanks for your help.

[BasicTek]

One of many possible issues with IIS-jakarta is the lack of support when something goes wrong. If at all possible use java SSO via AD and kerberos.

I didn't see all the details on the doc but to set it up in the past we had to remove and reinstall sometimes several times when it didn't work. Never figured out why.

Always try to get the connector working without authenticion enabled at 1st (anonymous in IIS) to simplify the setup.

IIS is looking for GET /InfoViewApp/logon.jsp and returns a 500 saying it is not found. This could indicate the jakarta redirect config files are not setup properly (proper host name/IP and directories to be redirected to tomcat)

Regards,

Tim