!Wiki configuration
The least painful approach to defining the location of your Wiki files is to have them located at the same drive as your Tomcat (or other web server) installation, and define the location in Unix format. For example, files in C:\JSPWiki\files are defined in the configuration file as /JSPWiki/files.

Also make sure to change the setting for {{log4j.appender.~FileLog.File}} in {{jspwiki.properties}} if you want a log-file to be created. This setting is hidden quite well near the end of the config-file. The format is the same as the {{jspwiki.fileSystemProvider.pageDir}}-setting, i.e. backslashes must be duplicated.

!Unpacking a .war file
Change the file extension from .war to .zip then unzip the file using a windows utility.   

!Resetting a Password
After running the Install.jsp page, an administrator account will be created with a random password if want to access the admin account or access any other account without the password, you can reset the password.  

Passwords are generally stored only as an encrypted hash so they can't be easily recovered, only reset.  To reset a password, create a new dummy username and password in the usual way, open the .xml file that contains username and password and copy the password hash from the dummy username and paste it over the password for the username you want to reset.

In windows you may have to change the security settings of the .xml file so you have permission to write to it.  

!Version control

If you need RCS-based version control for your JSPWiki installation on a Windows machine, download the implementation from [http://www.cs.purdue.edu/homes/trinkle/RCS/]. You only need the executables in the win32 directory of the rcs57pc1.zip.

The RCS executables will not work unless you set:
* PATH environment variable to point to the location of the executables
* TZ environment variable to a value suitable for your locale (this value must
  be set; I have failed to get it working properly, though).
* You also may need to set the LOGNAME environment variable; see [JSPWikiOnWindows] for more details.

!Version control alternative

You might also want to try out the [VersioningFileProvider], which provides versioning without RCS. It has not been tested as extensively as [RCSFileProvider], but it's quite a lot easier to set up.

Some potential issues:
* JAVA_HOME must point to the sdk, not the jre.
* In the properties file make sure your path names use double back slashes; alternatively you can replace them with single forward slashes
* Make sure there are no trailing spaces at the ends of lines containing a path or class name.
* In the properties file make sure your URL contains the port number. For example, enter something like [http://localhost:8080].
* Create the data directory specified in the properties file. It doesn't seem to be automatically created.
* Resin (http://caucho.com/) is easier to install and much faster than Tomcat.

!How To Link Tomcat 5 with IIS 6 on Windows 2003 Server using the JK2 ajp13 connector

Comprehensive illustrated guide at [http://tjworld.net/help/kb/0001_iis6-Tomcat5-JK2.html#conConnector]

!Further notes!

* [Can't use mapped drive in Windows as page directory|CanNotUseMappedDriveInWindowsAsPageDirectory]
See [InstallAtAformatik] and [WindowsInstallQuestion] for an example and more information.