http://www.onjava.com/pub/a/onjava/2002/07/31/tomcat.html http://www.onjava.com/pub/ct/33

When you later run XWiki in Tomcat you may get an Out Of Memory error, especially if you're trying to import large files into your wiki. To solve this allocate more memory to the JVM. For Tomcat this can be done by setting the JAVA_OPTS environment property (on Windows to allocate 300MB you would set JAVA_OPTS to -Xmx300m). If you are running Tomcat as service then defining JAVA_OPTS will not help. There is a utility provided in the bin folder of your Tomcat installation (for example for Tomcat 5.x on Windows it's called tomcat5w.exe). It's a GUI tool which can be used to set various options including the heap size.

http://bugs.sakaiproject.org/confluence/display/DOC/Section+-+Tomcat+Installation+(2.5)

    -Xmx768m
    -Xms768m
    -XX:PermSize=128m
    -XX:MaxPermSize=256m

c:\Program Files\Java\jre6\bin\client\Xusage.txt Server Info

    -Xmixed           mixed mode execution (default)
    -Xint             interpreted mode execution only
    -Xbootclasspath:
                      set search path for bootstrap classes and resources
    -Xbootclasspath/a:
                      append to end of bootstrap class path
    -Xbootclasspath/p:
                      prepend in front of bootstrap class path
    -Xnoclassgc       disable class garbage collection
    -Xincgc           enable incremental garbage collection
    -Xloggc:    log GC status to a file with time stamps
    -Xbatch           disable background compilation
    -Xms        set initial Java heap size
    -Xmx        set maximum Java heap size
    -Xss        set java thread stack size
    -Xprof            output cpu profiling data
    -Xfuture          enable strictest checks, anticipating future default
    -Xrs              reduce use of OS signals by Java/VM (see documentation)
    -Xcheck:jni       perform additional checks for JNI functions
    -Xshare:off	      do not attempt to use shared class data
    -Xshare:auto      use shared class data if possible (default)
    -Xshare:on	      require using shared class data, otherwise fail.

  The -X options are non-standard and subject to change without notice.

Most of this information came from these very helpful and better written links:

• The Apache Tomcat Connector - Reference Guide - Configuring IIS
• The Apache Tomcat Connector - Webserver HowTo - IIS Setup
• The Apache Tomcat Connector - Generic HowTo - Workers Howto
• Tomcat Wiki - Tomcat and IIS Howto

This link may also be helpful:

• Setting up Confluence with IIS - a similar article to this one that contains screenshots

http://www.atlassian.com/software/jira/docs/v3.11/iisintegration.html

my specifics

Java JDK path : C:\Program Files\Java\jre1.6.0_07 
Tomcat path : E:\Xwiki\Tomcat 6.0

JSP/Servlet webroot (via IIS/mod_jk) : E:\Xwiki\Tomcat 6.0\webapps 
JSP/Servlet webroot (via native Tomcat server, port 8080) : E:\Xwiki\Tomcat 6.0\webapps

Access JSP/Servlet pages via IIS/mod_jk : http://localhost/[jkmount-mapped url of your webapp] 
Access native Tomcat server : http://localhost:8080/ 

isapi_redirect.dll is placed in E:\Xwiki\Tomcat 6.0\bin\win32\i386\isapi_redirect.dll

When IIS calls isapi_redirect.dll, it checks for a local config file in the same directory as the dll. If the config file isn't there, it checks the registry (the registry is the normal way to configure it).

If you wish to increase the logging in the isapi.log file, set it to 'debug' instead of 'info'.

A virtual directory is needed within IIS to the isapi_redirect.dll file. The based on the registry entry “extension_uri” the dll will be accessed by Tomcat or IIS as “http:/jakarta/isapi_redirect.dll”; therefore, the virtual directory references “E:\Xwiki\Tomcat 6.0\bin\win32\i386”. (iis log file SYSTEM32/LogFiles/W3SVC1 )

• Using the IIS management console, add a new virtual directory to your IIS web site.
• The name of the virtual directory must be jakarta (see: entension_uri).
• Its physical path should be the directory where you placed isapi_redirect.dll (E:\Xwiki\Tomcat 6.0\bin\win32\i386).
• Give this new virtual directory “execute” access.

