Installation on Windows OS

Installation on the Windows platform is rather trivial, and consists of the following stages:

• Download and Install JRE from Oracle.
• Download and Install Tomcat from Apache.
• Download the latest build of PWM Current Build.
• Extract pwm.war from downloaded zip file and explode by copying to Tomcat Webapps folder
• Configure the applicationPath parameter in pwm/WEB-INF/web.xml.
• Start the configuration wizard by going to the default application url.

Installation Procedure:

JRE:

• JRE8u92 worked good for me (should use the latest).
• Download JRE from: Download JRE8 From Oracle
• Choose the right installer for your platform (32/64 Bit), from the latest version.
• Install JRE with default settings

Tomcat:

• 8.0.33 worked good for me (should try latest).
• Download Tomcat8 from: Download Tomcat 8 From Apache
• Should choose: 32-bit/64-bit Windows Service Installer
• Install Tomcat, unselect install the Web Manager application (we dont need it).
• Start the Tomcat service, and set the start action to Automatic.

PWM:

• Download PWM current latest build from: Download PWM Latest current build
• Extract pwm.war and copy to tomcat webapps folder (for 64bit os, default is at: C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps)
• Apache should automatically create the "pwm" directory under webapps, and extract the application inside.
• Now we have to edit the pwm/WEB-INF/web.xml file, to change the applicationPath parameter, see reference in the following link: http://www.pwm-project.org/pwm/public/reference/environment.jsp

I used a relative path which should work if you deployed it by this guide: applicationPath webapps\pwm\WEB-INF

• You can now start the configuration script by going to: http://localhost:8080/pwm/config/ConfigManager

Once a configuration is saved, PWM will operate in "Configuration Mode", which allows continued configuration changes to be made while you test PWM functionality. When all configuration changes are completed, you can Lock the PWM configuration, which will prevent any further direct changes via the web based ConfigManager. If you wish to make further changes to the configuration once the config is Locked, you can follow the instructions on the ConfigManager page. These steps require access to the server file system.

DeeJVince