You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by la...@locus.apache.org on 2000/10/16 04:07:04 UTC
cvs commit: jakarta-tomcat/src/etc jni_server.xml
larryi 00/10/15 19:07:02
Modified: src/etc Tag: tomcat_32 jni_server.xml
Log:
Update to use Tomcat 3.2 server.xml as the template.
Now assumes Tomcat is unzipped to the root of C drive,
i.e. c:\jakarta-tomcat. Also, the jni_connect.dll is assumed to be in the
win32\i386 directory under Tomcat's bin directory. This matches where it is
found relative to the directory where the Tomcat binary distribution is found.
Revision Changes Path
No revision
No revision
1.2.4.1 +234 -43 jakarta-tomcat/src/etc/Attic/jni_server.xml
Index: jni_server.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat/src/etc/Attic/jni_server.xml,v
retrieving revision 1.2
retrieving revision 1.2.4.1
diff -u -r1.2 -r1.2.4.1
--- jni_server.xml 2000/03/29 09:20:36 1.2
+++ jni_server.xml 2000/10/16 02:07:01 1.2.4.1
@@ -2,70 +2,261 @@
<Server>
<!-- Debug low-level events in XmlMapper startup -->
- <xmlmapper:debug level="2" />
+ <xmlmapper:debug level="0" />
- <!-- This is quite flexible; we can either have a log file per
- module in Tomcat (example: ContextManager) or we can have
- one for Servlets and one for Jasper, or we can just have
- one tomcat.log for both Servlet and Jasper.
-
- If you omit "path" there, then stderr should be used.
-
- verbosityLevel values can be:
- FATAL
- ERROR
- WARNING
+ <!--
+
+ Logging:
+
+ Logging in Tomcat is quite flexible; we can either have a log
+ file per module (example: ContextManager) or we can have one
+ for Servlets and one for Jasper, or we can just have one
+ tomcat.log for both Servlet and Jasper. Right now there are
+ three standard log streams, "tc_log", "servlet_log", and
+ "JASPER_LOG".
+
+ Path:
+
+ The file to which to output this log, relative to
+ TOMCAT_HOME. If you omit a "path" value, then stderr or
+ stdout will be used.
+
+ Verbosity:
+
+ Threshold for which types of messages are displayed in the
+ log. Levels are inclusive; that is, "WARNING" level displays
+ any log message marked as warning, error, or fatal. Default
+ level is WARNING.
+
+ verbosityLevel values can be:
+ FATAL
+ ERROR
+ WARNING
INFORMATION
DEBUG
- -->
+
+ Timestamps:
- <Logger name="tc_log"
- path="logs/tomcat.log"
- customOutput="yes" />
+ By default, logs print a timestamp in the form "yyyy-MM-dd
+ hh:mm:ss" in front of each message. To disable timestamps
+ completely, set 'timestamp="no"'. To use the raw
+ msec-since-epoch, which is more efficient, set
+ 'timestampFormat="msec"'. If you want a custom format, you
+ can use 'timestampFormat="hh:mm:ss"' following the syntax of
+ java.text.SimpleDateFormat (see Javadoc API). For a
+ production environment, we recommend turning timestamps off,
+ or setting the format to "msec".
+
+ Custom Output:
+
+ "Custom" means "normal looking". "Non-custom" means
+ "surrounded with funny xml tags". In preparation for
+ possibly disposing of "custom" altogether, now the default is
+ 'custom="yes"' (i.e. no tags)
+
+ Per-component Debugging:
+
+ Some components accept a "debug" attribute. This further
+ enhances log output. If you set the "debug" level for a
+ component, it may output extra debugging information.
+ -->
- <Logger name="servlet_log"
+ <!-- if you don't want messages on screen, add the attribute
+ path="logs/tomcat.log"
+ to the Logger element below
+ -->
+ <Logger name="tc_log"
+ verbosityLevel = "INFORMATION"
+ />
+
+ <Logger name="servlet_log"
path="logs/servlet.log"
- customOutput="yes" />
+ />
- <Logger name="JASPER_LOG"
- path="logs/jasper.log"
+ <Logger name="JASPER_LOG"
+ path="logs/jasper.log"
verbosityLevel = "INFORMATION" />
- <!-- Set the "home" attribute to point to where your in-process tomcat
- configuration is located. ContextManager home is the base directory
- for contexts, webapps/ and work/
- -->
- <ContextManager debug="2" workDir="work" home="D:\tomcat">
- <!-- ContextInterceptor className="org.apache.tomcat.context.LogEvents" / -->
+ <!-- You can add a "home" attribute to represent the "base" for
+ all relative paths. If none is set, the TOMCAT_HOME property
+ will be used, and if not set "." will be used.
+ webapps/, work/ and logs/ will be relative to this ( unless
+ set explicitely to absolute paths ).
+
+ You can also specify a "randomClass" attribute, which determines
+ a subclass of java.util.Random will be used for generating session IDs.
+ By default this is "java.security.SecureRandom".
+ Specifying "java.util.Random" will speed up Tomcat startup,
+ but it will cause sessions to be less secure.
+
+ You can specify the "showDebugInfo" attribute to control whether
+ debugging information is displayed in Tomcat's default responses.
+ This debugging information includes:
+ 1. Stack traces for exceptions
+ 2. Request URI's that cause status codes >= 400
+ The default is "true", so you must specify "false" to prevent
+ the debug information from appearing. Since the debugging
+ information reveals internal details about what Tomcat is serving,
+ set showDebugInfo="false" if you wish increased security.
+ -->
+ <ContextManager debug="0" workDir="work" showDebugInfo="true" home="c:/jakarta-tomcat" >
+
+ <!-- ==================== Interceptors ==================== -->
+
+ <!--
+ ContextInterceptor className="org.apache.tomcat.context.LogEvents"
+ -->
+
<ContextInterceptor className="org.apache.tomcat.context.AutoSetup" />
- <ContextInterceptor className="org.apache.tomcat.context.DefaultCMSetter" />
- <ContextInterceptor className="org.apache.tomcat.context.WorkDirInterceptor" />
- <ContextInterceptor className="org.apache.tomcat.context.WebXmlReader" />
- <ContextInterceptor className="org.apache.tomcat.context.LoadOnStartupInterceptor" />
+
+ <ContextInterceptor
+ className="org.apache.tomcat.context.WebXmlReader" />
+
+ <!-- Uncomment out if you have JDK1.2 and want to use policy
+ <ContextInterceptor
+ className="org.apache.tomcat.context.PolicyInterceptor" />
+ -->
+
+ <ContextInterceptor
+ className="org.apache.tomcat.context.LoaderInterceptor" />
+ <ContextInterceptor
+ className="org.apache.tomcat.context.DefaultCMSetter" />
+ <ContextInterceptor
+ className="org.apache.tomcat.context.WorkDirInterceptor" />
+
<!-- Request processing -->
- <RequestInterceptor className="org.apache.tomcat.request.SimpleMapper" debug="0" />
- <RequestInterceptor className="org.apache.tomcat.request.SessionInterceptor" />
- <RequestInterceptor className="org.apache.tomcat.request.SecurityCheck" />
- <RequestInterceptor className="org.apache.tomcat.request.FixHeaders" />
+ <!-- Session interceptor will extract the session id from cookies and
+ deal with URL rewriting ( by fixing the URL )
+ -->
+ <RequestInterceptor
+ className="org.apache.tomcat.request.SessionInterceptor" />
+
+ <!-- Find the container ( context and prefix/extension map )
+ for a request.
+ -->
+ <RequestInterceptor
+ className="org.apache.tomcat.request.SimpleMapper1"
+ debug="0" />
+
+ <!-- Non-standard invoker, for backward compat. ( /servlet/* )
+ -->
+ <RequestInterceptor
+ className="org.apache.tomcat.request.InvokerInterceptor"
+ debug="0" />
+
+ <!-- "default" handler - static files and dirs
+ -->
+ <RequestInterceptor
+ className="org.apache.tomcat.request.StaticInterceptor"
+ debug="0" />
+
+ <!-- Plug a session manager. You can plug in more advanced session
+ modules.
+ -->
+ <RequestInterceptor
+ className="org.apache.tomcat.session.StandardSessionInterceptor" />
+
+ <!-- Check if the request requires an authenticated role.
+ -->
+ <RequestInterceptor
+ className="org.apache.tomcat.request.AccessInterceptor"
+ debug="0" />
+
+ <!-- Check permissions using the simple xml file. You can
+ plug more advanced authentication modules.
+ -->
+ <RequestInterceptor
+ className="org.apache.tomcat.request.SimpleRealm"
+ debug="0" />
+
+ <!-- UnComment the following and comment out the
+ above to get a JDBC realm.
+ Other options for driverName:
+ driverName="oracle.jdbc.driver.OracleDriver"
+ connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
+ connectionName="scott"
+ connectionPassword="tiger"
+
+ driverName="org.gjt.mm.mysql.Driver"
+ connectionURL="jdbc:mysql://localhost/authority"
+ connectionName="test"
+ connectionPassword="test"
+ "connectionName" and "connectionPassword" are optional.
+ -->
<!--
- JNI connector, make sure that you update the native_lib
+ <RequestInterceptor
+ className="org.apache.tomcat.request.JDBCRealm"
+ debug="99"
+ driverName="sun.jdbc.odbc.JdbcOdbcDriver"
+ connectionURL="jdbc:odbc:TOMCAT"
+ userTable="users"
+ userNameCol="user_name"
+ userCredCol="user_pass"
+ userRoleTable="user_roles"
+ roleNameCol="role_name" />
+ -->
+
+ <!-- Loaded last since JSP's that load-on-startup use request handling -->
+ <ContextInterceptor
+ className="org.apache.tomcat.context.LoadOnStartupInterceptor" />
+
+ <!-- ==================== Connectors ==================== -->
+
+ <!-- JNI connector, make sure that you update the native_lib
Parameter to point to your jni_connect.dll
-->
<Connector className="org.apache.tomcat.service.JNIEndpointConnector">
- <Parameter name="native_lib" value="D:\tomcat\bin\i386\jni_connect.dll"/>
+ <Parameter name="native_lib"
+ value="c:/jakarta-tomcat/bin/win32/i386/jni_connect.dll"/>
</Connector>
- <!-- example - how to override AutoSetup actions -->
- <Context path="/examples" docBase="webapps/examples" debug="0" reloadable="true" >
- </Context>
- <!-- example - how to override AutoSetup actions -->
- <Context path="" docBase="webapps/ROOT" debug="0" reloadable="true" >
+ <!-- ==================== Special webapps ==================== -->
+ <!-- You don't need this if you place your app in webapps/
+ and use defaults.
+ For security you'll also need to edit tomcat.policy
+
+ Defaults are: debug=0, reloadable=true, trusted=false
+ (trusted allows you to access tomcat internal objects
+ with FacadeManager )
+
+ If security manager is enabled, you'll have read perms.
+ in the webapps dir and read/write in the workdir.
+ -->
+
+ <Context path="/examples"
+ docBase="webapps/examples"
+ debug="0"
+ reloadable="true" >
</Context>
- <Context path="/test" docBase="webapps/test" debug="0" reloadable="true" >
+ <!-- Admin context will use tomcat.core to add/remove/get info about
+ the webapplications and tomcat internals.
+ By default it is not trusted - i.e. it is not allowed access to
+ tomcat internals, only informations that are available to all
+ servlets are visible.
+
+ If you change this to true, make sure you set a password.
+ -->
+ <Context path="/admin"
+ docBase="webapps/admin"
+ debug="0"
+ reloadable="true"
+ trusted="false" >
</Context>
+ <!-- Virtual host example -
+ In "127.0.0.1" virtual host we'll reverse "/" and
+ "/examples"
+ (XXX need a better example )
+ (use "http://127.0.0.1/examples" )
+ <Host name="127.0.0.1" >
+ <Context path=""
+ docBase="webapps/examples" />
+ <Context path="/examples"
+ docBase="webapps/ROOT" />
+ </Host>
+ -->
+
</ContextManager>
</Server>
-