• Using the IIS management console, add isapi_redirect.dll as a filter in your IIS web site.
  • To create the website“

 
1. Right-Click on the Web Sites Folder and Select New -> Web Site
2. Click Next and enter "Academus" for a Description.
3. For the IP and Port settings, the default port 80 should be used. If you would like IIS to listen on a
specific interface you may select it here.
4. Click Next and select the path to the root of the web server:
INSTALL_ROOT\unicon\Academus\portal-tomcat-a\webapps
5. Click Next and select only the Read option.
6. Click Finish.
7. Right Click on the Academus Web Site and select properties.
8. On the Web Site Tab, change the Active Log Format to NCSA Common Log Format
9. On the Homepage Tab, select "A redirection to a URL" and Type in "http://SERVERNAME/portal" in
the "Redirect to:" entry box
10. Place a check mark next to the "A Directory below URL entered"
11. On the Documents Tab, remove all of the content page types and add index.html
12. Click apply, but do not close this dialog as we will need it in the next section

• Under the website properties, go to the ISAPI Filters tab and add a new filter called 'Jakarta-Tomcat' (I don not think the name references anything).
• The name of the filter should reflect its task (I use the name tomcat), its executable must be E:\Xwiki\Tomcat 6.0\bin\win32\i386\isapi_redirect.dll.
• The filter should go to:
  • E:\Xwiki\Tomcat 6.0\bin\win32\i386\isapi_redirect.dll

 
4.8 Add .properties mime type
3. In the IIS Manager, right-click on the local computer and select properties
4. Click the MIME Types... button
5. Click New and enter .properties in the Extension field and text/plain in the MIME type field
6. Click OK until you are back to the IIS Manager

If you're using IIS 6.0 you must also do the following:

Using the IIS management console, add the Jakarta Isapi Redirector to the Web Service Extensions.

• Right-click on Web Service Extensions and choose Add a new Web Service Extension.
• Enter tomcat for the Extension Name.
• Add the E:\Xwiki\Tomcat 6.0\bin\win32\i386\isapi_redirect.dll to the required files.
• Check the Set extension status to Allowed.
• Click on OK.

• Restart IIS (stop + start the IIS service)
• make sure that the tomcat filter is marked with a green up-pointing arrow.

I changed or created three configuration files. All of them were in E:\Xwiki\Tomcat 6.0\conf.

Unchanged

Example: server.xml is the main setup file for Tomcat that specifies virtual hosts, connectors and the like. I added a line to the standard Laszlo setup for the connector on port 8009. Please see the example file below. The original connector for port 8080 I left intact.

<Server port="8005" shutdown="SHUTDOWN">
  <Service name="LPS">
    <Connector port="8009" enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
  <Connector port="8080" />
    <Engine name="LPS" defaultHost="localhost">
      <Logger className="org.apache.catalina.logger.FileLogger" />
      <Host name="localhost" appBase="webapps" />
    </Engine>
  </Service>
</Server>

An example

/etc/tomcat/server.xml

This is the main configuration file for Tomcat.
Most of it should be set correctly and can be left alone. Please note the section:

  <Connector className="org.apache.tomcat.service.PoolTcpConnector"> 
     <Parameter name="handler" 
       value="org.apache.tomcat.service.http.HttpConnectionHandler"/> 
     <Parameter name="port" 
      value="8081"/> 
  </Connector> 

This configures Tomcat to be an HTTP server on port 8081.
You probably do not want this in a production environment,
it is a security risk, so comment it out once you have set everything up. Comments are done like in HTML, with <!- ... ->.

Near the bottom of the file is the Context section. Here is where you add new web applications.

  <Context path="/examples" 
     docBase="webapps/examples" 
     crossContext="false" 
     debug="0" 
     reloadable="true" > 
  </Context> 

The path defines the URL path that this context is for.
In this example, that would be http://localhost/examples/. docBase specifies where the web application is to be found. You may specify absolute paths,
but if you put a relative path it will be relative to TOMCAT_HOME which is /usr/share/tomcat in Debian, by default. crossContext allows the web app to access other contexts, default is true.
Default for debug is 0. reloadable=''true'' will cause the web application to be recompiled each time it is accessed, which may be bad for a production environment; default is ``true'' however.

