NxTop HowTo: Use IIS as front end to Apache Tomcat

thumbsshameΔιακομιστές

17 Νοε 2013 (πριν από 3 χρόνια και 11 μήνες)

123 εμφανίσεις

NxTop HowTo: Use IIS as front end to Apache Tomcat
This document describes how to install IIS and use ISAPI redirectors to use IIS SSL front end to connect
to Apache Tomcat.
Document Revision: 1.0
Document Date: 22-June-2010
Motivation
You may want to install IIS as a front end to Apache Tomcat instead of using Apache HTTP services for a
few reasons.
• Your more familiar with IIS and its configurations
• You already or are required to use IIS across your enterprise
• You want windows based bandwidth Throttling or access restriction
• You want to use your own Encryption techniques through IIS
• You may receive better performance depending on your environment
Procedure
1. Install NxTop Center
2. Install IIS with the default configuration + All of the “Application Development” **

3. Reboot the System
4. Get IIS-CONFIG.zip from VirtualComputer
5. Extract to C:\Inetpub (will create folder C:\Inetpub\IIS-CONFIG) – this folder contains iis-config,
isapi, and ssl-export folders.
6. Copy the folders in C:\Inetpub\IIS-CONFIG into C:\Inetpub
7. Go to C:\Program Files (x86)\Apache Software Foundation\Tomcat 6.0\Conf directory and make
a copy of the file server.xml
8. Go to C:\Inetpub\iis-config folder and double click iis-config.cmd
9. Go to C:\Program Files (x86)\Apache Software Foundation\Tomcat 6.0\
10. Edit server.xml – Under the section that says <!-- Should be 443 --> There is a section that starts
<Connect port = “443” all the way to keystorePass=”9786929332”/> - In front of the <Connect
port = “443” place the following: <!-- at the end of keystorePass=”9786929332”/> place the
following: --> The final outcome should look like this:
<!-- <Connector port="443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="100"
scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" tomcatAuthentication="false"
enableLookups="false" acceptCount="100” ciphers="SSL_RSA_WITH_RC4_128_MD5"
keystoreFile="/ssl/nxtopcenter_virtualcomputer_com.jks" keystorePass="97869209332"/> -->
11. This allows port 443 to be used by IIS
Verify It’s Running
You can verify that IIS is now accepting connections on port 443.
1. Go to C:\Inetpub\logs\LogFiles\W3SVC1. Open up the newest log file you see by date (the
format will show something like u_exyearmonthday.log – if you see something similar to the
following, IIS is working (x.x.x.x being the management server IP address, y.y.y.y being the nxtop
engine IP address):
x.x.x.x POST /Mgmt_EventChannel/EventChannel - 443 - x.x.x.x Java/1.6.0_13 200 0 0 15
x.x.x.x POST /Mgmt_EventChannel/EventChannel - 443 - x.x.x.x Java/1.6.0_13 200 0 0 15
x.x.x.x POST /Mgmt_EventChannel/EventChannel - 443 - x.x.x.x Java/1.6.0_13 200 0 0 46
x.x.x.x POST /Mgmt_EventChannel/EventChannel - 443 - x.x.x.x Java/1.6.0_13 200 0 0 15
2. A further check is to go to a client system, note the IP address of the system (Our Client is
y.y.y.y) in the NxTop console. Run a “Check Now” for updates. You should see the new IP
address looking for updates through the same log. Similar to below:
x.x.x.x POST /MgmtControl/ControlServlet version=1.7 443 - y.y.y.y - 200 5 0 233
x.x.x.x POST /MgmtControl/ControlServlet version=1.7 443 - y.y.y.y - 200 0 0 3448
x.x.x.x POST /MgmtControl/ControlServlet version=1.7 443 - y.y.y.y - 200 5 0 624
x.x.x.x POST /MgmtControl/ControlServlet version=1.7 443 - y.y.y.y - 200 0 0 1763
Precautions and Limitations
Editing the Server.xml file incorrectly could render your web access crippled. Make a copy of the
original file before editing.
Related Articles
http://www.iisadmin.co.uk/?p=72&page=1

http://tomcat.apache.org/tomcat-3.3-doc/Tomcat-Workers-HowTo.html

http://tomcat.apache.org/connectors-doc/reference/workers.html

** You can also install IIS with this command: Dism /online /enable-feature /featurename:IIS-
WebServerRole /featurename:IIS-WebServer /featurename:IIS-CommonHttpFeatures /featurename:IIS-
StaticContent /featurename:IIS-DefaultDocument /featurename:IIS-DirectoryBrowsing
/featurename:IIS-HttpErrors /featurename:IIS-ApplicationDevelopment /featurename:IIS-ASPNET
/featurename:IIS-NetFxExtensibility /featurename:IIS-ISAPIExtensions /featurename:IIS-ISAPIFilter
/featurename:IIS-HealthAndDiagnostics /featurename:IIS-HttpLogging /featurename:IIS-LoggingLibraries
/featurename:IIS-RequestMonitor /featurename:IIS-Security /featurename:IIS-RequestFiltering
/featurename:IIS-Performance /featurename:IIS-HttpCompressionStatic /featurename:IIS-
WebServerManagementTools /featurename:IIS-ManagementScriptingTools)