When you add a Context to this file, you must update the tomcat.conf that you copied from tomcat-auto, if you decided to copy it.
When you do Virtual Hosts (see Section [*]), you must add the information that would normally go in tomcat-auto to the correct <VirtualHost> section instead.

http://www.ccl.net/cca/software/UNIX/apache/solaris-t3.2b5/files/workers.properties.txt.shtml

http://www.ccl.net/cca/software/UNIX/apache/solaris-t3.2b5/files/workers.properties-12.shtml

The workers.properties file I created in E:\Xwiki\Tomcat 6.0\conf The workers file tells Tomcat about connectors or 'workers', which port, host and protocol they are using.

This is my configuration.

workers.tomcat_home=E:\Xwiki\Tomcat 6.0
workers.java_home=C:\Program Files\Java\jre1.6.0_07
# You should configure your environment slash... ps=\ on NT and / on UNIX
ps=\
# Define worker
worker.list=wikiWorker
# Set properties for worker 'wikiWorker' (ajp13)
worker.wikiWorker.port=8009
worker.wikiWorker.host=localhost
worker.wikiWorker.type=ajp13
worker.wikiWorker.cachesize=10
worker.wikiWorker.cache_timeout=600
worker.wikiWorker.socket_keepalive=1
worker.wikiWorker.recycle_timeout=300

This is an example.

# Define worker 'example'
worker.list=example
 
# Set properties for worker 'example' (ajp13)
worker.example.type=ajp13
worker.example.host=localhost
worker.example.port=8009
 
worker.example.cachesize=10
worker.example.cache_timeout=600
worker.example.socket_keepalive=1
worker.example.recycle_timeout=300

Another example

/etc/apache/mod_jk/workers.properties

A worker is basically a Tomcat listener, it waits for information from Apache and gives it to Tomcat.
This file comes with all the ``inprocess'' workers uncommented, 
the ``inprocess'' standing for ``in the Apache process'' which is not what we want to do.
Here is my workers.properties (note that the file comes with extensive comments):

  workers.tomcat_home=/usr/share/tomcat 
  workers.java_home=/usr/lib/jdk1.1/ 
  ps=/ 
  worker.list=ajp12,ajp13 
  worker.ajp12.port=8007 
  worker.ajp12.host=localhost 
  worker.ajp12.type=ajp12 
  worker.ajp12.lbfactor=1 
  worker.ajp13.port=8009 
  worker.ajp13.host=localhost 
  worker.ajp13.type=ajp13 
  worker.ajp13.lbfactor=1 
  worker.loadbalancer.type=lb 
  worker.loadbalancer.balanced_workers=ajp12,ajp13 
  worker.inprocess.class_path=$(workers.tomcat_home)$(ps)classes 

Correlation between uriworkermap and worker

Example uriworkermap.properties:

/examples/*=worker1
/axis/*=axis

Example workers.properties:

worker.list=worker1,axis

worker.worker1.host=192.168.1.23
worker.worker1.port=8009
worker.worker1.type=ajp13
worker.axis.host=192.168.1.11
worker.axis.port=8009
worker.axis.type=ajp13 

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

The uriworkermap.properties is a simple text file that determines the kind of requests that get passed on to Tomcat rather than being handled by IIS.

I created the uriworkermap.properties file in E:\Xwiki\Tomcat 6.0\conf

/xwiki/*=wikiWorker

This is Laszlo's example setup of the uriworkermap.properties file. I set it to handle everything with the url /lps-4.0.2, specifying * rather than *.lzx because I didn't want to have to add a line for every single file extension in Laszlo's directory.

/lps-4.0.2/*=defWorker
/lps-4.0.2/servlet/*=defWorker

If you wanted just .lzx files handled for instance you could just specify:

/lps-4.0.2/*.lzx=defWorker
/lps-4.0.2/servlet/*=defWorker

• if the user goes to http://hostname:8080/lps-4.0.2/my-apps/sample_app/src/sample.lzx they will only be conversing with Tomcat on port 8080 without involving IIS
• if the user goes to http://hostname/lps-4.0.2/my-apps/sample_app/src/sample.lzx IIS will see the request and pass it on to Tomcat using isapi_redirect.dll talking on port 8009